GSS 2 Define task with only WOL
Updated: 21 May 2010 | 8 comments
This issue has been solved. See solution.
We have 4000 workstations spread out over 10 facilities. I am trying to implement as much remote management on the machines for imaging and updates as possible.
We use Deep Freeze on all machines so there is a step between WOL and applying an update.
Since the list of machines and Mac addresses is persistent in GSS and is not in Deep Freeze I want to define a GSS task that will only send out WOL signals to groups of workstations.
What would be the simplest quickest non-change I could add to a task to use for this?
Discussion Filed Under:
Comments
Create a task
i am running console 11.5.1 and i was able to create this pretty easily.
create a new task
name it
click the network tab, check "use WOL"
back on the network tab hit "browse" on target machine group, highlight your desired group.
save
execute as desired
now you mentioned that you have 10 sites, i would assume they are seperated by routers or at least intellegent switches. depending on your network enviroment and how its configured you may not be able to send a WOL packet across subnets without additional configuration. Wake On Lan is typically done via multicast and forwarding multicast traffic is almost always disabled on intellegent switches and routers. but thats a different discussion
I have a console machine
I have a console machine sitting in the MDF of each facility so the packets make it to the machines.
Console version is 11.0.2.1573 and with just WOL selected on the NW tab and a target machine or groups the Execute tab stays greyed out until I add a task step.
To get around the greyed out
To get around the greyed out Execute button, just select "Refresh Configuration" on the General tab. This won't hurt your computers to do this, and it will keep the console up to date to boot.
I would agree that selecting
I would agree that selecting "Refresh Configuration" only is the way to go. Do not select "Refresh Inventory" however as it takes longer and requires more interaction with the machine. Export the Task Log to a text file for a handy summary of which machines woke correctly (If the refresh task ran, then the machine awoke). You can then check the WOL config locally if there is an issue on a specific machine.
Deep Freeze should not be
Deep Freeze should not be droping names out of the machine history. Once they have been discovered by the Deep Freeze Enterprise console, they should be persistent.... providing you are using version 6.x+.
I agree it should not drop
I agree it should not drop machines. Faronics says it should not drop machines.
The DF console is running ver 6.61. When I set the console up I had techs turn every machine in the building on and they all reported. If I turn them on now they popup on the appropriate group again.
I have the console set to WAN, network connections are set to stay on after console is shut down and a static ip which is in the client install but ......
must be an older version
that sounds like maybe a problem with the older version. how about haveing it execute a trivial task such as inventory refresh? that should make it an "official" task and allow you to save the job
It works if I do add
It works if I do add a step but the task runs for a very long time without completing. Doesn't look like it hurts anything to cancel it out and continue with the DF console.
Would you like to reply?
Login or Register to post your comment.