|
Posted by SecAdmin on April 30, 2007, 10:24 am
Please log in for more thread options
am trying to understand if it is ok to do a machine shutdown instead of a
domain logoff. We would like everyone to logoff their domain account each
day, but many just shutdown their computers. Does a shutdown do an orderly
domain logoff?
|
|
Posted by S. Pidgorny on April 30, 2007, 5:10 pm
Please log in for more thread options
If not using the power button, yes. It performs user logoff, running logoff
scripts, then running shutdown scripts (that is what's diffeent), then
poweroff.
Wehy do you insist on the domain logoff for the users every day?
--
Svyatoslav Pidgorny, MS MVP - Security, MCSE
-= F1 is the key =-
* http://sl.mvps.org * http://msmvps.com/blogs/sp *
> am trying to understand if it is ok to do a machine shutdown instead of a
> domain logoff. We would like everyone to logoff their domain account each
> day, but many just shutdown their computers. Does a shutdown do an
> orderly
> domain logoff?
|
|
Posted by DevilsPGD on May 1, 2007, 1:05 am
Please log in for more thread options
>If not using the power button, yes. It performs user logoff, running logoff
>scripts, then running shutdown scripts (that is what's diffeent), then
>poweroff.
>
>Wehy do you insist on the domain logoff for the users every day?
If another user will be using the machine before the original user
returns, this policy is absolutely critical since the new user cannot
safely log the old user off.
(Think of a 24/7 call center, where desks are typically shared -- Or any
shared computer environment really, be it part time, 24/7, or annoying
"new desk every day" environments)
At my $DAYJOB, it's recommended although not mandatory, as this allows
machines to patch themselves using the "Reboot if no user is logged in"
group policy, and allows login scripts to adjust machines to match
network changes (okay, this is rare, but it's a valid scenario)
It also ensures that a roaming profile is uploaded to the server so that
it can be backed up, so that users never lose more then a day's worth of
work should the machine suffer a failure while in operation.
I could probably dream up a few others. The first is the most common
I've run into in my professional experience.
--
Ah, the miracle mile, where value wears a neon sombrero and there's
not a single church or library to offend the eye.
-- Homer
|
| Similar Threads | Posted | | Port requirements for remote shutdown using 'shutdown -s -m \servername' | June 24, 2006, 6:15 am |
| Super Fast Shutdown | November 29, 2007, 6:26 pm |
| "Force shutdown from a remote system" | October 13, 2006, 3:26 pm |
| Shutdown with minor causes 0x84010001 and 0x80070020 | November 30, 2006, 2:25 pm |
| getting users to logoff | January 14, 2008, 11:47 am |
| Delete files with logoff/on script | June 3, 2008, 4:42 am |
| track employee time using logon & logoff | December 13, 2006, 7:40 pm |
| audit logon/logoff events on terminal server | July 18, 2007, 10:29 am |
| Excessive computer account logon/logoff loggining on security log | September 12, 2006, 5:23 am |
| Logon/Logoff Events in Local Security Log of Terminal Server | July 20, 2007, 2:39 pm |
|
XML Sitemap