I had to split the build and capture due to manual actions required and to do some validation before doing the capture. For the capture I created a separate task sequence that just has the capture actions it. This is optionally advertised and run on the master.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Trevor Sullivan Sent: Tuesday, January 14, 2014 3:12 PM To: mssms@lists.myitforum.com Subject: RE: [mssms] SCCM OSD not joining correct sitecode Eric, >From your first message, it sounds like you are using capture media? Are you >manually building the reference image? I'd recommend using a fully automated >Build & Capture task sequence. Cheers, Trevor Sullivan From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Giroux, Eric J Sent: Tuesday, January 14, 2014 1:01 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM OSD not joining correct sitecode I was able to get it to assign to the correct site by cleaning out the following registry entries during the build, as soon as the image comes down: HKLM\SOFTWARE\Microsoft\SMS\Mobile Client\AssignedSiteCode HKLM\ SOFTWARE \Microsoft\CCMSetup\LastValidMP HKLM\ SOFTWARE \Microsoft\CCM\SMSSLP HKLM\ SOFTWARE \Microsoft\CCM\CcmEval\LastSiteCode All these were still referencing the lab site where the image was created. The site code is assigning properly now, but I still seem to have a lingering issue with some stuck policy. I can't get NightWatchman to shutdown the machines deployed with the new image because it thinks there is a ConfigMgr job in progress. I can see remnants in execmgr.log referencing the package ID of the boot image used for the capture of the image: Could not find the policy in WMI for package xxxxxxx program * I can't seem to get it to forget about a couple of the packages from the old site where the image was created. Is there a way to force it to forget about old policy from the previous site? Thanks, Eric From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Johan van Dijk Sent: Monday, January 13, 2014 3:55 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM OSD not joining correct sitecode Forgot to mention that I got triggered for this while reading in the client patch installation logfile where it said "assigning sitecode from registry entry".... From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Johan van Dijk Sent: Monday, January 13, 2014 9:51 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: RE: [mssms] SCCM OSD not joining correct sitecode Had somewhat the same thing happening in my environment...although I uninstalled the client agent from the image it would fallback to the old sitecode, however not during the initial client installation but while it was being patched to one of the CU's.... It appeared to be the AssignedSiteCode registry entry in "HKLM\SMS\Mobile Client"...after removing the complete HKLM\SMS hive the issue went away... I guess it's a "feature" or so.... :) From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> [mailto:listsad...@lists.myitforum.com] On Behalf Of Giroux, Eric J Sent: Monday, January 13, 2014 5:29 PM To: mssms@lists.myitforum.com<mailto:mssms@lists.myitforum.com> Subject: [mssms] SCCM OSD not joining correct sitecode I'm having an issue with site code assignment during SCCM 2012 SP1 R3 OSD. Initially when implementing 2012 I was using my old images captured in SCCM 2007 and all was running fine. I have just recently implemented image updates where the images were created with SCCM 2012 for the first time, so the 2012 client was included in the WIM files. The problem I'm running into is that the images are created in a separate lab site/SCCM hierarchy. When I deploy the images in my production 2012 site/hierarchy, the machines are automatically joining the site code for the lab site where the images were created. I'm not doing any AD site boundaries so I don't believe AD is coming into play at all with automatic site code assignment. My ccmsetup logs from during the OSD process show the correct production site code and show the production site server being used for the SMSMP and SMSSLP variables. The first entries in the LocaionServices.log indicate the client being assigned to the lab site, not the production site. These images were captured using standard OSD capture media. Has anyone run into this where deploying images in a site different than where the images were created results in the client joining the old site? Thanks, Eric Giroux Senior Infrastructure Engineer Unum End User Computing E-mail: egir...@unum.com<mailto:egir...@unum.com> | Office: (207) 575-2482 Mobile: (207) 239-5190 | Fax: (207) 575-2158
