Asked by:
Software Installation Using GPO

Question
-
I am using GPO to push SCCM clients (assign to computer), logs looks fine (to me) but the client never got installed despite multiple reboot.
- GPO has been applied (this can be verified by gpresult )
- Appmgmt service is aware of the change ( this can be verified by app management event ID 302/308 etc.)
Below is the content of appmgmt.log, which I have trouble to interpret.
-------------- appmgmt.log begins --------------------
11-21 15:32:35:531
Software installation extension has been called for asynchronous policy refresh
The following policies are to be applied, flags are 1091.
SCCM Client Deployment (unique identifier {5B0DA2C9-994F-4A73-9403-20D02587B7FE})
System volume path = \\domain.com\SysVol\domain.com\Policies\{5B0DA2C9-994F-4A73-9403-20D02587B7FE}\Machine
Active Directory path = LDAP://CN=Machine,.....
Set the Active Directory path to LDAP://CN=Class Store,CN=Machine,....;.
Policy has not changed. Only assigned applications will be advertised.
Enumerating the managed applications which are currently applied to this user.
The following 1 managed applications are currently applied to this user.
ConfigMgr Client Setup Bootstrap from policy SCCM Client Deployment with state 509 and assign count 1.
Found assigned application ConfigMgr Client Setup Bootstrap from policy SCCM Client Deployment in the registry.
Found 1 applications locally that are not included in the set of applications from the Active Directory.
Software installation extension returning with final error code 0.------------------ appmgmt.log ends ------------------------------
- Moved by pbbergs [MSFT] Monday, November 25, 2013 12:46 PM
Friday, November 22, 2013 2:26 PM
All replies
-
Hi,
The issue is related to SCCM, you can ask for help from System Center Configuration Manager forums.
http://social.technet.microsoft.com/Forums/systemcenter/en-US/home?category=configurationmanager
Regards,
- Edited by Mandy Ye Monday, November 25, 2013 8:47 AM
Monday, November 25, 2013 8:47 AM -
Have your verified whether Group Policy has actually initiated the client install? From the above, it doesn't look like it has which means this is not a ConfigMgr issue but is instead a group policy issue.
To easily verify whether the client setup has started/been initiated, check c:\Windows\ccmsetup and/or c:Windows\ccm.
Jason | http://blog.configmgrftw.com
Tuesday, November 26, 2013 4:08 PM -
Sorry for not responding sooner. Yes the GPO is and has always been working. I purposedly added another app into same GPO and it got installed successfully on all types of clients. I am not an SCCM guy - I support the group policy only - but I am pretty confident that our SCCM folks need to figure out a proper switches for ccmsetup to make this to work. If anyone can give advices on this aspect, that'd be great.Thursday, December 12, 2013 3:03 PM
-
What about verifying the setup logs on the client to verify what actually has happened (as suggested above)?
Jason | http://blog.configmgrftw.com
- Edited by Jason Sandys [MSFT]MVP Thursday, December 12, 2013 3:06 PM
Thursday, December 12, 2013 3:06 PM