Link to home
Start Free TrialLog in
Avatar of ejefferson213
ejefferson213

asked on

Software installation of SCCM client

Trying to install the SCCM client on a freshly built Windows 7 machine which was placed in its own OU (to control the rollout of the client).  

GPRESULT is showing that the policy is applied but the software hasn’t been installed and the following events are in the event log:
•      Event 102 – installation of application …. has failed.  Error was 1612
•      Event 1112 – Group policy client side extension software installation was unable to apply one or more settings because the changes must be processed before system startup or user logon

The script was set up for assignment to the computer and the directory is seen on the workstation with Everyone having read/write permission.  I’ve setup synchronization processing and adjusted the wait time as described in various documents:

        Software Installations
        ----------------------
            GPO: Windows7SCCMClientInstall
                Name:             ConfigMgr Client Setup Bootstrap
                Version:          5.0
                Deployment State: Assigned
                Source:           \\sccm-cas\sms_100\bin\i386\ccmsetup.msi
                AutoInstall:      True
                Origin:           Applied Application
           
          GPO: Windows7SCCMClientInstall
                KeyName:     Software\Policies\Microsoft\Windows\System\GpNetworkStartTimeoutPolicyValue
                Value:       120, 0, 0, 0
                State:       Enabled

            GPO: Windows7SCCMClientInstall
                KeyName:     Software\Policies\Microsoft\Windows NT\CurrentVersion\Winlogon\SyncForegroundPolicy
                Value:       1, 0, 0, 0
                State:       Enabled

However, the software doesn't get installed.  I followed another article for changing the registry to get a log produced but the file doesn’t appear.  What am I doing wrong or where else can I look?

Thank you!
Avatar of Mike Taylor
Mike Taylor
Flag of United Kingdom of Great Britain and Northern Ireland image

Hi,

I doubt anyone can tell you why it's not working yet because you have not detailed the policy, or mentioned errors in any log files from gpresult or errors in rsop.

If you look at this they have a reasonable walkthrough of each method:
http://mycomputerlessons.com/sccm-client-top-3-methods-to-install-configmgr-2012-client/

(Just curious but why are you using GPO anyway? Most people/companies use client push. It's much simpler and easier normally.)

If your existing steps are the same as above, then you need to help troubleshooting the GPO by uploading logs.

Mike
Avatar of ejefferson213
ejefferson213

ASKER

Forgive me for not putting in enough information.  The event log entries I'm getting are:

The install of application ConfigMgr Client Setup Bootstrap from policy Windows7SCCMClientInstall failed.  The error was : %%1612

and

The Group Policy Client Side Extension Software Installation was unable to apply one or more settings because the changes must be processed before system startup or user logon. The system will wait for Group Policy processing to finish completely before the next startup or logon for this user, and this may result in slow startup and boot performance.

I chose to use GPO because, based on the different methods, it seemed the easiest to use.  However, I succumbed to your idea and did a client push.  I'm now looking the results over to see how it went.  I'd really like to get the GPO option fixed but I've run out of ideas. I looked at and did as the article said and the eventvwr says it was installed but there's no evidence of it anywhere.  No process, no service; even SCCM thinks there's no client software on the machine.  So I'll keep messing with it until I find a solution or rebuild it from scratch.
Hi,

1612 is just a generic MSI error code so doesn't help. It sounds like there are multiple GPOs applying and they are having a bit of a fight. It's hard to say what without running gpresult /full.

Some places use a mix of GPO + client push, just to get full coverage, as a kind of belt and braces approach. If one fails the other can install instead.

Is this just one machine or more? Your last sentence suggests just one.
For now, it's one machine being used to pave the way for upgrading Windows 7 to Windows 10.  Haven't gotten off to a good start.....  I'm going through the log on the client to see what's up because the SCCM server doesn't recognize that a client is on the machine.
ahhh. Reasons can be 1) certificate is wrong so machine is not trusted and won't talk to MP
2) wrong boundary
3) client seen but not enabled (in the console) - just right-click and enable it
4) no discovery is happening so new machines/clients don't appear
5) discovery is looking at wrong OU "   "
6) client in provisioning mode so is "stuck" in limbo
Thanks so much for your help!

