I'm assuming the registry settings were already set for autologin, domain, password, etc before you took the image?  Could any settings for autologin within the sysprep have possibly overriden these?  I only ask because I used to work with some machines that were autologins, but we set these keys later in the build process and never had any problems.

You could send a bat or vbscript as part of the job to reset the autologin and then do a "shutdown /r /t 10"

It is pretty off though. I would not expect the autologin to be changed.

If these are being joined to a domain, this could cause the issue you are seeing.

RichC,

It was already set to autologin out of the box. Plus, the terminal we first imaged had all these settings correct. We are quite new to Altiris - what roll does sysprep do? We do not have the sysprep setting ticked on distribution of the image. Any other ideas? It only happens to the new XP SP3 images.

Sean_Ebeling,

Have you got a copy of the scrip we could try? We cant understand why the HP Logon Manager looses the auto logon tick!

bhawver,

The terminals do not join a domain. One booted, the user account (should) auto login then the user can connect to our system via Citrix.

Any further ideas are greatly received!!

...which i'd assume you are when building a Universal Image for XP, there is a section in it that might look like this:

[GuiUnattended]
AdminPassword="xxxxxxxxxxx"
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=3

If that is set, i'd assume that it might override your default settings in the image (never tested this theory though...).  However, bhawver could also have a very good point...if you're joining a domain, a Group Policy might be changing these settings as well.

Simplest thing might just be to go through your build chain, and as one of the last steps, have it run a regedit and plug in your autologin keys and then reboot!  If it still does it after that, i'd be almost positive that this is being managed by Group Policy somehow.

Let us know how it goes...

RichC,

Im not using sysprep, so i dont think that it makes any odds in this case?

I've managed to call HP with regards to this, and after they have tested it, they have confirmed that after getting the image and redeploying via DS, that the autologin does not remember. They have suggested taking a thinstate capture of the termial, try redeploy, if that works - to use DS to distribute the USB'd image.

Im in the middle of this now and will let you know my results.

Hi -

I've only just gotten started using Ghost, and I'm a bit lost.

I run a computer lab with about 50 computers.  They all auto-login using a GPO set on the domain controller.  However, when I push out images to the computers with Ghost, the auto-login stops working (at least, for the first boot-up).  Is there any way I can fix this?

Thanks,
Eric

We set everything on our reference system including autologin pull an image setup the lab and deploy the image we don't have any problems with autologin for Win XP sp3. We do use sysprep,  I am using DS6.9 sp4 on a Win2003 box. I just completed a refresh of 400 systems in 9 labs without any problems using autologin and joining the domain.