It sounds like the group policy setting called "Restrict the user from
entering author mode" has been set to Enabled under User
Configuration\Administrative Templates\Windows Components\Microsoft
Management Console.
If you can edit the GPO applied to the OU where the Terminal Server is
located, try setting "Restrict the user from entering author mode" to
Disabled. Once replication of the policy change has occurred it should
apply at next logon. Then you should be able to open the snap-in.
If this does not work, place your user account and the terminal server into
the new OU and Disable this policy setting then reboot the terminal server
and logon with your user account.
What operating system is the Terminal Server running?
--
David Everett
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"newuser" <(E-Mail Removed)> wrote in message
news:24463249-B950-40CA-A628-(E-Mail Removed)...
> Hi All,
> I just took over a task of administrating a Terminal Service Server. The
previous administrator set up a group policy which restricts using of MMC to
open Console1.msc, and running Regedit.exe. When I tried to open the
Console1.msc as either a local or domain administrator, this message came up
"current policies prevent the Microsoft Management Console from openning in
author mode, contact your administrator for details."
>
> I also put the Terminal Service Server in a new OU and applied a new group
polciy to the OU in a hope that the OU group policy will overwrite the local
one. But it did not work. I wonder what I should do to gain access to the
local console1.msc and make changes to the policy.
>
>
> Thanks a lot!
|
Similar Threads
