Provisioning problem ----> winnt32 problem shown while running provisioning job
Somnath Shilimkar Nov 6, 2012 3:02 AMHi all,
I m trying for provisioning for win2k3r2 in VM ware... when i start newly created machine it takes ip from DHCP and start runing startnet.cmd
it has done pre-disk partitioning and post-disk partitioning as can see from results of provisioning job.
then when i run the provisioning job
following is the error i can see when i run provisioning job.
HIGHLIGHTED REGION SAYS --> System cannot find the drive specified.
'winnt32' is not recognized as an internal or external command operable program or batch file.
if anyone know what is this error means please tell me.
Same error i can see on startnet.cmd on machine which is under provisoning.
FOLLOWING IS THE FULL DESCRIPTION OF ALL CONFIGURATIONS I MADE FOR PROVISIONING.
IF I M WRONG SOMEWHERE PLEAE TELL ME.(actually i m trying this first time so dont know many things)
I am trying to provision Win2k3R2 Enterprise Edition.
i have created all setup as specified in White paper for provisioning.
let me specify everything in detail as follows -->
DATABASE SERVER --> is windows server 2003 enterprise edition with ip address 192.168.6.7 (static IP) hostname--> dbserver
SQL SERVER 2005 running on it.
APP SERVER --> is RedHat 5.x which is APPSERVER and IP is --> 192.168.6.129, hostname--> BBSA01
PXE server and TFTP server running on same machine
FILE SERVER --> not playing big role in this scenario with ip as 192.168.6.128
NOW following Provisioning related components are installed and configured as follows
1 )PXE and TFPT --> running on APPSERVER (192.168.6.129)
2) DHCP --> running successfully on DATABASE SERVER (192.168.6.7)
MEANS PXE/TFTP and DHCP NOT ON SAME MACHINE (but no problem its working fine)
3) DATA STORE
i have kept it on DATABASE SERVER means on 192.168.6.7, in F drive
as F:\pxestore
in side pxestore two directories F:\pxestore\Agents and F\pxestore\Win2k3r2
THIS MEANS PXE server and DATASTORE are not on same machines.
4) Shared this data store with pxeuser
5) Configure Data Store instances
4) configure System Packages
I M SUSPECTING THIS STEP AS ROOT CAUSE FOR THIS PROBLEM...IS THIS ABOVE STEP CORRECT ?
5) Image creation
Created succefully using Windows AIK and stored at APPSERVER (BBSA01) in <install directory>/NSH/tftproot
6) default image configuration
Done successfully as follows
in above image find YES for default boot image
System package created and then PROVISIONING JOB.