I read a couple of entries for VPro & Landesk but I am stuck of figuring out why Landesk is not mass waking up the devices during the scheduled tasks. Here in my organization, we are using Landesk v 8.8 on SP3. Our clients were provisioned using Simple Business because these are desktops & currently we don't have certificates for an Enterprise mode provisioning.
Here's the present scenario
- I have an office 2007 software distribution and I would like to do this off hours. I did check the 'Wake up devices' but it only turns on 1 / 100 devices per roll-out
- I was expecting that Vpro will mass turn on all devices and then install my MS office 2007
- What happened was when i clicked start now and 100 devices were dragged into the scheduled task, only 1 device was turned on by VPRO and the rest turned out to have an "OFF" status with message - Cannot find agent.
- I tried, minimizing the number of targets to 3 in order to isolate and the results were not consistent. sometimes only 1 device is turned on out of 3. sometimes when i use another set of 3 devices vpro turns them all on.
- I confirmed all devices were correctly provisioned and i can access them using the native http://<ip address>:16992 console & with the username & password.
Is there anyone out there experiencing the same problem as i have?
Thanks so much in advance for your answers.
There is a post SP4 patch that should address this issue for you. The vPro wake up command to more than one machine were overwritting each other so the last one seemed to be the only one waking up.
This is included in LDMS 9.0 sp1 as well
Thanks Rex. I'm relieved to know that this is already addressed by SP4 and LD 9 SP1. Since we are moving towards LD9, I think this is the most sensible path.
I can't wake a vpro machine and when i called tech support they said that WOL should be enabled in BIOS. This is besides Subnet Directed Broadcasts, which is another topic.
I can "Power On" a vpro device manually, but wake on lan doesn't work on a scheduled task even if Subnet Directed Broadcasts are allowed.
the vPro machine has to be provisioned to the LANDesk server then it can be woken up by vPro. You only have to enable it in the BIOS is you want to use the default WOL. Also vPro WOL does not use subnet directed broadcasts. WOL with vPro is an entire different process than the normal WOL. Sadly there is not a lot of vPro knowledge in support.
I didn't know that. So since i'm in the same boat as Christopher John, does this mean that by checking "Wake Devices" in a scheduled task this will wake all vpro capable devices (that have been provisioned) without changing the BIOS settings?
you can look at the task logs to see if they are reporting that it thinks the machine is vPro or not.
what version and patch level of LANDesk are you using?
I do have a GUID value in inventory scan.
So this means that these devices will use WOL from vPRO?
Cool. I'll give that a try to see how it work. I'll also make sure to disable WOL in BIOS also.
We are using Version 9 SP2
If you have the GUID and the mode of operation set in the inventory then it should attempt to use vPro wake up and if it fails then it falls back and attempts the BIOS WOL.
The other tests you may have done already is having the machine off and BIOS WOL disabled and selecting the vPro wake up option from a right click menu.
The calls come from different locations for a scheduled task but it was something that should have been fixed in 9.0 sp1 and should be in sp2 unless a change in sp2 broke it unintentionally I am sure