xc3ss1v3 Posted September 5, 2014 Report post Posted September 5, 2014 Good afternoon all... I've started noticing on systems where I've run a successful OS deployment via a standalone media, that the SCCM client never seems to function properly after OSD completion. If I open the client, it will have the default appearance with "IT Organization" in the top right. If I look in the management console at the device, it'll state that no client is installed. I've let a system sit over night thinking that SCCM just needed time to sort things out, but this did not appear to ever happen. The way I've been resolving is simply re-installing the client via push from the console. But, I'd obviously like for the client to work coming straight off OSD. As of now, the only installation property I'm specifying is SMSMP=servername.domain.com. Are there any other properties that I might include to help ensure the client is installed and set up properly during OSD? Is there a better property for specifying the management point? Thanks. Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted September 5, 2014 Report post Posted September 5, 2014 this sounds like your osd deployments are actually failing and leaving the client in provisioned mode or you have boundaries incorrectly setup, the way to find out is to start looking for those things, for provisioned mode check the registry as described here 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 and here http://social.technet.microsoft.com/Forums/systemcenter/en-US/5f33afe9-ca61-4a41-a192-fdb08c5cc619/sccm-client-issues-during-task-sequence-issues Quote Share this post Link to post Share on other sites More sharing options...
