bajeezus

If anyone's interested, I got my stuck "waiting for prestage content" to clear by using a CA certificate instead of the self-signed cert. I guess if you're running an https MP and an http prestage DP, you need to have that certificate. My other DPs that are not prestage do not have this problem and a self signed cert works just fine.

Hoping someone here have seen this. I have a couple of prestaged distribution points where I have manually extracted the content to but when looking at the DP status it still shows as "waiting for prestaged content." One DP I extracted the contents a couple weeks ago and the other from last week. I re-extracted both today using a /F switch and did a content validation but i'm still seeing the same thing in the status. Based on the PrestageContent.log, I suspect this may be the cause but i'm not sure how to resolve: Management point name is not defined PrestageContent 7/9/2013 7:18:56 AM 4352 (0x1100) Site Code: 'IS1' PrestageContent 7/9/2013 7:18:56 AM 4352 (0x1100) DP server: 'server1.my.domain' PrestageContent 7/9/2013 7:18:56 AM 4352 (0x1100) NAL Path: '["Display=\\server1.my.domain\"]MSWNET:["SMS_SITE=SI1"]\\server1.my.domain\' PrestageContent 7/9/2013 7:18:56 AM 4352 (0x1100) some DP settings are not defined. PrestageContent 7/9/2013 7:18:56 AM 4352 (0x1100) Failed to send package state messages to site server from remote DP. PrestageContent 7/9/2013 7:18:56 AM 4352 (0x1100) Don't see anything unusual in the Component Status for these two servers. They appear to be communicating with the MP just fine (besides this). I don't see anything in the distmgr about these two servers. Haven't tried re-installing the DP since it's quite a coincidence that two servers would exhibit the same issue. One server is actually a RODC so I used an account to install the DP services and the other is a straight up 2008 r2 server with the MP server added to it's local admin group. Finally, these two servers are the first prestaged DPs in my environment. I have 42 distribution points and the others are just working fine. SCCM 2012 SP1 DPs are Win2k8 R2 sp1 Any input would be greatly appreciated!

Bummer. Thanks..

Anybody know if it's possible to include Office 2010 updates as part of the OS Scheduled Updates? I have a fat image with Office installed and i'm looking to reduce deployment time by cutting down on the software updates during the deployment sequence (also be quicker than having to go through my Build and Image that takes around 6 hours or so).

Is it possible to create a device collection that would query the MDT tattooed registry for only machines that were deployed through SCCM (DeploymentMethod property)? I need to be able to segregate machines that were deployed via SCCM over ones that just got the client pushed out to them. Or if there are any other thoughts as to how to accomplish the result without using the tattoo, i'd like to hear them out as well.. Thanks!

Got it resolved. Looks like one of the free viewer apps from Autodesk was causing the issue. After re-creating the deployment type for Freedom Viewer 2013, the capture sequence is now working.

Hoping someone here has seen this error # before. Platform: SCCM 2012, No CAS, 1 PRI, 1 MP (https) several DPs (http) Scenario: Running a Config Manger 2012, MDT 2012 Integrated, Image and Capture task sequence and everything goes through fine until the Capture Group section, specifically in the "Prepare ConfigMgr Client" step. I get messages logged in the smsts.log and then the whole thing bombs: SMSTS.LOG Start to cleanup TS policy PrepareSMSClient 7/5/2012 2:32:43 PM 2284 (0x08EC) Launching command shell. OSDSetupHook 7/5/2012 2:33:20 PM 1664 (0x0680) executing command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 7/5/2012 2:33:20 PM 1664 (0x0680) executed command: C:\WINDOWS\system32\cmd.exe /k OSDSetupHook 7/5/2012 2:33:20 PM 1664 (0x0680) getPointer()->ExecQuery( BString(L"WQL"), BString(pszQuery), lFlags, pContext, ppEnum ), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\core\ccmcore\wminamespace.cpp,389) PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) ns.Query(sQuery, &spEnum), HRESULT=ffffffff (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,2800) PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) Wmi query 'select * from CCM_Policy where PolicySource = 'CcmTaskSequence'' failed, hr=0xffffffff PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) End TS policy cleanup PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) TS::Utility::CleanupPolicyEx(false), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\preparesmsclient.cpp,457) PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) Failed to delete policies compiled by TaskSequence (0xffffffff) PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) Failed to prepare SMS Client for capture, hr=ffffffff PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) pCmd->Execute(), HRESULT=ffffffff (e:\nts_sccm_release\sms\client\osdeployment\preparesmsclient\main.cpp,136) PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) Failed to prepare SMS Client for capture, hr=ffffffff PrepareSMSClient 7/5/2012 2:37:52 PM 2284 (0x08EC) Process completed with exit code 4294967295 TSManager 7/5/2012 2:37:52 PM 1700 (0x06A4) !--------------------------------------------------------------------------------------------! TSManager 7/5/2012 2:37:52 PM 1700 (0x06A4) Failed to run the action: Prepare ConfigMgr Client. Unknown error (Error: FFFFFFFF; Source: Unknown) TSManager 7/5/2012 2:37:52 PM 1700 (0x06A4) Weird thing is this is a thick image i'm building which includes around 20 applications. If I leave one application out then the capture sequence completes successfully. Is there a limitation as to how many applications can be installed in a task sequence? I know in the Application Installation step you can only have 9 but overall is there a max #?