The Art of OEM - nLite & OEM Preinstallation Part 6: Windows Deployment Services / Server 2008
#62
Posted 06 July 2007 - 11:20 AM
I have Windows XP Pro.
How can this tutorial be useful for me? if yes
What steps should i follow?
This post has been edited by NaDer_GenKO: 06 July 2007 - 01:43 PM
#63
Posted 06 July 2007 - 03:26 PM
NaDer_GenKO, on Jul 6 2007, 08:20 PM, said:
I have Windows XP Pro.
How can this tutorial be useful for me? if yes
What steps should i follow?
the main benefit for workstations is that you can slipstream large pieces of software in your windows installation, like Visual Studio or Office 2007.
Parts 1, 3 and 4 are applicable in this case, the main difference is that you just install the software you want in VMware and sysprep afterwards. I will make a Part 2 alternative for Windows 2000 / XP
#65
Posted 06 July 2007 - 04:56 PM
Kingskawn, on May 13 2007, 11:48 PM, said:
And thus...
HTML version on my website here (I will add PDF version to a download section)
Windows Designer Studio topic here (concerning app development, suggestions and feedback)
This thread stays as discussion for the guide itself. There will be a different topic for Art of OEM for Vista.
To get the newsletter, send a mail with the word 'subscribe' in subject, to dexter_inside@yahoo.com
This post has been edited by dexter.inside: 06 July 2007 - 04:57 PM
#66
Posted 08 July 2007 - 06:01 PM
the links of part2 ,3 and 4 on Art of OEM web site not working
I tested it for 3 days before and nothing changed. I'm Very sad Because I'm interesting in this scenario
#67
Posted 08 July 2007 - 06:51 PM
NaDer_GenKO, on Jul 9 2007, 03:01 AM, said:
the links of part2 ,3 and 4 on Art of OEM web site not working
I tested it for 3 days before and nothing changed. I'm Very sad Because I'm interesting in this scenario
sorry for that, I have made some minor adjustments to the text and moved all the images on my site. I am also making some space in Part 2 for a workstation-tuned scenario.
Edit: done, all the parts are now on my site. Issues specific to WHS are moved out from Part 2 for the moment, hope that clears out some of the confusions related to 2.2 - 2.4
PDF version: Art of OEM - revision 2.pdf , 6189 kb
This post has been edited by dexter.inside: 08 July 2007 - 08:06 PM
#68
Posted 09 July 2007 - 12:32 AM
for your fast response and for the great job and for your efforts
the site now working perfectly and I'm happy of this
the PDF is very nice
#69
Posted 12 July 2007 - 07:43 AM
I've been following the process, and I'm very impressed by not only your research, but also the detail in your guide! I had two little problems whilst following it though:
1) You have an absolute mountain of drivers; I realised not all of these are required, but as a general rule, will the mass storage drivers distributed with windows be sufficient for install on most computers, if you add them correctly into sysprep?
2) I was unsure how to transfer the settings across to the default user. I've created a second user, and installed everything I wish under that user, but how do I now transfer the settings to the default user? And do I need to do anything to the admin account? This is immediately before sysprep.
Many thanks!!
Wrayal
#70
Posted 12 July 2007 - 08:38 PM
wrayal, on Jul 12 2007, 04:43 PM, said:
The only real issue with missing drivers is that if you don't have the proper SATA drivers you won't be able to install windows (either Windows PE will not detect the hard drive at all, or Windows will BSoD with UNMOUNTABLE_BOOT_VOLUME at first boot). If you use the Universal ATA driver you may overcome that problem, though.
Quote
The default user data is in \Documents and Settings\Default User. If you already have the template user account, copy it over the Default User folder, overwriting files there. This is done after you've applied sysprep, and you are preparing to image it. Alternatively, there's the TweakUI Powertoy, that can do mostly the same thing. It's best to use TweakUI just before running sysprep.
If you want the administrator account disabled, you should run a script at first boot to disable it.
#71
Posted 12 July 2007 - 10:08 PM
The only other issue I had was that where BDD put all my drivers into a single folder, nLit only recognised one of those within this folder. I ended up manually putting them into separate folders (thankfully I didn't have nearly as many drivers as you!). Is this stupidity on my part?
Thanks,
Wrayal
[edit] Sorry, one final question, if I may: I saw you did the 'Ultimate' modification to 2k3 - did you also have the error stating you drivers were incompatible, and does this rectify itself once installed on hardware for which you can provide valid drivers?
This post has been edited by wrayal: 12 July 2007 - 10:14 PM
#72
Posted 12 July 2007 - 11:45 PM
MCE adds some stuff to startup, like cheching for extenders. I had no driver issues whatsoever on it.
#73
Posted 13 July 2007 - 12:21 PM
I have followed this guide, and am now testing my BartPE + Longhorn Setup ISO. The setup did get to the partition choice in my Server 2003 desktop, but, on the BartPE CD, it drops to the command shell of startnet.cmd, after I select the partition selection button, or Next. I did use an modified Longhorn setup, as I could not get an untouched one, but the only change is that there is no dotnetpe.cab, and there is a weird bitmap in the loading screen. Also, I'm deploying XP Pro, but the setup only wanted to run on 2003, so I built it with 2003.
Could anyone help?
-- Bas
#74
Posted 13 July 2007 - 06:38 PM
NetworkService, on Jul 13 2007, 09:21 PM, said:
I have followed this guide, and am now testing my BartPE + Longhorn Setup ISO. The setup did get to the partition choice in my Server 2003 desktop, but, on the BartPE CD, it drops to the command shell of startnet.cmd, after I select the partition selection button, or Next. I did use an modified Longhorn setup, as I could not get an untouched one, but the only change is that there is no dotnetpe.cab, and there is a weird bitmap in the loading screen. Also, I'm deploying XP Pro, but the setup only wanted to run on 2003, so I built it with 2003.
Could anyone help?
-- Bas
Probably because the Panther Setup engine uses ramdrive internally and the ramdrive.sys in XP is no good.
If there are missing dependencies, the setup routine just closes silently.
Have a look at Norton Ghost 12 rescue CD, it already has all the dependencies needed for this. I am currently writing an alternate scenario for Windows XP, in which the setup is launched from Symantec SRESHELL.
I've added the Panther SDKs on my project's download page
You will have to provide PIDGEN.DLL, SETUPP.INI and EULA.TXT for the OS you are installing.
This post has been edited by dexter.inside: 13 July 2007 - 07:07 PM
#75
Posted 14 July 2007 - 02:17 AM
What could be the problem?
-- Bas
#76
Posted 14 July 2007 - 04:34 AM
NetworkService, on Jul 14 2007, 11:17 AM, said:
What could be the problem?
-- Bas
Are you sure you got the .NET 2.0 working properly inside the PE ? There might be files with different versions and there are missing exports due to this reason... or...
Have you ran the SETUP.EXE locally (from a write-enabled folder) to see if it works properly?
If you still can't figure it out, get a evaluation for Norton Ghost 12 Recovery and add the stuff in your \SOURCES folder in their ISO. If it works there, the cause is your PE. I've also noticed that WinPE 2.0 boosts significantly the speed of the Panther SDK.
I've also had trouble with WinPE 1.x, and each time some missing export was to blame. AFAIK, the Panther run-time code requires a RAM drive, for temp folder and .NET 2.0
Hope to get Part 5 soon, I'm gathering screenshots in the mean time
If you discover anything else that I've forgot and should be in Part 4, let me know.
#77
Posted 14 July 2007 - 05:02 AM
EDIT: Hmm, I don't see a solution...
This post has been edited by NetworkService: 14 July 2007 - 05:17 AM
#78
Posted 14 July 2007 - 05:27 AM
#79
Posted 14 July 2007 - 06:23 AM
#80
Posted 14 July 2007 - 06:32 AM
Use in VMware: Edit -> Preferences -> Memory - Allow most virtual machine memory to be swapped
and in your VM: Options -> Advanced -> Disable memory page trimming
This cuts down some 33% out of performance, but will do the job for you
- ← IE8 Install from cmdlines (for xp sp3) working
- Unattended Windows 2000/XP/2003
- Help needed with XP Unattended Install →



Help

Back to top









