Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How can I stop post-image computer config from running?

Created: 11 Oct 2012 • Updated: 12 Oct 2012 | 10 comments
This issue has been solved. See solution.

I made the mistake of checking the "Automatically perform configuration task after completing this imaging task." when I created an updated UI.  The image was sysprepped so min-setup runs after imaging a computer.  The pc restarts and then immediately the Altiris Configure Computer box pops up on the screen.  The problem is that sysprep added the PC to the domain.  The image was made in my lab networks so the Configure Computer takes it out of the domain, puts it into a workgroup and renames the computer back to what it was when I made the image.  A coule of questions:

1. What is the source of the config information since this is not an actual task, it's the result of the box being ticked.

2. How can I stop this from running?

I've brought the computer up in Safe Mode after the first restart, so the Configure Computer does not run.  I've scoured the registry looking for the keys and settings that would cause this to run.  Zip.  If I stop the Altiris Agent service from starting, it never runs, but as soon as I start it, the Configure Computer window pops up and it runs.  So I know the Altiris Agent is what's initiating it.  I disconnected the PC from the network before starting the PC, but it still runs so I know that the computer does not actually have to talk to the deployment server for this to run.

Anybody have any ideas?  I have about 500 computers that will have this issue.  I'm trying to avoid having to rename, reboot, add to the domain, reboot again if I can just start in Safe Mode and kill the config process before it starts.

Thanks,

Tim

Comments 10 CommentsJump to latest comment

Network23's picture

Hi TimTheViking

I´m not 100% sure but I think it is stored in a File called aclient.cfg.

Try to delete this File within a DS Job before the Systems starts this should solve the Problem.

Hope this helps

Network23

SOLUTION
TimTheViking's picture

Hmm... That looks like all the information that the config process is doing.  I'll give it a try and let you know.  Thanks,T

Tim 

andykn101's picture

I think it's the AClient.cfg file in the root of the C: drive.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

TimTheViking's picture

Thanks!  That answered both my questions and solved my problem.  Now if I could only figure out a way to remove this file before the first boot!

andykn101's picture

1. Edit the image file directly to remove the file

2. Next time, before you run sysprep, take a backup image.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

TimTheViking's picture

andykn101, good advice but it doesn't help the 500 that were imaged with the mistake!

andykn101's picture

Could you not create a job or CD that will boot the PC to WinPE and delete the file from the hard disk then?

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

TimTheViking's picture

Hmmm... excellent thougth.  I'll see if that works.  Might be the only practical solution.  

None of these comptuers are in Altiris.  How can I get them to load WinPE by default when hitting F12 on startup?

Tim

andykn101's picture

Look at Initial Deployment.

Authorised Symantec Consultant (ASC) with Endpoint Management Limited, an Authorised Symantec Delivery Provider based in the UK.

Connect Etiquette: Please "Mark as Solution" posts that fix your problem.

TimTheViking's picture

I'm looking at it right now.  I've got a wait task set but when I power on the PC, hit f12, it goes times out on PXE and goes to the OS load.  Not having any luck getting it to load WinPE.