checks Posted March 23, 2006 Share Posted March 23, 2006 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? Link to comment Share on other sites More sharing options...
Br4tt3 Posted March 23, 2006 Share Posted March 23, 2006 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 RegardsTha Sausage Eater.. Link to comment Share on other sites More sharing options...
checks Posted March 23, 2006 Author Share Posted March 23, 2006 There is nothing specific in the sysprep.inf, I'm only trying to install 'Typical Settings' using DHCP to get ip address etc.. Link to comment Share on other sites More sharing options...
bluescreens Posted March 28, 2006 Share Posted March 28, 2006 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? Link to comment Share on other sites More sharing options...
RogueSpear Posted March 28, 2006 Share Posted March 28, 2006 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. Link to comment Share on other sites More sharing options...
dk_ Posted March 29, 2006 Share Posted March 29, 2006 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 = NoDNSDomain = fabrikam.comDNSSuffixSearchOrder = server1.fabrikam.com, fabrikam.comDontAddDefaultGatewayDefault = NoEnableICMPRedirect = NoEnableLMHosts = YesEnableSecurity = YesScopeID = REDMONDSyncDomainWithMembership = 1UseDomainNameDevolution = No[params.MS_TCPIP.Adapter01]SpecificTo = Adapter01DisableDynamicUpdate = NoEnableAdapterDomainNameRegistration = NoDefaultGateway = 193.1.1.1DHCP = YesDHCPClassId = abcDNSDomain = fabrikam.comDNSServerSearchOrder = server1.fabrikam.com, fabrikam.comIPAddress = 193.1.1.33,193.1.1.34IpAllowedProtocols = 10NetBIOSOptions = 1TcpAllowedProtocols = 10UdpAllowedProtocols = 10SubnetMask = 193.1.1.255WINS = YesWINSServerList = 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 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now