G
Guest
as part of the group policy that applies to our Thin Client terminals we have
a setting that hides the last logged on user, and also forces the default
domain that displays in the "Log on to:" box when the user presses
ctrl-alt-delete.
the problem is if the user presses ctrl-alt-delete as soon as it first shows
when the machine starts, the policy hasn't yet applied and it doesn't show
the correct logon domain, it displays the local mahine name, and it also
shows the local admin account as the user name.
If the user waits about 30 seconds before pressing Ctrl-alt-delete then the
policy applies and it all works fine.
As the terminals have a write filter it will always lose any last logged on
user information when rebooted, so it is quite important to blank out the
username, also we are migrating to a new domain so users will be confused if
they have to choose to logon on to a particular domain.
Is there a way of ensuring that all machine policies have applied before the
"Welcome to Windows" logon box is displayed?
Thanks
Ian
a setting that hides the last logged on user, and also forces the default
domain that displays in the "Log on to:" box when the user presses
ctrl-alt-delete.
the problem is if the user presses ctrl-alt-delete as soon as it first shows
when the machine starts, the policy hasn't yet applied and it doesn't show
the correct logon domain, it displays the local mahine name, and it also
shows the local admin account as the user name.
If the user waits about 30 seconds before pressing Ctrl-alt-delete then the
policy applies and it all works fine.
As the terminals have a write filter it will always lose any last logged on
user information when rebooted, so it is quite important to blank out the
username, also we are migrating to a new domain so users will be confused if
they have to choose to logon on to a particular domain.
Is there a way of ensuring that all machine policies have applied before the
"Welcome to Windows" logon box is displayed?
Thanks
Ian