jkirshy

SetupClient.exe /q /targetdir "c:\program files\Microsoft CRM" INSTALLLEVEL=2 /l c:\crm_client_setup_log.txtlook at this web site, its great...http://www.itninja.com/software/microsoft/dynamics-crm-2011-client/5-2606 deploy as a .exe

Stop using UEFI boot, or update your boot image to include the updated stuff for uefi.

Pxe booting depends a lot on the nic card in that pc. Update the bios of the pc's in question. If these are older computers put in a new nic or go to bios and make sure all options for nic card are correct, pxe ability, turned on etc. One last thing have your network guys make sure portfast is set on all of you switches. Your pic above shows clearly the pc is not contacting the wds service on the sccm server, due to too much activity or simply times out. Make sure in your registry of the sccm server find wds settings and double the packet size, you can Google that and find the exact key to adjust. Finally check your network card on your pc, is it optimized, have correct dns, ping and do you get good reaction times, does dns work by name and by ip, can you do nslookup by both also. Do you have dns set up correctly on all of your dns servers, you need an entry for you sccm server.

If you rename the pc, the mac is the same so eventually it will change in sccm to the new name. I've done it both ways. I just get tired of looking at all the dell minint-bla bla bla computer names until it goes away in sccm.

You have 2 issues. I would load a new sccm on new domain, you can import software packages etc. The process of capture profiles on such a big scale , im have not seen anything like that. Im sure if you asked this question on a domain admins site there is an answer.

Simple as above hit f8 if you have enabled tools in pxe and do an ipconfig. IF you get an address your network card on your boot image is good, and the problem is software task related. More than likely you will have no ip address.. Go to dell get the latest nic driver from dell, import it into your boot image. warning sometimes dell renames drivers, go to manufacture site and get driver for network card. once you load that missing driver, redeploy. then pxe boot success. I had the same problem and banged my head against the wall, even dell was telling me I had the right nic driver for dell 5610, however I googled that driver and found the one from the manufacture and it worked. I celebrated for days! Advice to anyone, on any new dell, download there cab files, import them into sccm, then user a windows 7 image or 8 and create a Software task sequence to combine the two. Capturing and deploying is a pain.

You really ask a difficult question to answer. First have you checked the logs on the client pc to find out why they failed, did you put a pre-requisite in your software deployment. Do you have any widows firewall issues by group policy or local, does your sccm acct have proper access. Sccm troubleshooting is log based. Use the log viewer that comes with Sccm. Are your pc's in the same v-lan or separated by hardware firewall rules. Certain ports have to be open , file and print sharing etc on the domain controller by GP. Check the account your running the software distribution as, or change it to troubleshoot. Check your logs on the server. Have you installed right click tools to help you troubleshot remotely. Connect to the client pcs, just because you get a software failed notice , does not necessarily mean the software actually did not get installed. As far as grouping can you group by logical name, location, ip range, Or group using a variable query statmemnt for example, here is one, im sure I got it here. I love this website. select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%Adobe of course change adobe for your software or lack of. This is just a starting point, look at your deployment see if your group you are deploying too actually shows each member, are they physically turned on.. Initiate a application cycle or machine policy on the whole group. so all pcs will get the latest advertisement. LOGS< LOGS LOGS> good luck.

Looks like your laptop drive is encrypted with bit locker. Your process might be slowed down by that. Make sure you format your drive with a 350 mb partition than the rest is for your c drive. For faster pxe speed, update your bios, change the packet size in your server registry for your WDS. ( google search for this one) It works great. You need to add a task sequence ( set task sequence Variable ) variable OSDPreserveDriveLetter False, to use the C drive. Make sure your connection to your windows iso or media is on your sccm server in your setup. In config mgr, turn on Pxe with tools. This way you can hit f8 at any time open up Log viewer and open up log file to see what is happening real time.

Pxe boot on Dell or any other manufacture. After all issues above are fixed. The next step is to find the manufacture of the network card, then use there drivers to inject into boot image. For dell there driver packages are renamed. For example the Intel 1217-LM driver is really the Intel Pro 1000 and uses a different inf file. This is very important. Also, don't put the Dell cab files in the task sequence, you will get some random storage errors upon task sequence completion.

Problem solved, turns out if you install windows 8.1 ADK, it will prevent you from restoring the boot images, no matter how you create them. My mistake was trying to uefi boot and reading some other blog that said install windows ADK 8.1 and you can then uefi boot. He should have said, update Sccm sp1 to R2 version and then you can work with uefi bios type of computers. http://deploymywindows.blogspot.com/2013/07/sccm-2012-sp1-specified-unc-path-does.html?showComment=1392048241859#c1118562768097924795 this is the article that helped me. Don't use adk 8..1 if your only on the sp1 version of Sccm 2012. Thanks all for helping.

Help, Im having the same issue, The boot images are gone I've followed all the above workarounds to recreate them. Question... I use the boot wizard in Sccm to add a boot image, I use the wim image that was created by the deployment and imaging tools, I browse to the wim image (boot.wim) but the second drop down box does not populate. Its like im not using the correct sources folder to pull the original boot file? Is the boot.wim originally come off of the windows 7 cd, or from the Sccm cd? If so is it from the sources folder. I think I use the boot.wim? I tried to recreated the DP point but it does not recreate the boot images? Probably because it sees the file structure already in place so the boot images don't get recreated. This all started because we have a bunch of new dells coming in that uefi boot and we cant get them to pxe boot, because of lack of network drivers. What a nightmare. Legacy or UEFI boot wont start up. Dell 9020. The next option is to go to r2 but im not sure if that will re-create the boot images. There has to be an easy answer??

I need some advice? How do most of you reconcile the device lists? I have 2393 in my all devices list, but only 1637.00 in all desktop and server clients. Ive massaged all the discover settings but want to make sure I have the optimum settings to pick up all devices that are under 60 days old. I put a new device on the network and the sccm client and mandatory software installs in under 15 minutes. I have some devices that are excluded from discovery, so they should not be in that list. I set the discover limit to only capture stuff from AD that has logged in to ad within the last 60 days. I Im preety sure my numbers are correct but my boss thinks im about 200 devices off. The list of devices changes constantly obviousoly. How can I reconcile the difference in number of devices in the default list of " All Systems" and "All Desktop and Service Clients" ? How do you make sure you are getting all the devices on your network.?

This topic should be closed. This issue was fixed by uninstalling Application web service point and website point. I blew away any remnants of IIS and reinstalled and then in sccm added the two roles and all is well.

What about the firewall policy on the client? By default we turn off the domain firewall on all pc's, probably not it but make sure its off, and the service off. Verify no other firewalls are running. Next I would check the permission on your site code folder on the server itself. Next, make sure your AD system container in system management entry for your sms_MP-site code, has the right permissions. Your sccm server should have full permission I have mine as sccm2012$. Watch ccm client log on your clients for errors, this is your key. Download client action tools. this standalone tool will give you all kinds of things to check on a client, wmi, firewall, policy's, repair, sccm client, client health tools. Oh and download latest right click tools they really give you a lot of tools to connect to the client! This is what is supposed to happen, To start the process, initiate machine policy retrieval and evaluation. This is the next process not sure where I got it from but most likely this web site. Once the agent is available on the network and the client is installed, the client goes through the following actions as part of the reporting process: 1.Client location services identify the site code and the MP it is supposed to connect to. 2.The client connects to the Management Point and downloads the policies. 3.Once the policies are downloaded it sends the heartbeat record to the server. 4.Once the server receives this heartbeat record these are converted in to DDR and processed. This will set the client flag to 1 which will make the client status display as Yes in the console. 5.On a regular basis the agent will send the heartbeat and if no heart beat or inventory shows up for a length of time then the client flag will be marked as 0 by the client flag maintenance task, setting the client status to No. So only if this process is completed and it continues to happen will the client remain reporting to the server. This is why I said earlier that client management is a continuous task. If this does not work, delete all ccm files on client c drive and re-install and watch log on client machine using cmtrace.exe a log trace tool.

System Center 2012 Configuration Manager , mastering the fundamentals. Kent agerluns on amazon. Make sure you get one that covers sp1!!

I have images galore, if you need any . just let me know.

