Deployment Solution

Hey everyone,

I have an issue that i've been trying to figure out for a few days and I seem to be striking out. In my Deployment jobs it seems that the sysprep file isn't joining to the domain once the image has dropped and goes through the initial sysprep setup process. However, If I simply reimage a machine it works without a hitch. My reimage job is obviously using the "create sysprep file from inventory data" so it is capturing this properly.

On New machines I have it set to use the sysprep.inf file located in the nscap\Deployment directory. (This is for windows XP) . The Identification area of the sysprep has a token in place of @Identification. Could it be possible that this token isn't working properly? I don't think that I've ever created it, so maybe that is the culprit... it's not there by default?

Has anyone else had an issue comparable to this one?

Can you not just include a 'Apply system configuration' task in your job to add it to the domain. I suppose its a workaround...

Hi

I agree to Joe you can definately follow that workarround to join the machine to the domain. However to resolve this issue i would suggested to take an image again with sysperp & try that image. These steps has help me lots of time.

Yea the work around really isn't feasible here as the domain account used to start the SMA when the machines boots for the first time fails to load because the machine didn't get joined to the domain. 

I've actually tried sysprepping a few image sets now to no avail..The way I've currently worked around this is using a custom sysprep file which has the correct domain information manually entered in it.

The generated sysprep file from Symantec is using the @identification token, which I can only assume has the incorrect information.. This is why known machines will image fine using the "generate sysprep from inventory config data" and the new machines won't... Because for the new machine it doesn't have any inventory machine config to go by.

Saeed --

Any idea where the information for the @Identification token is being pulled from? I didn't see it in my general list of tokens..(which could also be the problem as it doesn't actually exist.)

Is there a reason you cannot have the SMA installed to run using System credentials instead of a domain account? I believe that's the default; it works for me. Otherwise it would seem, if your behavior is true, that you've got a chicken-before-the-egg situation. One thing you could do is on your master image computer, join the domain, then explicitly add that domain account into the Local Administrators group.

Actually to your point...

The agent is running under the local system account (I just verified it). However for some reason when the machine initially boots up after the sysprep installation the agent is marked as "disabled". However if the machine joins the domain it starts up runs fine.. Strange eh?

* Just to point out to everyone that is going to ask, no I do not have the agent disabeld during the capture image process. I'm not sure why this is behaving like such..

Every since I placed the details directly into the sysprep file in regards to joining the domain, the problem has went away... Strange.