Asked by:
Client's are not fully functioning after installation

Question
-
Hi All,
After deploying a Windows 7 x64 image, the configuration manager client is installed, but not all options are available. On the general tab, the client certificate value is set to none. On the actions tab not all actions are available. The client is installed with the task sequence. For some reason the certificate won't install. When i push the client again from the SCCM Console, then it will activate again.
In the CertificateMaintenance.log i found this;
<![LOG[Raising pending event:
instance of CCM_ServiceHost_CertRetrieval_Status
{
DateTime = "20121011064740.308000+000";
HRESULT = "0x00000001";
ProcessID = 2868;
ThreadID = 2884;
};
]LOG]!><time="08:47:40.308-120" date="10-11-2012" component="CertificateMaintenance" context="" type="1" thread="2884" file="event.cpp:784">
<![LOG[Raising event:instance of CCM_ServiceHost_CertRetrieval_Status
{
ClientID = "GUID:ee8ea1ea-c13c-44cf-a3a0-03f89866429d";
DateTime = "20121011064754.014000+000";
HRESULT = "0x00000001";
ProcessID = 2868;
ThreadID = 2216;
};
]LOG]!><time="08:47:54.014-120" date="10-11-2012" component="CertificateMaintenance" context="" type="1" thread="2216" file="event.cpp:729">
<![LOG[Client is set to use HTTPS when available. The current state is 480.]LOG]!><time="08:48:00.782-120" date="10-11-2012" component="CertificateMaintenance" context="" type="1" thread="2340" file="ccmutillib.cpp:362">
<![LOG[Client is set to use HTTPS when available. The current state is 480.]LOG]!><time="09:05:49.946-120" date="10-11-2012" component="CertificateMaintenance" context="" type="1" thread="2744" file="ccmutillib.cpp:362">
<![LOG[Client is set to use HTTPS when available. The current state is 480.]LOG]!><time="09:13:04.608-120" date="10-11-2012" component="CertificateMaintenance" context="" type="1" thread="3372" file="ccmutillib.cpp:362">
<![LOG[Client is set to use HTTPS when available. The current state is 480.]LOG]!><time="09:23:01.553-120" date="10-11-2012" component="CertificateMaintenance" context="" type="1" thread="2940" file="ccmutillib.cpp:362">Does somebody know what 'State 480' means? The ccmsetup.log can be found here: http://www.scribd.com/doc/109693514/ And the ccmetup-ccmeval.log can be found here: http://www.scribd.com/doc/109694338
Regards,
Remy
- Edited by Remy K Friday, October 12, 2012 6:09 AM
Thursday, October 11, 2012 9:11 AM
All replies
-
What does ClientIDManagerStartup.log tell?
Any chance that the client is also stuck in provisioning mode? http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspxTorsten Meringer | http://www.mssccmfaq.de
Thursday, October 11, 2012 9:48 AM -
Hi Torsten,
thanks for your reply. When i look in the ClientIDManagerStartup.log i can see;
<![LOG[Skipping SMS_RemoteClient_ClientIdUpdated event since client is in provisioning mode.]LOG]!><time="08:47:53.796-120" date="10-11-2012" component="ClientIDManagerStartup" context="" type="1" thread="2200" file="ccmid.cpp:1046">
So you are right! Now i will investigate what's causing this...
Thursday, October 11, 2012 9:57 AM -
How did you deploy these systems and the client agents?
There was a sporadic issue in 2007 with clients getting stuck in provision mode (IME caused by Cisco VPN client deployment during the TS): http://blogs.technet.com/b/configurationmgr/archive/2010/09/13/solution-after-a-configmgr-2007-osd-task-sequence-completes-the-client-may-not-automatically-pull-down-policy.aspx
Jason | http://blog.configmgrftw.com
Thursday, October 11, 2012 8:56 PM -
These systems are deployed with the OSD task sequence. The client is also deployed with the task sequence.
Yesterday i removed all the software installations from the TS and the client was fully functioning after deployment. There is an application which is causing the problem probably. I'm going to add the software one by one to see which one is causing the problems..
Friday, October 12, 2012 6:08 AM -
Removing and recreating the packages for the task sequence solved my problem. Now the client is properly installed when the OSD task sequence is completed. Still a mystery how this problem was caused?
Friday, October 12, 2012 2:06 PM