Daniel, Thank you! I checked the registry and the client is indeed in provisioning mode. We are installing Windows Updates using the ztiWindowsUpdate script from MDT and the task sequence has a reboot step after the apply updates step. The timeout for the reboot was 1 second.
I adjusted the time out to be much longer than one second and will try the TS again to see if that makes a difference. Thanks again for the assistance. Jeff On Wed, Feb 19, 2014 at 9:54 AM, Daniel Ratliff <[email protected]> wrote: > Some more details. > > > > > https://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 > > > > > http://blogs.technet.com/b/configurationmgr/archive/2012/10/23/support-tip-configmgr-2012-client-goes-to-provisioning-mode-after-running-the-ccmeval-task.aspx > > > > *Daniel Ratliff* > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > *Sent:* Wednesday, February 19, 2014 10:50 AM > *To:* [email protected] > *Subject:* RE: [mssms] CM12 Client Issues after OSD > > > > Have you checked provisioning mode? > > > > *Daniel Ratliff* > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jeff Poling > *Sent:* Wednesday, February 19, 2014 10:38 AM > *To:* [email protected] > *Subject:* [mssms] CM12 Client Issues after OSD > > > > On one particular PC, after an OSD, the ConfigMgr client does not function > properly. The control panel applet is there but only shows four actions. > On Components, almost all the items show as Installed and not enabled. > > > > I've tried repairing the client with ccmrepair.exe to no avail. I tried > pushing the client and forcing a reinstall - also did not help. All of the > normal logs are clean - ccmsetup.log shows no errors with installation, > clientlocation.log shows no errors, locationservices.log shows no errors. > The only error I am seeing that could possibly relate is in CAS.log: > > > > "GetLogonUserSid failed at GetTokenSids 0x800703f0" > > > > A lookup on that error shows that it means: "An attempt was made to > reference a token that does not exist." > > > > Since this is an existing PC, I also tried deleting the object from > ConfigMgr and deleting the computer object from AD. No luck there either. > > > > I validated that the IP of the client is in an AD site and that a boundary > exists in a boundary group. > > > > I've tried multiple iterations and just cannot get this working. Has > anyone seen this before? > > > > Thanks, > > > > Jeff > > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information. > >
