NAV and LUadmin HOWTO<br>
<br>
Edgar Soldin<br>
<br>
edgar[at]soldin.de<br>
<br>
Revision 1.00           2003/02/28           Revised by: edso                <br>
Initial version.                                                             <br>
-----------------------------------------------------------------------------<br>
<br>
Table of Contents<br>
<br>
<ul>
1. Introduction<br>
<ul>
    1.1. Requirements<br>
    1.2. Getting additional Software<br>
</ul>
2. Setup<br>
<ul>
	2.1. LUAdmin<br>
	<ul>
		2.1.1. Installation<br>
		2.1.2. First Start<br>
		2.1.3. Create File Share and Hostfile<br>
		2.1.4. Change product.xml<br>
	</ul>
	2.2. NAV<br>
	<ul>
		2.2.1. Installation<br>
		2.2.2. First Start<br>
		2.2.3. Place Hostfile<br>
	</ul>
</ul>
3. Scheduled Tasks<br>
4. Maintenance<br>
5. Urls<br>
</ul>
-----------------------------------------------------------------------------<br>
<br>
1. Introduction<br>
<br>
This document should be a guide to set up an automated updating of symantec components using the LiveUpdate Administrator (LUAdmin) component. <br>
	<br>
The document focuses on Symantec's Norton Antivirus as this software relies on recent virus definitions and software component updates, but should work with every Symantec application that ship with Liveupdate. We will do the following steps together:<br>
	<ul>
	<li>check requirements</li>
	<li>download recent versions of </li>
		<ul>
		<li>LUAdmin (LiveUpdate Administration Utility)</li>
		<li>LU (LiveUpdate)</li>
		<li>Rnav (Norton Antivirus Removal Tool)</li>
		</ul>
	<li>set up Norton Liveupdate Administrator</li>
	<li>set up Norton Antivirus</li>
	<li>point LU to the dedicated machine's update share</li>
	<li>create a scheduled tasks for</li>
	<ul>
		<li>starting LUAdmin silently</li>
		<li>starting LU silently</li>
		</ul>
	<li>look at how to maintain the setup</li>
</ul>
1.1 Requirements<br>
<br>
The set up of LUAdmin especially makes sense in local area networks where <br>
<ol type="a">
	<li>internet bandwidth/traffic is very limited</li>
	<li>the amount of workstations exceeds the limit for manual maintenance</li>
	<li>an update of virus definitions only (Intelligent Updater) is not enough.</li>
</ol>
If none of the reasons above apply to your environment please consider using Intelligent Updater (see 5. URLs) instead. <br>
<br>
You will need the following<br>
<ol type="a" start="4">
	<li>a 24/7 uptime machine running a Win32 OS (Win9x/Me/NT/2k/XP) with
	   connection to the internet, we'll call it SERVER</li>
	<li>a workstation running a Win32 OS with connection to the above
	   mentioned SERVER</li>
	<li>licenses and installations for Norton Antivirus (e.g. NAV2003)</li>
	<li>MS Task Scheduler running as service</li>
</ol>
<ul>
Note: 
	<ul>Windows 95, mstask.exe was part of Internet Explorer 5 and above.</ul>
</ul>

Finally you will need patience and these skills<br>
<ol type="a" start="8">
	<li>know how to share a folder in the windows versions you are using</li>
	<li>basic knowledge of XML, if you plan to use Consumer versions</li>
</ol>
<br>
1.2. Getting additional Software<br>
<br>
Use the internet connected machine to retrieve:	<br>
	<br>
