Re: sysprep
From: Mike Kolitz (mikekol_at_idontlikespam.mvps.org)
Date: 03/19/04
- Next message: Tom Stout: "Win XP Pro startup"
- Previous message: Mike Kolitz: "Re: XP pro onto another computer?"
- In reply to: Woody: "sysprep"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Mar 2004 00:32:08 -0600
Woody,
You can check to see if your networking is setup properly during the setup
process by starting a command prompt window. You can do this by pressing
Shift+F10 on the keyboard during minisetup. From there, run ipconfig to
determine whether or not Windows is installing the drivers for your adapter,
or getting an IP address at all.
If not, you may need to add drivers for your new NIC to your Windows image.
-- Mike Kolitz MCSE 2000 MS-MVP - Windows Setup and Deployment Remember to check Windows Update often, and apply the patches marked as Critical! http://windowsupdate.microsoft.com Protect your PC! http://www.microsoft.com/security/protect "Woody" <anonymous@discussions.microsoft.com> wrote in message news:D9C5755F-3113-4482-BA1B-1E7DB0A0E51E@microsoft.com... > We use sysprep to "minisetup" a new pc for a user and set it with a unique machine name to add it to the domain. We usually use laptops that use a 3com(3c90x) network card adapter, but we are now using laptops with a Broadcom adapter. > > Anyway, now when we run sysprep on the new laptops, it can't seem to join the domain, sort of like it can't find the domain controller. Is it because of a "non-standard" net adapter? If so, is there a way around this? Can drivers be loaded for the card, if this is the problem, for use by sysprep? Any input would be greatly appreciated.
- Next message: Tom Stout: "Win XP Pro startup"
- Previous message: Mike Kolitz: "Re: XP pro onto another computer?"
- In reply to: Woody: "sysprep"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
