"The disk management services could not complete the operation"

I read this should happen when you try to run diskpart.exe from a harddisk installation of bartpe, but that is not the case for me.

Does anyone know how I can run diskpart in this situation?

Cheers

Complete error: Error Message: The Operating System Image You Selected Does Not Contain the Necessary Drivers for Your Network Adapter. Try Selecting a Different Operating System Image. If the Problem Persists, Contact Your System Administrator.

im using windows server 2003 What to do now..

Basically WDS was installed on the Domain Controller when SP2 was installed. Not knowing anything about WDS and with Microsoft kindly switching to WDS from RIS a bit of panic set in. In haste the network administrator I am trying to support removed RIS and now WDS on that server is not in mixed mode so the old RIS images are useless.

They have now set WDS up on a different server but I don't seem to be able to get it to pick up an address from the DHCP server and PXE boot to RIS/WDS. I have pointed option 066 in DHCP to the ip address of the other server and option 067 to pxeboot.com - but I am a little stuck and wondered if anybody else was running it successfully this way.

Any help will be very much appreciated.

Andy (Morphears)

I get to the point where "Setup is starting Windows" and I see the bootvid, but moments later I get a BSOD with the following information:

PROCESS1_INITIALIZATION_FAILED

STOP: 0x6b (0xC...3B, 0x2, 0x0, 0x0) (Shortened for your viewing pleasure )

The code 3B indicates that STATUS_OBJECT_PATH_SYNTAX_BAD [0xC000003B] :: The object path component was not a directory object.

Running Wireshark, I captured data that indicates that Windows Setup is in fact querying my Samba server and logging in (with no password, something that was explicitly allowed) but stops there. Attached are the details in text format.

Packets.txt

Problem is, that even though the request does seem valid (mostly), Windows Setup chokes for no apparent reason. Any ideas on how to fix this? I'm quite lost on anything else I can do for this...

Thanks

Jason

having a few problems with my RIS install. The setup completes but for some reason when it comes to running [GuiRunOnce] in the .sif file or using the cmdlines.txt RunOnceEx.cmd method I get the same issue saying that it can't find

"%systemdrive%\Install\<folder>\myfile.bat". When i come to look at C:\ once the windows install has completed the "Install" folder is missing but.... the files do copy across just after the computer has finished formatting just before you get the GUI stage of the windows xp installation.

Any help would be greatly appricated.

Please find attached the .sif files the install is using the ristndrd.sif and rinorpart.sif files are located in the i386 and the (templatesfolder)ristndrd.sif file is located in the templates folder within the i386 fold.er

(templatesfolder)ristndrd.sif

rinorprt.sif

ristndrd.sif

Here is my issue and failed understanding.

The driver files are for the 650 and 690 use the same names and I know I'm messing something up and this maybe it.

SYMMPI.xxx

I have added the new drivers for the 690 to the txtsetup.sif so that it now will format and copy files to it successfully but when windows loads to setup it gives me the famous blue screen error 07b.

I have added the 690 drivers to my drivers folder for windows but I can't figure out what is going on here. I'm guessing my txtsetup.sif is not perfect.

Here is what I have:

for the 690 I created a folder:

i386\DRV\003 - Copied all the driver files into this folder.

txtsetup.sif

[sourceDisksNames.x86]

1986 = %cdname%,%cdtagfilei%,,"\i386\DRV\003"

[sourceDisksFiles.x86]

iaahci.cat = 1,,,,,,3_,4,1,,,1,4

iaahci.inf = 1,,,,,,3_,4,1,,,1,4

iastor.cat = 1,,,,,,3_,4,1,,,1,4

iastor.inf = 1,,,,,,3_,4,1,,,1,4

iaStor.sys = 1,,,,,,4_,4,1,,,1,4

iastor.sys = 1,,,,,,3_,4,1,,,1,4

delpseud.inf = 1986,,,,,,,1986,0,0

mpixp32.cat = 1986,,,,,,,1986,0,0

symmpi.inf = 1,,,,,,3_,4,1,,,1,4

symmpi.inf = 1986,,,,,,,1986,0,0

symmpi.sys = 1,,,,,,4_,4,1,,,1,4

symmpi.sys = 1,,,,,,3_,4,1,,,1,4

symmpi.sys = 1986,,,,,,,1986,0,0

