Re: Locking Workstation Group Policy
From: Special Access (nonyadbidnezz_at_hotmail.com)
Date: 12/08/04
- Next message: Rebecca Chen [MSFT]: "RE: office sp1"
- Previous message: Chupacabra: "Active Directory Group Policies not showing in Group Policy editor"
- In reply to: Michael Ellingson: "Re: Locking Workstation Group Policy"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Locking Workstation Group Policy"
- Reply: Lanwench [MVP - Exchange]: "Re: Locking Workstation Group Policy"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 08 Dec 2004 21:12:57 GMT
On Wed, 8 Dec 2004 11:16:23 -0800, "Michael Ellingson"
<814ba72b1794496625@news.postalias> wrote:
nope. Users don't need admin rights to install something unless it
accesses the registry. If all it does is put itself in the WINNT dir
(if the user has write access) then it will work. We had a run in
last year with all the free christmas 3d screen savers to the point
where we limited the user's right to write in the WINNT directory.
>It does work and yes, it is groovy! :) I was a little worried about it
>working since the documentation does indicate you need all four configured.
>Giving users the flexibility to select their own screen saver helps dampen
>the fact we've got their computer locking automatically!
>
>As far as users installing their own screen savers, they should not be able
>to if they don't have local admin rights, right?
>
>"Andy Vaya" <herbwarrior@mmecpa.com> wrote in message
>news:eRMPIgV3EHA.3452@TK2MSFTNGP14.phx.gbl...
>> That's different from the documentation on the Screen Saver timeout
>> policy, but, if it works, groovy. I still like to specify screen saver
>> file in policy because it discourages users from trying to install them
>> (which can cause problems).
>>
>> Andy
>> "Michael Ellingson" <814ba72b1794496625@news.postalias> wrote in message
>> news:%230XF$ZV3EHA.4092@TK2MSFTNGP14.phx.gbl...
>>> Why do you not want to use the Screen Saver timeout policy? Our company
>>> uses it to lock our XP and 2000 workstations. We're using Screen Saver
>>> (Enabled), Screen Saver executable name (Not configured), Password
>>> protect the screen saver (Enabled), and Screen Saver timeout (Enabled)
>>> policies. This lets the user specify their own screen saver and if they
>>> don't specify one, the computer simply locks.
>>>
>>> Depending on your corporate objectives, this may work for you and give
>>> your users the flexibility to select their own screen saver.
>>>
>>> "Mike" <Mike@discussions.microsoft.com> wrote in message
>>> news:D4606F2A-38BE-48A8-82D4-5C48465770CE@microsoft.com...
>>>> Is there a Group Policy within Win 2003 Server that would allow a W2K or
>>>> WinXP workstation to be locked after a period of inactivity without
>>>> using the
>>>> password protect option with the screen saver?
>>>> We don't mind if the user has a particular screen saver they want to
>>>> use,
>>>> but we want to lock the workstation if not used within a time period.
>>>> We are trying to enforce the locking on any authenticated workstation
>>>> logged
>>>> onto the network.
>>>>
>>>>
>>>
>>>
>>
>>
>
- Next message: Rebecca Chen [MSFT]: "RE: office sp1"
- Previous message: Chupacabra: "Active Directory Group Policies not showing in Group Policy editor"
- In reply to: Michael Ellingson: "Re: Locking Workstation Group Policy"
- Next in thread: Lanwench [MVP - Exchange]: "Re: Locking Workstation Group Policy"
- Reply: Lanwench [MVP - Exchange]: "Re: Locking Workstation Group Policy"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|