This message was deleted.

Which ones are you referring to, the one to log a user in and then back out?

Yes

OK, you would need to check what the behaviour is set to for when user logs off, is it set to shutdown on logoff?

its set to shut down

I would turn that off then if possible, not sure if it is possible to filter it in some way or maybe exclude some users?

we never implemented it, but our thought was to use a script that would do the auto login, then log out, but the citrix desktop service set to manual and it would start it after the initial login, then it would register. That was how we were trying to get around to reboot

@langsbr i've tried that and it still triggers a reboot as soon as the service starts..

Maybe the hydration feature from BISF can help!? https://eucweb.com/kba/281219084515-2

You might need to set the service to disabled on the master and start it with the auto login script.

Ive done that. The issue is its a non-persistent image and the catalog is set to reboot on user log off.

I had it working let me see what I did

So yes, I had to set the services to disable on the master. Broker, ICA, and WEM or I would get the phantom " - " user, which would trigger a reboot. In the end I created a scheduled task that the login script calls, which has a delay of about 1 minute. Desktop logs off, scheduled task executes a script to enable and start the services. My login times went from 120 seconds down to 70 seconds... this is all hosted in AWS.