Scr1ptW1zard

Attached are the actual scripts used for each process. There is some commenting in the scripts, let me know if you have any specific questions concerning what is being performed. I still need to add some error checking, but the scripts perform as intended. crtdisks.cmd - Create disk partitions based on number of disks and specified options. fmtdisks.cmd - Format partitions based on OS and number of partitions. Variables in the scripts are as follows: netdsk - Mapped drive to distribution share. (N:) sn - Serial Number of system being provisioned. crtdisks.cmd fmtdisks.cmd

I am adding this to all my installs. I currently have only used this build on some newer IBM System X servers (x3500 & x3550) and my virtual (VMware) test servers. Without this, I experience the black screen, but all files can be seen just fine while under WinPE. IBM provides a scripting utility toolkit for creating the WinPE 1.6 environment. I was surprised that using this utility without modification, did not work without the addition of the MbrFix utility. Once added, my scripts perform as they should. Previously I had been using a DOS-based server provisioning process and did not experience this problem until I started migrating to the WinPE environment. The WinPE environment provides everything that my DOS-based process performed and much more. Thanks again.

Thanks Jazkal, I went back and created a WinPE 1.6 CD. At first I was receiving the same result, but then I recalled the need for the MbrFix utility. Once I added that back into the scripts, the WinPE 1.6 CD worked like a charm. I have not went back to the WinPE 2.0 build yet as there are more utilities that I require to perform the unattended build available under the Windows Server 2003 OS that is not available (yet) for Vista. Something to test: Doesn't the Bootsect utility provided with WinPE 2.0 perform the same function as MbrFix? My WinPE 2.0 build contains the following after formating the disks: bootsect.exe /nt52 ALL My WinPE 1.6 build contains the following after formating the disks: MbrFix.exe /drive 0 fixmbr /yes Thanks for your suggestions.

The %~d0 will simply display the current drive, which may not be the CDROM. Here is a batch file that will find all CDROMs and provide the environment variable of CD1, CD2, etc.: @echo off :::::::::::::::::::::::::: :: Title: GetCD.cmd :: :: Author: Scr1ptW1zard :: :: Date: 07/27/2007 :: :::::::::::::::::::::::::: echo list vol>.\listvol.dp setlocal enabledelayedexpansion set CD= for /f "tokens=3" %%a in ('diskpart /s .\listvol.dp^|find /i "-ROM"') do ( set /a count=!count! + 1 set CD!count!=%%a:) ::::::::::::::::::::: :: Display CDROMs :: ::::::::::::::::::::: :: NOTE: :: Variables begin with "CD" followed by a number. :: The number begins with 1 and increments to the total number of CDROMs set cd :::::::::::::::::::::::::::: :: Use CD# variables here :: :::::::::::::::::::::::::::: endlocal Hope this helps.

I have done some further testing the last couple of days, but the results are the same. I removed the registry entries from the WinPE boot CD and used the Windows source files with the hotfix applied. No change in the result. I added the registry entries to the WinPE boot CD and used an unpatched Windows source files. Again, no change. I have also tried using both the registry entries and the hotfix together, but still no luck. I have contacted my IBM technical representative to see if they could duplicate what I am experiencing. I have no idea when or if I will receive any feedback, so I welcome all suggestions.

Jazkal, Thank you for your reply. Yes, I am aware that the registry entries are to be added to my WinPE image, that is how I have implemented them. When I boot to the WinPE environment, I can launch regedit and see that the values are indeed set, so I thought this was correct. I believe you are referring to KB931761. I have obtained the hotfix and integrated this to the setup files for the Windows Server 2003 installation. Same problem... I guess my most frustrating aspect is that I am having the problem with only one type of system. I am going to move onto other systems next week to see if I get any other results. Other thoughts are welcome...

I am creating an unattended Windows Server 2003 installation process using WinPE 2.0. I have been testing the process on virtual systems to get the process working just the way I need it. Works perfectly every time. Moved on to one of our physical systems, an IBM x3500. Ran into some driver issues, which I expected, and integrated the drivers into my process as needed. Again, process works great on the IBM x3500. I thought I had it all figured out, until I ran the process on several of our IBM x3550 systems, the headaches began, the frustration level rose, and after a week of failure and disappointment, I gave up. Until now... My process is as follows: Boot to WinPE environment Request server information via HTA Create RAID configuration and logical drives Partition Drives Format Partitions (NTFS) Copy supporting files to system partition Initiate Windows Installation (C:\support\i386\winnt32.exe /syspart:c: /noreboot /s:C:\support\i386 /unattend:c:\support\winunatt.ini) That is the basic flow, it is more detailed by irrelevant to the issue I am having (I think). Through this point everything functions properly. At this point the system reboots, performs post, then at the point that it should boot and begin text mode setup, I get a black screen with a flashing cursor in the upper left corner of the screen. No error message. No attempt to boot any other device. I have been struggling with this problem for about two weeks now. I have tried the following suggestions found in this forum: Using "align=16065" with diskpart when creating partitions Adding the registry changes to WinPE prior to issuing diskpart reg load HKLM\PE-SYS c:\Winpe\Mount\Windows\system32\config\system Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /f Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /f Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /f Reg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /f reg unload HKLM\PE-SYS Formatting to FAT32 instead of NTFS The IBM systems I am using have different RAID controllers, but use the same drivers. The IBM x3500 has a ServeRAID 8k, where as the IBM x3550 has a ServeRAID 8k-l, Both are manufactured by Adaptec and I have obtained the latest drivers. I have also updated the firmware on the IBM x3550's RAID controller. I can successfully install Windows Server 2003 from CD using the same drivers. If I boot back into WinPE, I can browse the directory structure of the local disks and see all the files just as I should. I am stumpped! I'm sure I am missing something basic, any help would be appreciated.

Perhaps you could do this: Create a batch file (stub.cmd) with the following: %*>>results.txt Then, where you are calling your batch file, change to: stub.cmd mybatch.cmd Finally, make sure the echo is on in your original batch file. The commands you issued and their results will be in results.txt. Hope that helps! Scr1ptW1zard