Terminal Services Suddenly Disabled on Every Server

This is a problem that hopefully someone here has seen:
Yesterday at around 8:00 AM, we started getting calls from users who were
unable to log on to terminal servers (we only have 2 terminal servers).
Those who were previously logged on had no issues. Then, we found that we
could not connect to any server or workstation in our domain and site via
RDP. Searching through several systems, we found that the local GPO on every
single one (in Computer Config. > Admin. Templates > Windows Components >
Terminal Services), the "Allow users to connect remotely using Terminal
Services" setting was set to "Disabled." I've checked the GPOs for the
domain and OUs (there are no site-level GPOs), and all have that setting set
to "Not Configured", so it appears to have been set locally on EVERY box. I
can set the local policy to "Enabled" and it seems to hold, which means to me
that it's a local policy. But, why did this happen yesterday at 8 AM? Does
anyone know of a recent update that may have caused this in your environment?
Any ideas are welcome.

Thanks.

Hello David,

Normally policiews will not change themself. Maybe someone changed it by
mistake manual and then set it to not configured. This will NOT revert the
setting.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> This is a problem that hopefully someone here has seen:
> Yesterday at around 8:00 AM, we started getting calls from users who
> were
> unable to log on to terminal servers (we only have 2 terminal
> servers).
> Those who were previously logged on had no issues. Then, we found that
> we
> could not connect to any server or workstation in our domain and site
> via
> RDP. Searching through several systems, we found that the local GPO
> on every
> single one (in Computer Config. > Admin. Templates > Windows
> Components >
> Terminal Services), the "Allow users to connect remotely using
> Terminal
> Services" setting was set to "Disabled." I've checked the GPOs for
> the
> domain and OUs (there are no site-level GPOs), and all have that
> setting set
> to "Not Configured", so it appears to have been set locally on EVERY
> box. I
> can set the local policy to "Enabled" and it seems to hold, which
> means to me
> that it's a local policy. But, why did this happen yesterday at 8 AM?
> Does
> anyone know of a recent update that may have caused this in your
> environment?
> Any ideas are welcome.
> Thanks.
>