Hi,
I'm currently working on a project that involve the migration of +4000 Win9x/NT4/2K desktops to WinXP for an big corporation. The Windows XP part is complete, but the customer want an interim configuration built around Win2000. The problem is that i cant get SysPrep 1.1 (the one from W2K) to recognize the chipset drivers required for the newer P4 (such as on a Dell GX260) and this give BSOD during the setup. Microsoft documentation refer to an unattended setup as an RIS only installation and keep sysprep unattended installation doc for OEM only. We need to build an Ghost image that can be deployed via CD.
The process for Windows XP is :
1- an Windows XP image prepared with SysPrep
2- the image is a Ghost file, burnt on a bootable CD
3- a Mini-Setup is launched and the computer request a ComputerName, LocalAdminPassword and join the NT domain
The result is that Windows XP join the domain and start installing his application under 6 minutes, even on a low-end computer
I'd like a similar setup for Windows 2000 but with SysPrep 1.1, the Mini-Setup does not want to include the Intel INF drivers required to boot the computer. The content is sysprep.inf is working fine also (almost the same options for XP and 2000). I need to include additionnal drivers to keep only 1 image of Windows. Under XP, i added a BuildMassStorageSection in Sysprep and i work fine but not under 2000. I have a \i386\$oem$\1$\drivers folder and it work very well under XP but 2000 dont want to read/access it and I dont understand why. I have a good knowledge of deployment process and i'd like a technical explanation is possible.
HELP !!!
-HypNoTic
I'm currently working on a project that involve the migration of +4000 Win9x/NT4/2K desktops to WinXP for an big corporation. The Windows XP part is complete, but the customer want an interim configuration built around Win2000. The problem is that i cant get SysPrep 1.1 (the one from W2K) to recognize the chipset drivers required for the newer P4 (such as on a Dell GX260) and this give BSOD during the setup. Microsoft documentation refer to an unattended setup as an RIS only installation and keep sysprep unattended installation doc for OEM only. We need to build an Ghost image that can be deployed via CD.
The process for Windows XP is :
1- an Windows XP image prepared with SysPrep
2- the image is a Ghost file, burnt on a bootable CD
3- a Mini-Setup is launched and the computer request a ComputerName, LocalAdminPassword and join the NT domain
The result is that Windows XP join the domain and start installing his application under 6 minutes, even on a low-end computer
I'd like a similar setup for Windows 2000 but with SysPrep 1.1, the Mini-Setup does not want to include the Intel INF drivers required to boot the computer. The content is sysprep.inf is working fine also (almost the same options for XP and 2000). I need to include additionnal drivers to keep only 1 image of Windows. Under XP, i added a BuildMassStorageSection in Sysprep and i work fine but not under 2000. I have a \i386\$oem$\1$\drivers folder and it work very well under XP but 2000 dont want to read/access it and I dont understand why. I have a good knowledge of deployment process and i'd like a technical explanation is possible.
HELP !!!
-HypNoTic