Aurock

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.