Problem is.. i cant remember where these came from.. I thought it was
a communicator.adm file... but now i'm wondering if it was a custom
adm i wrote but cant find it in the add/remove adms section..
Can anyone refresh my memory on how to remove these.. they are
interfering with 2007 communicator settings that I need to change,
forcing things to be locked out.. whats worse is.. they aren't in
their own policy like they should be.. i intertwined them in the
default domain policy when i did this..
Thanks for any help
You can use rsop.msc to check if settings are applied through GPO
--
Cordialement,
Mathieu CHATEAU
English blog: http://lordoftheping.blogspot.com
French blog: http://www.lotp.fr
"markm75" <mark...@msn.com> wrote in message
news:1193017104....@i13g2000prf.googlegroups.com...
markm75 schrieb:
> Can anyone refresh my memory on how to remove these.. they are
> interfering with 2007 communicator settings that I need to change,
> forcing things to be locked out.. whats worse is.. they aren't in
> their own policy like they should be.. i intertwined them in the
> default domain policy when i did this..
Have a look at the Default Domain Policy and see if the settings are
made there. You can check with rsop.msc on a client, that has the
settings applied. Rsop.msc shows you where policy settings come from.
Once you're sure they're from the DefDomPol (or any other policy), you
can edit the policy again and set the settings to "Not configured" to
reset everything to the default value.
If that is a custom ADM template you created yourself and the settings
are not stored within the following regkeys:
HKEY_LOCAL_MACHINE\Software\Policies
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies
HKEY_CURRENT_USER\Software\Policies
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies
you'll have to reset the settings (maybe from "Disabled" to "Enabled" /
from "Enabled" to "Disabled") because outside these 4 reg-paths, the
default value will not be set back to the "default" when you choose "Not
configured".
See:
http://www.gpoguy.com/FAQs/tattoo.htm
cheers,
Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Well i did verify where these are coming from.. its definitely the
def. dom. policy.. "extra registry settings".. via :
HKEY_LOCAL_MACHINE\Software\
sub keys..
Problem is.. in the def. domain policy, i dont see these settings
anywhere, so i'm not sure how to "remove" them per say.. they aren't
in the gui anyway.....
I was able to verify.. its definitely the settings under HKLUsers \
software\policies\Microsoft\Communicator..
If i delete this key.. "communicator" then i can change the settings
in the communicator 2007 client, which were previously just "blank"..
Now I just need to find a way to do this deletion globally...
Obviously i cant just disable the default domain policy?
markm75 schrieb:
> I was able to verify.. its definitely the settings under HKLUsers \
> software\policies\Microsoft\Communicator..
>
> If i delete this key.. "communicator" then i can change the settings
> in the communicator 2007 client, which were previously just "blank"..
>
> Now I just need to find a way to do this deletion globally...
> Obviously i cant just disable the default domain policy?
Okay - as you said, it's the DefDomPol - so you should be able to import
that Communicator.adm template again (right-click "User Configuration"
node - "Add/Remove template..") and then edit the policy (e.g. set them
back to "Not Configured") and everything should get back to "normal".
This was the ticket! Thanks again for the refresher :)