- a recent LU install<br>
ftp://ftp.symantec.com/public/english_us_canada/liveupdate/updates/lusetup.exe<br>
<br>
- the recent LUAdmin install<br>
ftp://ftp.symantec.com/public/english_us_canada/liveupdate/updates/luau.exe<br>
<br>
- the recent Rnav utility (optional)<br>
http://service1.symantec.com/SUPPORT/nav.nsf/949e46314f0916a0852565d00073bbfd/33497f6e8a319ece88256ace0076cc02/$FILE/Rnav2003.exe<br>
<br>
-----------------------------------------------------------------------------<br>
<br>
2. Setup<br>
<br>
If you want to save time or are short on machines use the same machine for installing LUAdmin and NAV on.<br>
<br>
<br>
2.1. LUAdmin<br>
<br>
I assume you will do a standard full install. E.g. Simply execute the install executable and click on NEXT and OK.<br>
<br>
<br>
2.1.1. Installation<br>
<br>
Execute luau.exe locally (over the network it takes ages until the setup interface appears). <br>
<br>
Known Problems: <br>
<br>
a) Sometimes the first Setup Screen with the status run bar virtually stops at 98 percent. Keep patient for 15 minutes or so, the install will go on.<br>
<br>
b) For some reason, sometimes the installation keeps running in the background without opening the setup screen. In this case use another machine and install there. Eventually copy the 'Liveupdate Administration' Folder to the SERVER's Program Files folder.<br>
<br>
<br>
2.1.2. First Start<br>
<br>
Click away the greeting screen. <br>
<br>
To retrieve a recent product list do the following:<br>
 <br>
 <ul>
 Languages of Updates: <br>
  Tick -> English<br>
 Symantec Product Line: <br>
  Mark -> LiveUpdate, Click -> Button Details (on the right)<br>
   Tick -> LiveUpdate Administration Utility<br>
 Download Directory:<br>
   c:\navupdates<br>
 Click Retrieve Button (upper right corner)<br>
</ul>
Next choose globally the languages of your software packages AND the Software Packages you want to update. Note the new language called SymAllLanguages, which came with the new Product List.<br>
<ul>
E.g. Languages of Updates: Tick -> English, SymAllLanguages <br>
     Symantec Product Line: <br>
     	Mark -> Norton Antivirus Product Updates<br>
     	Click -> Button Details (on the right)<br>
     	 Tick -> Norton AntiVirus 5.x (Windows NT Workstation)<br>
     	 Tick -> Norton AntiVirus 5.x, 6.x, 7.x (Windows 9x)<br>
    <br>
Note: 
<ul>
 Norton AntiVirus 5.x (Windows NT Workstation) is NAV2001 for NT<br>
 Norton AntiVirus 5.x, 6.x, 7.x (Windows 9x) is NAV2001 for Win9x<br>
These are the last NAV consumer versions officially supported by LUAdmin. Officilally ONLY corporate NAV versions and other enterprise Symantec/Norton products are supported :( since then. BUT there is a workaround ;). See (2.1.4. Change product.xml).<br>
</ul>
</ul>
<br>
2.1.3. Create File Share and Hostfile<br>
<br>
In order to give the workstations access to the update files we have to share the LUAdmin Download Directory c:\navupdates. It's very convenient to make it world readable by allowing anonymous access to the update share. It saves us setting up specific accounts. Just enable read access for the group Everybody. Keep the share name 'navupdates'.<br>
<br>
Now you should be able to access \\SERVERNAME\navupdates. <br>
<ul>Note: <ul>In order for anonymous access to a windows share, the following must be configured</ul>
<ul>
Enabled Guest user, with the right to access shares, everything else can be disabled, e.g. local login. Under XP you have to enable 'Control Panel -> Administrative Tools -> Local Security Police -><br>
Security Settings -> Local Policies -> Security Options -> Network Access: Let Everyone permissions apply to anonymous users'.<br>
</ul>
</ul>
Start LUAdmin again or if it's still running <br>
 <br>
 Click (on the left side) on Host File Editor.<br>
 <br>
 From the Menubar select File -> New and File -> Save it under 'liveupdt.hst' in a newly created folder c:\navupdates\hostfile.<br>
 <br>
 Add now the first host<br>
  Name: your choice (the displayed name in LU)<br>
  Country/Area: your choice (the displayed location in LU)<br>
  URL or IP Address: \\SERVERNAME\navupdates (the folder where update files are located)<br>
  Type: LAN (the used access protocol HTTP,FTP,LAN or MODEM)<br>
<br>
 Add a second entry (all fields ame as above but)<br>
  Name: another than the above choice of yours<br>
  URL or IP Address: \\SERVERIP\navupdates<br>
  Use the IP address instead of the Wins Name here which is a good idea in case the windows name resolution fails.<br>
<br>
 File->Save again.<br>
