RE: Workstation Shutdown / Logoff Policy :VSMail mx1

We don't do anything to force screen savers or restarts/shutdowns of PCs and
laptops.

We have managed to get most people to run as limited users. This means we do
spend some considerable time rebuilding application installers to fix where
they write logs or to change file system permissions so that they will work
for limited users. Unfortunately we still have some people who are still
running as administrators on their computers.

Peter Eden
Workgroup Technology Support
University of Toronto

-----Original Message-----
From: Kirk Foutts [mailto:kfoutts@xxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, August 17, 2006 3:13 PM
To: focus-ms@xxxxxxxxxxxxxxxxx
Subject: RE: Workstation Shutdown / Logoff Policy :VSMail mx1

This brings up another ?. I think this is a good discussion, but it
appears most are doing pretty much the same thing. The
other question
is local admin rights. Some software companies are still
writing software that require the user to have local admin
rights for their program to work correctly - as Scott says
I've had to learn to live with this. It amazes me that a
company like Corbel, now Relius with all its MS connections
and IT niches is still doing this. Anyway it seems to me that
when Vista hits, this is going to be a huge mess.



-----Original Message-----
From: Thompson, Scott [mailto:scott.thompson@xxxxxxxxxxxxx]
Sent: Thursday, August 17, 2006 9:56 AM
To: focus-ms@xxxxxxxxxxxxxxxxx
Subject: RE: Workstation Shutdown / Logoff Policy :VSMail mx1

I have a one hour lockout on the screen saver set via global
group policy. I would like to set it for a shorter time, but
I have mobile users who give presentations and whatnot
offsite. I have found that a
15 minute timout is too short, and a 1 hour - though too long
for my taste - is at least acceptable.

The last company I worked for I pushed the windows updates
using daisy - a program created in winbatch that I modified
to suit my needs - basically a WSUS server. When I inhereted
this company (as director of sysadmin :)) everyone had local
admin rights. After I learned to live with it (you have to
pick your battles) I configured everyones automagic updates
via group policy to install the udpates when available, and
then pester the user to reboot (yeah, I got some complaints
on that, but I like to call it tough love). It's actually
working quite well. When I run a baseline on the network a
day or two after black Tuesday it comes back very clean.

Cheers,
Scott

-----Original Message-----
From: Jamie Fullerton [mailto:Jamie.Fullerton@xxxxxxxx]
Sent: Wednesday, August 16, 2006 3:19 PM
To: focus-ms@xxxxxxxxxxxxxxxxx
Subject: RE: Workstation Shutdown / Logoff Policy :VSMail mx1

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.

--------------------------------------------------------------
----------
---
--------------------------------------------------------------
----------
---


--------------------------------------------------------------
----------
---
--------------------------------------------------------------
----------
---


--------------------------------------------------------------
-------------
--------------------------------------------------------------
-------------




---------------------------------------------------------------------------
---------------------------------------------------------------------------

Relevant Pages

  • Re: How to enforce password protected screen saver globally?
    ... I changed our Default Domain Policy at 4:00pm yesterday and find this morning ... that all the XP clients are operating with the screen savers policy as ... The Win2K clients are not, ... to make changes to the screen saver time out and the password protection (not ...
    (microsoft.public.win2000.security)
  • Re: Screensaver
    ... wireless Laser mouse and how it was interfering with the screen savers in windows. ... I needed to clean up my system and ended up reformatting the HD and re-installing windows, of course, I had to download all the updates. ...
    (microsoft.public.windowsxp.hardware)
  • Screensaver
    ... Some time ago I posted a message about the effect of the MS 6000 wireless Laser mouse and how it was interfering with the screen savers in windows. ... I needed to clean up my system and ended up reformatting the HD and re-installing windows, of course, I had to download all the updates. ...
    (microsoft.public.windowsxp.hardware)
  • Re: [SLE] 9.3 - KDE - Screen Saver not Saving - stalls?
    ... > 9.3, all updates, when the screen savers start, they start and run for ... I have some bizarre behavior with screen savers, ... I'm on a laptop with 9.3, and acpi is enabled, with power saving set. ...
    (SuSE)
  • control of clients screen saver/wallpaper
    ... I am new to SBS2003 and wondered is it possible to control what screen savers ... and wallpapers are displayed on clients PC's? ...
    (microsoft.public.windows.server.sbs)