Sysprep Joining Domain

G

Guest

I've created an XP-Pro image, and i've gotten everything to work sofar,
except for the adding to the domain part. Here is my sysprep.inf so far:

;SetupMgrTag

[Unattended]
OemSkipEula = Yes
OemPnPDriversPath
= "Drivers\865\Audio;Drivers\865\Nic;Drivers\865\video;Drivers\845\NIC;Drivers\845\audio"

[GuiUnattended]
AdminPassword = "********"
EncryptedAdminPassword = No
OEMSkipRegional = 1
TimeZone = 40
OemSkipWelcome = 1

[UserData]
ComputerName =
ProductID = **********************
FullName = "joe"
OrgName = "shmo"

[Display]
BitsPerPixel = 32
Vrefresh = 75
Xresolution = 1024
YResolution = 768


[SetupMgr]
DistFolder = C:\sysprep\i386
DistShare = whistlerdist


[Networking]


[Identification]
JoinDomain = JOE

[sysprepcleanup]

What my goal is, to have it run thru mini-setup, ask for a product key, ask
what type of network settings (Typical or Custom), and to join the "JOE"
domain with out using an automatic login.
What I am having problems with, is getting mini-setup to ask me to choose
the network settings (right now it just installs the defaults), and joining
the JOE domain, it stops on the "workgroup or computer domain" screen and has
"JOE" in the domain field, and when I click NEXT, it does prompt me for a
username to add to the domain, but after I enter the information it just sits
there and hangs, then about 20-30 mins later it comes up with an error "the
domain could not be accessed due to networking problems.". I've checked all
of my network connections, and it is generating a new SID for the computer.

I've tried alot of possible sou
 
G

Guest

You may have run into the fact that your network connections are not fully
active until the next reboot.

To work around this I use a runonce script that autologs on to the machine
after sysprep does it's reboot. The script joins the domain using embedded
credentials.
 
G

Guest

but that would be a security risk, wouldn't it?

Jockel said:
You may have run into the fact that your network connections are not fully
active until the next reboot.

To work around this I use a runonce script that autologs on to the machine
after sysprep does it's reboot. The script joins the domain using embedded
credentials.

Kezden said:
I've created an XP-Pro image, and i've gotten everything to work sofar,
except for the adding to the domain part. Here is my sysprep.inf so far:

;SetupMgrTag

[Unattended]
OemSkipEula = Yes
OemPnPDriversPath
= "Drivers\865\Audio;Drivers\865\Nic;Drivers\865\video;Drivers\845\NIC;Drivers\845\audio"

[GuiUnattended]
AdminPassword = "********"
EncryptedAdminPassword = No
OEMSkipRegional = 1
TimeZone = 40
OemSkipWelcome = 1

[UserData]
ComputerName =
ProductID = **********************
FullName = "joe"
OrgName = "shmo"

[Display]
BitsPerPixel = 32
Vrefresh = 75
Xresolution = 1024
YResolution = 768


[SetupMgr]
DistFolder = C:\sysprep\i386
DistShare = whistlerdist


[Networking]


[Identification]
JoinDomain = JOE

[sysprepcleanup]

What my goal is, to have it run thru mini-setup, ask for a product key, ask
what type of network settings (Typical or Custom), and to join the "JOE"
domain with out using an automatic login.
What I am having problems with, is getting mini-setup to ask me to choose
the network settings (right now it just installs the defaults), and joining
the JOE domain, it stops on the "workgroup or computer domain" screen and has
"JOE" in the domain field, and when I click NEXT, it does prompt me for a
username to add to the domain, but after I enter the information it just sits
there and hangs, then about 20-30 mins later it comes up with an error "the
domain could not be accessed due to networking problems.". I've checked all
of my network connections, and it is generating a new SID for the computer.

I've tried alot of possible sou
Click to expand...
Click to expand...
 
G

Guest

It could be but it is possible to do this with no technician interaction. It
would depend on your environment. I work in a large corporation and all of
our deployments are done by in house staff. You have to have some level of
trust because anyone working with your system images can break into them if
they are sitting at the console.

Our goal was to nearly completely automate the process.

Kezden said:
but that would be a security risk, wouldn't it?

Jockel said:
You may have run into the fact that your network connections are not fully
active until the next reboot.

To work around this I use a runonce script that autologs on to the machine
after sysprep does it's reboot. The script joins the domain using embedded
credentials.

Kezden said:
I've created an XP-Pro image, and i've gotten everything to work sofar,
except for the adding to the domain part. Here is my sysprep.inf so far:

