jensm wrote:
Hi, Good news. We are shipping the 16.5 patch today. The build number is 16.5.0.135.
It is right that we had problems last week when we attempted to ship it. There were too many install failures related to the toolbar update. The patch installer did not take into account the beta SafeWeb toolbar that we shipped last year over Norton Labs.
The history with the 16.5 patch is that it is one of the largest patches we sent out for a while. For 2008 and 2007 we did not send a patch for the .5 update because the legacy MSI based installers were too complex and the likelihood for massive install failures too high. We are updating roughly 10 million systems. The 16.5 patch actually requires two patches. One to prepare the patch and another one contains the actual files. Over the last week we mostly worked on the preparation patch. It basically updates the patch technology to the latest version so that the second patch goes through smoothly.
The way we stage the LiveUpdate patch is that we first post it for about 30-60 minutes. Then, on the following days we look into any issues we encountered. If everything goes well we post the patch permanently. Obviously, last week we didn’t make it to the second phase.
This year we do have a new installation technology that also performs patching. Our testing went well and we are confident that the patching experience will be positive for all of our customers.
In addition we are going to update the Norton Update Center download links with the latest layouts. The link is www.norton.com/nuc . It takes a few hours for us to change the underlying layouts on this page but they should be live later today.
We will publish a detailed 16.5 changelist on the forum later today. The 16.5 code is basically the underlying code of the N360 Version 3 infrastructure. It includes all bug fixes since we shipped 16.0 that are also in N360. This is really a quality release and addresses our top Support issues, including feedback from this forum.
Our store download and trial will also be updated asap. This is on our online store and unfortunately always takes 1-2 days.
Message Edited by Tim_Lopez on 03-17-2009 03:49 PM
jensm wrote:
In the future we will be more proactive with technical details.
Here is a list of some of the changes for 16.5:
- Fixed an issue where you may not be able to access shared folders on a computer connected to your home network.
- Fixed an issue where the Quick Scan Open Security History expansion was not working on first click.
- Fixed an issue in Home Networking Map - not warning the user that another user is viewing the map.
- Fixed an issue in Home Networking – removing a remotely monitored device does not persist.
- Fixed unnecessary UAC warnings during install/configuration.
- Fixed a crash in Home Networking Map User Interface.
- Fixed a crash in the AntiVirus Scan User Interface.
- Fixed a contributing issue for Error 3040,10001
- Improved Home Networking remote monitoring Antivirus item formatting
- Added option to allow Pulse Updates to run when laptop is on battery power (Settings/Miscellaneous Settings)
- Added SONAR support for Vista 64-bit
- Allow Context Scanning (Right-Click file scanning) for Vista 64-bit
- Added Norton Product Tamper Protection support for Vista 64-bit
- Added UMPC support (install UI fits now, auto panning for small screens)
- Added Norton Safe Web integration (watch out for more deails in a separate thread)
(the following issues were also fixed in the 16.2 patch)
- Changes to allow future LiveUpdates better handle error conditions.
- Fixed an issue with 64-bit LiveUpdate patches.
- Fixed several Winqual reported errors.
- Fixed a compatibility issue with Microsoft Outlook Connector after installation of Norton Add-On Pack.
- Fixed an issue where the product would sometimes interfere with its own ability to match IDS signatures properly.
(the following issues were also fixed in the 16.1 patch)
- Fixed issue where Protection updates download but date does not change.
- Fixed issue where in some cases, if you looked at the details of which updates succeeded and which failed, it would show all updates failed even though only one update failed.
- Fixed issue where Virus Definitions were considered non-valid in certain scenarios.
- Fixed instance where Advanced Protection will fail to start.
- Fixed issue where LiveUpdate fails to download and apply Web Protection definitions.
- Fixed issue with Identity Safe showing garbled characters in a few areas of the User Interface.
- Fixed multiple instances of ccSvcHst.exe crashes caused by components.
- Fixed issue with ccSvcHst failing to shutdown on a reboot (End Task dialog displayed indefinitely).
We thank you jensm for a more in depth reply on this issue, to which is what we should have received in the first place.
In the future though, do us all a big favor, as you mentioned, be more proactive with technical details, this when you inform your Administrator Tim_lopez. Quite certain that Tim could do without the grief, not failing to mention Symantec keeping their customers happy as well 
Chris1 wrote:
Tim_Lopez wrote:
Hello Chris1,
I’m sorry that you feel that I have not been straight forward and honest about this patch. Unfortunately there is no other information besides the information that I have already posted on this forum, and that other threads that have been started on this subject. The controlled release means that some people will get it and some people won’t. This is only temporary until the patch is released fully to the general public. This should be released soon. I know I sound like a broken record, but this is the honest truth that I am relaying to you.
These forums are peer-to-peer discussion forums and Symantec Employees post here when they can on their spare time. They don’t get around to responding to every thread that is posted. Your questions you had regarding 16.2 were answered by other users in the forums.
Perhaps the wording in my initial announcement should have stated that the 16.5 patch will be released soon, and that some users would start seeing the patch show up soon. In any case, it’s the same situation.
I’m sorry that it seems that with the 16.2 and 16.5 patches, that you were left in the dark regarding the status. I’ve done my best to keep everyone updated with information when I have it. I apologize if you feel that it is not enough information. However, it is all the most recent information that I have. I know that the patch is nearing completion of the controlled release. However, I can’t give commitments on dates or times when the controlled release will be complete, as this is something that is likely to change. I would rather give the honest facts out.
Again, I’m sorry if you feel that I have not been honest. However, I have been and will continue to be.
No need for you to be sorry at all, NOR do I feel that you have not been straight forward and honest, however you being the Admin on this forum should be better informed by Symantec on Specifics and not left out in the cold by them to Generalization. It makes you look like a idiot, not good.
I do understand that this forum is a peer-to-peer discussion forum, and that the Symantec Employees whom post here do so on their spare time, but that has no bearing on why it took you until now to answer me. Needless to say I did let that 16.2 thread slide, even though you where the person that I directly asked the question of, and after two responses from helpful different members of this forum, my “SPECIFIC” question was still NOT answered.
Tim when a person directly asks me a question on a forum I will at all times answer him or her back with a reply, regardless if another member has answered that question on my behalf or not. It is only proper etiquette of you to do so as well, which was NOT the case in this thread :
Specific question was :
http://community.norton.com/norton/board/message?board.id=nis_feedback&message.id=24988&query.id=1245540#M24988
2.) Please explain in greater detail as too exactly what you mean by your satement: You are distributing this 16.2 patch in a more controlled manner?
Furthermore your answer does not make any common sense : “The controlled release means that some people will get it and some people won’t.”
It does not expalin why a person whom installed NIS 2009 on 2 Identical computers that I had built for him on the same day with only “ONE” out of “TWO” of his computers receiving the 16.5 Update. Both of which have the very same ip includingNIS 2009 installed on each of them within minutes apart.
How do you explain that? This question I would like you to get a answer from Symantec for me.
Tim you do not have to make a apology to me, its not required, but I will tell you, that you will NOT be off my hook until I get that answer from Symantec lol!
Lol Tim you are now off my hook 
Message Edited by Chris1 on 03-17-2009 05:37 PM