Hunter Posted October 6, 2017 Posted October 6, 2017 Hi guys, I am having issues with SCCM and deploying the client through all of my different "builds". This recently happened after an update to our syscent server, and our builds no longer work correctly. We have attempted a WMI fix and even repairing the management point with no success. We are all truly stuck in the mud with this issue. I have attached a text document with the error messages Fingers crossed there is a wizard out there who can help, Many thanks, HCCMsetup.txt
Steve21 Posted October 6, 2017 Posted October 6, 2017 When you say the client do you mean the SCCM client? or the OS? It looks as if your boundaries aren't setup right from the errors. What's the settings for them? Steve
Steve21 Posted October 6, 2017 Posted October 6, 2017 Also how many sites are you supposed to have? As it seems you have a CHS and CRI setup that are being queried? Steve
Hunter Posted October 6, 2017 Author Posted October 6, 2017 Hi Steve, I am currently searching for the boundary settings, when I said client I was asking about SCCM client side sorry I should have been more specific. We only have the one site which is CHS as far as I understand the CRI is a distribution point. Thankyou Steve H
Steve21 Posted October 6, 2017 Posted October 6, 2017 It's under admin->Hierachy, then the boundaries and boundary group page. Steve
Hunter Posted October 6, 2017 Author Posted October 6, 2017 ok have located steve, shall I copy and paste all boundaries and B-groups?
Steve21 Posted October 6, 2017 Posted October 6, 2017 If you could do a screenshot of both pages (Assuming if you don't mind posting it on here?) Steve
Hunter Posted October 6, 2017 Author Posted October 6, 2017 Sadly I cannot get the files to upload from my work computers via PM too you, will have to wait until my manager is back for permission to upload on here. Apologies H
Steve21 Posted October 6, 2017 Posted October 6, 2017 That's no worries, Can always drop you an email too to use if it's easier, but best check with nick when he's back Steve 1
Hunter Posted October 6, 2017 Author Posted October 6, 2017 an email would be smashing, I shall ask anyway but I think it would be best via an outlook message
nickbro Posted October 7, 2017 Posted October 7, 2017 I think we've fixed it, silverlight install had become corrupt (was 0 bytes). Downloaded the correct installer and it seems to be installing via push. Now for a task sequence 1
nickbro Posted October 7, 2017 Posted October 7, 2017 Spoke too soon. Task Sequence does not work correctly. In the clientservicing.log file got a constant Client is not yet registered but no FSP is available. The thing doesn't want to install any applications.
Jamoire Posted October 7, 2017 Posted October 7, 2017 Spoke too soon. Task Sequence does not work correctly. In the clientservicing.log file got a constant Client is not yet registered but no FSP is available. The thing doesn't want to install any applications. We had a similar error after latest sccm build, it turned out our reboot steps in the task sequence were too short and the ts was rebooting while the client was busy causing the issue. Increased the timer in the reboot steps (i think to 45 secs but would have to check) and all was good. Might he worth a try. 1
nickbro Posted October 7, 2017 Posted October 7, 2017 Hi @Jamorie, We don't have any restart commands in our task sequence after the OS has installed. I removed those when the new ADK came out. I have now added a restart command in after it enables bitlocker to try and do something, but it seems to still hang on installing applications. The task sequence service stops, CCMexec is using a lot of CPU time and getting that error in the log a lot. This is what our task sequence looks like
Hunter Posted October 9, 2017 Author Posted October 9, 2017 No luck as of yet Gents can try add a restart command in the task seq too see what happens?
Steve21 Posted October 9, 2017 Posted October 9, 2017 That's basically the same error you were having before, it can't find a management point to resolve against. Do you have the fallback role enabled? If so if you manually specify a fallback status point does it go through ok? Steve
Hunter Posted October 9, 2017 Author Posted October 9, 2017 by manually specify do you mean try add a "fallback role" as we already have one in Servers and site system roles.
Steve21 Posted October 9, 2017 Posted October 9, 2017 (edited) Basically if it's failing to get to or access a MP it'll be default just go blargh and wait, if you add the FP role and add it as it's failback point even if it can't reach the main one it'll go back to the other one. (But yes if you're using only one server it'll probably have the same issues with the FSP!) But you should be able to see in the logs if it's failing to get it as it could be something as stupid as the SSL cert it uses to access the management portal is expired etc Under locationservices.log it'll show you what MP it's trying to connect to and if it's failing, and then under ClientIDManagerStartup.log it'll show when it's registering the GUID it's using, and you can check this on the MP to see if it's receiving the request under the log. There's so many things it could be that blocks a registration from permissions, a firewall rule, even down to proxy settings if it's not bypassing it when trying to access the HTTPS portal. Steve Edited October 9, 2017 by Steve21
Hunter Posted October 9, 2017 Author Posted October 9, 2017 right will check on the MP this evening inc checking the SSL cert for the auth, will let you guys know tomorrow Have a good evening, H
Steve21 Posted October 9, 2017 Posted October 9, 2017 right will check on the MP this evening inc checking the SSL cert for the auth, will let you guys know tomorrow Have a good evening, H Just a note but if you're gonna check those logs those are both client side not MP side, the SSL is MP. MP side logs would be MP_Registration.log to reference the GUIDs in ClientIDManagerStartup.log Steve
nickbro Posted October 9, 2017 Posted October 9, 2017 Been through the logs, no issues in the locationservices log file, no red or yellow execept for stuff to do with AAD. I've reinstalled the fallback role (remove role, check sitecomp.log for completion then add role), will try a build again. It's odd that using the push client from SSCM it installs fine.
Steve21 Posted October 9, 2017 Posted October 9, 2017 Been through the logs, no issues in the locationservices log file, no red or yellow execept for stuff to do with AAD. I've reinstalled the fallback role (remove role, check sitecomp.log for completion then add role), will try a build again. It's odd that using the push client from SSCM it installs fine. It won't always flag up in the log checker yellow/red if you mean about the mp as it depends how you are deploying it (boundaries vs force etc), does it show it actually finding an mp? On the client push settings are you setting a mp as part of the variables though? As in using something like smssitecode=? Steve
nickbro Posted October 9, 2017 Posted October 9, 2017 Client push just uses SMSSITECODE=CHS. I'm doing a rebuild now, it's at the apply device drivers stage. I couldn't major in that log file, it all looked fairly good actually.
Steve21 Posted October 9, 2017 Posted October 9, 2017 Ah ok so that's fixed to install that.l for the push install One thing I don't know if you did check yet in Contenttransfermanager.log for a "failed base64encode" error as that would stop the cache downloading but that was hotfixed a while ago so shouldn't be an issue if it's only recently upgraded What bit is actually failing now then just the driver installs? Full OS etc works up to then? Steve
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