Sysprep v1.1 Error - Windows 2000

bigJcee · 06-28-2005, 08:23 AM

Hello everyone, this is my first post here. Hopefully I can receive help for the problem I am running into.

I am attempting to configure Sysprep v1.1 for use on Windows 2000 SP4 PC's. I have Sysprep v2.0 working on our Windows XP SP2 PC's, but I'm running into trouble with the Windows 2000 boxes.

Sysprep v1.1 runs fine until it reaches the point where it attempts to add the PC to our domain. The machine will sit at the screen where it tries to add the PC to the domain, and after 2-3 minutes, the following error is displayed:

Network Configuration
The workstation driver is not installed. Would you like to proceed for now, and try joining a domain later?

Here is what the pertinent section of my sysprep.ini file looks like, with our organization information removed of course:

[Identification]
JoinDomain = ourdomain.org
DomainAdmin = ourdomain.org\administrator
DomainAdminPassword = ourdomain.org\password

I have also tried the following variation on this file, with the same results:

[Identification]
JoinDomain = ourdomain.org
DomainAdmin = ourdomain.org\administrator
DomainAdminPassword = password

I've searched the web extensively, as well as Microsoft's website in particular, to no avail. Some documents seem to indicate that this may be a problem with the Windows install itself, and that a reinstall is warranted. However, I am able to manually (from within My Computer > Properties) add the machine to the domain in question. Additionally, the error is repeatable on different PC's using different Ghosted images. All of this leads me to believe there is a problem with how my sysprep.ini file is formatted.

If anyone could offer me a solution for this I'd really appreciate it. :)

bigJcee

bigJcee · 06-28-2005, 09:19 AM

Sorry, the file mentioned above should read sysprep.inf, not syprep.ini. Thanks.

bigJcee

johnz · 07-19-2005, 10:03 PM

Had this one recently. One of two things fixed it.

I believe Symantec Antivirus (Ent Ed) v9 screwed with the process. Uninstalled v9 then took an image. All worked OK.

The other possibility (less likely) is that the machine was not removed from an AD domain prior to sysprepping.

kevinbelonzi · 07-21-2005, 05:34 AM

I am having an issue with updating a current Windows 2000 image that I have. The issue that I'm seeing is that the sysprep will run fine. After the new hard drive is imaged, it comes up to the screen where you name the machine and the keyboard and mouse don't work.

Has anyone seen this before. It never caused a problem with the original image and I did nothing with updating the sysprep file from the original.

06-28-2005, 08:23 AM	#1 (permalink)
bigJcee Registered User Join Date: Jun 2005 Posts: 2 OS: Windows 2000	Sysprep v1.1 Error - Windows 2000 Hello everyone, this is my first post here. Hopefully I can receive help for the problem I am running into. I am attempting to configure Sysprep v1.1 for use on Windows 2000 SP4 PC's. I have Sysprep v2.0 working on our Windows XP SP2 PC's, but I'm running into trouble with the Windows 2000 boxes. Sysprep v1.1 runs fine until it reaches the point where it attempts to add the PC to our domain. The machine will sit at the screen where it tries to add the PC to the domain, and after 2-3 minutes, the following error is displayed: Network Configuration The workstation driver is not installed. Would you like to proceed for now, and try joining a domain later? Here is what the pertinent section of my sysprep.ini file looks like, with our organization information removed of course: [Identification] JoinDomain = ourdomain.org DomainAdmin = ourdomain.org\administrator DomainAdminPassword = ourdomain.org\password I have also tried the following variation on this file, with the same results: [Identification] JoinDomain = ourdomain.org DomainAdmin = ourdomain.org\administrator DomainAdminPassword = password I've searched the web extensively, as well as Microsoft's website in particular, to no avail. Some documents seem to indicate that this may be a problem with the Windows install itself, and that a reinstall is warranted. However, I am able to manually (from within My Computer > Properties) add the machine to the domain in question. Additionally, the error is repeatable on different PC's using different Ghosted images. All of this leads me to believe there is a problem with how my sysprep.ini file is formatted. If anyone could offer me a solution for this I'd really appreciate it. :) bigJcee Last edited by bigJcee : 06-28-2005 at 08:29 AM.

07-19-2005, 10:03 PM	#3 (permalink)
johnz Registered User Join Date: Jul 2005 Posts: 1 OS: XP	Re: Problems with sysprep Had this one recently. One of two things fixed it. I believe Symantec Antivirus (Ent Ed) v9 screwed with the process. Uninstalled v9 then took an image. All worked OK. The other possibility (less likely) is that the machine was not removed from an AD domain prior to sysprepping.

07-21-2005, 05:34 AM	#4 (permalink)
kevinbelonzi Registered User Join Date: Jul 2005 Posts: 1 OS: Windows XP Professional	Another Sysprep problem I am having an issue with updating a current Windows 2000 image that I have. The issue that I'm seeing is that the sysprep will run fine. After the new hard drive is imaged, it comes up to the screen where you name the machine and the keyboard and mouse don't work. Has anyone seen this before. It never caused a problem with the original image and I did nothing with updating the sysprep file from the original.

06-28-2005, 09:19 AM	#2 (permalink)
bigJcee Registered User Join Date: Jun 2005 Posts: 2 OS: Windows 2000	Sorry, the file mentioned above should read sysprep.inf, not syprep.ini. Thanks. bigJcee