symmpi.tag = 1,,,,,,3_,4,1,,,1,4

symmpi.tag = 1986,,,,,,,1986,0,0

[HardwareIdsDatabase]

PCI\VEN_1000&DEV_0054&SUBSYS_1F041028 = "symmpi"

PCI\VEN_1000&DEV_0054&SUBSYS_1F061028 = "symmpi"

PCI\VEN_1000&DEV_0054&SUBSYS_1F071028 = "symmpi"

PCI\VEN_1000&DEV_0054&SUBSYS_1F081028 = "symmpi"

PCI\VEN_1000&DEV_0054&SUBSYS_1F091028 = "symmpi"

PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028 = "symmpi"

PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028 = "symmpi"

PCI\VEN_1000&DEV_0058&SUBSYS_1F101028 = "symmpi"

PCI\VEN_1000&DEV_0058&SUBSYS_021D1028 = "symmpi"

PCI\VEN_1000&DEV_0621 = "symmpi"

PCI\VEN_1000&DEV_0622 = "symmpi"

PCI\VEN_1000&DEV_0624 = "symmpi"

PCI\VEN_1000&DEV_0626 = "symmpi"

PCI\VEN_1000&DEV_0628 = "symmpi"

PCI\VEN_1000&DEV_0030 = "symmpi"

PCI\VEN_8086&DEV_2922&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2829&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_282A&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor"

[sCSI.Load]

symmpi = symmpi.sys,4

iaStor = iaStor.sys,4

[FileFlags]

symmpi.sys = 16

[sCSI]

symmpi = "LSI Logic PCI Fibre Channel Host Adapter"

symmpi = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)"

symmpi = "Dell SAS 5x and SAS 6x Controller Driver (Windows XP 32-bit)"

iaStor = "Intel® ICH9 SATA AHCI Controller (Desktop/Server/Workstation)"

iaStor = "Intel® ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)"

iaStor = "Intel® 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation)"

iaStor = "Intel® 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)"

iaStor = "Intel® 82801HEM SATA RAID Controller (Mobile ICH8M-E)"

iaStor = "Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"

iaStor = "Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"

iaStor = "Intel® 82801GHM SATA RAID Controller (Mobile ICH7MDH)"

iaStor = "Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)"

iaStor = "Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)"

iaStor = "Intel® 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"

iaStor = "Intel® 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"

690 txtsetup.oem

# txtsetup.oem - version XP.9 for SYMMPI Windows XP driver

#

# ***********************************************************************

# *

# Copyright 2006 LSI Logic, Corp. All rights reserved. *

# *

# This file is property of LSI Logic, Corp. and is licensed for *

# use as is. The receipt of or posession of this file does not *

# convey any rights to modify its contents, in whole, or in part, *

# without the specific written consent of LSI Logic, Corp. *

# *

# ***********************************************************************

#

# format for txtsetup.oem.

#

# General format:

#

# [section]

# key = value1,value2,...

#

#

# The hash ('#') introduces a comment.

# Strings with embedded spaces, commas, or hashes should be double-quoted

#

[Disks]

# This section lists all disks in the disk set.

#

# <description> is a descriptive name for a disk, used when

# prompting for the disk

# <tagfile> is a file whose presence allows setup to recognize

# that the disk is inserted.

# <directory> is where the files are located on the disk.

#

d1 = "Dell SAS 5x and SAS 6x Controller Driver (Windows XP 32-bit)",\symmpi.tag,\

[Defaults]

# This section lists the default selection for each 'required'

# hardware component. If a line is not present for a component,

# the default defaults to the first item in the [<component_name>]

# section (see below).

#

# <component_name> is one of computer, display, keyboard, mouse, scsi

# <id> is a unique <within the component> string to be associated

# with an option.

scsi = DELL_SAS

[scsi]

# This section lists the options available for a particular component.

#

# <id> is the unique string for the option

# <description> is a text string, presented to the user in a menu

# <key_name> gives the name of the key to be created for the component in

# HKEY_LOCAL_MACHINE\ControlSet001\Services

DELL_SAS = "Dell SAS 5x and SAS 6x Controller Driver (Windows XP 32-bit)",symmpi

[HardwareIds.scsi.DELL_SAS]

id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F041028", "symmpi"

