Video Screencast Help

Cannot Wake-On-LAN on a group of PCs by Altiris 7.1

Created: 28 Feb 2014 | 9 comments

I found Altiris NS can WOL one PC by tickle method successfully.

However, when I try to WOL two or more PCs, WOL is failed.

Also, I found a strange point that when WOL 1 PC, it takes 1 to 2 minutes to finish the task.

If WOL two or more PCs, the task is finished immediately.

I have no idea why WOL only success on one PC individually.

Thanks.

 

Also, can WOL wake up a group of PC by "Filters", or "Organization Group"?

(Note: all tested PCs are in same subnet and I am sure that at least one PC in that subnet is powered on)

 

Operating Systems:

Comments 9 CommentsJump to latest comment

sergei Z's picture

Hi Daniel, could you please attach the agent logs from the client machine that is supposed  to wake the other machines?

The logs can be found in "C:\ProgramData\Symantec\Symantec Agent\Logs" for Vista/2008 and greater or in "C:\Program Files\Altiris\Altiris Agent\Logs"for XP/2003

 

thanks!

sergei zjaikin, senior principal software engineer, symantec

Daniel Chan 852's picture

Hi Sergei,

Thanks a lot for your reply.

Actually, I am using tickle method for wake up the group of PCs.

Altiris NS server will find a powered on client in target subnet to send boardcast magic packet.

I don't know which powered on client is selected.

=========================================================================

So, I test it by setup an environment which has only 3 clients winXP PCs (ATS-GHOST02, ATS-GHOST03 and ATS-GHOST05) and a NS server (TEST-ATS) (attached the setting "setting.jpg")

I power off ats-ghost03 and 05 and start "tickle client" task (attached "Tasks.jpg").

It is found no new log generated in the log file of ats-ghost02 and no magic pocket captured by wireshark.

But I found it is completed the task in log of NS server (attached "a - Copy of NS.log").

=========================================================================

Note:

If I wake up ats-ghost03 only, it works fine. And I can captured the magic pocket send out by wireshark.

 

Thanks.

AttachmentSize
wol questions.zip 164.58 KB
sergei Z's picture

Daniel, could you please turn on Trace and Verbose logging severities on your server? You can do that using Altris Log Viewer, run the application, go to menu -> Options -> Log Options -> NS Settings -> Loggable Severities and checkTrace and Verbose checkboxes. 

Then please run the task again and there should be more records in the log file.

I assume your client machines are configured correctly and can be waked using WOL test utilities, right?

thanks!

sergei zjaikin, senior principal software engineer, symantec

Daniel Chan 852's picture

Hi Sergei,

Attached please found the log of NS  : "a - Copy (2PC - 3.48pm).log".

The Task (wake up 2 PCs) is send out at "Mar 04 07:48:00". Trace and Verbose are clicked.

=======================================================================

I try to wake up ats-ghost05 only by same task successfully.

And it is also success for only wake up ats-ghost03 by same task.

So, I sure that both PC are configured correctly for WOL.

Thanks.

AttachmentSize
WOL_Log.zip 29.58 KB
sergei Z's picture

Unfortunatelly you hit the old bug in 7.1 version that does not allow multiple machines to be waked up. This bug has been fixed in 7.5 release. You may want to contact the technical support to see if there is some hotfix available for 7.1 version.

Another option for you to try is to use different tasks, there are couple of "Power management" tasks in different folders and "Restart Computer" task that can also wake the machine up.

Please try them, hopefully some of them will work for you.

 

sergei zjaikin, senior principal software engineer, symantec

sergei Z's picture
Turned out there is a hot fix available.
It should be versioned 7.1 SP2 MP1 created in July of 2012 or later.

sergei zjaikin, senior principal software engineer, symantec

Daniel Chan 852's picture

Hi Sergei,

Thanks for your suggestions.

I try "Power Control" : "Wake-up (send Wake-On-LAN)" before, but it is only worked for same subnet or its IP still kept in ARP table of network switch (it will be clear after power off the PC 4 hours). However, I need to wake up PC through cross subnet.

"Power management" seems need the OOB management environment.

As you know, which method is better for waking up PC by cross subnet?

Thanks.

sergei Z's picture

Tickle is supposed to work across subnets, I'm not familiar with OOB tasks though.

Seems that there is no choice but to install that update.

sergei zjaikin, senior principal software engineer, symantec