McCoyIT
asked on
SCCM Client Push Installation - No site code
I have set up an SCCM test environment - a primary site, and a single secondary site server.
I did manage to get client push installation working, for the most part.. problem being the client is not getting a site code, and does not show up in the console as having the client installed.
I've done a fair bit of searching on this to try and find where the problem is, so I'll try to summarize what I've found / tried so far:
- The client can ping the site server, and visa versa, and the site server can connect to the admin share on the client. The site server also appears to be able to connect to the client by WMI (tested by wmimgmt.msc)
- I've specified several switches on the client push installation:
SMSSITECODE=MC2 SLP=MC1 SMSDIRECTORYLOOKUP=NOWINS FSP=MC1
(MC2 is my secondary site where both the secondary site server and client are located, MC1 is the primary site)
- I Have tried setting boundaries by both Active Directory site and IP subnet
- The primary site server, secondary site server computer accounts and the service account I use for client push installation all have full control of the object and all descentants for the System Management contatiner in AD.
- The primary site server, secondary site server computer accounts are both in the local administrator group on the SQL server (which is on a separate server from SCCM itself).
I've also pasted in some lines from log files on the client relating to the site code:
smscliui.log:
ClientLocation.log:
LocationServices.log
After a lot of time spent searching error codes I'm pretty much stuck here, if anybody has any tips I would very much appreciate it.
I've been wondering if this could have anything to do with permissions on the system management container, or with IIS permissions on the primary or secondary site server? Any way to test that?
I did manage to get client push installation working, for the most part.. problem being the client is not getting a site code, and does not show up in the console as having the client installed.
I've done a fair bit of searching on this to try and find where the problem is, so I'll try to summarize what I've found / tried so far:
- The client can ping the site server, and visa versa, and the site server can connect to the admin share on the client. The site server also appears to be able to connect to the client by WMI (tested by wmimgmt.msc)
- I've specified several switches on the client push installation:
SMSSITECODE=MC2 SLP=MC1 SMSDIRECTORYLOOKUP=NOWINS FSP=MC1
(MC2 is my secondary site where both the secondary site server and client are located, MC1 is the primary site)
- I Have tried setting boundaries by both Active Directory site and IP subnet
- The primary site server, secondary site server computer accounts and the service account I use for client push installation all have full control of the object and all descentants for the System Management contatiner in AD.
- The primary site server, secondary site server computer accounts are both in the local administrator group on the SQL server (which is on a separate server from SCCM itself).
I've also pasted in some lines from log files on the client relating to the site code:
smscliui.log:
<![LOG[WARNING - Client is currently unassigned or an error occurred retrieving the assigned site. GetAssignedSite() returned : 0X80040002]LOG]!><time="15:11:09.599+420" date="02-09-2011" component="smscliui" context="" type="2" thread="3160" file="clicfgdlg.cpp:2383">
<![LOG[Attempt to auto discover site has failed. Error: 0X40002]LOG]!><time="15:11:10.504+420" date="02-09-2011" component="smscliui" context="" type="3" thread="3160" file="clicfgdlg.cpp:1668">
<![LOG[SMS Site code has not been changed.]LOG]!><time="15:11:12.064+420" date="02-09-2011" component="smscliui" context="" type="1" thread="3160" file="clicfgdlg.cpp:2042">ClientLocation.log:
<![LOG[Assigning client to site 'MC2']LOG]!><time="08:55:07.169+420" date="02-09-2011" component="ClientLocation" context="" type="1" thread="2552" file="smsclientclass.cpp:485">
<![LOG[Unable to verify the sitecode 'MC2', AD schema is not extended or SLP is not present. Cannot continue site assignment.]LOG]!><time="08:55:07.387+420" date="02-09-2011" component="ClientLocation" context="" type="3" thread="2552" file="smsclientclass.cpp:544">LocationServices.log
<![LOG[Sending Fallback Status Point message, STATEID='500'.]LOG]!><time="00:04:15.244+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="fspclientdeployassign.cpp:49">
<![LOG[Failed to send status 500 to the FSP (80072EE7)]LOG]!><time="00:04:19.846+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="1008" file="fspclientdeployassign.cpp:143">
<![LOG[Processing pending site assignment.]LOG]!><time="00:04:19.846+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="lsad.cpp:3328">
<![LOG[Assigning to site 'MC2']LOG]!><time="00:04:19.846+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="lsad.cpp:3334">
<![LOG[LSVerifySiteVersion : Verifying Site Version for <MC2>]LOG]!><time="00:04:19.846+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="lsad.cpp:5321">
<![LOG[LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6487.0000' for site 'MC2']LOG]!><time="00:04:20.205+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="lsad.cpp:5129">
<![LOG[LSVerifySiteVersion : Verified Client Version '4.00.6487.2000' is not greater than Site Version '4.00.6487.0000'. Client can be assigned to site <MC2>.]LOG]!><time="00:04:20.205+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="lsad.cpp:5452">
<![LOG[Assignment site code for site 'MC2' is 'MC1'Site codes do not match]LOG]!><time="00:04:20.221+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="lsad.cpp:4295">
<![LOG[Sitecode 'MC2' is invalid, client will not be assigned.]LOG]!><time="00:04:20.236+420" date="02-09-2011" component="LocationServices" context="" type="2" thread="1008" file="lsad.cpp:3357">
<![LOG[Sending Fallback Status Point message, STATEID='602'.]LOG]!><time="00:04:20.236+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="1008" file="fspclientdeployassign.cpp:49">
<![LOG[Failed to send status 602 to the FSP (80072EE7)]LOG]!><time="00:04:24.823+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="1008" file="fspclientdeployassign.cpp:143">
<![LOG[Client SSL is disabled. Setting state to 0x0.]LOG]!><time="08:55:07.356+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="2552" file="ccmutillib.cpp:184">
<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="08:55:07.356+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="2552" file="lsad.cpp:2261">
<![LOG[Unable to find SLPs in Registry and AD, policy prevents failover to WINS for lookup]LOG]!><time="08:55:07.387+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="2552" file="lsad.cpp:2286">
<![LOG[LSGetAssignmentSiteCodeForSiteFromSLP : Unable to get the list of SLPs]LOG]!><time="08:55:07.387+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="2552" file="lsad.cpp:4098">
<![LOG[LSGetAssignmentSiteCodeForSite: Failed to get Assigned Site Code from AD and SLP]LOG]!><time="08:55:07.387+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="2552" file="lsad.cpp:4236">
<![LOG[Current AD site of machine is Corporate]LOG]!><time="15:11:10.099+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="916" file="lsad.cpp:457">
<![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="15:11:10.457+420" date="02-09-2011" component="LocationServices" context="" type="1" thread="916" file="lsad.cpp:2261">
<![LOG[Unable to find SLPs in Registry and AD, policy prevents failover to WINS for lookup]LOG]!><time="15:11:10.504+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="916" file="lsad.cpp:2286">
<![LOG[LSGetAssignedSiteFromSLP : Unable to get the list of SLPs]LOG]!><time="15:11:10.504+420" date="02-09-2011" component="LocationServices" context="" type="3" thread="916" file="lsad.cpp:1986">After a lot of time spent searching error codes I'm pretty much stuck here, if anybody has any tips I would very much appreciate it.
I've been wondering if this could have anything to do with permissions on the system management container, or with IIS permissions on the primary or secondary site server? Any way to test that?
Hi,
Line - Unable to find SLPs in Registry and AD, policy prevents failover to WINS for lookup]LOG]!><time="08:55:
Try amending the Client push variable SMSSLP=MC1 instead of SLP=MC1
SMSSITECODE=MC2 SMSSLP=MC1 SMSDIRECTORYLOOKUP=NOWINS FSP=MC1
Line - Unable to find SLPs in Registry and AD, policy prevents failover to WINS for lookup]LOG]!><time="08:55:
Try amending the Client push variable SMSSLP=MC1 instead of SLP=MC1
SMSSITECODE=MC2 SMSSLP=MC1 SMSDIRECTORYLOOKUP=NOWINS FSP=MC1
ASKER
Still no luck after changing that switch.
I'll note a couple more things.
I've run the Management Point Troubleshooter from the ConfigMgr 2007Toolkit V2 and everything passed for both the primary and secondary sites.
When the client push installation finishes, I see this error in the ccmsetup.log file:
<![LOG[Sending Fallback Status Point message, STATEID='400'.]LOG]!><time
<![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="08:5
Also in C:\Windows\System32\CCM\Lo
In FSPStateMessage.log:
<![LOG[Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7]LOG]!><time="09:17:
<![LOG[[CCMHTTP] HTTP ERROR: URL=HTTP://MC1/SMS_FSP/.sms_fsp, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NO
In Location Services.log:
<![LOG[Sending Fallback Status Point message, STATEID='500'.]LOG]!><time
<![LOG[Failed to send status 500 to the FSP (80072EE7)]LOG]!><time="09
<![LOG[Processing pending site assignment.]LOG]!><time="0
<![LOG[Assigning to site 'MC2']LOG]!><time="09:17:4
<![LOG[LSVerifySiteVersion
<![LOG[LSGetSiteVersionFro
<![LOG[LSVerifySiteVersion
<![LOG[Assignment site code for site 'MC2' is 'MC1'Site codes do not match]LOG]!><time="09:17:4
<![LOG[Sitecode 'MC2' is invalid, client will not be assigned.]LOG]!><time="09:
<![LOG[Sending Fallback Status Point message, STATEID='602'.]LOG]!><time
<![LOG[Failed to send status 602 to the FSP (80072EE7)]LOG]!><time="09
I also took a look at the ccm.log file on the secondary site server, and noticed this when it tires to install the client:
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 2/10/2011 9:15:31 AM 2060 (0x080C)
---> Unable to connect to WMI (r) on remote machine "SCCMCLIENT2", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2/10/2011 9:15:31 AM 2060 (0x080C)
which I find odd, because I actually logged into the secondary site server with the service account I use for client push installation and tested WMI using the instructions in the solution here:
https://www.experts-exchange.com/questions/23076759/SCCM-2007-Cient-push-installation-fails-Unable-to-connect-to-WMI.html
and I was able to connect to the client machine.
So once again I'm stuck at the point where the client push installation completes, but the client does not get assigned any site code.
I'll note a couple more things.
I've run the Management Point Troubleshooter from the ConfigMgr 2007Toolkit V2 and everything passed for both the primary and secondary sites.
When the client push installation finishes, I see this error in the ccmsetup.log file:
<![LOG[Sending Fallback Status Point message, STATEID='400'.]LOG]!><time
<![LOG[sending with winhttp failed; 80072ee7]LOG]!><time="08:5
Also in C:\Windows\System32\CCM\Lo
In FSPStateMessage.log:
<![LOG[Failed in WinHttpSendRequest API, ErrorCode = 0x2ee7]LOG]!><time="09:17:
<![LOG[[CCMHTTP] HTTP ERROR: URL=HTTP://MC1/SMS_FSP/.sms_fsp, Port=80, Protocol=http, SSLOptions=0, Code=12007, Text=ERROR_WINHTTP_NAME_NO
In Location Services.log:
<![LOG[Sending Fallback Status Point message, STATEID='500'.]LOG]!><time
<![LOG[Failed to send status 500 to the FSP (80072EE7)]LOG]!><time="09
<![LOG[Processing pending site assignment.]LOG]!><time="0
<![LOG[Assigning to site 'MC2']LOG]!><time="09:17:4
<![LOG[LSVerifySiteVersion
<![LOG[LSGetSiteVersionFro
<![LOG[LSVerifySiteVersion
<![LOG[Assignment site code for site 'MC2' is 'MC1'Site codes do not match]LOG]!><time="09:17:4
<![LOG[Sitecode 'MC2' is invalid, client will not be assigned.]LOG]!><time="09:
<![LOG[Sending Fallback Status Point message, STATEID='602'.]LOG]!><time
<![LOG[Failed to send status 602 to the FSP (80072EE7)]LOG]!><time="09
I also took a look at the ccm.log file on the secondary site server, and noticed this when it tires to install the client:
CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e SMS_CLIENT_CONFIG_MANAGER 2/10/2011 9:15:31 AM 2060 (0x080C)
---> Unable to connect to WMI (r) on remote machine "SCCMCLIENT2", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 2/10/2011 9:15:31 AM 2060 (0x080C)
which I find odd, because I actually logged into the secondary site server with the service account I use for client push installation and tested WMI using the instructions in the solution here:
https://www.experts-exchange.com/questions/23076759/SCCM-2007-Cient-push-installation-fails-Unable-to-connect-to-WMI.html
and I was able to connect to the client machine.
So once again I'm stuck at the point where the client push installation completes, but the client does not get assigned any site code.
Do you have any 3rd party HTTP proxy redirection (Anywhere+ / Scansafe)?
ASKER
Don't have anything like that. The client I'm testing on is a clean install of Windows 7, only software that has been loaded on it is Trend Micro A/V.
Hi - Sorry - My emails down so I didnt get notification of your comments - I have to head off for the weekend now.. Will help further if I can on Monday.
If anyone else wants to jump in to help in the meantime please feel free!
All the best
If anyone else wants to jump in to help in the meantime please feel free!
All the best
ASKER
No worries, I appreciate the help!
I may have actually found the solution to my problem.
I was looking a the "LocationServices.log" file, and noticed this line:
"Assignment site code for site 'AAA' is 'BBB' Site codes do not match" (AAA would be my secondary site, BBB would be my primary site code)
Which led me to this:
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/75537fcf-44c3-4184-883e-dbe547f4cfc8/
"That's the problem: "Attempting to assign client to secondary site". You cannot assign clients to secondary sites - only primaries."
So I guess I was completely misunderstanding how site codes are supposed to work.
In my case where I have a single primary site at our data center, and will have a bunch of secondary sites across our WAN, do all clients need to be assigned to the primary site?
I was under the assumption before that clients would need to be assigned to the secondary site at their physical location in order to send and receive data (receive packages, updates, OSD etc) from the correct site server, but if all the clients are assigned to the primary site server, then I would assume that would be based on the secondary site's boundaries?
If somebody could cofirm this for me I would very much appreciate it.
for the time being it appears I have a functioning test client.. when I changed the SMSSITECODE switch to the primary site code then uninstalled the client locally and pushed it out again, the site code was assigned successfully.
I may have actually found the solution to my problem.
I was looking a the "LocationServices.log" file, and noticed this line:
"Assignment site code for site 'AAA' is 'BBB' Site codes do not match" (AAA would be my secondary site, BBB would be my primary site code)
Which led me to this:
http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/75537fcf-44c3-4184-883e-dbe547f4cfc8/
"That's the problem: "Attempting to assign client to secondary site". You cannot assign clients to secondary sites - only primaries."
So I guess I was completely misunderstanding how site codes are supposed to work.
In my case where I have a single primary site at our data center, and will have a bunch of secondary sites across our WAN, do all clients need to be assigned to the primary site?
I was under the assumption before that clients would need to be assigned to the secondary site at their physical location in order to send and receive data (receive packages, updates, OSD etc) from the correct site server, but if all the clients are assigned to the primary site server, then I would assume that would be based on the secondary site's boundaries?
If somebody could cofirm this for me I would very much appreciate it.
for the time being it appears I have a functioning test client.. when I changed the SMSSITECODE switch to the primary site code then uninstalled the client locally and pushed it out again, the site code was assigned successfully.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Perfect, and thanks for the tip on boundaries, I have it set up by subnets now and I'll leave it that way because we have clients that move between sites as well.
ASKER