Cannot join to domain after sysprep (XP SP2)

  • Thread starter Thread starter Barkley Bees
  • Start date Start date
B

Barkley Bees

I completed an updated XP SP2 build of our internal image and performed
sysprep -reseal -mini. The system drivers get detected and correctly
installed but I am having a problem with the system joining the domain.

When the Mini-setup wizard is about to complete it correctly asks me if I
want to join domain xxx. I select yes, and it prompts me for credentials
which I input (tried with domain administrator and others) but then it hangs
for about 3-4 minutes and returns an unexpected error and asks me if I want
to join the domain later. With no choice I opt for the workgroup option.
After booting into XP the NetSetup.LOG shows the following:

06/01
23:49:51 -----------------------------------------------------------------
06/01 23:49:51 NetpDoDomainJoin
06/01 23:49:51 NetpMachineValidToJoin: 'COMPUTERNAME'
06/01 23:49:51 NetpGetLsaPrimaryDomain: status: 0x0
06/01 23:49:51 NetpMachineValidToJoin: status: 0x0
06/01 23:49:51 NetpJoinWorkgroup: joining computer 'COMPUTERNAME' to
workgroup 'WORKGROUP'
06/01 23:49:51 NetpValidateName: checking to see if 'WORKGROUP' is valid as
type 2 name
06/01 23:49:51 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as
MACHINE] returned 0x0
06/01 23:49:51 NetpValidateName: name 'WORKGROUP' is valid for type 2
06/01 23:49:51 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
06/01 23:49:51 NetpJoinWorkgroup: status: 0x0
06/01 23:49:51 NetpDoDomainJoin: status: 0x0
06/01
23:50:21 -----------------------------------------------------------------
06/01 23:50:21 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:21 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:21 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpDoDomainJoin
06/01 23:50:22 NetpMachineValidToJoin: 'COMPUTERNAME'
06/01 23:50:22 NetpGetLsaPrimaryDomain: status: 0x0
06/01 23:50:22 NetpMachineValidToJoin: status: 0x0
06/01 23:50:22 NetpJoinDomain
06/01 23:50:22 Machine: COMPUTERNAME
06/01 23:50:22 Domain: DOMAIN
06/01 23:50:22 MachineAccountOU: (NULL)
06/01 23:50:22 Account: DOMAIN\Administrator
06/01 23:50:22 Options: 0x40001
06/01 23:50:22 OS Version: 5.1
06/01 23:50:22 Build number: 2600
06/01 23:50:22 ServicePack: Service Pack 2
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain 'DOMAIN', flags:
0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the specified
domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc '\\DOMCON001':
0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574
06/01
23:50:47 -----------------------------------------------------------------


** the above sequence repeats several times in the log file.

From the above I can see that the domain is validated so network
connectivity is there but the below are the error portions:

06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain 'DOMAIN', flags:
0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the specified
domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc '\\DOMCON001':
0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574

Early on in my image setup testing I didn't have any problems joining a test
machine to the domain but now that I have finalized the build it, of course,
spits out this problem.
For reference, the system is XP SP2, IE7, Adobe Reader 8.1.5, Symantec
AntiVirus Corp 10.1.7.7000, WinZip 11.2 and most critical MS security
patches up to this month (minus SP3).

Appreciate any advice or words of wisdom that anyone can offer.
 
Barkley Bees said:
I completed an updated XP SP2 build of our internal image and performed
sysprep -reseal -mini. The system drivers get detected and correctly
installed but I am having a problem with the system joining the domain.

When the Mini-setup wizard is about to complete it correctly asks me if I
want to join domain xxx. I select yes, and it prompts me for credentials
which I input (tried with domain administrator and others) but then it hangs
for about 3-4 minutes and returns an unexpected error and asks me if I want
to join the domain later. With no choice I opt for the workgroup option.
After booting into XP the NetSetup.LOG shows the following:

