Windows 2K8 R2: Base Image Capture
noodleNT
August 17th, 2009
When you install Windows 2K8 R2 it creates an extra partion called "System Reserved". If I try and to a base capture of the computer without the DAGENT installed, it wont let me restore it because the boot drive isn't found. Is there a trick to capturing the R2 image without this extra partition?
I have already done the BCDEdit tricks that you do for Vista, Windows 7 and Windows 2k8 to fix the partition mapping:
@ECHO OFF
REM Execute BCDEdit and prepare for imaging.
REM Find the system root and append system32 and BCDedit
%SYSTEMROOT%/system32/Bcdedit.exe -set {bootmgr} device BOOT
%SYSTEMROOT%/system32/Bcdedit.exe -set {default} device BOOT
%SYSTEMROOT%/system32/Bcdedit.exe -set {default} osdevice BOOT
shutdown /r
RE: Windows 2K8 R2: Base Image Capture
Try the following:
BCDEDIT /set {bootmgr} device partition:c:
BCDEDIT /set {default} device partition:d:
BCDEDIT /set {default} osdevice partition:d:
this could be done after restoring an image too. MEaning as script job after a imaging job.
nelson
This extra partition is a
This extra partition is a hiden partition. So there is no D: drive.
How would you run this after the image is copied down? Can it be done in PE?
Also, does this problem just
Also, does this problem just go away if the DAgent is installed when we start the capture?
Have to do it in PE
If I run the command in PE it works. When booted into windows the D: partition doesn't exist so the command fails.
@ECHO OFF
REM FIX BOOT Order with BCDEDIT
bcdedit /store c:\boot\BCD /set {bootmgr} device boot
bcdedit /store c:\boot\BCD /set {default} device PARTITION=d:
bcdedit /store c:\boot\BCD /set {default} osdevice PARTITION=d:
Have to do it in PE
Yes, see when u deploy and image u are already in preboot so run a script job in preboot to fix this issue.
Nelson
This is odd.... if I try to
This is odd.... if I try to run the command after the Rdeploy job, although it runs succesfully, the computer fails to boot the OS. Yet, if I put in a reboot betwen the Rdeploy job and the BCDEDIT job, the OS loads correctly. Any idea how to get around this needed reboot?
For whatever reason, if I use
For whatever reason, if I use a USB drive with WinPE on it, then I can assign C and D as expected. I'm not sure what Altiris does to WinPE but it ends up changing the drive letters so if I run it through Altiris WinPE, I have to use C and H. I have to use H because our Dells have a bunch of drive letters assigned because of the card reader. You can find out what drive letters are being assigned by breaking the Altiris WinPE load by hitting CTRL - C after Altiris WinPE finishes loading WinPE networking. Then run diskpart --> list volume to see what drive letters are being applied. This might be the reason why some are getting the message that D doesn't exist. Like I say, I don't know what or why Altiris WinPE changes things around besides the fact that the mappings to the express share are setup during this process but I don't knwo why the drive letters change.
Would you like to reply?
Login or Register to post your comment.