I have a Sccm 2012R1 server running fine. Wsus and windows pxe updates are a issue for me. Our Wsus server is another server managed by another person. Because of company policies I cant change how updates are sent out. We do a staged update across the Wan, 13 different companies and test update groups, then production ou's. My question can sccm deploy software updates to and OS image without Software Update Point installed? I have multiple os packages that I deploy through pxe, however I cannot use sccm to update the images because there is no communication to Wsus. I have tried installing sup on my sccm but no updates are seen by sccm. The two machines don't talk. Our wsus server is a separate machine that through gp updates go to each machine when deployed and of course all clients are pointed to wsus server as source to get updates. I cant use Sccm to deploy windows updates. What I cant find is how sccm talks to wsus and gets it updates with or without a SUP point? Can I just get updates myself using Sccm console only? How can I enable os updates for pxe packages with a different wsus site. Do I even need a Software update point? If not how do I set up communication between sccm and wsus to get auto approved updates from my wsus server? I've done a lot of research and installed the wsus admin console on sccm, to talk to wsus server with a sup on my sccm server and it did not work either. Any ideas, I know its a complicated issues but any help would be appreciated, this site has been the best for me in my learning experience with Sccm 2012 R1

I installed Sccm 2012 with r1 when it first came out and it was a major pain in the neck. I have a good running R1 version finally after 3 months and a nice 5 day class. I would advise anyone to wait 6 months before using R2. 15 hour days get rough. It might be easier to uninstall Sccm, delete the db from your sql machine. Go to active directory and remove all references to your site code in systems mgmt container. Re-install all using the same site code, you can do that because I've done it. The same site code will make all your client find the new Sccm server. Remember after you advertise your new sccm server in ad, it will take about a day to have all pc's show up. Use a query in reports to monitor any new pcs found in the last 48 hours so you can keep an count on sccm finding new computers daily. ( I have a query if you need it) A lot of people would say suck it up and fix it. I guarantee you are at a point that you will be chasing your tail for 3 month or so as new issues come out. Your pxe issues are strange, your client upgrades are an issue with the r2 release. I have r1 running perfect with over 2500 users and 3500 computers over 14 companies and multiple states including Canada. Remember SCCM 2012 is very far reaching software and you can do so much with it and you should not be having all these issues. Important on your ad, delete the entry in system Management. Let Sccm republish it. Go to your dns and delete all entries pointing to Sccm. I would format drive on your server and do a complete os reload and then sccm. The only unknow issue is will the new client software R2 talk to a non r2 version, My answer would be yes it will talk to your new R1 sccm server.

I did the same thing, but then I had to re-distribute and re-deploy to the my distribution group.

I don't know why I go anywhere else to find sccm info. I always return to this great site. Thanks and Great Job!

Microsoft's SCCM has a new feature called "wake up proxy" whereby host a pretends to be host b (host a spoof's the mac address of host when host b goes to sleep. Needless to say, we were seeing tons of mac address flapping and port-security issues. On the client settings that you deploy to your devices, If you have power management selected and have wake up proxy as yes or enabled, it wll cause network card " flapping" or rebroadcast of your mac address accross the wan. This will trigger port security and bring down your network. Refer to the Cisco Tac Below. Only in sp1 sccm 2012. Dont enable this feature, your network and security team will hate you once they found out SCCM 2012 sp1 caused this! What a nightmare. This is apparently a pretty new issue. over 2k users experiecned rolling blackouts of there ports becuase we have port security turned on our switches. Suck it Microsoft! https://supportforums.cisco.com/thread/2220560

Simple Fix , since you have reinstalled Sccm 2012, your sccm windows folders dont have the correct permissions. You can either delete them and reload sccm, or look at the permission on all your sccm folders and add the appropriate permissions. Start by adding authenticed users to the folders in question. This will effect the normally shared folders , that are shared out including the sms_site code shared folder and the inbox for clients to get the ddr record from the sever so the client can be managed. I had this exact issue.

Ok, this is a secret. Windows 7- xp clients, use right click tools thru config mgr, connect to the C$ share on each pc. Delete the ccmsetup directory on the clients windows directory. Then push or deploy the client and it will work.!!Ccmsetup, runs as a service thru sccm console! but not thruough right click tools. The best way to deploy clients, have it on each new pc, push the client thru confg mgr, Have a gp to force install clients. Beware of firewall issues on clients , set up a gp to force domain firewall policy to be disabled. If its a remote client in another physical office that goes thru a cisco firewall , have your security team open up sql ports, windios file and sharing ports and WMI! GET RIGHT CLICK TOOLS!!! DELETE OLD CCMSETUP DIR IN WINDOWS! Create Device collections to manage your computers easily.

