Windows 7 installs on D Drive
Hi, I have created a W7 enterprise x86 Reference build using WAIK, since I need to have the build time as short as possible and I also need to have Microsoft Forefront Client Security in the build (and not connected to the network since this causes a problem with the mom element of FCS). The reference build contains two partitions, one system (which has no drive letter and is hidden, and one for the operating system (which is how the OS would be created if you insert the W7 CD and do a manual setup) I followed the following article which I thought would install the OS to the C: drive but it still places it on the D: drive 1. Create 2 Partitions under Partition Disk 0 Step: 1st Partition for BitLocker Partition Name: BDE Partition Type: Primary Use specific size: 300 MB Check Make this the boot partition File system: NTFS (Quick Format) Variable: BDEPART 2nd Partition for Operating System Partition Name: OS Partition Type: Primary Use a percentage of remaining free space: 100% File system: NTFS (Quick Format) Variable: OSPART 2. Apply Operating System Step: Select the location where you want to apply this operating system Destination: Logical drive letter stored in a variable Variable Name: OSPART Could someone please tell me how they have created a W7 reference build which has two partitions and have successfully install the OS on the C: drive. I would then be able to run the bitlocker task to the C: drive. Thank you.
July 5th, 2010 7:03pm

are you using the install media of Windows 7 in ConfigMgr to do this ? if so use build and capture instead , if not explain how you are creating and then deploying the image My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2010 7:17pm

To add to Niall's answer, this is a known behavior of using the install.wim from the Vista/7/2008/2008 R2 DVD/media. It is a best practice to re-capture a full installation of Windows and then use the re-captured image for your deployment tasks. It is also a best practice to use a build and capture task sequence to perform this re-capture.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
July 5th, 2010 8:54pm

Hi, I am using WAIK and WSIM to create the reference build, and then I capture the build to wim from winpe disk and import into sccm. Then run the client task sequence in sccm to deploy the image. The deployment comes up straight away saying it is installing to D:\, even though the image contains one hidden drive for system utilities and one C: drive for the OS. It must be possible to tell the task sequence to deploy to the OS partition (I thought the process above would do this using variables). I am using WAIK and WSIM since I have read many articles on this and it seems the best way to go to automate the reference build which has office 2010 and antivirus contained in the image rather than installed as software installs. Also installing office 2010 this way would take an age) On a side note is it possible to install Widows 7 enterprise just using one partition i.e. the OS partition and then perhaps create the system utility later on in sccm using dispart or the bitlocker partition tool? Thanks.
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2010 11:56am

ok then, so why do it that way ? as Jason has said it is best practise to use a Build and Capture task sequence to recapture your image, you can apply any changes made to unattend.xml that you did in WSIM later using a separate deploy task sequence which can be used to deploy the captured image as regards your side note, yes it's perfectly possible particularly if you use a build and capture task sequence in the first place, cheers niall My step by step SCCM Guides I'm on Twitter > ncbrady
July 6th, 2010 12:43pm

Is it actually showing up as D: when it's completed? or just during the apply image step? (in which winpe probably sees it as D:) MCTS: ConfigMgr, MDT http://myitforum.com/cs2/blogs/cnackers/default.aspx
Free Windows Admin Tool Kit Click here and download it now
July 6th, 2010 6:56pm

Hi, It actually installs to the D: drive and finishes up on the D: drive which then fails later on when trying to complete the sccm client install. I have done what Jason and Niall says and used a build and capture sequence which I'm quite impressed with. This just gets around the problem by only creating one partition i.e. the C: drive. Thanks.
July 9th, 2010 11:12am

Hi, It actually installs to the D: drive and finishes up on the D: drive which then fails later on when trying to complete the sccm client install. I have done what Jason and Niall says and used a build and capture sequence which I'm quite impressed with. This just gets around the problem by only creating one partition i.e. the C: drive. Thanks. It was never intended for people to just deploy the install.wim :) so it's a best practice to just do a build/capture and then deploy that... Glad it's working out for you.. MCTS: ConfigMgr, MDT / http://myitforum.com/cs2/blogs/cnackers/default.aspx
Free Windows Admin Tool Kit Click here and download it now
July 9th, 2010 7:30pm

I can appreciate this but simply do not understand it. Why would the Install.wim install to D: rather than C: and everyone just accepts this and shrugs their shoulders? What is the intended purpose of the install.wim if not to make it just a little easier on a over burdened technician who now has to capture and build an image. One of the very reasons I was sold on this by the rep from Microsoft was that I could just use the Install.wim directly from them to create my task sequences quickly. This does sound like something that could be easily remedied from Microsoft.
January 7th, 2011 5:00pm

Whys are questions for the product group(s) involved. Stand-alone MDT works around this issue because it always does a full install. From my perspective, the intention is to force you to use the best practice but I don't know if that's the real answer or not. Build and Captures do not add much to the process and actually, if done correctly, save you loads of time in the long run. The best part is that a build and capture is nearly identical to a deploy so you really don't have to learn anything new.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2011 5:17pm

Now I am starting to understand why my son uses a MAC. I guess I am uncertain why people accept this level of service from Microsoft. I can appreciate using best practices but why you have someone sell you this as a time saving feature only to discover it actually doesnt work properly and everyone just accepts it is beyond me. thanks for the quick reply Jim
January 7th, 2011 5:30pm

Although many would share your opinion as stated above, those folks have never tried to actually manaage a Mac in an enterprise environment. Although seemingly easier to use for users, management of Macs en masse is horrible. I'm sorry that a sales person told you something wrong, I'm sure that'll never happen from an Apple sales person and they will never oversell or misrepresent their product. Also, as I pointed out above, what you perceieved as a time saving feature, in the long isn't really. There are very good reason why re-capturing the image is a best practice and saving time is among them.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
January 7th, 2011 6:13pm

I actually have to run a very diverse network and MAcs are not my favourite either. I am no fan of Macs I guess I keep hearing this "There are very good reason why re-capturing the image is a best practice and saving time is among them" However no one has explained to me why it is better than simply using a pre built .wim file and how it saves me time when all I had to do with the install.wim I recieved was copy it to a share. Can you please point me to an article which explains this to me and why build and capture is better in the long run
January 7th, 2011 6:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics