J.R. Sitman
asked on
I am looking for an Alternative to EMCO Remote Shutdown
We use EMCO Remote Shutdown to reboot computers at all our offices. The program is great, however, the latest version is very expensive.
We currently leave all the computers on so they get updates at night. I have them scheduled to reboot twice weekly.
I am looking for suggestions on an alternative.
We currently leave all the computers on so they get updates at night. I have them scheduled to reboot twice weekly.
I am looking for suggestions on an alternative.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
What are the exact requirements?
Is it enough just to go through the Active Directory computers and reboot if reachable, running this as a PowerShell task twice a week at a single machine?
Do you need logging, if yes to which extent?
Is it enough just to go through the Active Directory computers and reboot if reachable, running this as a PowerShell task twice a week at a single machine?
Do you need logging, if yes to which extent?
ASKER
I do not want to use PowerShell. No experience.
1. Be able to scan the domain and add computers
2. Be able to reboot on a schedule, at least twice a week
3. Get emailed on success or failure
4. Keep records of success or failure
1. Be able to scan the domain and add computers
2. Be able to reboot on a schedule, at least twice a week
3. Get emailed on success or failure
4. Keep records of success or failure
I do not want to use PowerShell. No experience. [snide remark on] I don't want to read. No Experience [snide remark off]
The easiest way to get experience is by doing. None of us knew how to walk but after several failed attempts we learned how to.
starter script
If computer is off then is it a success or failure?
if we cannot connect to computer is it a failure?
if we send the restart command do we wait for it to come back online? Could be an hour if doing significant updates.
The easiest way to get experience is by doing. None of us knew how to walk but after several failed attempts we learned how to.
starter script
# Get a list of computers
$computers = get-adcomputer -filter * | select-object -expandproperty name
# Item one completed
$mycomputer = $env:computername # we don't want to restart this computer until the end
foreach ($computer in $computers) {
if ($computer -ne $mycomputer) {
restart-computer -name $computer
}
}
restart-computer -name $mycomputer
}
define exactly what you mean by success or failure? If computer is off then is it a success or failure?
if we cannot connect to computer is it a failure?
if we send the restart command do we wait for it to come back online? Could be an hour if doing significant updates.
ASKER
Thanks for the feedback and I agree "is by doing". But not going to learn Powershell. :-)
EMCO lets you emulate the DomainYes, and very expensive
ASKER
RemoteRebootx is not exactly what I was looking for but it was the best option.
Thanks
Thanks
ASKER