Can't join computer to domain after sysprep

[Guest Jaleel]

Hello,

 

after capture image from referance computer, the deployment finish but with

one issue:

 

after image installation during Microsoft Deployment and WDS, the sysprep

should start, but the computer faild to join to domain with the following

Error Message:

 

An Invalid domain was specified. would you like to procced for now and try

joining a domain later.

 

this message really confuse me, the deployment on Labtop Dell Latitude D505.

 

it's very important to join computer to domain after deployment

 

Regards

[Guest Meinolf Weber]

Re: Can't join computer to domain after sysprep

 

Hello Jaleel,

 

Is the image created from a domain member machine or from standalone workstation?

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

> Hello,

>

> after capture image from referance computer, the deployment finish but

> with one issue:

>

> after image installation during Microsoft Deployment and WDS, the

> sysprep should start, but the computer faild to join to domain with

> the following Error Message:

>

> An Invalid domain was specified. would you like to procced for now and

> try joining a domain later.

>

> this message really confuse me, the deployment on Labtop Dell Latitude

> D505.

>

> it's very important to join computer to domain after deployment

>

> Regards

>

[Guest Jaleel]

RE: Can't join computer to domain after sysprep

 

Sorry the labtop is Dell Latitude D820

 

"Jaleel" wrote:

> Hello,

>

> after capture image from referance computer, the deployment finish but with

> one issue:

>

> after image installation during Microsoft Deployment and WDS, the sysprep

> should start, but the computer faild to join to domain with the following

> Error Message:

>

> An Invalid domain was specified. would you like to procced for now and try

> joining a domain later.

>

> this message really confuse me, the deployment on Labtop Dell Latitude D505.

>

> it's very important to join computer to domain after deployment

>

> Regards

[Guest Jaleel]

Re: Can't join computer to domain after sysprep

 

From WorkStation, Workgroup member

 

Thanks

 

"Meinolf Weber" wrote:

> Hello Jaleel,

>

> Is the image created from a domain member machine or from standalone workstation?

>

> Best regards

>

> Meinolf Weber

> Disclaimer: This posting is provided "AS IS" with no warranties, and confers

> no rights.

> ** Please do NOT email, only reply to Newsgroups

> ** HELP us help YOU!!! http://www.dts-l.org/goodpost.htm

>

> > Hello,

> >

> > after capture image from referance computer, the deployment finish but

> > with one issue:

> >

> > after image installation during Microsoft Deployment and WDS, the

> > sysprep should start, but the computer faild to join to domain with

> > the following Error Message:

> >

> > An Invalid domain was specified. would you like to procced for now and

> > try joining a domain later.

> >

> > this message really confuse me, the deployment on Labtop Dell Latitude

> > D505.

> >

> > it's very important to join computer to domain after deployment

> >

> > Regards

> >

>

>

>

[Guest Jabez Gan [MVP]]

Re: Can't join computer to domain after sysprep

 

Please try using this tool to change the SIDof the comp:

http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx

 

now, try rejoining the domain.

 

If it doesn't work, try pinging the domain. Does it give a response?

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"Jaleel" <Jaleel@discussions.microsoft.com> wrote in message

news:2D5991BF-A7E6-4A91-9417-C649BA264B07@microsoft.com...

> Hello,

>

> after capture image from referance computer, the deployment finish but

> with

> one issue:

>

> after image installation during Microsoft Deployment and WDS, the sysprep

> should start, but the computer faild to join to domain with the following

> Error Message:

>

> An Invalid domain was specified. would you like to procced for now and try

> joining a domain later.

>

> this message really confuse me, the deployment on Labtop Dell Latitude

> D505.

>

> it's very important to join computer to domain after deployment

>

> Regards

[Guest Harry Bates]

Re: Can't join computer to domain after sysprep

 

Jabez, this would not normally be the case but he is welcome to try it. If

he was adding a computer to a domain and there was 1. a computer with the

same name or 2. a computer with the same SID, and the account used to

authenticate creating an object under the particular OU didn't have

overwrite objects permission, the error would be "access denied" (I think

it's error 59 if I'm not mistalen, but it's been a few years since I've

coded a joindom), not "invalid domain". His problem is browsing. What he can

do is confirm that the NIC is active with DNS and WINS before it tries to

find the domain, and try joining the domain 2 different ways. 1. FQDN like

subdomain.domain.local or 2. Join the domain via it's NetBIOS short name. If

the NIC is active and the DCs are playing well, both should actually work.

But to isolate it from NetBIOS to DNS, he should try both ways.

 

"Jabez Gan [MVP]" <mingteikg@blizNOSPAMhosting.com> wrote in message

news:A6A3FF63-CF43-49C5-94B5-75608A9457AA@microsoft.com...

> Please try using this tool to change the SIDof the comp:

> http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx

>

> now, try rejoining the domain.

>

> If it doesn't work, try pinging the domain. Does it give a response?

>

> --

> Jabez Gan

> Microsoft MVP: Windows Server - File Storage

 

>> An Invalid domain was specified. would you like to procced for now and

>> try

>> joining a domain later.

>>

>> this message really confuse me, the deployment on Labtop Dell Latitude

>> D505.

>>

>> it's very important to join computer to domain after deployment

>>

>> Regards

>

[Guest Jabez Gan [MVP]]

Re: Can't join computer to domain after sysprep

 

Hey Harry,

 

Yep I am aware that this would not normally be the case, but I've seen quite

some different errors if there's duplicate SID - and yes one of them is

"Access is denied" or something similar.

 

But if all fails, trying this step wouldn't hurt. ;)

 

--

Jabez Gan

Microsoft MVP: Windows Server - File Storage

"Harry Bates" <harry.bates@NO-SPAMlmco.com> wrote in message

news:ePcDISwUIHA.748@TK2MSFTNGP04.phx.gbl...

> Jabez, this would not normally be the case but he is welcome to try it. If

> he was adding a computer to a domain and there was 1. a computer with the

> same name or 2. a computer with the same SID, and the account used to

> authenticate creating an object under the particular OU didn't have

> overwrite objects permission, the error would be "access denied" (I think

> it's error 59 if I'm not mistalen, but it's been a few years since I've

> coded a joindom), not "invalid domain". His problem is browsing. What he

> can do is confirm that the NIC is active with DNS and WINS before it tries

> to find the domain, and try joining the domain 2 different ways. 1. FQDN

> like subdomain.domain.local or 2. Join the domain via it's NetBIOS short

> name. If the NIC is active and the DCs are playing well, both should

> actually work. But to isolate it from NetBIOS to DNS, he should try both

> ways.

>

> "Jabez Gan [MVP]" <mingteikg@blizNOSPAMhosting.com> wrote in message

> news:A6A3FF63-CF43-49C5-94B5-75608A9457AA@microsoft.com...

>> Please try using this tool to change the SIDof the comp:

>> http://technet.microsoft.com/en-us/sysinternals/bb897418.aspx

>>

>> now, try rejoining the domain.

>>

>> If it doesn't work, try pinging the domain. Does it give a response?

>>

>> --

>> Jabez Gan

>> Microsoft MVP: Windows Server - File Storage

>

>

>>> An Invalid domain was specified. would you like to procced for now and

>>> try

>>> joining a domain later.

>>>

>>> this message really confuse me, the deployment on Labtop Dell Latitude

>>> D505.

>>>

>>> it's very important to join computer to domain after deployment

>>>

>>> Regards

>>

>

>