Edited by crashnburn, 13 July 2015 - 07:23 PM.
#1
Posted 13 July 2015 - 07:16 PM
#2
Posted 14 July 2015 - 10:12 AM
Hi Carshnburn,
A WIM is a file based disk image, not a sector based image, you cannot wim image the whole disk (including the boot sectors).
If you really want to use the WIM format (which has advantages like keeping the image small), you will need to prepare the destination disk (create, partition, format, set the boot sectors ...).
As for sysprep, I am no expert there but I believe this is needed only if you change significantly the hardware (motherboard, etc).
Regards,
Erwan
#3
Posted 14 July 2015 - 07:43 PM
There is no conversion required: boot a UEFI machine and load a MBR VHD image.My thought is that by going to .WIM I bypass the whole converstion drama between MBR/BIOS & GPT/UEFI as the .WIM is agnostic of both of them? Is this a valid thought or not?
Or boot a UEFI machine and load a GPT VHD image.
As for testing: use a fixed size VHD image.
A dynamically max 500gb (100gb occupied) VHD disk is a bad idea at a 250gb hard disk.
The max VHD disk has to be storable: use a 1tb hard disk at a 500gb (100gb occupied) VHD disk
Yes, file based transfer is a good idea:
dism capture/apply to a new created fixed size vhd.
If both systems uses AHCI at storahci.sys: do not use sysprepWhere and how would you recommend applying the SYSPREP?
8.1 requests CPU specs, kernel and hal are equal, both systems uses a pci bus.
The transfered system will boot, however be aware third party drivers may interfere.
#4
Posted 14 July 2015 - 09:13 PM
Hi Carshnburn,
A WIM is a file based disk image, not a sector based image, you cannot wim image the whole disk (including the boot sectors).
If you really want to use the WIM format (which has advantages like keeping the image small), you will need to prepare the destination disk (create, partition, format, set the boot sectors ...).
As for sysprep, I am no expert there but I believe this is needed only if you change significantly the hardware (motherboard, etc).
Regards,
Erwan
My intent is not to image the boot sectors but allow me to recreate fresh boot specs on/ for the VHD.
Yes, hardware will change significantly as this will be my go to VHD that can be moved from machine to machine when needed/ wanted.
There is no conversion required: boot a UEFI machine and load a MBR VHD image.
Or boot a UEFI machine and load a GPT VHD image.
As for testing: use a fixed size VHD image.
A dynamically max 500gb (100gb occupied) VHD disk is a bad idea at a 250gb hard disk.
The max VHD disk has to be storable: use a 1tb hard disk at a 500gb (100gb occupied) VHD disk
Yes, file based transfer is a good idea:
dism capture/apply to a new created fixed size vhd.
If both systems uses AHCI at storahci.sys: do not use sysprep
8.1 requests CPU specs, kernel and hal are equal, both systems uses a pci bus.
The transfered system will boot, however be aware third party drivers may interfere.
cdob - well, this is what I was troubled about last year; the whole MBR/BIOS v/s GPT/UEFI or Mixed mode booting. It was rather confusing.
It could've been windows 7 playing trouble maker, but I am wondering and maybe you are right.. Were my troubles unfounded?
I am hoping the file based transfer using WIM simplifies things.
I am guessing making the VHD bootable should be as simple as a few BCDBOOT commands? Right?
Well.. I think the machines are all AHCI.. E.g. Thinkpads T6x, X6x and new Machines Surface Pro 3 and other machines. But, will Win 8.x not create drama on new hardware without a Sysprep.. especially due to DRIVER PROFILES from previous MACHINE HARDWARE?
That way before the OS moves to new machine it gets "cleansed" of drivers that were applicable to previous machine. ? Thoughts?
That being said, Could you please shed some light on "how"/ "when" "where" would you suggest "h/w & driver profile cleansing" SYSPREPs in the above steps (original post).
I read somewhere / an MVP had suggested doing Sysprep on a Virtual Machine (Hyper V etc); for some reason - not sure if I remember but maybe something to do with less conflicting hardware + driver state.
PS: Experiences of errors/ issues/ troubles anyone has faced in doing Syspreps that I can avoid by taking cautionary steps ??
#5
Posted 14 July 2015 - 10:20 PM
Wasn't a UEFI GOP graphic card involved? A hardware without Windows 7 support? Wasn't this the main reason?It could've been windows 7 playing trouble maker, but I am wondering and maybe you are right.. Were my troubles unfounded?
I don't understand 'Virtualize Win8.1'? How do you like to boot he VHD?I am guessing making the VHD bootable should be as simple as a few BCDBOOT commands? Right?
Do you like to run a virutal machine? Do you like to use native VHD boot?
YEs, bcdboot handles native boot. remember /f BIOS and /f UEFI
Windows 8.x is designed for limited roaming.But, will Win 8.x not create drama on new hardware without a Sysprep..
Roaming with Windows To Go https://technet.micr...y/hh831833.aspx
Win 8.x will not create drama on new hardware without a Sysprep, as long you use native drivers.
Third party drivers may cause issues.
Do you expect Lenovo power manager to run at other hardware?
Sorry bad example, not supported at win 8.
In general: avoid hardware manufacturer addons.
If you force me to use sysprep:
Given the T61 example.
I would transfer the VHD image to a USB MBR SSD.
Run bcdboot to the USB drive.
Boot win 8 from the USB SSD at the T61.
Remove hardware manufacturer programs.
And run sysprep / shutdown.
A virtual machine would adding drivers relating the virtual machine. This is the second choice in my opinion.doing Sysprep on a Virtual Machine
Added:
Given a Intel IDE machine with active intelide.sys
This windows booted at a AMD chipset machine:
intelide.sys is deactivated: demand start StartOverride=3
The Enum entry is cleaned
Windows 8 cleans boot drivers at transfer to other hardware.
http://reboot.pro/to...g-bios-setting/
Windows 8 disables not required boot drivers at boot
I would not use sysprep as for a simple transfer to other hardware.
- crashnburn likes this
#6
Posted 19 July 2015 - 07:11 PM
#7
Posted 20 July 2015 - 05:46 AM
That is the objective, to not WIM any of the boot or sector information.
And my objective is to create a fresh set of Boot information.
PS: Both of the above is because going from MBR/BIOS to GPT/UEFI
Hi Carshnburn,
A WIM is a file based disk image, not a sector based image, you cannot wim image the whole disk (including the boot sectors).
If you really want to use the WIM format (which has advantages like keeping the image small), you will need to prepare the destination disk (create, partition, format, set the boot sectors ...).
As for sysprep, I am no expert there but I believe this is needed only if you change significantly the hardware (motherboard, etc).
Regards,
Erwan
I will be moving it from Old BIOS hardware Thinkpad T6x/X6x to newer only UEFI Surface Pro 3 and/ or similar. So, I am thinking SYSPREP or any similar Cleansing process would help.
Cdob - I did a GPTGEN conversion on the Disk2VHD generated VHD; MBR > GPT
I can skip File System conversion if I go to a WIM using DISM.
See my original and new hardware. Only is only BIOS and new one does not support Legacy CSM. Pure UEFI.
There is no conversion required: boot a UEFI machine and load a MBR VHD image.
Or boot a UEFI machine and load a GPT VHD image.
As for testing: use a fixed size VHD image.
A dynamically max 500gb (100gb occupied) VHD disk is a bad idea at a 250gb hard disk.
The max VHD disk has to be storable: use a 1tb hard disk at a 500gb (100gb occupied) VHD disk
Yes, file based transfer is a good idea:
dism capture/apply to a new created fixed size vhd.
If both systems uses AHCI at storahci.sys: do not use sysprep
8.1 requests CPU specs, kernel and hal are equal, both systems uses a pci bus.
The transfered system will boot, however be aware third party drivers may interfere.
I'd guess both use AHCI, and I will clean most 3rd party drivers out. But, to avoid taking any hardware/ driver crap forward, neither MS or especially 3rd party drivers like Lenovo/ Thinkpad stuff.
I have removed a bunch manually but some of the stuff refuses to go/ not sure how to clean. (I have been using Nirsoft and SysInternals to track stuff but no way to clean them out).
I am not sure if there is any other way to CLEANSE besides SYSPREP.
Yes. I guess it was GOP thingy (learned that from MSFN). Hence, I dropped the ball at the time.
Native Boot VHD.
Thanks for the Command-line options. Although I ran it without them and the default seems to have applied i.e. UEFI on SPro 3.
Wasn't a UEFI GOP graphic card involved? A hardware without Windows 7 support? Wasn't this the main reason?
I don't understand 'Virtualize Win8.1'? How do you like to boot he VHD?
Do you like to run a virutal machine? Do you like to use native VHD boot?
YEs, bcdboot handles native boot. remember /f BIOS and /f UEFI
Windows 8.x is designed for limited roaming.
Roaming with Windows To Go https://technet.micr...y/hh831833.aspx
Win 8.x will not create drama on new hardware without a Sysprep, as long you use native drivers.
Third party drivers may cause issues.
Do you expect Lenovo power manager to run at other hardware?
Sorry bad example, not supported at win 8.
In general: avoid hardware manufacturer addons.
If you force me to use sysprep:
Given the T61 example.
I would transfer the VHD image to a USB MBR SSD.
Run bcdboot to the USB drive.
Boot win 8 from the USB SSD at the T61.
Remove hardware manufacturer programs.
And run sysprep / shutdown.
A virtual machine would adding drivers relating the virtual machine. This is the second choice in my opinion.
Added:
Given a Intel IDE machine with active intelide.sysSpoiler
This windows booted at a AMD chipset machine:
intelide.sys is deactivated: demand start StartOverride=3
The Enum entry is cleaned
Windows 8 cleans boot drivers at transfer to other hardware.
Spoiler
http://reboot.pro/to...g-bios-setting/
I would not use sysprep as for a simple transfer to other hardware.
As per some posts on windows-noob (MS MVP for Deployment) a VM would an be easier place to cleanse things before Imaging as it is more actual OEM Hardware agnostic.
Not sure how the Intel vs AMD thing will help here.. if some Thinkpad HW/ Driver info stays on before Imaging.
#8
Posted 22 July 2015 - 07:22 PM
I have completed through these phases of the project. Using this context, please help me with this further at this location:
http://reboot.pro/to...e-boot-vhd-how/
Also tagged with one or more of these keywords: bios, mbr, wim, image, gpt, uefi, vhd, partition, virtual, physical
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users