nickbro Posted October 9, 2017 Posted October 9, 2017 Freshrebuild, location services, 4th line Assigning to site 'CHS' Further down it says: Retrieved lookup MP(s) from AD Still hangs on Installing Applications, no MSIexec signs of life
nickbro Posted October 9, 2017 Posted October 9, 2017 ContrentTranaferManager CcmGetDPAuthToken failed errors. 0x80004005. It looks like it's even trying to use branchcache which I thought I'd disabled.
nickbro Posted October 9, 2017 Posted October 9, 2017 Got Error signing client message as well in clientauth
Steve21 Posted October 9, 2017 Posted October 9, 2017 If it's error on signing do you have it set to use HTTP or HTTPS under the MP/DP point General settings Steve
nickbro Posted October 9, 2017 Posted October 9, 2017 Only HTTP. We do have a CA but it's only for wifi
nickbro Posted October 10, 2017 Posted October 10, 2017 Right, no joy at all. How can I get the management point to be auto discovered again? I've removed and added the roll but that hasn't fixed it. Can only install the client via SCCM push it seems.
Hunter Posted October 13, 2017 Author Posted October 13, 2017 Hi guys have been poking around a little and have come up with this issue now, Couldn't find an MP source through AD. Error 0x80004005 ccmsetup 10/10/2017 16:24:34 20624 (0x5090) Current directory '\\ah-cj\admin$\ccmsetup' is not a valid source location. ccmsetup 10/10/2017 16:24:34 20624 (0x5090) No valid source or MP locations ccmsetup 10/10/2017 16:24:34 20624 (0x5090) [5.00.8540.1007] Params to send '5.0.8540.1006 Deployment "\\ah-cj\admin$\ccmsetup\ccmsetup.exe" ' ccmsetup 10/10/2017 16:24:34 20624 (0x5090) ccmsetup 10/10/2017 16:24:34 20624 (0x5090) Raised pending client deployment state message. ccmsetup 10/10/2017 16:24:34 20624 (0x5090) CcmSetup failed with error code 0x80004005 ccmsetup 10/10/2017 16:24:35 20624 (0x5090) issues with management point contacting active directory? and no valid management source?
Steve21 Posted October 13, 2017 Posted October 13, 2017 (edited) Hi Hunter, That's back to my original email where I was asking about boundaries unless you're specifying the MP during the install variables. If it's not finding the sources either is that a valid path you're trying to use? \\ah-cj\admin$\ccmsetup <- As I thought your server was named the syscent one? (Or was that the client name?) Steve Edited October 13, 2017 by Steve21
Hunter Posted October 13, 2017 Author Posted October 13, 2017 our server is named Syscent-01, I have asked about the boundaries and I am assured that they are correct?
Steve21 Posted October 13, 2017 Posted October 13, 2017 If you copy the setup folder locally on a machine, and force an install locally (command line). ccmsetup.exe SMSSITECODE=CHS SMSMP=cri-syscent-01.crick.internal /mp:cri-syscent-01.crick.internal /ForceInstall Assuming you are using CHS as you said previously as the site code, and run it what happens? (Might be able to try it without the /mp if needed but see if that runs first) Steve
Hunter Posted October 13, 2017 Author Posted October 13, 2017 Running this installs the client correctly, after the corrupt one is uninstalled ccmsetup.exe SMSSITECODE=CHS
Hunter Posted October 13, 2017 Author Posted October 13, 2017 (edited) Newsccmlog.txtHi Steve Previous post was Nick, I have done as you suggested and have a log of what currently is going on. It seems to be working if not slowly. Will be heading down to D&T to cut out some students project now, will be back at 15:30. takecare H Edited October 13, 2017 by Hunter
Steve21 Posted October 13, 2017 Posted October 13, 2017 (edited) If that manual one works basically it's got to be down a few things really :s Either you have firewall issues if it can't connect back (client wise), and running it as admin is raising permissions to allow it to add it. The network account you're using to push the clients doesn't have the right permissions to read what it needs to via the SMS Site shares etc. I take it the push install account has high enough access to get everything? The boundary is incorrect so it can't find said machine, or you aren't pushing a specific site down as part of the installer and AD isn't configured for the schema to allow it to find it. From a broken machine (Not the test one if you did install that fine as it might have changed firewall settings etc) - Do these two load? http://cri-syscent-01/sms_mp/.sms_aut?mplist http://cri-syscent-01/sms_mp/.sms_aut?mpcert Firewall wise are these able to connect to SCCM server- 80,8530,443,8531,445,135 As the logged on user that you're using for push installs can you access \\cri-syscent-01/SMS_CHS shares etc (or whatever yours is named) Also on a side point, I noticed in your other log your AD isn't returning a line either. Did you configure AD with the extended properties or aren't you normally using that? On a DC open adsiedit.msc go into the domain->system->system management and let me know what's in that please (Also whether your SCCM server has permissions on that "folder") Steve Edited October 13, 2017 by Steve21
nickbro Posted October 13, 2017 Posted October 13, 2017 Hi @Steve21, I'm still struggeling to figure out why it would of just stopped working. Apart from installing the 1706 update we hadn't changed anything. Screenshot of those pages, which load Firewall on the server is off while we try and resolve this issue. The user account we are using is the Domain Administrator account (bad I know but wanted to rule out that issue). Configure AD? Where do I go for that? Screenshot from ADSI This is our boundary settings, AD setting and DHCP scope. Note that DHCP only leases from 185.0, 184.0 is for static/reservation based devices.
Steve21 Posted October 13, 2017 Posted October 13, 2017 (edited) Hi Nick, I don't know if you checked it before when I mentioned it, but did you check that you're not on the bugged version of 1706? Could be a lot of hassle for nothing if so The first few days of the release (Aug 8th~) there were some major issues, and they released a hotfix which should show up in the servicing menu. Edit - Wrong versioning, Previous to 5.00.8540.1601 (Think it was 1300?) is the bugged version of 1706, 5.00.8540.1601 was the replacement. That's console versioning, not client/site. Will read through the screenies in a min once home Steve Edited October 13, 2017 by Steve21
nickbro Posted October 13, 2017 Posted October 13, 2017 We didn't install the update until the end of September
nickbro Posted October 13, 2017 Posted October 13, 2017 Woohoo fixed it. Re-published system centre in AD and it's working again now. YIPPEE!!!!
Steve21 Posted October 13, 2017 Posted October 13, 2017 Woop woop If you check in ADSI is it showing your boundaries in AD now too? You did have an IP range one right? STeve
nickbro Posted October 13, 2017 Posted October 13, 2017 Doesn't seem to be anything new in ADSI, but it's working so I'm not going to worry. Yep had all the boundaries in, only unpublished and republished the ad settings. We can actually start fixing the laptops now without taking 2 days.
Hunter Posted October 17, 2017 Author Posted October 17, 2017 Still not working, client failing to register. Unsure why.
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