I don’t have any GPO that’s doing anything like that. However, I looked at one of the DCs in the test domain, and it has a key set close to what you list. It’s under Mobile Client\AssignedSiteCode.
From: [email protected] [mailto:[email protected]] On Behalf Of Jason Lang Sent: Friday, March 06, 2015 1:03 PM To: [email protected] Subject: RE: [mssms] RE: SCCM in the lab Do you, or did you ever, have the ADM GPO’s set to push the old site code to the agents? That information Tattoo’s. Even if the GPO’s are removed, the registry information stays put and overrides all other methods of specifying sitecodes. This bit us when we tried migrating from 2007 to 2012. No matter what we did, the agent always tried to register to the old Site Code. I would check the associated registry keys, and either use the gpo to set a new one, or use a startup script or WinRM to wipe them entirely. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Mobile Client\GPRequestedSiteAssignmentCode More information here: http://myitforum.com/myitforumwp/2012/10/05/configmgr-client-gpo-assignment-removal/ Jason Lang From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Friday, March 6, 2015 3:41 PM To: '[email protected]' Subject: RE: [mssms] RE: SCCM in the lab Yes, it does. Right from the start it thinks it should be connecting to the old Site code of TST. The new site code is WLD. Assigning to site 'TST' LocationServices 3/3/2015 1:26:40 PM 804 (0x0324) LSIsSiteCompatible : Verifying Site Compatibility for <TST> LocationServices 3/3/2015 1:26:40 PM 804 (0x0324) Attempting to retrieve lookup MP(s) from AD LocationServices 3/3/2015 1:26:40 PM 804 (0x0324) The MP name retrieved is 'WildSCCM1.WILD.dfg.ca.gov' with version '7958' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) MP 'WildSCCM1.WILD.dfg.ca.gov' is compatible LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Lookup Management Points from AD: LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Name: 'WildSCCM1.WILD.dfg.ca.gov' HTTPS: 'N' ForestTrust: 'N' LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Retrieved lookup MP(s) from AD LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7958.1000' for site 'TST' LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSIsSiteVersionCompatible : Site Version '5.00.7958.1000' is compatible. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSIsSiteCompatible : Site <TST> Version '5.00.7958.1000' is compatible. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSVerifySiteAssignment : Client can be assigned to site <TST>. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Attempting to retrieve lookup MP(s) from AD LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Lookup Management Points from AD: LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Name: 'WildSCCM1.WILD.dfg.ca.gov' HTTPS: 'N' ForestTrust: 'N' LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Retrieved lookup MP(s) from AD LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Site and assignment site code match. Verifying site. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSIsSiteCompatible : Verifying Site Compatibility for <TST> LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Attempting to retrieve lookup MP(s) from AD LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Lookup Management Points from AD: LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Name: 'WildSCCM1.WILD.dfg.ca.gov' HTTPS: 'N' ForestTrust: 'N' LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Retrieved lookup MP(s) from AD LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7958.1000' for site 'TST' LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSIsSiteVersionCompatible : Site Version '5.00.7958.1000' is compatible. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSIsSiteCompatible : Site <TST> Version '5.00.7958.1000' is compatible. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) LSVerifySiteAssignment : Client can be assigned to site <TST>. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) Client is not assigned to a site. Cannot get portal info. LocationServices 3/3/2015 1:26:41 PM 804 (0x0324) From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Gerry Borger Sent: Friday, March 06, 2015 12:07 PM To: [email protected]<mailto:[email protected]> Subject: RE: [mssms] RE: SCCM in the lab On the client that is assigned to the old site code, does the LocationServices.log have any relevant info? Regards, Gerry Borger Sr Solutions Architect, Adaptiva From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Friday, March 6, 2015 11:28 AM To: '[email protected]' Subject: RE: [mssms] RE: SCCM in the lab Well, the schema was extended before, and the install did populate the System Management OU with the new info, not the old. The old info was gone before I started the new install. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dwayne Allen Sent: Friday, March 06, 2015 11:19 AM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] RE: SCCM in the lab Did you have AD pulishing turned on for the old site? ----- Dwayne Allen [email protected]<mailto:[email protected]> (479) 310-0027 On Fri, Mar 6, 2015 at 1:14 PM, Heaton, Joseph@Wildlife <[email protected]<mailto:[email protected]>> wrote: Ok, so strange thing happened. I actually went through the uninstall, instead of just ripping SCCM out. This also cleaned up the System Management container, as well. I did choose a different site code when installing the new SCCM, which is on a new server VM. The old VM was unjoined from the domain, and deleted from disk. I’m looking at the devices that the new SCCM has discovered, and I notice that none of them have the client (I didn’t set up client push, so this is fine). I go to push the client to the new SCCM server, then go look in Control Panel. I see that Configuration Manager is shown, so I open it up, and lo and behold, is shows that it is assigned to the OLD SCCM server and site code, which I thought I had gotten rid of. Anyone know what the heck happened, or where I can look to start investigating? Thanks, Joe From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Daniel Ratliff Sent: Tuesday, March 03, 2015 1:17 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SCCM in the lab Exactly, also don’t use the same site code. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Marcum, John Sent: Tuesday, March 03, 2015 4:12 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: SCCM in the lab I assume it's on a VM? Just delete the VM, clean out the System Management container and build a new VM with the version you want. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Tuesday, March 03, 2015 3:10 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] SCCM in the lab I have a lab environment, in which I had originally setup SCCM 2012 R2, on a Server 2012 box. Well, now I need to plan out and test the upgrade of our production environment, which is SCCM 2012 SP1. I want to remove SCCM from my lab environment, so that I can do a clean install of the older version. I’m getting ready to exercise my google-fu, but thought I’d ask here as well, in case someone has already done this, and has a reference that I could look at. Thanks, Joe Heaton Enterprise Server Support Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: (916) 323-1284<tel:%28916%29%20323-1284> ________________________________ Confidentiality Notice: This e-mail is from a law firm and may be protected by the attorney-client or work product privileges. If you have received this message in error, please notify the sender by replying to this e-mail and then delete it from your computer. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
