Hardware Question


11/08/2018 895 views

Im trying to search for all devices in K1000 that do not have wake on LAN enabled in the BIOS and enable them if possible. Any ideas on how to accomplish this would be greatly appreciated!

2 Comments   [ + ] Show comments


All Answers


If you have the Command|Configure installed you can just call that install to create the bios file.  I have created a script that will read 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.


Also there is a sub-directory "HAPI" under either directory and you must also copy those files to same directory as the main program files.  The contents of the zip will look like so:

run this kscript to create a text file on all machines

This creates a file in the kace directory that you can read read all or part of with 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))

Answered 11/08/2018 by: SMal.tmcc
Red Belt

  • you can use the same zip file to run kscripts to change the bios for you. https://www.dell.com/support/manuals/us/en/04/command-configure-v4.1/dcc_cli_4.1.0/running-dell-command--configure-commands?guid=guid-841e0f66-ea28-430e-bde2-0aceb4f95d95&lang=en-us
  • I use a similar method, but since we install Command|Configure as part of our standard setup I call the cctk directly from a Custom Inventory Rule:
    ShellCommandTextReturn(cmd /c ""c:\program files (x86)\Dell\Command Configure\x86_64\cctk.exe"" --autoon --autoonhr --autoonmn)

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