id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F061028", "symmpi"

id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F071028", "symmpi"

id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F081028", "symmpi"

id = "PCI\VEN_1000&DEV_0054&SUBSYS_1F091028", "symmpi"

id = "PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028", "symmpi"

id = "PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028", "symmpi"

id = "PCI\VEN_1000&DEV_0058&SUBSYS_1F101028", "symmpi"

id = "PCI\VEN_1000&DEV_0058&SUBSYS_021D1028", "symmpi"

# This section lists the files that should be copied if the user

# selects a particular component option.

#

# <file_type> is one of driver, port, class, dll, hal, inf, or detect.

# See below.

# <source_disk> identifies where the file is to be copied from, and must

# match en entry in the [Disks] section.

# <filename> is the name of the file. This will be appended to the

# directory specified for the disk in the [Disks] section to form the

# full path of the file on the disk.

[Files.scsi.DELL_SAS]

driver = d1,symmpi.sys,SYMMPI

inf = d1,symmpi.inf

inf = d1,delpseud.inf

catalog = d1,mpixp32.cat

[Config.SYMMPI]

# This section specifies values to be set in the registry for

# particular component options. Required values in the services\xxx

# key are created automatically -- use this section to specify additional

# keys to be created in services\xxx and values in services\xxx and

# services\xxx\yyy.

#

# <key_name> is relative to the services node for this device.

# If it is empty, then it refers to the services node.

# If specified, the key is created first.

# <value_name> specifies the value to be set within the key

# <value_type> is a string like REG_DWORD. See below.

# <value> specifies the actual value; its format depends on <value_type>

value = Parameters\PnpInterface,5,REG_DWORD,1

650 txtsetup.oem

# txtsetup.oem - version XP32.5 for SYMMPI Windows drivers (Windows XP)

#

# ***********************************************************************

# *

# Copyright 2002 LSI Logic, Corp. All rights reserved. *

# *

# This file is property of LSI Logic, Corp. and is licensed for *

# use as is. The receipt of or posession of this file does not *

# convey any rights to modify its contents, in whole, or in part, *

# without the specific written consent of LSI Logic, Corp. *

# *

# ***********************************************************************

#

# format for txtsetup.oem.

#

# General format:

#

# [section]

# key = value1,value2,...

#

#

# The hash ('#') introduces a comment.

# Strings with embedded spaces, commas, or hashes should be double-quoted

#

[Disks]

# This section lists all disks in the disk set.

#

# <description> is a descriptive name for a disk, used when

# prompting for the disk

# <tagfile> is a file whose presence allows setup to recognize

# that the disk is inserted.

# <directory> is where the files are located on the disk.

#

d1 = "LSI Logic Ultra320 1020/1030 Driver (XP)", \symmpi.tag, \

[Defaults]

# This section lists the default selection for each 'required'

# hardware component. If a line is not present for a component,

# the default defaults to the first item in the [<component_name>]

# section (see below).

#

# <component_name> is one of computer, display, keyboard, mouse, scsi

# <id> is a unique <within the component> string to be associated

# with an option.

scsi = SYMMPI_XP32

[scsi]

# This section lists the options available for a particular component.

#

# <id> is the unique string for the option

# <description> is a text string, presented to the user in a menu

# <key_name> gives the name of the key to be created for the component in

# HKEY_LOCAL_MACHINE\ControlSet001\Services

SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)",symmpi

[HardwareIds.scsi.SYMMPI_XP32]

id = "PCI\VEN_1000&DEV_0621", "symmpi"

id = "PCI\VEN_1000&DEV_0622", "symmpi"

id = "PCI\VEN_1000&DEV_0624", "symmpi"

id = "PCI\VEN_1000&DEV_0626", "symmpi"

id = "PCI\VEN_1000&DEV_0628", "symmpi"

id = "PCI\VEN_1000&DEV_0030", "symmpi"

# This section lists the files that should be copied if the user

# selects a particular component option.

#

# <file_type> is one of driver, port, class, dll, hal, inf, or detect.

# See below.

# <source_disk> identifies where the file is to be copied from, and must

# match en entry in the [Disks] section.

# <filename> is the name of the file. This will be appended to the

# directory specified for the disk in the [Disks] section to form the

# full path of the file on the disk.

[Files.scsi.SYMMPI_XP32]