06/01
23:49:51 -----------------------------------------------------------------
06/01 23:49:51 NetpDoDomainJoin
06/01 23:49:51 NetpMachineValidToJoin: 'COMPUTERNAME'
06/01 23:49:51 NetpGetLsaPrimaryDomain: status: 0x0
06/01 23:49:51 NetpMachineValidToJoin: status: 0x0
06/01 23:49:51 NetpJoinWorkgroup: joining computer 'COMPUTERNAME' to
workgroup 'WORKGROUP'
06/01 23:49:51 NetpValidateName: checking to see if 'WORKGROUP' is valid as
type 2 name
06/01 23:49:51 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as
MACHINE] returned 0x0
06/01 23:49:51 NetpValidateName: name 'WORKGROUP' is valid for type 2
06/01 23:49:51 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
06/01 23:49:51 NetpJoinWorkgroup: status: 0x0
06/01 23:49:51 NetpDoDomainJoin: status: 0x0
06/01
23:50:21 -----------------------------------------------------------------
06/01 23:50:21 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:21 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:21 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpDoDomainJoin
06/01 23:50:22 NetpMachineValidToJoin: 'COMPUTERNAME'
06/01 23:50:22 NetpGetLsaPrimaryDomain: status: 0x0
06/01 23:50:22 NetpMachineValidToJoin: status: 0x0
06/01 23:50:22 NetpJoinDomain
06/01 23:50:22 Machine: COMPUTERNAME
06/01 23:50:22 Domain: DOMAIN
06/01 23:50:22 MachineAccountOU: (NULL)
06/01 23:50:22 Account: DOMAIN\Administrator
06/01 23:50:22 Options: 0x40001
06/01 23:50:22 OS Version: 5.1
06/01 23:50:22 Build number: 2600
06/01 23:50:22 ServicePack: Service Pack 2
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain 'DOMAIN', flags:
0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the specified
domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc '\\DOMCON001':
0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574
06/01
23:50:47 -----------------------------------------------------------------


** the above sequence repeats several times in the log file.

From the above I can see that the domain is validated so network
connectivity is there but the below are the error portions:

06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain 'DOMAIN', flags:
0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the specified
domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc '\\DOMCON001':
0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574

Early on in my image setup testing I didn't have any problems joining a test
machine to the domain but now that I have finalized the build it, of course,
spits out this problem.
For reference, the system is XP SP2, IE7, Adobe Reader 8.1.5, Symantec
AntiVirus Corp 10.1.7.7000, WinZip 11.2 and most critical MS security
patches up to this month (minus SP3).

Appreciate any advice or words of wisdom that anyone can offer.
Click to expand...


It appears the error you are getting, 1396 or 0x574, is actually associated with an error message I've seen in the past, "The target account name is incorrect." It usually means from a worst case scenario that a trust or machine account is invalide, which doesn;t appear to be in your case, to simply it cannot connect to it.

A number of issues can cause this. One of the major causes is using the incorrect DNS addresses. If you are using an ISP's DNS address anywhere, that will cause it. If your domain is a single label name domain, that will cause it as well. If you are using the NetBIOS name of the domain, and the DC is across a WAN link, and there is no NetBIOS name support, that will cause it, too. A multihomed DC (more than one NIC), will also definitely cause it. Also another possible cause is if you named the machine the same name as a computer account that still exists in the domain, that can cause it as well.

