Wake-on-LAN Schedule Relay Labels?
I created a WOL schedule yesterday to wake computers in a lab 30 minutes before patching begins. From what I see based on the detect and deploy job, the WOL command didn't deploy to the computers. I have verified several times that WOL does with with these desktops by sending WOL commands to the computers from the K1000 and Symantec Ghost. Do I need to assign a Relay Label? What is a relay label?
Setup a smart relay label for each of your subnets and use that as the machines to do the wol command. You just need one machine in that label to be on. The only time your WOL will work without a relay label is the machine you have a browser to the SMA open and you want to wake machines on that same subnet.
If you have the Command|Configure installed you can just call that install to read or change the bios file. You do not need to create the zip, just call the cctk.exe from that install directory.
I have created a scripts that will read or change the bios on Dell machines even if the CCTK is not installed. I installed the command configure on my tech station and just grabbed the needed files from it and added them as dependencies to the script.
To do this you need to create a ZIP from the Command|Configure installed to any workstation. You can get the install here:
(you can also create a distribution with the SMA to push out to all machines if you prefer it installed vs portable)
After it installs on the station navigate to (this is on a x64 machine) the install directory and send the four files and the files in the HAPI sub-directory to a zip file
The sub-directory "HAPI" under either directory, you must also copy those files to same directory as the main program files. The contents of the zip will look like so:
This gives you a zip file you can attach to a kscript to call the program if you do not have it installed. If installed just point the kscript to install directory.
the commands can be found here:
These will be the 3 settings you need to set:
cctk --autoon=selectdays:Fri --autoonhr=22 --autoonmn=35
Use the script above as an example (you need to load hapi to get commands to process) then you can create launch lines for the cctk to do the tasks. You can set and also change set bios passwords with a script.
if you want a station to be booted when you walk in
cctk --autoon=weekdays --autoonhr=06 --autoonmn=30
You can also use this to read the bios into CIR's
to read the entire file:
Shellcommandtextreturn(cmd /c if exist C:\ProgramData\quest\KACE\user\bios.txt type C:\ProgramData\quest\KACE\user\bios.txt)
to read one line from the file use the findstr command
CIR List Bios Boot Order
ShellCommandTextReturn(cmd /c @echo off && for %g in (c:\programdata\quest\kace\user\bios.txt) do (findstr /b /c:"bootorder" %g))
CIR get wake on lan status
ShellCommandTextReturn(cmd /c @echo off && for %g in (c:\programdata\quest\kace\user\bios.txt) do (findstr /b /c:"wakeonlan" %g))
CIR get embnic status
ShellCommandTextReturn(cmd /c @echo off && for %g in (c:\programdata\quest\kace\user\bios.txt) do (findstr /b /c:"embnic" %g))
CIR get deep sleep ctrl
ShellCommandTextReturn(cmd /c @echo off && for %g in (c:\programdata\quest\kace\user\bios.txt) do (findstr /b /c:"deepsleepctrl" %g))