<br>
<br>
2.1.3. Change product.xml<br>
<br>
If you are using NAV Corporate you can jump over this paragraph.<br>
<br>
Because LUAdmin is generally using the same mechanism as LU to get the update files from the same symantec servers that a LU on a workstation would use, it is possible to receive initially not offered updates (e.g. for NAV Consumer).<br>
I will start by explaining how the procedure works and we'll set up the workaround together.<br>
<ul>
The LUAdmin Procedure: <br>
<ul>On the the symantec server LUAdmin will find the file livetri.zip, which is a zip archiv containing 'liveupdt.tri', the list of ALL available updates.<br>
LUAdmin will extract the list and compare this list of offered updates with the enabled ones in C:\Program Files\LiveUpdate Administration\product.xml. This file is simply a representation of the choices made in LUAdmin. If the fields Language and Product Name match, the specified files will be downloaded. This goes on until the whole list is finished. <br>
Thereafter a new livetri.zip is created holding only a list of the downloaded product updates  and placed in the Download Directory, where our workstations will find it and choose themselves a sublist of product updates to download.</ul>
<br>
The Standard LU Procedure:<br>
<ul>The standard LU procedure does it the same way but directly from the symantec server. It does not have a product.xml. I didn't find out where the current Symantec products regustered with LU are stored. Therefore we'll have to find them out piece by piece.</ul>
</ul>
<br>
There is a file called Product.Catalog.LiveUpdate in one of these locations depending on which Operating System (OS):<br>
	<br>
	Win9x/Me -> <br>
	 c:\windows\All Users\Application Data\Symantec\LiveUpdate\<br>
	WinNT/2k/XP -><br>
	 C:\Documents and Settings\All Users\Application Data\Symantec\LiveUpdate\<br>
<br>
It is a very complete list of Symantec products and will help us in finding out the Product Names necessary to enter in product.xml.<br>
<br>
The Workaround:<br>
With the now gained knowledge, we can start adding products to the product.xml. <br>
How? First we have to find out which updates exactly are missing.<br>
<br>
In LUAdmin goto Retrieve Updates (on the left side). Then deactivate in the Menu Bar Tools -> Options -> Retrieve -> Retrieve Update Options -> Remove unselected products from TRI files. Doublecheck your settings Languages, Products, Download directory again. Then do an initial download of updates by pressing the [Retrieve...] button (upper right corner). Eventually there is an amount of new updates and a list with ALL available updates at symantec's server in the on \\server\navupdates.<br>
<br>
Now we point a LU on a workstation or a machine with products not included in product.xml to our SERVER (see 2.2.3. Place Hostfile). Start LU by executing C:\Program Files\Symantec\LiveUpdate\LUALL.EXE .<br>
Click through all dialogs (NEXT>>) and in the end there will be a list of update errors and successes. Write down the EXACT name of the packages that gave errors.<br>
<br>
Find these package names in the field DESCRIPTIVENAME in Product.Catalog.LiveUpdate on the same machine and write down the matching PRODUCTNAME. Add this Product Name in an entry like this to the product.xml on the server. <br>
<br>
If this doesn't work. Try it this way:<br>
Locate the local Downloads folder. It is located in the same place as the Product.Catalog.LiveUpdate file. Look there for empty files of 0kb size. Write down their names. Find these files in the list livetri.zip->liveupdt.tri, which was downloaded there as well. Write down their ProductName field value. <br>
<br>
Add the products to the LUAdmin product.xml list. Generally it makes sense to have them in an own product line, to have an easy overview.<br>
<br>
BEGIN------------------------------------------------------------------------<br>
<samp>
&lt;product_line&gt;<br>
&lt;display_name&gt;Specials&lt;/display_name&gt;<br>
&lt;selected&gt;yes&lt;/selected&gt;<br>
&lt;languages&gt;<br>
&lt;/languages&gt;<br>
&lt;products&gt;<br>
&lt;product&gt;<br>
&lt;display_name&gt;DESCRIPTIVENAME&lt;/display_name&gt;<br>
&lt;tri_file_name&gt;PRODUCTNAME&lt;/tri_file_name&gt;<br>
&lt;selected&gt;yes&lt;/selected&gt;<br>
&lt;/product&gt;<br>
&lt;/product_line&gt;<br>
</samp>
--------------------------------------------------------------------------END<br>
Here a new Productline was added, called Specials and is by default selected (every product update in it will be downloaded regardless of its own Selected field).<br>
<br>
<ul>Note: <ul>You can find working version of product.xml for NAV2001,2002,2003 in the examples directory. All these Product Names, for the different platform and their equivalents in Product.Catalog.LiveUpdate show up in DESCRIPTIVENAME.PRODUCTNAME.Mapping.txt in the examples directory.</ul></ul>
<br>
ATTENTION:
<ul>
When LUAdmin is selected in the LUAdmin Product List every time a new file product.xml (recent BUT limited list of downloadable product updates) is downloaded and replaces C:\Program Files\LiveUpdate Administration\product.xml. Your former selection will stay, but manual changes, as the ones we did will disappear. To circumvent this either:
<br><br>
	- set product.xml read only, <br>
	   <ul>
	   - advantage <ul>you are still updating LUAdmin software component</ul>
	   - disadvantages
	   	<ul>
	      you have to set/unset the attribute every time you are changing your selection<br>
	      new allowed products will not appaer in the list<br>
		</ul>
		</ul>
	or<br>
	<br>
	- disable the update of LUAdmin in the Product List at all<br>
	   <ul>
	   - advantage - no set/unset file attribute problem<br>
	   - disadvantage - no LUAdmin updates<br>
	   </ul>