driver = d1,symmpi.sys,SYMMPI

inf = d1,symmpi.inf

catalog = d1,mpixp32.cat

[Config.SYMMPI]

# This section specifies values to be set in the registry for

# particular component options. Required values in the services\xxx

# key are created automatically -- use this section to specify additional

# keys to be created in services\xxx and values in services\xxx and

# services\xxx\yyy.

#

# <key_name> is relative to the services node for this device.

# If it is empty, then it refers to the services node.

# If specified, the key is created first.

# <value_name> specifies the value to be set within the key

# <value_type> is a string like REG_DWORD. See below.

# <value> specifies the actual value; its format depends on <value_type>

value = Parameters\PnpInterface,5,REG_DWORD,1

I can add these files the way Microsoft recommends in your RIS sif and then in the textmode folder and it works just fine.

I;ve used RIS in a previous job and we're just starting to use it here for our installations. I prefer it to Ghost, which is our current method. I have a batch of 10 Compaq Mini 110c Netbooks, which will be soon be followed by an additional 150 units! Having spent some time working on this we have the following:

Windows XP Pro SP3 installation from fresh download from Microsoft Licensing site

RIS install with modifications to include NIC and SATA drivers

Install completes and we get BSOD on reboot after windows portion

We've made progress from yesterday, when we couldn't get past initial RIS screens. My question now is what can be causing the BSOD after windows reboot. The message flashes for a fraction of a second and starts "A problem has been detected..." The screen only goers as far as "Technical informa." at which point screen goes blank. I can;t really get anything useful from this to try and work through the problem. I've included NIC, SATA and Display drivers in OemInstallPaths. My instinct is that it's a display related problem.

I get the same issue if I make it full unattended or if I don't. If I do Safe Mode with Command Prompt on subesequent reboots the last driver that loads is ...\System32\Drivers\Mup.sys.

Any thoughts?

issue we're having is, we build & sysprep the client PC, however, we are unable to delete the account created for preparing the PC, so what happens is:

we create an account called "TEMP", login & do all the updates, install our basic app package (avast free, openoffice, itunes etc), then run sysprep. when we deploy the image & create a new user account "OWNER" for example, when we login, XP Home logs us in as "TEMP"!!

any idea on how to remove all user info in the home edition like you can on pro?? not a problem with Vista or 7, just XP Home (of which a great deal of our customer base still use, cos they dont see point in changing from somert they've used for 10 years dammit!!)

Cheers!!

I've been using the TFTP32 based RIS install for quite some time and it worked perfectly for my scenario. I used OEM distribution share to automatically install softwares, updates and other things. The problem im facing now is that i've almost 10 different WinXP setups ranging from WinXP SP1 to SP3. In order to use OEM folders, i have to copy the same OEM folder in all 10 WinXP directories so that it can be copied during network install.

To conserve space and make my life easier, i experiment to rename the "i386" directory so that i can put all my WinXP installation in same base directory having rename their i386 folder. After some trial and error (patching setupldr.bin, editing txtsetup.sif and dosnet.inf) i was able to achieve this to some extent.

The textmode setup works fine and copies everything to hardisk but as soon as the GUI Mode setup starts, it prompt me for the location of the i386 directory. It shows me that it is searching "C:\$win_nt$.~ls\i386" while my original files are in "C:\$win_nt$.~ls\i387" directory (i have renamed i386 to i387). Now i want to fix this but im unable to find the location where it is pulling this address from.

If someone can provide any help, i shall be grateful to him.

Thanks.

the pxe-boot works fine, the pc receives an ip from dhcp

the wds server is contacted and i get to see to boot-menu from my wds server

then it goes wrong: when I select a wim-file to boot i get an error screen saying 0x000000f - a required device is missing (???)

so the wim-file is not loaded to the pc

any ideas??

on other pc's everything works fine.

I don't think it's a network issue because we replaced the pc's and with the 'old' pc's pxe boot worked...

The strangest thing is that sometimes the wim-file does load, and i don't see any reason why (I didn't change a thing).

please help, I'm stuck here

My initial idea is to put office in a folder on the flat image....ex: $oem$\install\applications\office\2003\ but with all the reading I have done I really haven't seen a better way, can it be compressed to save space?

