Sam_Brown Posted June 21, 2013 Posted June 21, 2013 Evening All, Two issues I've been having and hoping for some sort of help! 1) I can deploy Windows 7 using SCCM. It will install the drivers. Join the domain and also install the Config Manager Client however once the computer has finished building, despite the fact it has the client installed it's not showing up in SCCM as having the client installed and it can't communicate with the server. Is there something extra I need to do during the TS to enable it to connect and talk to the SCCM Server? 2) I have created an Office 2010 Application and placed in in the TS at the end to be installed however it never happens! Is there some sort of special way I need to add applications to enable them to be installed during OSD? I'm sure these questions are fairly basic but I'm having a bit of trouble with them. Hope someone can help!
adamf Posted June 21, 2013 Posted June 21, 2013 In both situations it would be useful to have a look at the SMSTS.log file. Can you post it?
Gatt Posted June 22, 2013 Posted June 22, 2013 1) Make sure the Package "Configuration Manager Client Package" is distributed to your Distribution Point(s) and is part of your TS sequence 2) If this is part of your TS above, then it wont deploy if 1) isn't completing Also, for 2) check the "General Information" tab - about half way down there is a check box for "Allow this application to be installed for the Install Application task sequence action without being deployed" - Not sure if its actually needed - but worth ticking anyway! But check 1) is working first - this is crucial! As already asked - we need your SMSTSLog.log file to look why is failing..
Sam_Brown Posted June 24, 2013 Author Posted June 24, 2013 Ok... just performed a rebuild. Configuration Manager is showing up under Control Panel however it only has 6 tabs and is missing the "Configurations" tab. Under General it doesn't have any sort of information regarding the site code, certificate or management point! There errors I have are as follows... "unable to read SMS client cert from environment" Not restoring SMS client cert" "Non Fatal error 0x80070057" in sending task sequence execution message to MP" Failed to install SMS Client 0x80004005 "401 Authentication failure on request with anonymous access" "Failed to open \microsoft\sms\mobile client\registry ket" The client did not get checked for RWH OpLock Type? Any ideas?
Gatt Posted June 24, 2013 Posted June 24, 2013 (edited) Not sure offhand and can't have a decent look at the moment. But it looks like a permissions issue given the 8004005 error that's causing the client to not fully install into WMI and the registry. Will try gave a proper look tomorrow (3rd edit - Damn tablet!!) Edited June 24, 2013 by Gatt
Sam_Brown Posted June 24, 2013 Author Posted June 24, 2013 Someone has advised I might want to create a custom ConfigMgr Client Package. I might give this ago.
Gatt Posted June 24, 2013 Posted June 24, 2013 I just edited the default one. Though this will have no effect until your agent is installed correctly. You need to look at sorting the permissions problem first.
Gatt Posted June 25, 2013 Posted June 25, 2013 Had a look and it sounds familiar to an issue I had when I reinstalled SCCM In your ccmsetup.log do you have a line similar to: [color=#000000][font=Verdana]Couldn't verify 'C:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi' authenticode signature. Return code 0x800b0101 If so, there is a known bug in SP1 about this and a hotfix was released to resolve it [/font][/color]Installation error 0x800b0101: System Center 2012 Configuration Manager Service Pack 1 client
Sam_Brown Posted July 1, 2013 Author Posted July 1, 2013 Still no luck and the above didn't help unfortunately. Also if it helps when I try and manually assign it to a site in Control Panel I get "Configuration Manager did not find a site to manage this client". Bah.
Sam_Brown Posted July 1, 2013 Author Posted July 1, 2013 Interesting... when deploying an image created using Build and Capture it fails as above. I have just deployed a Task Sequence using the install.wim straight from the DVD and it seems to have gotten further. The client can see the site code and has a UID for SCCM now. There don't seem to be as many options under the "actions" tab however as there were on computers already built where the Client was pushed out to. :/
Gatt Posted July 1, 2013 Posted July 1, 2013 I've had this - sometimes it takes a while to pull stuff down. Ont he odd occasion I've ran the ccmrepair.exe file on the %WINDIR%\CCM folder
Sam_Brown Posted July 1, 2013 Author Posted July 1, 2013 Just remoted onto the laptop now and can see it's got all the options. Seems like it's pulled down the client settings since the client first went on. Good times. Still unsure why the client wouldn't work when using the Build and Capture generated image. Something about not liking the fact it had the client instead in the image?
nbxviet Posted October 6, 2016 Posted October 6, 2016 Hello Mr Sam_Brown, i have a problem with same your problem you fixed it, are you? Would you like to tell me how to fix it
Sam_Brown Posted October 7, 2016 Author Posted October 7, 2016 Hello Mr Sam_Brown, i have a problem with same your problem you fixed it, are you? Would you like to tell me how to fix it This was a long time ago! I believe that the fix was making sure the SCCM Client wasn't a part of the image.
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