This is my client log when trying to get the client installed on windows 7. Looks good except for the last line. Looks like an iis issue. Anyone have exact web dav and bits settings that are supposed to be set. Or should I just delete all web sites, and iis and try to reinstall. Out of 2k clients only about 20 are picking up new sccm 2012 client. This issue is going to kill me! ==========[ ccmsetup started in process 5056 ]========== ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) CcmSetup version: 5.0.7711.0000 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Ccmsetup command line: ccmsetup.exe /mp:sccm2012 /logon smssitecode=842 /forceinstall ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Command line parameters for ccmsetup have been specified. No registry lookup for command line parameters is required. ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Command line: ccmsetup.exe /mp:sccm2012 /logon smssitecode=842 /forceinstall ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) SslState value: 224 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) CCMHTTPPORT: 80 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) CCMHTTPSPORT: 443 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) CCMHTTPSSTATE: 224 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) CCMHTTPSCERTNAME: ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) FSP: ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) CCMFIRSTCERT: 1 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Config file: ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Retry time: 10 minute(s) ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) MSI log file: C:\Windows\ccmsetup\client.msi.log ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) MSI properties: SMSSITECODE="842" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1" ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Source List: ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) MPs: ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) sccm2012 ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) No version of the client is currently detected. ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Updated security on object C:\Windows\ccmsetup\. ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent. ccmsetup 4/24/2013 10:49:30 AM 8764 (0x223C) Downloading file C:\ccmsetup.exe ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Downloading C:\ccmsetup.exe to C:\Windows\ccmsetup\ccmsetup.exe ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) File download 24% complete (262144 of 1052528 bytes). ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) File download 49% complete (524288 of 1052528 bytes). ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) File download 74% complete (786432 of 1052528 bytes). ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) File download 99% complete (1048576 of 1052528 bytes). ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) File download 100% complete (1052528 of 1052528 bytes). ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Download complete. ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Running as user "jkirshy" ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Detected 78773 MB free disk space on system drive. ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Only one MP sccm2012 is specified. Use it. ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Searching for DP locations from MP(s)... ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Current AD site of machine is TIC LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) Local Machine is joined to an AD domain LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) Current AD forest name is ntsupport.tic.toshiba.com, domain name is ntsupport.tic.toshiba.com LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) DhcpGetOriginalSubnetMask entry point is supported. LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) Begin checking Alternate Network Configuration LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) Finished checking Alternate Network Configuration LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) Adapter {79F03CF8-90B5-41CD-BFD2-BA0103E1EFC6} is DHCP enabled. Checking quarantine status. LocationServices 4/24/2013 10:49:31 AM 8764 (0x223C) Sending message body '<ContentLocationRequest SchemaVersion="1.00"> <ClientPackage/> <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0"> <ADSite Name="TIC"/> <Forest Name="ntsupport.tic.toshiba.com"/> <Domain Name="ntsupport.tic.toshiba.com"/> <IPAddresses> <IPAddress SubnetAddress="10.3.16.0" Address="10.3.16.27"/> </IPAddresses> </ClientLocationInfo> </ContentLocationRequest> ' ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Sending message header '<Msg SchemaVersion="1.1"><ID>{EAD1D8F6-F7EB-47B1-A95A-6C32437A7E8B}</ID><SourceHost>IS-JKIRSHY-790</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:IS-JKIRSHY-790:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>sccm2012</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2013-04-24T15:49:31Z</SentTime><Body Type="ByteRange" Offset="0" Length="1062"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) CCM_POST 'HTTP://sccm2012/ccm_system/request' ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Failed to receive ccm message response. Status code = 500 ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) GetDPLocations failed with error 0x80004005 ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C) Failed to get DP locations as the expected version from MP 'sccm2012'. Error 0x80004005 ccmsetup 4/24/2013 10:49:31 AM 8764 (0x223C)