My goal is to have a completely automated flat image which I'm doing pretty good for the start of it, I keep reading around on the unattended install area to get all the info I can lol.

net localgroup Administrators XXXX-Admins /add>>c:\postinstall\PostInstallReport.txt error message "System error 1789: The trust relationship between this workstation and the primary domain failed."

net localgroup "Remote Desktop Users" XXXX-Admins /add>>c:\postinstall\PostInstallReport.txt error message "System error 1789: The trust relationship between this workstation and the primary domain failed."

net localgroup Administrators XXXX-XXXX /add>>c:\postinstall\PostInstallReport.txt error message "System error 1789: The trust relationship between this workstation and the primary domain failed."

Basically, I copy an XP CD on to my PC, use nLite to integrate drivers, updates, applications etc. Insert the RIS files (and Answer file) in the I386 folder, copy to RIS server and away you go! It's always worked no problems and my current out of date image also works fine. However, when I tried to create a new image using the same method I've done for years, it formats the hard drive and then gives me an error saying setup cannot format this partition. Yet, if I create an unattended CD/DVD out of the same source (having removed the RIS files and replace with WINNT.sif) it works fine!

In addition to the mayhem I have copied a vanilla XP image, no integration of nothing at all except network card drivers for my VM and it gives the exact same problem!

Any ideas what could be going on here?

Basically, the DC7100 will RIS fine, if I don't have anything but -

[MassStorageDrivers]

"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = Retail

If I go and add -

"Intel® ICH8M-E/ICH9M-E/5 Series SATA RAID Controller" = OEM

It blue screens with 0x0000007E

If I remove the line it builds fine.

Below is what my TXTSETUP.OEM looks like -

; Copyright © 2003-10 Intel Corporation

;#############################################################################

;#

;# Filename: TXTSETUP.OEM

;#

;#############################################################################

[Disks]

disk1 = "Intel® Rapid Storage Technology Driver", iaStor.sys, \

[Defaults]

scsi = iaStor_8ME9ME5

;#############################################################################

[scsi]

iaStor_8ME9ME5 = "Intel® ICH8M-E/ICH9M-E/5 Series SATA RAID Controller"

;#############################################################################

[Files.scsi.iaStor_8ME9ME5]

driver = disk1, iaStor.sys, iaStor

inf = disk1, iaStor.inf

catalog = disk1, iaStor.cat

;#############################################################################

[Config.iaStor]

value = "", tag, REG_DWORD, 1b

value = "", ErrorControl, REG_DWORD, 1

value = "", Group, REG_SZ, "SCSI Miniport"

value = "", Start, REG_DWORD, 0

value = "", Type, REG_DWORD, 1

;#############################################################################

; iaAHCI.inf

[HardwareIds.scsi.iaStor_8ME9ME5]

id = "PCI\VEN_8086&DEV_282A&CC_0104","iaStor"

Can you guys see anything wrong with what I am doing? How come the DC7100 can build with no mass storage drivers?

Thank you.

After digging my a** off @ Google for an answer, I've thrown the white towel and came here for an answer =).

I would like to integrate DP's drivers into my RIS image, but for some reason i cannot get it to work.

I'm using:

- DP Base 8.12.5

- RVM Integrator 1.6.1 beta 2.1 (Is this really the newest?)

- Autoimage 0.9.8

While i managed to integrate the update pack(latest post-sp3 QFE) and 2 add-ons packs( wmp11 & ie8 + updates by yum), the DP doesn't get integrated.

I got about 90% of all the drivers i need and use, but I would like to have the other 10% covered by a DP so i wont waste time.

I've read somewhere that DP cannot be integrated into an existing RIS image. If that's the case, how would i do it? Create a new one and slipstream it with nlite?

Any help would be appreciated.

i have and xp disc which someone has given me which has updates within it and on doing "risetup.exe" there is a folder in d:\Remoteinstall\Setup\English\WINDOWS\i386\svcpack - Can I remove this \svcpack folder to make sure this is a flat basic xp install. As RIS only installs basic flat xp installs remotely due to the site being remote and being pxeclient?

Let me know before I remove this folder as Im not sure if it will affect the image just created on the RIS server

ive was successful in the past when running ris on its own separate server but connecting via AD and for DNS to a DC.

Ran risetup in order to just make a basic copy of an xp image on the RIS server

