In a native mode site, after an OSD task sequence is finished, the
ConfigMgr client cannot get policy.  After significant review of logs, I
determined it is because the certificate from the local PKI does not get
installed prior to the ConfigMgr client install.  It seems that after
waiting 10-20 minutes following the task sequence completion, then the
client starts working.

Is this to be expected? Has anyone seen this and determined a way to get
the certificate installed in Windows without waiting for group policy
autoenrollment and then a subsequent policy retrieval by the ConfigMgr
client?

Thanks,

Jeff


Reply via email to