Client Management Suite

I do not seem to have the ability to wake up machines through CMS 7.  I right-click on the machines from the computers view (Manage -> Computers).  I then click on Remote Management -> Manage Power State and Redirection.  When the box pops up, it shows me reboot and power off  when the computer is powered on.  When the machine is powered off, reboot and power off are obviously greyed out.  Power on is greyed out all the time, regardless of power state on the pc. 

Am I missing a piece of CMS 7?  I thought I installed the full Client Management Suite, but I don't seem to have the ability to wake up pcs through it.  WOL is working fine through DS 6.9 SP5 as well as our current production NS 6 server.  This CMS 7 server I am testing with prior to migrating does not seem to give me the ability to use WOL on machines.  I'm sure it is due to the fact I'm so new with CMS 7.  I just need to know what I am missing or if I am looking in the wrong place.

Hi.

Power states from "Manage Power State" menu are managed using different technologies. Power-Off and Restart could be done using VMI. But to power-on the computer it should support the out-of-band technology (ASF, AMT or DASH) on hardware level and these technologies should be properly configured. To detect computers with out-of-band support you may enable "Out of Band Discovery" policy (Settings -> Agents/Plug-ins -> Remote Management -> Out of Band Management -> Out of Band Discovery). Once the OOB computers discovered, you should install "Out of Band Task Agent" to them and configure the supported OOB technology (you may use "OOB Management" portal from "Console -> Home -> Remote Management" and documentation for OOB Management solution).

Alternatively you may use NS WOL task that utilize network adapter's WOL functionality (please see the attachment. to change the default selection of this task you need to clone it).

Hope this helps,

Alex.

Alex Bizjajev,

I'm looking into the OOB settings now.  I did have everything enabled and installing, but it's not having much luck waking configured and enabled machines either.  I just started on it, though, so I'll take some more time with it.

As for the NS canned job, I have already cloned that and made a power on job.  When I run it, it takes the full 5 minute timeout (default setup) and shows that the job completed.  Unfortunatley, the job never actually does complete.  The console reports it completed, but the machine still does not wake up.

Looks like OOB is not working properly because the Intel AMT items are not installed.  Upon further investigation, it appears that this requires SQL 2005.  Since this is still just a test server with limited clients, I only installed the SQL Express that came with CMS 7.  I'm assuming that I will not be able to get Intel AMT to work without having SQL 2005 installed, so I guess I can give up on that testing for now.

This still doesn't explain why the WOL event (after cloning the canned event) will not work.  If this works the same way NS 6 did, I should not be having any issues.  Everything is configured the same way on this test server as our production NS 6 server.  WOL is working fine from the NS 6 server.

Hi Jeremy,

I could suggest to launch NS log, select to log all the trace messages in "Options->Log Options" and execute the task - if there won't be any obviouse errors then try to verify the client's IP and port availability from the NS server computer (or from the task server computer if you have standalone task-server).

Thank you,

Alex.