Re: Screensaver Group Policy not working

so the "_" was the real problem?
Great.

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"Cyborg" <andrewwhite@xxxxxxxxxxxxxx> wrote in message
news:1A7FB2C6-7B59-4E9F-AB87-0557835D10C2@xxxxxxxxxxxxxxxx
I think all it was, was the fact that the screensaver name had an
underscore between the name eg "my_screensaver.scr" renamed it to just
"screensaver.scr" and it worked.
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:ee%23Fn3cBIHA.2268@xxxxxxxxxxxxxxxxxxxxxxx
Is the screensaver working?

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"Cyborg" <andrewwhite@xxxxxxxxxxxxxx> wrote in message
news:44AC8909-A60B-46B1-8C1B-2B3F69236AE0@xxxxxxxxxxxxxxxx
Should the screensaver tab say "none" it;s greyed out which is right,
just not sure if it should say the name of the screensaver?


"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:uxyLsHaBIHA.4956@xxxxxxxxxxxxxxxxxxxxxxx
You selected the enforce option and is being applied?

In that case you should have a conflict Policy at the OU or you have
the setting "Block Inheritance" enabled at OU level.

Now you've the correct Screen Saver but isn't working? In that case I
suggest you to check if the any installed program is interfering with
the screen server, or if the screensaver is working correctly, or you
may want to check if any of these KBs help:

http://support.microsoft.com/kb/305357
http://support.microsoft.com/kb/815424
http://support.microsoft.com/kb/816563


--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"Cyborg" <andrewwhite@xxxxxxxxxxxxxx> wrote in message
news:74F169C1-FE83-4989-B8B8-4CBF1AFBEDAC@xxxxxxxxxxxxxxxx
I just selected the enforce option on the default domain policy and ran
the rsop.msc and it now says the correct screensaver name, but if i go
to the screensaver tab on the latop it is greyed out and blank.


"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:u64AVuZBIHA.5752@xxxxxxxxxxxxxxxxxxxxxxx
After you ran rsop.msc you say that the old screen saver policy is
use correct?
Because this is a user policy and assuming that you used that same
policy to change the screen saver, 2 things can be happening:
1- The User isn't getting the most recent policy (this can be cause
because of machine configuration, connectivity issues, or GPO
permissions)
2 - SMB signing is required on the domain controller but isn't
enabled on the client machine.
3 - You've loopback policy assigned to the magine and it's overriding
the modified GPO (In that case you can follow Florian suggestion).

Check errors and/or warnings in eventlog. Userenv debug log can also
be used to track down the problem.
-

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"Cyborg" <andrewwhite@xxxxxxxxxxxxxx> wrote in message
news:866D56E0-7C9B-4711-AA9C-B5A121217541@xxxxxxxxxxxxxxxx
Thusing that rsop.msc, the policy is still using the old screensave,
the thing is this is the default domain policy, any ideas?


"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:eIbaYkSBIHA.324@xxxxxxxxxxxxxxxxxxxxxxx
type in cmd
Rsop.msc

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"Gonzo" <apollo13@xxxxxxxxxxxxxx> wrote in message
news:%238dyqHSBIHA.4496@xxxxxxxxxxxxxxxxxxxxxxx
I always do the gpupdate /force and logoff, not tried the other
part, how do I do that?

"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message
news:O%23ngE9RBIHA.4160@xxxxxxxxxxxxxxxxxxxxxxx
Hi
run gpupdate /force, logoff login then on the workstation and
then use the rsop.msc and check if the policy is being applied
correctly.

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

"Gonzo" <apollo13@xxxxxxxxxxxxxx> wrote in message
news:%23xp7B7RBIHA.5652@xxxxxxxxxxxxxxxxxxxxxxx
This is strange, I have had everyone use the logon.scr via a
group policy. We now have had new one designed and I have had a
logon script copy it to everyones system32 folder and then
changed the group policy to the new sreensaver name, but it
never gets changes. All users still use the logon.scr, any ideas
why? There screensaver options are all greyed out which is how I
like it, could this be the problem?



















.

Relevant Pages

  • Re: Operations Masters
    ... Jorge Silva ... MCSE, MVP Directory Services ... it does not connect to DC1, ...
    (microsoft.public.windows.server.active_directory)
  • Re: IE Clear Upon Exit - Impact I/O
    ... Jorge Silva ... MCSE, MVP Directory Services ... Please no e-mails, any questions should be posted in the NewsGroup ...
    (microsoft.public.windows.server.active_directory)
  • Re: Need to force logoff for one user only at night
    ... Jorge Silva ... MCSE, MVP Directory Services ... after the client's logon hours have expired. ...
    (microsoft.public.windows.server.active_directory)
  • Re: what gpo setting is this?
    ... Jorge Silva ... MCSE, MVP Directory Services ... For that policy you need to create a conflict policy that reverses ...
    (microsoft.public.windows.server.active_directory)
  • Re: Auditing on DC.
    ... Jorge Silva ... MCSE, MVP Directory Services ... policy. ...
    (microsoft.public.windows.server.active_directory)
Loading