me really what know how this has turned out
common dougal tell us all about it, we all been in similar situations
common dougal tell us all about it, we all been in similar situations
Glitches in XP after change mobo (Pics)
- Thread starter dougal
- Start date
- Replies 26
- Views 3036
Just do a sysprep with generalize option ticked. Job done.
Yup, win7 is easy as it was designed to work like that. A generalised image is all the windows 7 install cd contains. You could capture your machine as a wim image, replace the install.wim on the installation DVD and have a completely custom windows 7 install.
Xp is more of a pain in the ass.
Sent from my iPhone using Tapatalk. Please excuse any crazy auto corrects or lack of detail (links to info sources)
Xp is more of a pain in the ass.
Sent from my iPhone using Tapatalk. Please excuse any crazy auto corrects or lack of detail (links to info sources)
This is also how Windows Deployment Services (WDS) on Windows Server 2003 SP2 and upwards works.
It uses a modified boot.wim image to netboot (PXE) and captures or deploys .WIM images to/from the clients
Since introducing the .WIM image and the newer Sysprep in Vista and Server 2008 (and improving upon it in Windows 7 and Server 2008 R2) it now makes machine upgrades and mass hardware swap really easy.
Sorry to go slightly off topic with this, but it does mean that you can (if you should want to) keep the same Windows install when swapping or upgrading your PC nowadays - something that's not been possible easily since the Windows 9x days.
Boot.wim is a winpe wim, not a os install wim.
I don't really know which part of my post you were saying it's the same as :-/
But yes, this is what I do all day everyday - building images/builds for customers and deployment solutions/methods.
Internally we use wds and a heavily modified winpe wim that handles several hundred different image installs our engineers use. Using wds "properly" and having each image have its own boot.wim and menu entry just isn't practical for us.
Sccm also isn't practical for most, but we do use it for customers we have a domain connection to via VPN or such
Wds was a nice improvement from ris though.
Sent from my iPhone using Tapatalk. Please excuse any crazy auto corrects or lack of detail (links to info sources)
I don't really know which part of my post you were saying it's the same as :-/
But yes, this is what I do all day everyday - building images/builds for customers and deployment solutions/methods.
Internally we use wds and a heavily modified winpe wim that handles several hundred different image installs our engineers use. Using wds "properly" and having each image have its own boot.wim and menu entry just isn't practical for us.
Sccm also isn't practical for most, but we do use it for customers we have a domain connection to via VPN or such
Wds was a nice improvement from ris though.
Sent from my iPhone using Tapatalk. Please excuse any crazy auto corrects or lack of detail (links to info sources)
I clone a partition on a fresh install using GParted on Ubuntu once I have everything set up nicely. If something screws up I simply boot back to Ubuntu, delete and restore the windows partition and presto, fresh system again.
No need to find CDs or type in licence keys or anything that way
No need to find CDs or type in licence keys or anything that way
@ Dougal: have you tried any of the above advice? if so, has any of it helped?