Ghost Solution Suite

Hi there,

 

I have an HPdc7700 Convertible desktop that I've captured an image from.  I have transferred the image back to the local machine on a hidden partition.  There is a join script (exe file) that needs to be transferred to the machine's C drive in order to join to the domain via the execute task.  The issue I have is that Ghost seems to be stuck on that process.  But when I log onto the computer and manually join the machine to the domain, the file gets transferred over and the join script gets run.  So essentially I join the machine and then it gets joined again by the script, which is what I wanted it to do in the first place.

 

I've searched this board and Google for about a week and have found nothing that is of help.  Is it the way I'm capturing the image?  Is it the way the task is set up?

 

Thanks.

Ghost is stuck on "that" process.  Meaning running the join domain or meaning the transfer file process?

 

Im assuming you can run the script manually on the machine without error?  I have had dialog boxes or yes/no prompts hang scripts on me that I wasnt aware of until I retested while watching the script run manually.

Hi,

 

Sorry, "That" process meaining transfer files.  The join.exe is the file to be transferred.

 

Yes, I can run the join manually without error.

 

I am fairly inexperienced in administering Ghost, especially when it comes to account information and domains.  And since I inherited this position with no training, it makes it even more challenging.

 

I just noticed a couple of warnings as well:

 

'Create Machine Account'

- "failed to create an administrative connection to the domain controller ME:  The referenced accont is currently locked out and may not be logged into."

 

And the first of 2 'Post Configuration Status'

- "failed to join domain ME:  Logon failure:  unknown username or bad password."

 

The second one is successful.  But this may be because I manually joined the machines.

 

I don't know if these being new machines has anything to do with it, but it seems that this is when everything has started going wrong.

 

This could also be related to my other thread:

 

Thanks.

Those warnings are in coming from your task log?

 

Sounds like you are trying to get ghost to join the domain, then transferring your script to join the domain.  I would suggest taking the join domain part out of the template and just assign it to some workgroup. 

 

Using GSS 1.1 (Ghost 8.2) the problem with joining the domain doing what you are suggesting above is that the computer is not properly named until after the first boot in to the OS and the client starts and names the computer and then reboots.  So joining the domain at that first boot stage is problematic at best.   In GSS 2.0 the computer boots up with the proper name from the first boot and when you join the domain you are joining it with the proper name. 

 

I am not sure what join.exe is, if its something you made or is freeware.  Netdom.exe is a microsoft free tool and works very well every time.

Hi,

 

The join.exe is made but not by myself.  I did try to reimage with the template assigned to a workgroup and it will stay on transfer files until the end of time (or until I manually join the machine).  Although there are no warnings this way.

 

For the most part, the templates are and have been unchanged since I inherited this position.  Same goes with the method of joining the machines.

 

What is and where can I find netdom.exe?  Is it something that gets included in the task?

 

If you look at the link to my other post, is there something in there (a step maybe) that I am missing or should not include? 

 

Thanks.

 

 

Since you have some support folks helping on that other issue im going to bow out.  I can't imagine why the computer is not transferring the file properly.  Assuming the client is still in communication with the server after it is imaged then it should just work.

Thanks for all your help David!

Stormtrooper, I dont know if you have gotten around this problem or not.  A couple of days ago with GSS 2.01 I was using the transfer files feature in a task.  In windows the transfer was not working at all.  IN the log files for gss 2.01 client I could see it getting the transfer command but doing nothing else.  I cancelled the task and under "Network" tab of my task I chose to set unicast and it started working after that.  I did not try the other protocols in the tab.   Maybe this will help your 8.2 problem?

Hi David,

 

I haven't figured it out yet but I will see if it's the same with 8.2.  The thing is that this doesn't happen all the time.  Sometimes it works like a charm and sometimes it will hang forever.

 

Thanks.