Ghost 8 not joining Domain when the image is ON the domain

[mattx]

Thought I had seen it all with Ghost but this is a new one. Have an image with the PC ON / part of the domain. Go go Ghost it - run sysprep and before you ask - the 'remove pc from the domain' is UN-TICKED - image takes fine - does the mini setup but does not join the domain - you have to logon to the PC locally, and then add it.

Don't get it - the PC WAS ALREADY part of the domain why after it's ghosted or you use the image on another PC it decides to not to ?

Is this a new feature of Windows ? Anyone seen this before ?

[sted]

is the task you use to clone set to configure?

are you using a 2008 server/domain if so theres a policy somewhere about nt4 style something or other that needs altering

is teh console correctly added to domain in the options?

 

or are you joining it using a the sysprep file itself?

[mattx]

is the task you use to clone set to configure?

are you using a 2008 server/domain if so theres a policy somewhere about nt4 style something or other that needs altering

is teh console correctly added to domain in the options?

 

or are you joining it using a the sysprep file itself?

 

Its on a 2003 server domain - and it's using a sysprep file which I have checked and is fine - [ used it many times before without a problem ]

[mattx]

Well thats a whole day down the toilet - have tried 5 images - all do the same thing.

PC on the domain - ghost it, use sysprep, it does the sysprep, takes the image then you have to add the PC to the domain again afterwards - why ? No plausiable explaination - yet another stupid IT related un-solvable software problem.

I've been using Ghost 8.0 for 5 years, never had this problem - why suddenly now ? Then people wonder why I think working in this god for saken industry sucks. I can't be bothered to try and fix it, I'll just add the PCs to the domain afterwards - I'll then knock off a sarcastic E-mail to a Symantec & MS as that will make me feel better.

I'm going home.

Edited July 16, 2010 by mattx

[sted]

Well thats a whole day down the toilet - have tried 5 images - all do the same thing.

PC on the domain - ghost it, use sysprep, it does the sysprep, takes the image then you have to add the PC to the domain again afterwards - why ? No plausiable explaination - yet another stupid IT related un-solvable software problem.

I've been using Ghost 8.0 for 5 years, never had this problem - why suddenly now ? Then people wonder why I think working in this god for saken industry sucks. I can't be bothered to try and fix it, I'll just add the PCs to the domain afterwards - I'll then knock off a sarcastic E-mail to a Symantec & MS as that will make me feel better.

I'm going home.

 

you can always create a config task in ghost to name/domain them

[K.C.Leblanc]

You haven't changed your password have you?

[mattx]

you can always create a config task in ghost to name/domain them

 

I'll knock something up in AutoIT !!

Bleeding computers - nothing but trouble !!

[mattx]

You haven't changed your password have you?

 

No - I know I'm thick and stupid, but no.

[DMcCoy]

Sysprep and before you ask - the 'remove pc from the domain' is UN-TICKED

 

why after it's ghosted or you use the image on another PC it decides to not to ?

 

Is sysprep or ghost set to join it to the domain? Seeing as you are running sysprep - resetting the machine SID, breaking the link to the machine account on the domain. Even if it doesn't think it's been unjoined.

[Michael]

Just a thought, just before you go to add the machine manually, have you checked the event logs on the workstation to see why it couldn't be added? I don't think it's permissions related or that the account is disabled, presumably because you're using the same credentials manually?

[K.C.Leblanc]

No - I know I'm thick and stupid, but no.

 

Sorry, It's the kind of thing I do all the time.

[mattx]

Sorry, It's the kind of thing I do all the time.

 

Your too honest.

[glennda]

Can't say i have seen that before, but i was always told (by a previous boss) to create images without putting the machine on the domain, just create the image then sysprep it, after syspreping then put the machine on the domain through the mini-setup. I don't see a reason why it "shouldn't" make a difference, but you know what Microsoft are like!

[computer_expert]

Can't say i have seen that before, but i was always told (by a previous boss) to create images without putting the machine on the domain, just create the image then sysprep it, after syspreping then put the machine on the domain through the mini-setup. I don't see a reason why it "shouldn't" make a difference, but you know what Microsoft are like!

 

I've always done it that way as I remember reading (in several different places) and being told not to image computers that have already been joined to a domain.

[Messa]

Is Ghost installed on a domain controller? We once had this problem with 7.5, installed ghost just on a member server and worked a treat!

[Michael]

Imaging workstations already connected to a domain is absolutely fine. When you run Sysprep and the machine requests a restart/shutdown, it's at this point you should take an image.

 

Mini setup then runs and your answer file will re-join the machine to the domain.