Linfit Posted October 19, 2017 Posted October 19, 2017 OK, I am at my wits end with this one. I set up SCCM last year and had it working fine for updates and endpoint protection. Over the summer, we updated most of our clients from Win 7 to 10 (2016 Enterprise LTSB). Since then I have been unable to deploy the SCCM client to any Windows 10 workstations succesfully. Deployment to 7 or Server works no problem. To 10, push deployment fails: it copies the sccmsetup.exe, gets as far as initiating the BITS downloads for the other parts, but stalls at that point and never recovers. If I try a manual install using the command line on the workstation, I can get the install to appear to complete by using the /nosystem switch, but the client doesn't seem to communicate properly with the server - its shows in the console as having the correct site code and as active, but it isn't getting policy and always shows a grey query mark rather than the green tick, so its seems to know the client is there but communications are impaired in some way: this suggests the install isn't quite right in some way. Its on every machine, every new image we build for testing. I have tried totally clean images, no GPO's, no other software, same result. In contrast, we built a Win 7 machine and push client install worked first time and the client was in the console and up and running withing 5 minutes. Servers, (all types from 2008r2 up to 2016) are fine, but no joy with 10. SCCM is the latest 1706 version 5.0.8540, and fully patched, and technet confirms its compatible with 10 LTSB. I have been all over the web looking at possible causes, tried all the obvious ones (boundaries, broken MP or DP) even went so far as to do a complete re-install of SCCM with a new site code: but if it was any of these things I presume it wouldn't work on 7 either. My gut feeling is that it may be something to do with WMI issues, perhaps permissions, but my knowledge in this area is weak so am not really sure what I am looking at. Has anyone else had issues with SCCM and Win 10, or any suggestions for what else I might look at ?
forkies Posted October 19, 2017 Posted October 19, 2017 Can you ping the windows 10 device from the server using hostname?
nickbro Posted October 19, 2017 Posted October 19, 2017 Check the silver light file size in the client folder. If it's 0bytes it's currupt
sparkeh Posted October 19, 2017 Posted October 19, 2017 (edited) Anything interesting in the logs on the client? I am thinking of client.msi.log for installation problems, ccmeval.log for evaluation problems, ccmexec, ccmmessaging.log for any problems sending messages to server, clientauth.log for issues registering client with server (I seem to remember having an issue with this and win 10), location services.log ...to name a few [emoji3] Edited October 19, 2017 by sparkeh
skell Posted October 20, 2017 Posted October 20, 2017 FYI, the logs for the client install are at c:\WIndows\CCMSETUP\logs The two main ones in there are ccmsetup.log and client.msi.log If its failing quickly, the information you need will be in ccmsetup.log Are you able to manually install it from the client, rather than push from the server?
Linfit Posted October 20, 2017 Author Posted October 20, 2017 Can you ping the windows 10 device from the server using hostname? Yes, no issues with this, I can ping any of the workstations I try by hostname. I have checked our DNS and records seem correct, scavenging is on and working, no relevant stale records.
Linfit Posted October 20, 2017 Author Posted October 20, 2017 Anything interesting in the logs on the client? I am thinking of client.msi.log for installation problems, ccmeval.log for evaluation problems, ccmexec, ccmmessaging.log for any problems sending messages to server, clientauth.log for issues registering client with server (I seem to remember having an issue with this and win 10), location services.log ...to name a few [emoji3] ccmsetup.log shows it checks that the files it needs are not present, identifies the DP and finds the packages on there, and starts BITS downloads for them, one example being: [LOG[Adding file 'http://SysCent-Server.SMSC.Local:80/SMS_DP_SMSPKG$/NEW00002/i386/vcredist_x86.exe' to BITS job The BITS downloads never start, I see repeated attempts: [LOG[Download Update: A recoverable error has occurred. A retry attempt will be made.] and eventually the BITS downloads time out. I then get this: [LOG[Failed to download files through BITS. Error: 0x800706d9, Description There are no more endpoints available from the endpoint mapper. [LOG[Failed to get client version for sending state messages. Error 0x8004100e] [LOG[[] Params to send '5.0.8540.1006 Deployment Error 0x800706d9. Path http://SysCent-Server.SMSC.Local/SMS_DP_SMSPKG$/NEW00002'] [LOG[sending Fallback Status Point message to 'SYSCENT-SERVER.SMSC.LOCAL', STATEID='309'.] [LOG[] [LOG[state message with TopicType 800 and TopicId {09EE4C15-CC39-47ED-BC5D-6FCC395A07B1} has been sent to the FSP] [LOG[Failed to download from DP 'http://SysCent-Server.SMSC.Local/SMS_DP_SMSPKG$/NEW00002', error 0x800706d9.] [LOG[Enumerated all 1 DP locations but none of them is good. Fallback to MP.] [LOG[Cost settings successfully set on '{D8D68A5E-C446-4D4A-BB00-DF63D9E6709F}'.] [LOG[using branch cache option.]LOG] It then tries to get the same files but this time from a different location on the server - (presumably because it is now trying the management point instead of the DP ?) [LOG[Adding file 'HTTP://SysCent-Server.SMSC.Local:80/CCM_Client/i386/vcredist_x86.exe' to BITS job But this too just results in repeated [LOG[Download Update: A recoverable error has occurred as before.
Steve21 Posted October 20, 2017 Posted October 20, 2017 Do you have the firewall disabled in your 10 image/ If so try it with it enabled (service wise) Steve 1
Linfit Posted October 20, 2017 Author Posted October 20, 2017 Yes, and the service is not running. You mean turn the Firewall service on and then try it ? Will give that a go.
sparkeh Posted October 20, 2017 Posted October 20, 2017 If that doesn't fix it I think it worth checking that the client push account has valid credentials
Linfit Posted October 20, 2017 Author Posted October 20, 2017 Well *******r. It was the ******* firewall service. Turned on firewall service on two test clients and they are deployed and showing in the console within half an hour. Thanks ever so much @Steve21, I owe you mucho beers if you are ever North of Manchester. Been fiddling with this off an on since the start of term. Hours wasted going down google rabbit holes. Why isn't it documented anywhere that the firewall service needs to be running !!!
Steve21 Posted October 20, 2017 Posted October 20, 2017 It's SCCM none of the gotchas are documented It's to do with the way it allows traffic in win10 basically until the "disabled" service really disables itself you're blocking traffic and when it's on it'll let it through ironically Ps on my way to your local pub!!! Steve
smithson83 Posted October 29, 2017 Posted October 29, 2017 Just stumbled upon this, I've been having the same issue... If this is the issue, you'll be owed a few more beers @Steve21. Never thought to check the ******* firewall service
Hunter Posted November 7, 2017 Posted November 7, 2017 will try today as we are having the same issues, will let you know
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now