Desktop shutsdown as soon as it opens

[Tubes]

We have 12 NT/1.8 servers and I am experiencing a problem on two of them. Some users (including admins!), logging on for the first time each day will have the desktop delivered and as soon as it is fininshed logging in, it will shutdown.

This will only happen for the first logon and will be fine for the remainder of the day. All users are created from a template and so can't be a config error. I've searched Citrix and have found two related issues, one with UNIX and the second dealing with double entries in the registry of cmstart.exe after an upgrade to XP, neither of which apply to this case.

Anyone had this problem?

TIA

Tubes

 

[Highland]

Are any errors appearing in the Event Logs around the time of a failed login....????

After the login fails does the server return to a login window....???? Does Citrix admin show an active login on the server....????

 

[Tubes]

No errors are reported. The login doesn't fail, it logs you in and then does a clean logout.

The logout returns you to the normal client desktop, in my case NT 4 W/S.

In regards to the MFAdmin, it shows the connection, then just removes the connection as if I had called for the logout.

Thanks for listening

Tubes

 

[Highland]

Is the logon running OK the 2nd time you try....???

If there are no errors, is something trying to run once in a login script, but not set to run during the 2nd login attempt....????

U might be able to see in Citrix Admin which processes are starting during the login....????

Does it matter which client you use for the 1st login...??? Ie. It's not a problem with the client PC ur using...???

 

[Tubes]

Highland, thanks for the input. This is more of an itch than a rash problem. Answers follows.

Runs perfect! No problems, actually it appears to run quicker. Takes me or the other users to expected desktop without problems.

Big problem with with second issue. Our servers are geared to reboot each night. As SysAdmin, not many people get in before me so I can't see what I'm calling at startup, as it will happen on the console as well as remote.

We have three client scenario (can there be a plural to that?) that we use. NT, 2K, and mostly 9x. Two of the incidents are NT, one 9x. Client shouldn't be an issue as one NT (mine) us using most recent, and others are previous release.