;SetupMgrTag

[Unattended]
OemSkipEula = Yes
OemPnPDriversPath
= "Drivers\865\Audio;Drivers\865\Nic;Drivers\865\video;Drivers\845\NIC;Drivers\845\audio"

[GuiUnattended]
AdminPassword = "********"
EncryptedAdminPassword = No
OEMSkipRegional = 1
TimeZone = 40
OemSkipWelcome = 1

[UserData]
ComputerName =
ProductID = **********************
FullName = "joe"
OrgName = "shmo"

[Display]
BitsPerPixel = 32
Vrefresh = 75
Xresolution = 1024
YResolution = 768


[SetupMgr]
DistFolder = C:\sysprep\i386
DistShare = whistlerdist


[Networking]


[Identification]
JoinDomain = JOE

[sysprepcleanup]

What my goal is, to have it run thru mini-setup, ask for a product key, ask
what type of network settings (Typical or Custom), and to join the "JOE"
domain with out using an automatic login.
What I am having problems with, is getting mini-setup to ask me to choose
the network settings (right now it just installs the defaults), and joining
the JOE domain, it stops on the "workgroup or computer domain" screen and has
"JOE" in the domain field, and when I click NEXT, it does prompt me for a
username to add to the domain, but after I enter the information it just sits
there and hangs, then about 20-30 mins later it comes up with an error "the
domain could not be accessed due to networking problems.". I've checked all
of my network connections, and it is generating a new SID for the computer.

I've tried alot of possible sou
Click to expand...
Click to expand...
Click to expand...
 
G

Guest

apparently there is a fix for my problem, I neglected to mention that I am
also using Novell 4.90sp1a and there is an issue with sysprep, now the only
thing i'm trying to figure out is how to prompt for network configuration,
(choosing between typical and custom) there are cases where i would need this
to happen. If anyone has a sugestion, please inform.

thanks



Jockel said:
It could be but it is possible to do this with no technician interaction. It
would depend on your environment. I work in a large corporation and all of
our deployments are done by in house staff. You have to have some level of
trust because anyone working with your system images can break into them if
they are sitting at the console.

Our goal was to nearly completely automate the process.

Kezden said:
but that would be a security risk, wouldn't it?

Jockel said:
You may have run into the fact that your network connections are not fully
active until the next reboot.

To work around this I use a runonce script that autologs on to the machine
after sysprep does it's reboot. The script joins the domain using embedded
credentials.

:

I've created an XP-Pro image, and i've gotten everything to work sofar,
except for the adding to the domain part. Here is my sysprep.inf so far:

;SetupMgrTag

[Unattended]
OemSkipEula = Yes
OemPnPDriversPath
= "Drivers\865\Audio;Drivers\865\Nic;Drivers\865\video;Drivers\845\NIC;Drivers\845\audio"

[GuiUnattended]
AdminPassword = "********"
EncryptedAdminPassword = No
OEMSkipRegional = 1
TimeZone = 40
OemSkipWelcome = 1

[UserData]
ComputerName =
ProductID = **********************
FullName = "joe"
OrgName = "shmo"

[Display]
BitsPerPixel = 32
Vrefresh = 75
Xresolution = 1024
YResolution = 768


[SetupMgr]
DistFolder = C:\sysprep\i386
DistShare = whistlerdist


[Networking]


[Identification]
JoinDomain = JOE

[sysprepcleanup]

What my goal is, to have it run thru mini-setup, ask for a product key, ask
what type of network settings (Typical or Custom), and to join the "JOE"
domain with out using an automatic login.
What I am having problems with, is getting mini-setup to ask me to choose
the network settings (right now it just installs the defaults), and joining
the JOE domain, it stops on the "workgroup or computer domain" screen and has
"JOE" in the domain field, and when I click NEXT, it does prompt me for a
username to add to the domain, but after I enter the information it just sits
there and hangs, then about 20-30 mins later it comes up with an error "the
domain could not be accessed due to networking problems.". I've checked all
of my network connections, and it is generating a new SID for the computer.

I've tried alot of possible sou
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

sysprep ignoring computer name 1
Unable to join the domain using sysprep ... 2
Sysprep'ed machine hangs when joining domain 1
Sysprep with SATA drive 4
XP SP2 Sysprep - drivers not installed during mini-setup wizard? 3
Sysprep doesn't find drivers? 5
Hardware not being found with sysprep. 1
Sysprep Hangs 2

Top