To your points, we're not using certificates; there's only one server and boundary.  The site server sees the machine so the OU discovery is working fine but I don't see the "enable" button you were referring to.  

Looking through the client log, I see this error message:

<![LOG[File 'C:\Windows\ccmsetup\SCEPInstall.exe' with hash 'AC332171CF5034A9BDF65B787AECAB6A0FD141A8B75DABCD7EBED7B0EE23B372' from manifest doesn't match with the file hash '13CD2A30B91048F71720919953C058A67747E14BF51367667BF042274D9FA43C']LOG]!><time="12:15:02.305+300" date="01-10-2017" component="ccmsetup" context="" type="2" thread="2960" file="util.cpp:2695">

And searching on this, it was suggested to "grab the file from another site".  Well, we don't have another site so I renamed the directory on the intended client and will attempt to do another install from the site server.    Stay tuned.....

Maybe it got confused when I first attempted to do this via a GPO (which failed and then seemed to work (at least according to the event log)) and then did as you suggested and tried doing a client push.
"we're not using certificates" - You are: ALL CM clients install a certificate. That is how CM works and ensures that the client is to be trusted.

SCEPInstall is the installer for Endpoint Protection. That is a separate component of CM, and not part of the standard agent install (the file is there but is NOT used). The error is easy: the hash (a mathematical checksum that compares what the source IS to what is downloaded local) are identical. You just need to re-distribute (Update source) to fix that. Don't grab files from other places. You can't believe *everything* you read on the Internet!

Mike

PS: Deploying Endpoint protection is not very common and needs planning so if you are not intending to use it, you can ignore it, but you MUST update the package "Configuration Manager Client Package" using Update Distribution Points.
Wish I could just spend quality time on this and knock it out but, and I'm sure you're familiar with this, I'm pulled in lots of directions.

Thanks for the "training"!  I'll take your suggestion and reload the client installation software (once I go back and figure out how I did that).  Stay tuned... (and thanks again!!)
I am very familiar with the fickleness of others. I once had an in-tray and labelled it: very urgent, very, very urgent and very, very, very urgent. I was off for 2 days and the guy who stood in for me suddenly understood why.
When you say "re-distribute (Update source)", how is that done?  I went into SCCM, software library/packages and did a "Create package from definition" and pointed to the shared client folder on my server.  It created another Client Upgrade Package which I deployed.  Is this the proper sequence?
ASKER CERTIFIED SOLUTION
Avatar of Mike Taylor
Mike Taylor
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'm sure there's a light at the end of this tunnel.  Thanks again for your help.

I deleted the packages, added the source version column you suggested, recreated the package and deployed it.  After waiting 5 minutes and seeing nothing (watching task manager on client PC), I simply highlighted the single PC whose in the desired collection and selected Install Client.  It did attempt the install but it still gives me the same hash errors.  Should I simply attempt to reload the files from the DVD?  Sorry to belabor this....  The CCMSetup log says:

<![LOG[File 'C:\Windows\ccmsetup\vc50727_x64.exe' with hash '0551A61C85B718E1FA015B0C3E3F4C4EEA0637055536C00E7969286B4FA663E0' from manifest doesn't match with the file hash '9ADDD703E50B6A0D48C8FF625278CEE3BD7D86874A36AD6589DE9688C086522D']LOG]!><time="13:07:48.665+300" date="01-17-2017" component="ccmsetup" context="" type="2" thread="2024" file="util.cpp:2695">

And it says that for all the files being downloaded.
On a hunch, I renamed the CCMSETUP directory on the client thinking that perhaps the process wasn't reloading the files and sure enough, the new directory was created and the install went forward.  Thanks so much for your help!!!!
Glad you got it sorted. Sometimes the client does odd things (1 in 1000) and you just have to file it under "life" :).