i can always get the Remote install tabe on the RIS DC where i can then locate my xp image installed.

i can always select F12 and it does prompt for my logon details

This is my issue, no matter if i use an administrators account or create a user with domain admin privileges it still says logon issue at my client pxeclient pc. why???????? 3 weeks works down the drain.

Thanks

Jason

This only occurs with 2003 server installed through RIS, no of the other OS's has this issue (XP, Vista, Windows 7 both x86 and x64)

If 2003 is installed via cd the msi with the /fav switch installs without incident.

I've reinstalled 3.1, and even installed 4.5 but the same failure occurs.

Any suggestions?

Thanks

I've bought 40 computers, HP DX7500, and I created an image for those computers. I am having a problem with the Intel Adapter (Gigabit Model: 82567V-2) -

I've read the README file from the INTELXP package (RIS_INF's folder) - And I did step by step from the README file.

What I did is this:

I've created the NIC folder in: [iMAGE_ROOT]\$oem$\$1\Drivers\NIC

and I've added those files:

e1000msg.dll

e1000nt5.din

E1000NT5.SYS

e1000325.cat

e1000325.din

e1000325.inf

E1000325.sys

nicco2.dll

NicInstY.dll

And I've added the files that i've been told to add from the README to the: [iMAGE_ROOT]\i386 folder.

I've deleted all the *.PNF files from the i386 folder also, changed the riprep.sif file (Added the line: OemPnpDriversPath = \Install\Drivers\NIC)

I did a restart to the Service and also to the Windows Deployment Service, but I am still getting the error:

"The operating system image you selected does not contain the necessary drivers for your network adapter"

I am very familiar with the RIS, but I cannot resolve this problem. I've tried everything, even tried to forward it to the Intel 100 Ethernet's driver folder.

Any one have a solution for this case?

Thank you very much! ! !

I've recently installed a RIS on Windows 2003 Server Standard Edition.

The problem that I'm facing is that the RIS server doesn't increment my computer number. So every time I install a new pc, it has the same name as I configured it into Remote Installation Services Properties.

Is there a way that I can enter manually the computer number when RIS starts the installation?

My ristndrd.sif file looks like this:

[data]

floppyless = "1"

msdosinitiated = "1"

OriSrc = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

OriTyp = "4"

LocalSourceOnCD = 1

[setupData]

OsLoadOptions = "/noguiboot /fastdetect"

SetupSourceDevice = "\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

[unattended]

OemPreinstall = yes

DriverSigningPolicy = Ignore

OemPnpDriversPath = \Drivers\A01;\Drivers\C01;\Drivers\N01;\Drivers\V01

FileSystem = LeaveAlone

ExtendOEMPartition = 0

TargetPath = \WINDOWS

OemSkipEula = yes

InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"

LegacyNIC = 1

UnattendMode = "ReadOnly"

OemSkipEula = yes

[userData]

FullName = "%USERFIRSTNAME% %USERLASTNAME%"

OrgName = "%ORGNAME%"

ComputerName = %MACHINENAME%

ProductID = "win-serial"

[GuiUnattended]

OemSkipWelcome = 1

OemSkipRegional = 1

TimeZone = %TIMEZONE%

AdminPassword = "password"

[TapiLocation]

CountryCode = 40

AreaCode = 268

[RegionalSettings]

InputLocale = 0409:00000409

SystemLocale = 0409

UserLocale = ”0409

[Display]

BitsPerPel = 16

XResolution = 800

YResolution = 600

VRefresh = 60

[Networking]

[NetServices]

MS_Server=params.MS_PSched

[identification]

JoinDomain = RO

MachineObjectOU = "%MACHINEOU%"

CreateComputerAccountInDomain = Yes

DoOldStyleDomainJoin = Yes

[RemoteInstall]

Repartition = Yes

UseWholeDisk = Yes

[OSChooser]

Description ="Microsoft Windows XP Professional SP2"

Help ="Automatically installs Microsoft Windows XP Professional without prompting the user for input."

LaunchFile = "%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"

ImageType =Flat

Version="5.1 (2600)"

I saw that in ?:\RemoteInstall\OSChooser\English is a file called custom.osc, but I don't know how to add this file into RIS setup process.

Did anybody encountered this issue?

Thanks in advance.