Forum Home
Press F1
Thread ID: 139361	2015-04-20 22:33:00	Using sysprep	Tony (4941)	Press F1

Post ID	Timestamp	Content	User
1399021	2015-04-21 02:27:00	snip I'm reluctant to just do the rebuild and power up and hope, because if that doesn't work I'll be forced to reinstall everything whether I like it or not. Puzzled as to why you said that. That is why you are making images. IF the powerup and hope doesn't work, just lay your backup image back onto the drive. Quite frankly, reading about all the possible gotchas with sysprep, I'd always give the suck it and see method first crack.	linw (53)
1399022	2015-04-21 02:44:00	I'll certainly be doing the backups. I cited the link you give in my original post. I obviously didn't make it clear enough. Do you know from personal experience if it works as advertised? Sorry Never saw the link. Adaptive has worked every time I've had to use it, that's for when a customers Motherboard has gone bang. Like I said before nothing is 100% certain, but it would be better than using sysprep. Sysprep is Fine for what its designed to do, but there are a few problems that can arise on some installs. Sysprep is really meant for new installs to be deployed onto different hardware, generally after the install has been made into a image / .wim file. have a full read HERE (technet.microsoft.com) Its not really meant for existing long time running Installs, not to say it cant be done, but it often causes problems. "IF" you use sysprep what ever you do don't select oobe (out-of-box experience ) this will cause all sorts of problems with your account and run through the complete setup, Country, Product key etc all over again. I know this wont mean anything, but heres how its meant to work, .wim Files 6402 They are both .wim Files, the bottom one should be obvious as to what it is, the top one, its from a PC I built for a customer a few weeks back, I just "KNOW" shes going to muck up the Operating system ( already damaged it within 2 days and fixed once), so I imaged it first and dumped on the server so when its in need to reinstall it back to how it was when delivered , it will simply be put back and all up and going again within 15 minutes instead of the full day of installing, updates, all her programs etc.	wainuitech (129)
1399023	2015-04-21 05:07:00	Puzzled as to why you said that. That is why you are making images. IF the powerup and hope doesn't work, just lay your backup image back onto the drive. Quite frankly, reading about all the possible gotchas with sysprep, I'd always give the suck it and see method first crack.No disrespect, but that doesn't make sense to me. I make the images I change the hardware I reboot and it doesn't work At this point if I reload the images I am no further forward as I still have the new hardware and an "old" OS. Unless I'm missing something, which is entirely possible.	Tony (4941)
1399024	2015-04-21 05:12:00	Thanks Wainui - I think I'll try Adaptive. What you have written has reinforced all the concerns I had after reading various other pages about using sysprep. I too came to the conclusion it wasn't really designed for the "changing the hardware and wanting to save time" scenario. Too many conditions where it may not work.	Tony (4941)
1399025	2015-04-21 05:45:00	Thanks Wainui - I think I'll try Adaptive. What you have written has reinforced all the concerns I had after reading various other pages about using sysprep. I too came to the conclusion it wasn't really designed for the "changing the hardware and wanting to save time" scenario. Too many conditions where it may not work. One thing, If after you run Adaptive you get a few messages on bootup, don't panic (mr Mainwaring) On the odd computer you need to change a couple of reg keys. It should boot fine just you may get a few messages esp after the first boot. If it does this, just post and I can post the exact reg changes ( takes a few seconds).	wainuitech (129)
1399026	2015-04-21 05:57:00	Cheers - I'll report back. All I have to do now is find some uninterrupted time to redo the hardware.	Tony (4941)
1399027	2015-04-21 07:06:00	Not enitrely sure why you'd use sysprep in this situaton. Usually, sysprep is used on domain based computers where you "prep" an image so that when you boot the computer Windows regenerates the System SID's (Security identifiers) such as computer name etc. Doing this means you don't end up with duplicate computer names and or IP addresses on your domain/network. Having said all that it doesn't mean you won't be successful. Would be interesting to see what your results are. Cheers,	chiefnz (545)
1399028	2015-04-21 07:44:00	Not enitrely sure why you'd use sysprep in this situaton. Usually, sysprep is used on domain based computers where you "prep" an image so that when you boot the computer Windows regenerates the System SID's (Security identifiers) such as computer name etc. Doing this means you don't end up with duplicate computer names and or IP addresses on your domain/network. Having said all that it doesn't mean you won't be successful. Would be interesting to see what your results are. Cheers, If you read a couple of the earlier posts you'll see I'm not going to use sysprep after all, partly for the reasons you've described.	Tony (4941)
1399029	2015-04-21 11:50:00	No disrespect, but that doesn't make sense to me. I make the images I change the hardware I reboot and it doesn't work At this point if I reload the images I am no further forward as I still have the new hardware and an "old" OS. Unless I'm missing something, which is entirely possible. All I am saying is if you try the easy way and it turns to custard (unlikely), you can always go back and decide what to try next. Simple, really, and makes sense to me!	linw (53)
1399030	2015-04-21 19:42:00	All I am saying is if you try the easy way and it turns to custard (unlikely), you can always go back and decide what to try next. Simple, really, and makes sense to me! Except I can't go back because I've changed the hardware - unless you are suggesting I change all that back too. It's a;ll moot anyway as I'm not going to use sysprep anyway.	Tony (4941)
1 2 3 4