Jump to content

Software to shutdown multiple remote PC's, that integrates with AD?


Recommended Posts

Posted (edited)

Hi Guy's/Gal's,

 

I was wondering if anyone knew of any software to shutdown multiple remote PC's, that integrates with AD? But also has a report function built-in, eg how many PC's were left on, the amount of money saved by shutting down those PC's, how "green" we are and any other reports that may be requested.

 

Thanks

 

-Ken

Edited by Kitkatninja
thanks added
Posted (edited)

I have written a little batch file which runs PSShutdown. This file also writes back to the server echoing the on screen messages [effectively recording everything that is displayed while PSShutdown is running.

 

I have a single GPO calling the batch file for all the workstation/laptops in all OUs on the domain but I plan to have differing GPOs so that the shut-down can start at different times and allow staff to cancel the shut-down if they are working at a dedicated staff [only] machine.

 

I can post more details tomorrow.

 

Would this be of any use?

Edited by 6Foot2
Add detail to the post.
  • Thanks 1
Posted
I'd be interested in such a batch file to go into my "little black book" for future reference!

 

OK I will post what I have tomorrow.

Posted (edited)

This is what I have in place currently:

 

echo. | time/t > PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

psshutdown -m "This computer will shutdown in 5 minutes. Please save any unsaved work." -t 300 -f \\Station01.ChildDomain.ParentDomain.local >> PSShutdown.TXT 2>&1

echo. | time/t >> PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

psshutdown -m "This computer will shutdown in 5 minutes. Please save any unsaved work." -t 300 -f \\Station02.ChildDomain.ParentDomain.local >> PSShutdown.TXT 2>&1

echo. | time/t >> PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

psshutdown -m "This computer will shutdown in 5 minutes. Please save any unsaved work." -t 300 -f \\Station03.ChildDomain.ParentDomain.local >> PSShutdown.TXT 2>&1

echo. | time/t >> PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

.....

.....

.....

psshutdown -m "This computer will shutdown in 5 minutes. Please save any unsaved work." -t 300 -f \\Station300.ChildDomain.ParentDomain.local >> PSShutdown.TXT 2>&1

echo. | time/t >> PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

psshutdown -m "This computer will shutdown in 5 minutes. Please save any unsaved work." -t 300 -f \\Station301.ChildDomain.ParentDomain.local >> PSShutdown.TXT 2>&1

echo. | time/t >> PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

psshutdown -m "This computer will shutdown in 5 minutes. Please save any unsaved work." -t 300 -f \\Station302.ChildDomain.ParentDomain.local >> PSShutdown.TXT 2>&1

echo. | time/t >> PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

 

This is the output at the server:

 

06:30 PM

Wed 07/01/2009

06:30 PM

Wed 07/01/2009

PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems

Copyright © 1999-2006 Mark Russinovich

Sysinternals - www.sysinternals.com

The network path was not found.

Connecting to Station01.ChildDomain.ParentDomain.LOCAL...

 

Couldn't access Station01.ChildDomain.ParentDomain.LOCAL:

Make sure that the default admin$ share is enabled on Station01.ChildDomain.ParentDomain.LOCAL.

If Station01.ChildDomain.ParentDomain.LOCAL is already performing a shutdown operation you must

abort it before issuing a different command.

06:31 PM

Wed 07/01/2009

PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems

Copyright © 1999-2006 Mark Russinovich

Sysinternals - www.sysinternals.com

Station02.ChildDomain.ParentDomain.LOCAL is scheduled to power off in 00:05:00.

Connecting to Station02.ChildDomain.ParentDomain.LOCAL...

 

Starting PsShutdown service on Station02.ChildDomain.ParentDomain.LOCAL...

 

Connecting with psshutdown service on Station02.ChildDomain.ParentDomain.LOCAL...

 

06:31 PM

Wed 07/01/2009

PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems

Copyright © 1999-2006 Mark Russinovich

Sysinternals - www.sysinternals.com

Station03.ChildDomain.ParentDomain.LOCAL is scheduled to power off in 00:05:00.

Connecting to Station03.ChildDomain.ParentDomain.LOCAL...

 

Starting PsShutdown service on Station03.ChildDomain.ParentDomain.LOCAL...

 

Connecting with psshutdown service on Station03.ChildDomain.ParentDomain.LOCAL...

 

06:31 PM

Wed 07/01/2009

....

....

....

 

I have bracketed each station/laptop shutdown command with

 

echo. | time/t > PSShutdown.TXT

echo. | date/t >> PSShutdown.TXT

 

because at the time of writing the batch file we were having trouble with comms on our network and I wanted to see:

 

If the stations were seeing the shutdown command/being found by the shutdown command.

How long it was taking to go from station to station.

 

It may not be very neat but it does the job.

 

I will be moving away from this method of shutting the stations down soon. When I wrote the original version of this batch file we were using Server 2003. We have since moved over to Server 2008. I can now add a scheduled task in Group Policy for each OU. Once the sheduled task is in place the scheduled task will run locally and all the stations will shutdown together, rather than sequentially, so I can have all stations shutdown in less than 5 minutes [compared with the 3 to 4 hours it currently takes]

 

Hope this helps.

Edited by 6Foot2
Correct post content.
  • Thanks 2
  • 3 weeks later...
Posted
Hi Guy's/Gal's,

 

I was wondering if anyone knew of any software to shutdown multiple remote PC's, that integrates with AD? But also has a report function built-in, eg how many PC's were left on, the amount of money saved by shutting down those PC's, how "green" we are and any other reports that may be requested.

 

Thanks

 

-Ken

 

Hi.

You can use Network Shutdown Tool. It's program can shutdown, reboot, wakeup a group of network PCs.

I have been using this program on our domain.

Posted
Lanview 3 is a great little piece of software that tells you how long a machine has been left on. We have a hit list of staff that are prone to leaving machines on.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...