We're forcing a nightly reboot using the 'shutdown' app. This is done
for two reason:
1.) can't count on the users to do it
2.) file lock issues on one regularly updated network share.
-----Original Message-----
From: Thor (Hammer of God) [mailto:thor@hammerofgod.com]
Sent: Thursday, August 17, 2006 8:55 AM
To: Focus-MS
Subject: Re: Workstation Shutdown / Logoff Policy :VSMail mx1
So, from the looks of most of the replies, folks are counting on
GPO/WSUS to enforce screenlock/updating, but rely on the end-user to
restart their systems.
Anyone actually forcing reboots?
t
On 8/16/06 12:18 PM, "Jamie Fullerton" <Jamie.Fullerton@ndbt.com>
spoketh to
all:
Our current policy is that all stand-alone workstations have their
screensaver set to a 10 minute screensaver with the password required
to log back into the system. We encourage people to power off their
machines at night but we don't become the Power Gestapo in enforcing
this.
Our WSUS is configured to redeploy an update if the client is powered
down during the initial push of an update (normally an early morning
hour with little other traffic on the network).
On our Citrix clients all clients have their session terminated after
three hours of inactivity. This ensures that all clients are logged
out at the end of the business day. If for whatever reason they are
not fully logged off the servers, the Citrix servers themselves are
rebooted once a day as well.
----------------------------------------------------------------------
-----
----------------------------------------------------------------------
-----
------------------------------------------------------------------------
---
------------------------------------------------------------------------
---
---------------------------------------------------------------------------
---------------------------------------------------------------------------