Based on your posted info, it is difficult to provide a specific diagnosis. Please elaborate a bit more on the above info I mentined, as well as post an unedited ipconfig /all of a sample desktop (so we can see what DHCP is giving out), as well as a local DC.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(e-mail address removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay
 
"Ace Fekay [Microsoft Certified Trainer]" <[email protected]>
wrote in message
Barkley Bees said:
I completed an updated XP SP2 build of our internal image and performed
sysprep -reseal -mini. The system drivers get detected and correctly
installed but I am having a problem with the system joining the domain.

When the Mini-setup wizard is about to complete it correctly asks me if I
want to join domain xxx. I select yes, and it prompts me for credentials
which I input (tried with domain administrator and others) but then it
hangs
for about 3-4 minutes and returns an unexpected error and asks me if I
want
to join the domain later. With no choice I opt for the workgroup option.
After booting into XP the NetSetup.LOG shows the following:

06/01
23:49:51 -----------------------------------------------------------------
06/01 23:49:51 NetpDoDomainJoin
06/01 23:49:51 NetpMachineValidToJoin: 'COMPUTERNAME'
06/01 23:49:51 NetpGetLsaPrimaryDomain: status: 0x0
06/01 23:49:51 NetpMachineValidToJoin: status: 0x0
06/01 23:49:51 NetpJoinWorkgroup: joining computer 'COMPUTERNAME' to
workgroup 'WORKGROUP'
06/01 23:49:51 NetpValidateName: checking to see if 'WORKGROUP' is valid
as
type 2 name
06/01 23:49:51 NetpCheckNetBiosNameNotInUse for 'WORKGROUP' [ Workgroup as
MACHINE] returned 0x0
06/01 23:49:51 NetpValidateName: name 'WORKGROUP' is valid for type 2
06/01 23:49:51 NetpSetLsaPrimaryDomain: for 'WORKGROUP' status: 0x0
06/01 23:49:51 NetpJoinWorkgroup: status: 0x0
06/01 23:49:51 NetpDoDomainJoin: status: 0x0
06/01
23:50:21 -----------------------------------------------------------------
06/01 23:50:21 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:21 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:21 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01
23:50:22 -----------------------------------------------------------------
06/01 23:50:22 NetpDoDomainJoin
06/01 23:50:22 NetpMachineValidToJoin: 'COMPUTERNAME'
06/01 23:50:22 NetpGetLsaPrimaryDomain: status: 0x0
06/01 23:50:22 NetpMachineValidToJoin: status: 0x0
06/01 23:50:22 NetpJoinDomain
06/01 23:50:22 Machine: COMPUTERNAME
06/01 23:50:22 Domain: DOMAIN
06/01 23:50:22 MachineAccountOU: (NULL)
06/01 23:50:22 Account: DOMAIN\Administrator
06/01 23:50:22 Options: 0x40001
06/01 23:50:22 OS Version: 5.1
06/01 23:50:22 Build number: 2600
06/01 23:50:22 ServicePack: Service Pack 2
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is valid as
type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN' returned
0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain 'DOMAIN',
flags:
0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the specified
domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc '\\DOMCON001':
0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574
06/01
23:50:47 -----------------------------------------------------------------


** the above sequence repeats several times in the log file.

From the above I can see that the domain is validated so network
connectivity is there but the below are the error portions:

06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain 'DOMAIN',
flags:
0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the specified
domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc '\\DOMCON001':
0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574

Early on in my image setup testing I didn't have any problems joining a
test
machine to the domain but now that I have finalized the build it, of
course,
spits out this problem.
For reference, the system is XP SP2, IE7, Adobe Reader 8.1.5, Symantec
AntiVirus Corp 10.1.7.7000, WinZip 11.2 and most critical MS security
patches up to this month (minus SP3).

Appreciate any advice or words of wisdom that anyone can offer.
Click to expand...


It appears the error you are getting, 1396 or 0x574, is actually associated
with an error message I've seen in the past, "The target account name is
incorrect." It usually means from a worst case scenario that a trust or
machine account is invalide, which doesn;t appear to be in your case, to
simply it cannot connect to it.

A number of issues can cause this. One of the major causes is using the
incorrect DNS addresses. If you are using an ISP's DNS address anywhere,
that will cause it. If your domain is a single label name domain, that will
cause it as well. If you are using the NetBIOS name of the domain, and the
DC is across a WAN link, and there is no NetBIOS name support, that will
cause it, too. A multihomed DC (more than one NIC), will also definitely
cause it. Also another possible cause is if you named the machine the same
name as a computer account that still exists in the domain, that can cause
it as well.

Based on your posted info, it is difficult to provide a specific diagnosis.
Please elaborate a bit more on the above info I mentined, as well as post an
unedited ipconfig /all of a sample desktop (so we can see what DHCP is
giving out), as well as a local DC.

--
Ace

Thank you very much for your reply Ace. It appears to have been as simple as
making the below change to my sysprep.inf

Before:

[Identification]
JoinDomain=domain

After:

[Identification]
JoinDomain=domain.com

For some reason after making updates to the XP image (application version
updates and Microsoft updates) and then doing a sysprep, it would not join
to "domain" but after changing it to "domain.com" it joins without any
issues. Rather odd but it seems ok now.
 
Barkley said:
I completed an updated XP SP2 build of our internal image and
performed sysprep -reseal -mini. The system drivers get detected
and correctly installed but I am having a problem with the system
joining the domain.
When the Mini-setup wizard is about to complete it correctly asks
me if I want to join domain xxx. I select yes, and it prompts me
for credentials which I input (tried with domain administrator and
others) but then it hangs for about 3-4 minutes and returns an
unexpected error and asks me if I want to join the domain later.
With no choice I opt for the workgroup option. After booting into
XP the NetSetup.LOG shows the following:
Click to expand...
06/01 23:50:22 NetpDoDomainJoin 06/01 23:50:22
NetpMachineValidToJoin: 'COMPUTERNAME' 06/01 23:50:22
NetpGetLsaPrimaryDomain: status: 0x0 06/01 23:50:22
NetpMachineValidToJoin: status: 0x0 06/01 23:50:22 NetpJoinDomain
06/01 23:50:22 Machine: COMPUTERNAME
06/01 23:50:22 Domain: DOMAIN
06/01 23:50:22 MachineAccountOU: (NULL)
06/01 23:50:22 Account: DOMAIN\Administrator
06/01 23:50:22 Options: 0x40001
06/01 23:50:22 OS Version: 5.1
06/01 23:50:22 Build number: 2600
06/01 23:50:22 ServicePack: Service Pack 2
06/01 23:50:22 NetpValidateName: checking to see if 'DOMAIN' is
valid as type 3 name
06/01 23:50:22 NetpCheckDomainNameIsValid [ Exists ] for 'DOMAIN'
returned 0x0
06/01 23:50:22 NetpValidateName: name 'DOMAIN' is valid for type 3
06/01 23:50:22 NetpDsGetDcName: trying to find DC in domain
'DOMAIN', flags: 0x1020
06/01 23:50:37 NetpDsGetDcName: failed to find a DC having account
'COMPUTERNAME$': 0x525
06/01 23:50:37 NetpDsGetDcName: found DC '\\DOMCON001' in the
specified domain
06/01 23:50:37 NetUseAdd to \\DOMCON001\IPC$ returned 1396
06/01 23:50:37 NetpJoinDomain: status of connecting to dc
'\\DOMCON001': 0x574
06/01 23:50:37 NetpDoDomainJoin: status: 0x574
06/01
23:50:47
Click to expand...
Early on in my image setup testing I didn't have any problems
joining a test machine to the domain but now that I have finalized
the build it, of course, spits out this problem.
For reference, the system is XP SP2, IE7, Adobe Reader 8.1.5,
Symantec AntiVirus Corp 10.1.7.7000, WinZip 11.2 and most critical
MS security patches up to this month (minus SP3).

Appreciate any advice or words of wisdom that anyone can offer.
Click to expand...

Ace said:
It appears the error you are getting, 1396 or 0x574, is actually
associated with an error message I've seen in the past, "The target
account name is incorrect." It usually means from a worst case
scenario that a trust or machine account is invalide, which doesn;t
appear to be in your case, to simply it cannot connect to it.

A number of issues can cause this. One of the major causes is using
the incorrect DNS addresses. If you are using an ISP's DNS address
anywhere, that will cause it. If your domain is a single label name
domain, that will cause it as well. If you are using the NetBIOS
name of the domain, and the DC is across a WAN link, and there is
no NetBIOS name support, that will cause it, too. A multihomed DC
(more than one NIC), will also definitely cause it. Also another
possible cause is if you named the machine the same name as a
computer account that still exists in the domain, that can cause it
as well.
Based on your posted info, it is difficult to provide a specific
diagnosis. Please elaborate a bit more on the above info I
mentined, as well as post an unedited ipconfig /all of a sample
desktop (so we can see what DHCP is giving out), as well as a local
DC.
Click to expand...

Barkley said:
Thank you very much for your reply Ace.
It appears to have been as simple as making the below change to my
sysprep.inf

Before:

[Identification]
JoinDomain=domain

After:

[Identification]
JoinDomain=domain.com

For some reason after making updates to the XP
image (application version updates and Microsoft
updates) and then doing a sysprep, it would not join
to "domain" but after changing it to "domain.com"
it joins without any issues. Rather odd but it seems
ok now.
Click to expand...

As Ace Fekay said, looked like a DNS issue. Using the FQDN will naturally
work better in al ost all situations.
 
Barkley Bees said:
Thank you very much for your reply Ace. It appears to have been as simple as
making the below change to my sysprep.inf

Before:

[Identification]
JoinDomain=domain

After:

[Identification]
JoinDomain=domain.com

For some reason after making updates to the XP image (application version
updates and Microsoft updates) and then doing a sysprep, it would not join
to "domain" but after changing it to "domain.com" it joins without any
issues. Rather odd but it seems ok now.
Click to expand...

Glad you figured it out as being the domain name. As Shenan said, it is always better to use the FQDN.

Ace
 
Yes indeed, FQDN all the way! Thank you both very much! Much appreciated.

"Ace Fekay [Microsoft Certified Trainer]" <[email protected]>
wrote in message
Barkley Bees said:
Thank you very much for your reply Ace. It appears to have been as simple
as
making the below change to my sysprep.inf

Before:

[Identification]
JoinDomain=domain

After:

[Identification]
JoinDomain=domain.com

For some reason after making updates to the XP image (application version
updates and Microsoft updates) and then doing a sysprep, it would not join
to "domain" but after changing it to "domain.com" it joins without any
issues. Rather odd but it seems ok now.
Click to expand...

Glad you figured it out as being the domain name. As Shenan said, it is
always better to use the FQDN.

Ace
 
Back
Top