Client's, once assigned, will never reassign themselves to another site. So, those old clients will continue to try to locate the resources from the old site. You'll need to manually log in and reassign them or you can use client push to reinstall them which will reassign them also. You can't actually use my script though as it only checks to ensure the client is assigned to the correct site but will not reassign them - There's a technical reason why that's not feasible during startup (but I don't remember what it is off-hand).
As for RESETKEYINFORMATION, as long as the client is joined to the domain, it can get the key information from AD with ConfigMgr 2012 so that option doesn't really provide any value anymore (except for clients that can't get to the domain info). J From: [email protected] [mailto:[email protected]] On Behalf Of Ben Glenz Sent: Monday, April 14, 2014 1:22 AM To: [email protected] Subject: RE: [mssms] sccm client installation issues I think you could also use the Client Startup Script from Jason to fix this http://blog.configmgrftw.com/configmgr-client-startup-script/ From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of s kissel Sent: Montag, 14. April 2014 04:14 To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] sccm client installation issues Have you tried putting in RESETKEYINFORMATION=TRUE in your install routine? http://technet.microsoft.com/en-us/library/gg699356.aspx ________________________________ From: [email protected]<mailto:[email protected]> To: [email protected]<mailto:[email protected]> Subject: [mssms] sccm client installation issues Date: Sat, 12 Apr 2014 14:40:23 -0500 I'm sort stuck between a rock and tree...I've recently (1 month ago) upgraded to R2 (sccm2012) new hardware / vm. The DB is on a SQL cluster and the application resides on a VM (win2012). So everything is good, clients reporting in, the old 2012 RTM has been decommed. I now have one single primary and ip address range's, our AD Sites / Services boundaries are set with /8 and I had issues. So I went with ranges rather than allowing the boundaries to be created and added into the single group. I currently have over 11k objects discovered via (network / heartbeat / ad system); of those 11K I have 3700 (windows -client / server) and 900 (macintosh) and 3800 (mobile / tablet). Pretty good numbers. So one item I'm noticing on a few systems that are outside the US primarily in EMEA / HKG / Syd, is that they have the old RTM site code. I've done some spot checking within the schema, the old site code is not published, DNS is good, the new R2 server has rights to publish and the new site code is presented. Now on some of the client the ccmsetup log shows the following: The MP set to the new server and the return code of 0, which is an indication of success installation. However, within the locationservices.log I'm seeing a "failed to retireve DNS service record using _mssms_mp_(old sitecode).tcp_child domain, DNS returned error 9003" Not sure what is generating that since the system -> systemmanagement has no record of the old site code at the forest / domain / child domain level. Has anyone seen this before, I've done everything by even doing a manual (psexec remote execution of ccmsetup /uninstall) rebooted the resource and then executed a auto install as well as manual and still fails. Thanks Thomas
