Aurock

Thanks

SCCM 2012 SP1 beta, and MDT 2012 update 1, (6.1.2373.0)

I went through this guide yesterday, but when i'm checking on things in the SCCM console today I see that the deployment package for endpoint definitions is showing an error. Looking in the distmgr.log, I see it repeating the same error over and over: Snapshot processing content with ID 16804470 ... SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) The source directory \\configmgr\sources$\WSUS\Updates\EndpointProtection\61109c4d-e497-4eb2-9ff4-69bd5e735b01 doesn't exist or the SMS service cannot access it, Win32 last error = 2 SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) STATMSG: ID=2306 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=configmgr.domain.com SITE=001 PID=6688 TID=9664 GMTDATE=Wed Nov 14 16:57:02.734 2012 ISTR0="\\configmgr\sources$\WSUS\Updates\EndpointProtection\61109c4d-e497-4eb2-9ff4-69bd5e735b01" ISTR1="0010001F" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="0010001F" SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) Failed to take snapshot of one or more contents in package 0010001F SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) CDistributionSrcSQL::UpdateAvailableVersion PackageID=0010001F, Version=3, Status=2302 SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=configmgr.domain.com SITE=001 PID=6688 TID=9664 GMTDATE=Wed Nov 14 16:57:02.756 2012 ISTR0="Endpoint Protection Defenitions" ISTR1="0010001F" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="0010001F" SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) Failed to process package 0010001F after 26 retries, will retry 74 more times SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:02 AM 9664 (0x25C0) Used 0 out of 3 allowed processing threads. SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:07 AM 3388 (0x0D3C) The last source update time for pkg 00100008 is 11/13/2012 5:37:24 PM Central Standard Time SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:07 AM 3388 (0x0D3C) The next start time for pkg 00100008 is 11/14/2012 5:37:00 PM Central Standard Time SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:07 AM 3388 (0x0D3C) Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 11/14/2012 10:57:07 AM 3388 (0x0D3C) Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 11/14/2012 11:03:33 AM 8992 (0x2320) I have confirmed that the path it's complaining about actually doesn't exist. There are lots of other folders in that path, but there is no folder named 61109c4d-e497-4eb2-9ff4-69bd5e735b01 What did I do wrong?

With MDT integration enabled, the task sequence looks a bit different. The enable bitlocker step, in particular, doesn't offer the same options. If I create an MDT task sequence, does the pre-provisioning still work the same? Do I just need to pre-set variables for the bitlocker settings, such as BDEInstall, BDEPin, BDERecoveryKey, BDEKeyLocation, etc?

Thanks. So should I bring over the branches of customsettings.ini that I had in MDT, using that to skip bitlocker on desktops and enable it on laptops? I don't mind staying with what works, but I don't want to force SCCM to work the way I used MDT if SCCM has a better way to deal with the same problems.

We recently purchased system center 2012 and plan to put it into production once SP1 is final. However, we couldn't get management licenses for all of our systems at the time, so initially we had planned to only use system center to manage our servers and a small test group of clients. Is it possible to have other clients that aren't managed by SCCM still point to the SCCM server to get their updates, or will I have to maintain a seperate wsus server for those computers until we get everything under management by SC?

I've been using MDT for a few years now, up to and including MDT 2012 update 1. Now we've purchased SC2012, and I'm trying to rebuild the deployment setup in SCCM to do the same things I did before in MDT. It looks like there are several areas where things might work in a different way. Rather than trying to manually recreate the exact steps I had in MDT, I wanted to check first to see if there's a better way to accomplish the same goals in SCCM. The question of the moment is regarding bitlocker. In MDT, I had set customsettings.ini up with different sections for laptops and desktops, and depending on the IsLaptop variable, it would jump to whichever was appropriate. For laptops, I enabled bitlocker. For Desktops, I didn't. I created a new mdt task sequence in SCCM (sp1 beta), and I see that it has steps included for pre-provisioning bitlocker and enabling bitlocker, both are conditional on the existence of an OSDBitlockerMode variable. I don't know how that variable is set, but I'd like the same setup I had with MDT, such that bitlocker is only enabled on laptops. What's the best way to do this?

I've run into this exact same issue. Did you ever find a resoultion? I've tried using AD Users & Computers from the WDS server, from a DC, from a windows 7 box, none of them give me an option to move beyond that first screen and add more info.