Deployment Solution

Does anyone know if there is a fix for the broken WOL in DS 6.9 SP5?

This affects WOL attempts thorugh remote WOL Proxies and is mentioned as a known problem in the release notes up to MR2.

The axEngine after an undetermined period of time stops sending out WOL MAC addresses in the SendWOL= communication. AxEngine sends blank MAC address to WOL proxies, WOL stops working

I guess Symantec don't really care about 6.9 users much now and are trying to push users to that horribly unweildy 7.1.

Hi Jeremy,

This has been a problem for many releases of DS -it's not just SP5 MR2.

The problem is from a troubleshooting point of view is that Symantec Support haven't been able to get resources to a customer in time to investigate it before they've had to restart the engine (the workaround). 

I've had a couple of hopeful calls asking if it's a problem *now*, but this bug isn't helpful -it's not even easily reproducible in the *same* environment. This particular bug in my mind isn't therefore an issue of neglect by Symantec.

If however you are unlucky (or lucky) enough to have this being a constant niggle then support will certainly love to talk to you. Anything which would finally get to the bottom of this one will be helpful and much appreciated I'm sure.

Kind Regards,
Ian./

Well the new semester has begun today and I'm seeing this problem again.  Ever since we expanded Altiris to cover the offsite campuses, I've had this problem.  There was a long lull with the summer break, but today the server has already hung up multiple times. 

We have less than 3000 clients around the county so I would think DS could handle it - but that's proving not to be the case. 

And I don't believe that that Article 4214 is worth much.  It's showing I have 292 clients with Refresh Connection enabled (still a work in progress).  Could 292 out of 3000 cause this much grief?? 

Restarting the server takes care of it for a little while.  But rebooting a server multiple times a day is one pathetic way of handling the issue. 

Why can't Symantec/Altiris get this right?  Seriously?  How many years has the product been out and yet continues to suffer from this same thing? 

I do understand your frustrations -you seem to suffer from this issue a lot worse than we do here. Have you raised this with support? As it's so frequent, I think support might want to get you running the debug version of the engine.

Kind Regards,
Ian./

Thanks for the response ian.  I actually have not contacted support yet because I dread the battle of trying to convey to some Indian who knows nothing about Altiris the issues I'm having only to be asked repetitive and irrelevant questions and given scripted suggestions as solutions.

I've called them before and I absolutely, hate it.  HATE IT.  I mean, it's like speaking with some random Joe off the street, who barely knows English, and has an Altiris manual in front of them to read from.  Eventually you can get through to someone who knows something, but I disdain that first layer response so much that I do everything in my power to figure it out via the forums, threads, knowledgebase etc.

Sorry for the rant :-/

I'm continuing to read through more articles, and even going back through the initial setup for now.  I'm close to biting the bullet though.

Once you've gotten through the front line of support, you should be fine and talk to someone more knowledgeable.

I fondly recall having to spell out A-L-T-I-R-I-S to the front line folks. You just have to see the funny side sometimes.....