witch (7th April 2011)
witch (7th April 2011)
I still can't image the damn thing and now of course I have hit the limit and it wont sysprep anyway.
I have had to rebuild this machine twice all ready and if I have to do it again I will cry, scream or hit something - or someone.
I have looked on the web and tried all the work arounds, regedits etc - and nothing works
Can anyone tell me how to sort it out so that I can try and get the imaging sorted without having to rebuild the machine again, It is hard to do as most of our software is too old to have msis and so I have to install everything one by one.
I really cant do this again...can anyone help??
My boss is getting pretty concerned about the lack of his new IT suite and I dont know how much longer he will wait.
All help gratefully received
Last edited by witch; 25th April 2011 at 09:51 PM.
The best way to do these types of things is build the image on a virtual machine and get it so it can be applied to the computer you want. You can then use snapshots and revert to snapshot to save you rebuilding from scratch every time. You would do snapshots at critical stages such as basic install, all apps installed, just before sysprep etc etc. It makes this kind of process a lot quicker.
Witch, have you tried using MDT?
This way you can install Windows 7 freashly each time along with any drivers, and also get it to install software as needed
I didn't use any captured images after switching to MDT
If you need any help PM me tomorrow and I'll try and help
is it still stuck not showing the hdd when you boot into wds?
does the laptop have ide/ahci mode in bios if so try turning it to ide to clone/restore (a pain i agree but should work) or even shove the hdd with your image in another laptop that does wds happily at least that way you haev your image and so just need to worry about deployment. Are these still the hp620's cant rememebr if that was this thread or another as i rebuilt a dozen a fortnight or so ago using a std win7 boot image no mods (they are slow as owt to clone but they have a pants nic iirc seems nobody fits gb (or even 1/2 decent) lan cards to laptops no more).
if you have an 08r2 server it is possible to get wds to add its own drivers to the boot files but i cant remember how.
Just double checking you are trting to take an image of a syspreped pc as it wont image if its not sysprepped correctly.
I am still having the issue with imaging even though I have DEFINITELY sypreped OK. (have been through it with a couple of local guys who know what they are doing)
BUT the current issue is that Win 7 does not allow you to sysprep more than three times even though it is a volume licence.
This is server 2003 not 2008.
So...are we saying that I must rebuild my image again? And if so I could use a different method?
As I said, msi would be lovely but not really possible and building msis for all the software would be a lovely idea but just not possible time-wise even though I am sure it would save me time in the long run.
These are desktops BTW, not laptops. No other modes in the BIOS
I have no virtual machines and no time, on 15 hours a week, to even try and sort that out
Witch, MDT may still be of usefor imaging, It might be a bit quicker than a full WDS Image too
Also with regards to the MSI's - with MDT you could use AutoIT to "record" the installs..
Thanks - but I dont really know what that is and it isnt going to help me avoid rebuilding, is it?
It has to be simple and easy or I will be lost
MDT = Microsoft Deployment Toolkit (2010) -> Microsoft Deployment Toolkit
You create a Share, then a Boot Image that can be added to WDS
Then import your OS, Drivers and Applications
You use Task Sequences to script the install of Windows and any drivers and apps
It is primarily wizard driven when you boot, but these can be automated with Answer files and tailored for specific makes & models of PCs...
I had it so it only prompted for a PC name and any apps
Apps can be grouped (eg Generic apps, teacher apps (eg sims, smartboards) etc)
witch (25th April 2011)
Sorry, but I don't think that is within my capabilities, on my own! sounds great but I know my limits and I just dont have the time (and never do) to have a play.
I am still really just after a way to get around windows reluctance to allow more than three attempts at sysprep.
Fair enough, thought it might have been of use...
Gatt: I am grateful and sure it would be of use but I just don't know enought to do it - thanks anyway
Sukh: Tried that and it didnt work I'm afraid
I am nowhere with injecting drivers as I realised I had done the sysprep limit before I got to have a go
There are currently 1 users browsing this thread. (0 members and 1 guests)