Using 2003 RIS Server to deploy XP SP2 image (with all drivers installed)

Image deploys ok to machine but when the 'mini-setup', sysprep runs for the first time it takes upto 9 mins for windows to install the network components.

After this long pause, the machine successfully joins the domain.

The machine in question is a HP nc6220 laptop which as a Broadcom NIC, Intel Pro/Wireless 2200BG NIC and integrated Bluetooth.

Any ideas how I can cut down on the amount of time it takes to install the networking components?

nothing comes to mind except checking that you have the correct entries in the sysprep.inf for naming resolution. DNS, WINS, Gate and so on...

Best Regards

Tha Sausage Eater..

There is nothing specific in the sysprep.inf, I'm only trying to install 'Typical Settings' using DHCP to get ip address etc..

Using 2003 RIS Server to deploy XP SP2 image (with all drivers installed)

Image deploys ok to machine but when the 'mini-setup', sysprep runs for the first time it takes upto 9 mins for windows to install the network components.

After this long pause, the machine successfully joins the domain.

The machine in question is a HP nc6220 laptop which as a Broadcom NIC, Intel Pro/Wireless 2200BG NIC and integrated Bluetooth.

___

Sorry - I don't understand.

If you're using the RIS server to deploy XPSP2 images, where does Sysprep come into this?

You're using RIS to deploy the image, then Sysprepping the result for some reason? Why?

I think what he's referring to is RIPrep. Basically it allows RIS to deploy a canned image kind of like sysprep does with CD/DVD media. I don't like procedure at all, but it does seem to have quite a following.

to Br4tt3 - think the same

If you dhcp server send to deploying machine only IP - big reason to long resolveing NAME, IP of Primary Domain Controller. Try to manually set network parameters like:

[MS_TCPIP parameters]

DeadGWDetectDefault = No

DNSDomain = fabrikam.com

DNSSuffixSearchOrder = server1.fabrikam.com, fabrikam.com

DontAddDefaultGatewayDefault = No

EnableICMPRedirect = No

EnableLMHosts = Yes

EnableSecurity = Yes

ScopeID = REDMOND

SyncDomainWithMembership = 1

UseDomainNameDevolution = No

[params.MS_TCPIP.Adapter01]

SpecificTo = Adapter01

DisableDynamicUpdate = No

EnableAdapterDomainNameRegistration = No

DefaultGateway = 193.1.1.1

DHCP = Yes

DHCPClassId = abc

DNSDomain = fabrikam.com

DNSServerSearchOrder = server1.fabrikam.com, fabrikam.com

IPAddress = 193.1.1.33,193.1.1.34

IpAllowedProtocols = 10

NetBIOSOptions = 1

TcpAllowedProtocols = 10

UdpAllowedProtocols = 10

SubnetMask = 193.1.1.255

WINS = Yes

WINSServerList = 193.1.1.95,193.1.1.97

---

And another solution - disable Intel Pro/Wireless 2200BG NIC and integrated Bluetooth and test after this.

to bluescreens

"where does Sysprep come into this?" at final stage, then resealing deployed OS