Ghost Solution Suite

I will try to keep this brief.

My task sequence in GSS 3.1 build 607, Maintenance Package 3 is this:
1 - Create Disk Image.  This is my base image with updates applied
2 - Run script which includes deleting logs and running Sysprep OOBE.  I'm using /generalize /oobe /quit /unattned...unattend.xml
3 - Create Disk Image.  This is the sysprepped image.

I am also utilizing SetupComplete.cmd (Windows\Setup\Scripts) to remove the Altiris agent.
I am using DHCP on the Ghost server, but the machines I deploy to will have statice IP's.
I can deploy the image using Ghost, and I can enter my static IP.  However, when I try to join the PC to the domain, I get the message 'Network path not found'.

I can ping all relevant devices and I can access the internet.

If I take GSS3.1 out of the equation and create my images manually, I do not have this problem.  This leads me to believe that there is some remnant being left behind by the Altiris agent.

Suggestions?

Eddy,

Did you try using the fully qualified domain name when doing the configuration job? IE. domain.local.

Removing the agent is not a priority when sysprepping and re-joining the domain. In fact if you are using the option "Boot to production to complete configuration" you will need the agent on the client machine as this is the only way it can check back in with the console to complete the task.

Thank you Brycen,

I am using the FQDN.  We remove the Alitiris agent prior to sysprepping because we aren't using GSS to deploy the image.  We are using Ghostcast (standalone) to deploy the images, not a task within GSS, so the 'Boot to production' option doesn't actually come into play.

Could this be because the images are being developed on a small network with DHCP enabled, and when the actual production machines are on a network using static IPs?

Eddy

Eddy,

Are you setting a static i.p. within the Ghost Boot Disc (during the configuration)? If so the below article may be of some use...

https://support.symantec.com/en_US/article.TECH225264.html

It is strange that you can ping and access the internet but cannot reach your AD when trying to join the machine back to the domain.

Are you able to deploy the image, boot up to windows and then join the domain?

I have resolved my dilema, but not the issue.  Basically, I have changed the order of what I am doing.  As mentioned above, my task consists of starting with taking an image of the updated computer, then running my cleanup script (which includes sysprep), and then taking an image of the sysprepped image.  I had created a SetupComplete.cmd file that would then remove my unattend.xml file and uninstall and remove all references to the Altiris agent.

Everything is still the same except for when Altiris is being removed.  I have removed the SetupComplete.cmd file and added a command within the unattend.xml file used during sysprep - FirsLogonCommands.  Basically, once the local admin logs in, and prior to reaching the desktop, I am running the same batch file I created earlier to remove Altiris.  After doing this, I have no problem joining the computer to the domain.

There must something about removing Altiris during the post Sysprep configuration (SetupComplete.cmd) that's interfering with the domain join process.  At this point, though, I'm fine with how I've worked around the issue.

Thank you.
Eddy

Eddy,

Have you attempted to remove the altiris agent as the last step in your script?

Deploy the sysprepped image, after the computer boots to windows run the script to remove Altiris.

That's basically how I got around the problem.  I'm removing Altiris after sysprep and as the local Admin is logging in using the 'FirstLogonCommands' option in the unattend file for sysprep.