Firstcom
asked on
Installed a replacement SCCM environment to replace our old SCCM environment and client deployments grab old SiteCode
Our current environment is with Config Manager 2012R2. We have a CAS and two primaries. Those three servers are in readonly mode due to Microsoft trying to fix an issue we had with replication. Microsoft cannot fix the issue or get them back out of readonly mode. I have spun up another SCCM server and have installed Current Branch onto it. I am going to just a Primary site, as we do not need a CAS or the 2nd primary. I had set up the boundaries on Branch based on the previous CM environment. I then, after taking the lab, went through discovery and told it to create boundaries for anything that it finds. After going through the discovery, it created two new boundaries.
When trying to push the client from SCCM Current Branch, it installs the client, but installs it with the old SCCM 2012R2 Site Code. I then turned off the old servers (CAS & 2 primaries) and then decided to try to install it manually. If I copy the client installer from the Branch server and install it manually, I get the warning that This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries. It then proceeds to grab the old Site Code once again, but cannot install (I believe due to the servers being turned off temporarily).
How is the best way to proceed on this? I have pasted the log from the manual install. I can see in the log where it sees the old and new SiteCodes as coming back in the initial query. There is a warning that the install threw before proceeding to pick the original SiteCode HQ1, instead of the new SiteCode CM1.
If you need any further information to make your recommendation, please ask and I will give you what I can. We still have a lot of settings on the old system (even though it may be in read only) that I am trying to view to rebuild onto the new server. If I can get the clients to start pushing to the test group, I can then proceed with creating the other aspects of SCCM (applications, task sequences, packages, other collections, client settings, etc.)
4/13/2017 9:56:26 AM ==========[ ccmsetup started in process 9192 ]========== ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Launch from folder C:\Network\SCCM Client Current Branch\Client\ ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM CcmSetup version: 5.0.8458.1526 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Folder 'Microsoft\Microsoft\Confi
4/13/2017 9:56:26 AM Folder 'Microsoft\Microsoft\Confi
4/13/2017 9:56:26 AM [DEV01885] Running on 'Microsoft Windows 10 Pro' (10.0.14393). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Ccmsetup command line: "C:\Network\SCCM Client Current Branch\Client\ccmsetup.exe
4/13/2017 9:56:26 AM Local Machine is joined to an AD domain ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Current AD forest name is firstcom.local, domain name is firstcom.local ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Domain joined client is in Intranet ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Begin checking Alternate Network Configuration ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Finished checking Alternate Network Configuration ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Current AD site of machine is Chesterfield-MO ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Attempting to query AD for assigned site code ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=MSSMSRo
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=mSSMSSi
4/13/2017 9:56:27 AM LSIsSiteCompatible : Verifying Site Compatibility for <HQ1> ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Current AD forest name is firstcom.local, domain name is firstcom.local ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Domain joined client is in Intranet ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'HQ1' ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=mSSMSMa
4/13/2017 9:56:27 AM LSGetSiteVersionFromAD : Successfully retrieved version '5.00.8239.1403' for site 'HQ1' ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSIsSiteCompatible : Site Version = '5.00.8239.1403' Site Capabilities = <Capabilities SchemaVersion="1.0"><Prope
4/13/2017 9:56:27 AM LSIsSiteVersionCompatible : Site Version '5.00.8239.1403' is compatible. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSIsSiteCompatible : Site <HQ1> Version '5.00.8239.1403' is compatible. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM The client will be assigned to the first valid site ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSGetAssignedSiteFromAD : Trying to Assign to the Site <HQ1> ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Got site code 'HQ1' from AD. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=mSSMSMa
4/13/2017 9:56:27 AM OperationalXml '<ClientOperationalSetting
4/13/2017 9:56:27 AM Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM The MP name retrieved is 'configmanager.firstcom.lo
4/13/2017 9:56:27 AM MP 'configmanager.firstcom.lo
4/13/2017 9:56:27 AM Retrieved 1 MP records from AD for site 'HQ1' ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM FromAD: FSP = configmanager.firstcom.loc
4/13/2017 9:56:27 AM FromAD: command line = SMSSITECODE=HQ1 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Current AD forest name is firstcom.local, domain name is firstcom.local ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Domain joined client is in Intranet ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CMPInfoFromADCache requests are throttled for 01:00:00 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Found MP http://configmanager.firstcom.local from AD ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM SslState value: 224 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Detected sitecode 'HQ1' from AD. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPPORT: 80 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPSPORT: 443 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPSSTATE: 224 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPSCERTNAME: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM FSP: configmanager.firstcom.loc
4/13/2017 9:56:27 AM CCMFIRSTCERT: 1 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Config file: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Retry time: 10 minute(s) ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM MSI log file: C:\WINDOWS\ccmsetup\Logs\c
4/13/2017 9:56:27 AM MSI properties: CCMFIRSTCERT="1" CCMHTTPPORT="80" CCMHTTPSCERTNAME="" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" FSP="configmanager.firstco
4/13/2017 9:56:27 AM Source List: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM MPs: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM http://configmanager.firstcom.local ccmsetup 7764 (0x1E54)
--------------------------
I then tried to do a manual install with the parameter SMSSITECODE=CM1 in the command line at the command prompt, it installs. After it is done installing, I open up Configuration Manager from the control panel and the Site Code textbox is empty. The only value that it will take is HQ1 (the old primary). I am attaching that log file.
ccmsetup---Manual-install-with-CM1-S.log
When trying to push the client from SCCM Current Branch, it installs the client, but installs it with the old SCCM 2012R2 Site Code. I then turned off the old servers (CAS & 2 primaries) and then decided to try to install it manually. If I copy the client installer from the Branch server and install it manually, I get the warning that This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries. It then proceeds to grab the old Site Code once again, but cannot install (I believe due to the servers being turned off temporarily).
How is the best way to proceed on this? I have pasted the log from the manual install. I can see in the log where it sees the old and new SiteCodes as coming back in the initial query. There is a warning that the install threw before proceeding to pick the original SiteCode HQ1, instead of the new SiteCode CM1.
If you need any further information to make your recommendation, please ask and I will give you what I can. We still have a lot of settings on the old system (even though it may be in read only) that I am trying to view to rebuild onto the new server. If I can get the clients to start pushing to the test group, I can then proceed with creating the other aspects of SCCM (applications, task sequences, packages, other collections, client settings, etc.)
4/13/2017 9:56:26 AM ==========[ ccmsetup started in process 9192 ]========== ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Launch from folder C:\Network\SCCM Client Current Branch\Client\ ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM CcmSetup version: 5.0.8458.1526 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Folder 'Microsoft\Microsoft\Confi
4/13/2017 9:56:26 AM Folder 'Microsoft\Microsoft\Confi
4/13/2017 9:56:26 AM [DEV01885] Running on 'Microsoft Windows 10 Pro' (10.0.14393). Service Pack (0.0). SuiteMask = 272. Product Type = 18 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Ccmsetup command line: "C:\Network\SCCM Client Current Branch\Client\ccmsetup.exe
4/13/2017 9:56:26 AM Local Machine is joined to an AD domain ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Current AD forest name is firstcom.local, domain name is firstcom.local ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Domain joined client is in Intranet ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Begin checking Alternate Network Configuration ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Finished checking Alternate Network Configuration ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Current AD site of machine is Chesterfield-MO ccmsetup 7764 (0x1E54)
4/13/2017 9:56:26 AM Attempting to query AD for assigned site code ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=MSSMSRo
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=mSSMSSi
4/13/2017 9:56:27 AM LSIsSiteCompatible : Verifying Site Compatibility for <HQ1> ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Current AD forest name is firstcom.local, domain name is firstcom.local ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Domain joined client is in Intranet ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'HQ1' ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=mSSMSMa
4/13/2017 9:56:27 AM LSGetSiteVersionFromAD : Successfully retrieved version '5.00.8239.1403' for site 'HQ1' ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSIsSiteCompatible : Site Version = '5.00.8239.1403' Site Capabilities = <Capabilities SchemaVersion="1.0"><Prope
4/13/2017 9:56:27 AM LSIsSiteVersionCompatible : Site Version '5.00.8239.1403' is compatible. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSIsSiteCompatible : Site <HQ1> Version '5.00.8239.1403' is compatible. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM The client will be assigned to the first valid site ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM LSGetAssignedSiteFromAD : Trying to Assign to the Site <HQ1> ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Got site code 'HQ1' from AD. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Performing AD query: '(&(ObjectCategory=mSSMSMa
4/13/2017 9:56:27 AM OperationalXml '<ClientOperationalSetting
4/13/2017 9:56:27 AM Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM The MP name retrieved is 'configmanager.firstcom.lo
4/13/2017 9:56:27 AM MP 'configmanager.firstcom.lo
4/13/2017 9:56:27 AM Retrieved 1 MP records from AD for site 'HQ1' ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM FromAD: FSP = configmanager.firstcom.loc
4/13/2017 9:56:27 AM FromAD: command line = SMSSITECODE=HQ1 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Current AD forest name is firstcom.local, domain name is firstcom.local ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Domain joined client is in Intranet ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CMPInfoFromADCache requests are throttled for 01:00:00 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Found MP http://configmanager.firstcom.local from AD ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM SslState value: 224 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Detected sitecode 'HQ1' from AD. ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPPORT: 80 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPSPORT: 443 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPSSTATE: 224 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM CCMHTTPSCERTNAME: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM FSP: configmanager.firstcom.loc
4/13/2017 9:56:27 AM CCMFIRSTCERT: 1 ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Config file: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM Retry time: 10 minute(s) ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM MSI log file: C:\WINDOWS\ccmsetup\Logs\c
4/13/2017 9:56:27 AM MSI properties: CCMFIRSTCERT="1" CCMHTTPPORT="80" CCMHTTPSCERTNAME="" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" FSP="configmanager.firstco
4/13/2017 9:56:27 AM Source List: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM MPs: ccmsetup 7764 (0x1E54)
4/13/2017 9:56:27 AM http://configmanager.firstcom.local ccmsetup 7764 (0x1E54)
--------------------------
I then tried to do a manual install with the parameter SMSSITECODE=CM1 in the command line at the command prompt, it installs. After it is done installing, I open up Configuration Manager from the control panel and the Site Code textbox is empty. The only value that it will take is HQ1 (the old primary). I am attaching that log file.
ccmsetup---Manual-install-with-CM1-S.log
ASKER
But the original server with HQ1 is in Read-Only mode. How would I delete those boundaries?
You can delete them from AD directly. If you shut down old SCCM or remove its permissions to SYSTEM MANAGEMENT container then it cannot re insert the boundaries back.
Container is here https://cmsbsttp.files.wordpress.com/2012/11/screen-33.png
Check which computers & groups have permissions on it. Remove old servers from permissions after noting current settings.
Remove just one boundary and then push the client again. If it works then remove all of the old boundaries. They will have HQ1 etc in name.
Container is here https://cmsbsttp.files.wordpress.com/2012/11/screen-33.png
Check which computers & groups have permissions on it. Remove old servers from permissions after noting current settings.
Remove just one boundary and then push the client again. If it works then remove all of the old boundaries. They will have HQ1 etc in name.
ASKER
After deleting the HQ1 references in AD per your previous statement, the client still is having issues. I am manually installing from my local PC and run into the following errors (I will attach the log file):
1. 4/14/2017 12:33:55 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 10140 (0x279C)
2. 4/14/2017 12:33:59 PM Failed to persist AAD on-boarding info. Error 0x80070002 ccmsetup 6540 (0x198C)
3. 4/14/2017 12:33:59 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 6540 (0x198C)
4. 4/14/2017 12:33:59 PM sending with winhttp failed; 80072efd FSPStateMessage 6540 (0x198C)
5. 4/14/2017 12:34:02 PM Failed to send HTTP request. (Error at WinHttpSendRequest: 0x80072efd) ccmsetup 6540 (0x198C)
6. 4/14/2017 12:34:02 PM GetDPLocations failed with error 0x80072efd ccmsetup 6540 (0x198C)
7. 4/14/2017 12:34:02 PM Failed to get DP locations as the expected version from MP 'http://ConfigManager16.firstcom.local'. Error 0x80072efd ccmsetup 6540 (0x198C)
8. 4/14/2017 12:34:02 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 6540 (0x198C)
9. 4/14/2017 12:34:02 PM sending with winhttp failed; 80072efd FSPStateMessage 6540 (0x198C)
10. 4/14/2017 12:44:02 PM Failed to send HTTP request. (Error at WinHttpSendRequest: 0x80072efd) ccmsetup 6540 (0x198C)
11. 4/14/2017 12:44:02 PM GetDPLocations failed with error 0x80072efd ccmsetup 6540 (0x198C)
12. 4/14/2017 12:44:02 PM Failed to get DP locations as the expected version from MP 'http://ConfigManager16.firstcom.local'. Error 0x80072efd ccmsetup 6540 (0x198C)
13. 4/14/2017 12:44:02 PM Location request failed with error 0x80072efd, status code 200. MP 'http://ConfigManager16.firstcom.local' could be busy at this moment. ccmsetup 6540 (0x198C)
Then it states that it will retry in 10 minutes.
1. 4/14/2017 12:33:55 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 10140 (0x279C)
2. 4/14/2017 12:33:59 PM Failed to persist AAD on-boarding info. Error 0x80070002 ccmsetup 6540 (0x198C)
3. 4/14/2017 12:33:59 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 6540 (0x198C)
4. 4/14/2017 12:33:59 PM sending with winhttp failed; 80072efd FSPStateMessage 6540 (0x198C)
5. 4/14/2017 12:34:02 PM Failed to send HTTP request. (Error at WinHttpSendRequest: 0x80072efd) ccmsetup 6540 (0x198C)
6. 4/14/2017 12:34:02 PM GetDPLocations failed with error 0x80072efd ccmsetup 6540 (0x198C)
7. 4/14/2017 12:34:02 PM Failed to get DP locations as the expected version from MP 'http://ConfigManager16.firstcom.local'. Error 0x80072efd ccmsetup 6540 (0x198C)
8. 4/14/2017 12:34:02 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 6540 (0x198C)
9. 4/14/2017 12:34:02 PM sending with winhttp failed; 80072efd FSPStateMessage 6540 (0x198C)
10. 4/14/2017 12:44:02 PM Failed to send HTTP request. (Error at WinHttpSendRequest: 0x80072efd) ccmsetup 6540 (0x198C)
11. 4/14/2017 12:44:02 PM GetDPLocations failed with error 0x80072efd ccmsetup 6540 (0x198C)
12. 4/14/2017 12:44:02 PM Failed to get DP locations as the expected version from MP 'http://ConfigManager16.firstcom.local'. Error 0x80072efd ccmsetup 6540 (0x198C)
13. 4/14/2017 12:44:02 PM Location request failed with error 0x80072efd, status code 200. MP 'http://ConfigManager16.firstcom.local' could be busy at this moment. ccmsetup 6540 (0x198C)
Then it states that it will retry in 10 minutes.
ASKER
After rebooting the computer and the new SCCM server, the client install fails quicker now. I will attach the full log file.
The last few errors are:
1. 4/14/2017 2:38:36 PM Failed to download client files by BITS. Error 0x800704dd ccmsetup 9880 (0x2698)
2. 4/14/2017 2:38:36 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 9880 (0x2698)
3. 4/14/2017 2:38:36 PM Failed to download from DP 'http://ConfigManager16.firstcom.local/SMS_DP_SMSPKG$/CM100002', error 0x800704dd. ccmsetup 9880 (0x2698)
4. 4/14/2017 2:38:36 PM Failed to download client files by BITS. Error 0x800704dd ccmsetup 9880 (0x2698)
5. 4/14/2017 2:38:36 PM Failed to connect to policy namespace. Error 0x8004100e ccmsetup 9880 (0x2698)
6. 4/14/2017 2:38:36 PM Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 9880 (0x2698)
7. 4/14/2017 2:38:36 PM CcmSetup failed with error code 0x800704dd ccmsetup 9880 (0x2698)
ccmsetup---Fails-to-install-and-quit.log
The last few errors are:
1. 4/14/2017 2:38:36 PM Failed to download client files by BITS. Error 0x800704dd ccmsetup 9880 (0x2698)
2. 4/14/2017 2:38:36 PM Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 9880 (0x2698)
3. 4/14/2017 2:38:36 PM Failed to download from DP 'http://ConfigManager16.firstcom.local/SMS_DP_SMSPKG$/CM100002', error 0x800704dd. ccmsetup 9880 (0x2698)
4. 4/14/2017 2:38:36 PM Failed to download client files by BITS. Error 0x800704dd ccmsetup 9880 (0x2698)
5. 4/14/2017 2:38:36 PM Failed to connect to policy namespace. Error 0x8004100e ccmsetup 9880 (0x2698)
6. 4/14/2017 2:38:36 PM Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 9880 (0x2698)
7. 4/14/2017 2:38:36 PM CcmSetup failed with error code 0x800704dd ccmsetup 9880 (0x2698)
ccmsetup---Fails-to-install-and-quit.log
ASKER
I noticed that the previous comment didn't get the file uploaded. Here is that file.
ccmsetup---Manual-Install-Failed.log
ccmsetup---Manual-Install-Failed.log
If you can see the sccm icon in control panel then it means that your client is installed. In this case you should check the logs in
c:\windows\ccm\logs
if the client is not yet installed then install it totally locally (bypassing remote servers) this way:
copy all client files from new SCCM to c:\temp\client on a test machine. You can get these from
C:\Program Files\Microsoft Configuration Manager\Client on sccm server
then run
CCMSetup.exe /source:C:\TEMP\client SMSSITECODE=CM1
This will install the client totally locally.
configmanager.firstcom.loc
configManager16.firstcom.l
See if you can open this url from client http://ConfigManager16.firstcom.local
If it works then try this url
https://ConfigManager16.firstcom.local/sms_mp/.sms_aut?mplist
and https://ConfigManager16.firstcom.local/sms_mp/.sms_aut?mplist
If these work then your new MP is most probably working and you should check ClientIDManagerStartup.log
c:\windows\ccm\logs
if the client is not yet installed then install it totally locally (bypassing remote servers) this way:
copy all client files from new SCCM to c:\temp\client on a test machine. You can get these from
C:\Program Files\Microsoft Configuration Manager\Client on sccm server
then run
CCMSetup.exe /source:C:\TEMP\client SMSSITECODE=CM1
This will install the client totally locally.
configmanager.firstcom.loc
configManager16.firstcom.l
See if you can open this url from client http://ConfigManager16.firstcom.local
If it works then try this url
https://ConfigManager16.firstcom.local/sms_mp/.sms_aut?mplist
and https://ConfigManager16.firstcom.local/sms_mp/.sms_aut?mplist
If these work then your new MP is most probably working and you should check ClientIDManagerStartup.log
ASKER
Configmanager.firstcom.loc
Configmanager16.firstcom.l
When opening http://ConfigManger16.firstcom.local, I get the default IIS page
I then tried https://ConfigManager16.firstcom.local/sms_mp/.sms_aut?mplist - https doesn't work; however, I did not setup any secured keys. If I change it to http://, I get the following xml
- <MPList>
- <MP Name="CONFIGMANAGER16.FIRS
<Version>8458</Version>
- <Capabilities SchemaVersion="1.0">
<Property Name="SSLState" Value="0" />
</Capabilities>
</MP>
</MPList>
You then asked that I go to another link, but it appears to be an exact duplicate to the prior https: link. I assume you meant me to try a different link.
After copying the Client folder to the local PC and installing it with the following command:
ccmsetup /source c:\temp\client SMSSITECODE=CM1
it installs, but it puts in the old sitecode HQ1, not CM1 as was in the parameter. I am attaching the ccmsetup log file that is located in c:\windows\ccmsetup\logs.
Please let me know of any other information that I can provide to you to help me to resolve this issue.
ccmsetup---Manual-Install-after-rebo.log
Configmanager16.firstcom.l
When opening http://ConfigManger16.firstcom.local, I get the default IIS page
I then tried https://ConfigManager16.firstcom.local/sms_mp/.sms_aut?mplist - https doesn't work; however, I did not setup any secured keys. If I change it to http://, I get the following xml
- <MPList>
- <MP Name="CONFIGMANAGER16.FIRS
<Version>8458</Version>
- <Capabilities SchemaVersion="1.0">
<Property Name="SSLState" Value="0" />
</Capabilities>
</MP>
</MPList>
You then asked that I go to another link, but it appears to be an exact duplicate to the prior https: link. I assume you meant me to try a different link.
After copying the Client folder to the local PC and installing it with the following command:
ccmsetup /source c:\temp\client SMSSITECODE=CM1
it installs, but it puts in the old sitecode HQ1, not CM1 as was in the parameter. I am attaching the ccmsetup log file that is located in c:\windows\ccmsetup\logs.
Please let me know of any other information that I can provide to you to help me to resolve this issue.
ccmsetup---Manual-Install-after-rebo.log
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
You figured it out! Thank you.
Deleting the two HKLM entries allows me to install both manually and with a client push and it points to the correct SiteCode. One last question though. Only one of the HKLM entries repopulates on the PC. Is there cause to be concerned with this? The HKLM entry that does not repopulation is HKEY_LOCAL_MACHINE\SOFTWAR
Deleting the two HKLM entries allows me to install both manually and with a client push and it points to the correct SiteCode. One last question though. Only one of the HKLM entries repopulates on the PC. Is there cause to be concerned with this? The HKLM entry that does not repopulation is HKEY_LOCAL_MACHINE\SOFTWAR
Cannot say for sure but does not seem likely. This article http://blog.coretech.dk/heh/new-agents-will-not-re-assign-to-configmgr-2012-site/ mentions 3 keys with GPO in name
REG delete "hklm\SOFTWARE\Microsoft\S
REG delete "hklm\SOFTWARE\Microsoft\S
REG delete "hklm\SOFTWARE\Microsoft\S
Lower entries are normally left at defaults so should be OK. The entries will populate if you set them via GPO. Most people will not use GPO for this.
If this entry is set for SCCM 2016 then there is no need for a GPO. https://jthys.files.wordpress.com/2011/12/sccm_adpublish.jpg
Try to disable this in the older SCCM though. It may try to create conflicting entries in "System Management" container.
REG delete "hklm\SOFTWARE\Microsoft\S
REG delete "hklm\SOFTWARE\Microsoft\S
REG delete "hklm\SOFTWARE\Microsoft\S
Lower entries are normally left at defaults so should be OK. The entries will populate if you set them via GPO. Most people will not use GPO for this.
If this entry is set for SCCM 2016 then there is no need for a GPO. https://jthys.files.wordpress.com/2011/12/sccm_adpublish.jpg
Try to disable this in the older SCCM though. It may try to create conflicting entries in "System Management" container.
ASKER
Deleting the two HKLM entries in the registry allowed me to deploy the client correctly. Thank you for your time and help!
You need to delete boundaries from HQ1, they are getting published in AD.