</ul>
I recommend setting the product.xml read only.<br>
<br>
The maintenance of this setup is connected to some more labor expense. You should from time to time do manual LiveUpdates on ALL the different platforms and consumer versions of NAV. As the product list is not delivered by Symantec, the update package list has to build up over time.  When new update packages get available they'll show up as errors in the LU. Then you should add these by repeating the above mentioned steps.<br>
<br>
ATTENTION: <br>
Remember to leave LUAdmin -> Menu Bar -> Tools -> Options -> Retrieve -> Retrieve Update Options -> Remove unselected products from TRI files disabled in order for this to work.<br>
<br>
2.2. NAV<br>
<br>
I assume you will do a standard full install. E.g. Simply execute the install executable and click on NEXT and OK.<br>
<br>
<br>
2.2.1. Installation<br>
<br>
The installation will ask you if you want NAV to do a full scan, automatic updates, enable Autoprotect. Disable the first two. Finish the installation. <br>
<ul>
Known Problems:
<ol type="a">
<li>Sometimes the installation fails to register with with LiveUpdate.</li>
<li>Other mysterious errors.</li>
</ol>
In all these cases try to clean the box from NAV at all using Rnav2003.exe (see 5.Urls Rnav2003). Eventually reboot and install NAV again.<br>
</ul>
2.2.2. First Start<br>
<br>
Doubleclick on the NAV Autoprotect Icon, click through the registration w/o registering of course and enter the Norton Antivirus screen.<br>
<br>
<br>
2.2.3. Place Hostfile and try to update<br>
<br>
Copy the hostfile (see 2.1.3. Create Hostfile ...) to C:\Program Files\Symantec\LiveUpdate.<br>
Now go into the Norton Antivirus screen, click LiveUpdate (upper left corner). Hope the best and monitor the update process. <br>
<br>
Known Problems:<br>
<br>
a) LU1814: LiveUpdate could not retrieve the update list<br>
Possible reasons: <br>
- Can't reach update server. Check network connection, availability of \\SERVER\navupdates<br>
- you didn't download the updates beforehand (see 2.1.2. First Start)<br>
<br>
-----------------------------------------------------------------------------<br>
<br>
3. Scheduled Tasks<br>
<br>
Download the .job files I prepared in the examples directory and put them into c:\windows\tasks or setup some yourself. <br>
LUAdmin and LU are both executable silently i the background. This Run commands worked for me. <br>
 "C:\Program Files\Symantec\LiveUpdate\LUALL.EXE" -s<br>
 "C:\PROGRA~1\LIVEUP~1\LuAdmin.exe" -silent<br>
<ul>
Note: <ul>Under WinNT/2k/XP without a windows domain, you can't use the same account on every machine for executing the scheduled tasks. Enter account and password every time you add the scheduled task.</ul>
</ul>
-----------------------------------------------------------------------------<br>
<br>
4. Maintenance<br>
<br>
The maintenance expense is minimal. This is why we set it up this way, isn't it? However if you are using Consumer versions you will have to check the LU from time to time manually as described in 2.1.3. Change product.xml.<br>
<br>
-----------------------------------------------------------------------------<br>
<br>
5. Urls<br>
<br>
How to use the LiveUpdate Administrator with Norton AntiVirus Corporate Edition 7.x<br>
<address>http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2000012812551548</address><br>
<br>
How to uninstall Norton AntiVirus by using the Rnav2003.exe removal utility<br>
<address>http://service1.symantec.com/SUPPORT/nav.nsf/docid/2001092114452606</address><br>
<br>
How to update using Intelligent Updater<br>
<address>http://service1.symantec.com/SUPPORT/nav.nsf/8d071816eedd7cac88256c0e005a96e5/8e432d0efb95a8a088256666006e0f9c?OpenDocument</address><br>
<br>
-----------------------------------------------------------------------------