03-04-2009 03:30 AM
Your're english is certainly better than mine :)
I again would suggest to Symantec that they know who the people are and this time I will call them moaners having network problem and especially having a customer base and that I AGAIN, request a link be sent to my email for both the english and the french version of this new patch.
This is the only acceptable solution for me and barring that, I don't think I will even try to reload 2009 on the servers for the remaining time of my customers subscriptions.
I don't have to spell out what I will suggest for the 2010 version do I.
PS, Hope this english version is good enough for you to understand Tony
03-04-2009 08:19 AM
03-04-2009 12:31 PM
Report on patch: I have been running the updated NAV2009 since yesterday approx. 9:30am. No problems yesterday. Today we had a problem on one workstation with an email program acting strangely (it stores the mailboxes and other data on the shared hard drive on the server that is running NAV2009). Symptoms were different than what we had seen when NAV2009 blocked access to the server's disk. Rebooted the workstation and everything works, which leads me to believe that it was not NAV-related. Before the patch, once a workstation lost access the only way to get things working again was to reboot the server, which would restore access to the server's shared hard disk.
Conclusion: I want to give it another day before I'm reasonably confident that the problem has been solved.
03-04-2009 02:05 PM
Sounds good Paul,
Thanks for the update, your conclusion seems correct because for sure the only way out before was to reboot the server, not just reboot, we had to powerdown because in my case it stayed stuck at the shutdown screen.
Hope you give us feedback again tomorrow.
03-05-2009 11:05 AM
04-06-2009 06:31 PM
I must say, this doesn't come as a surprise to me (see my posting under the name KuroshB on this PC Magazine Discussions thread about NIS 2007 -- August 14, 2007) ... I'm left torn between feeling that a) Norton products do a great job of protecting your computer when they work, and b) Symantec is severly lacking in two areas: QA and Tech Support. Here we are, April 2009, using NIS 2009 and the same problem was re-introduced in the latest product? I only haven't noticed sooner / done something about it because my client base is small, and luckily the client who most likely would have been affected by this issue (see above link) hasn't upgraded the "server" to NIS 2009 yet. Luckily, should I need to do so, this issue won't appear... but look at the various issues that NIS 2009 16.5 introduced? Many people unable to use LiveUpdate ... various BSOD issues. These are not small glitches! I can tolerate some of this nuisance myself, since I don't run a peer-to-peer network for day-to-day operations... but IT support professionals are not able to "make excuses" for Symantec when things don't work.
To re-state, NIS 2009 is a great product ... seems to have some great features and improvements, etc. Now, why is it that such a great product doesn't have excellent QA and Tech Support to go along with it? It took the posting mentioned above to get some quality tech support (who concluded that my workaround, discussed earlier in this thread of excluding some folders from AutoProtect on the server, was the "best" workaround possible at the time), instead of those whose only suggestion was to "reinstall" the product. Doesn't Symantec understand that quality QA would avoid so many of these hassles, both for them and their customer base? Honestly, I can sympathize with many here when they say it should not have taken this long for NIS 2009 to have been "patched". They knew about this issue since at least NIS 2007 (if not sooner) ... how did it get re-introduced into NIS 2009 without someone noticing? Yes, it's new technology and all that good stuff... that's what quality QA is for. Learn from the past, make something better, and test it to be sure it works!