I'm a student from Belgium, currently working as an intern at VTB-VAB. My job is to make a complete analysis of software that has the ability to remotely deploy / distribute other software packages to clientpc's.

When testing prism everything works fine except for one strange issue with the WOL option. It seems to boot 5 clients out of 10 in my testenvironment. I'm using a DHCP server, the clients have ben separated into 2 different OU's in active directory. It seems to boot and install the computers in OU "bkh" fine, but the computers in OU "ict" aren't booting at all.

I've tried out shareware to boot my computers and that works fine.

Anybody got a clue how to solve this issue?

With kind regards,

freakkzz

Here are some troubleshooting ideas:

·         Are the 5 computers in the "ict" OU in a different network segment from the ones in "bkh" OU? (Check tcpip subnet settings on computers in both OUs to find out.) If so, you need to have an awake and polling computer in the ict OU to forward Prism’s wake up packets to the powered-off computers in that network segment. Power-on one of the 5 computers in ict, then assign the wake-up task to the other 4 computers.

·         When you configured the properties of the task for the ict OU, did you set it up to allow unattended installation?

·         Do other tasks successfully run when assigned to computers in the ict OU?