A
AlanN
Hi there,
We have some servers i'd like to auto-login - though most of what they do
runs as a service, some legacy desktop applications point blank refuse to
play nicely and must be run under a domain account. As the servers are on a
domain, the control userpasswords2 method of auto-logon will not work (the
options do not appear on a domain machine). TweakUI would be overkill and a
pain to roll out, so the registry is our only option.
If we were to restrict the Winlogon key in the registry to the local admins
group via ACL, what's the worst that could happen? (Please bear in mind that
the only people who ever access this server do it via a local intranet site
over the anonymous IUSR account, and people in the local admins group).
Thanks!
We have some servers i'd like to auto-login - though most of what they do
runs as a service, some legacy desktop applications point blank refuse to
play nicely and must be run under a domain account. As the servers are on a
domain, the control userpasswords2 method of auto-logon will not work (the
options do not appear on a domain machine). TweakUI would be overkill and a
pain to roll out, so the registry is our only option.
If we were to restrict the Winlogon key in the registry to the local admins
group via ACL, what's the worst that could happen? (Please bear in mind that
the only people who ever access this server do it via a local intranet site
over the anonymous IUSR account, and people in the local admins group).
Thanks!