[gosherm]

Finally, a definitive solution (hack?) for Norton SystemWorks 2005 custom unattended install.

Brief history of the problem:
As many of you know, there are numerous threads asking how to do an unattended install with NSW 2005. Now, out of all of these threads, the best advice is to use the following commandline:

NSWSETUP.EXE /O REBOOT=ReallySuppress /qb-

Unfortunately, that causes NSW to install pretty much darn near everything. Now, that may work for some people, but there are several threads asking how to do this with a custom install.

Until now, the best way to do this was to just delete the unwanted components... well, that worked good for most things, but not all things (such as "UnErase" and "UnFormat" -- I like my recycle bin just how it is, thank you very much).

So, after lots of playing around over the past few days, I have come up with a solution... finally.

First, you will need ORCA to edit a MSI file with. This utility can be found in the Microsoft Platform SDK (OS Independent). Install the SDK (the only component you really need to install is Microsoft Windows Installer SDK\Tools), then browse to the bin folder in the install path (default is C:\Program Files\Microsoft Platform SDK\Bin) and run the ORCA.msi file to install ORCA.

Second, you'll probably want to run the NSW installer in a VM or something to capture the log file (%temp%\Norton SystemWorks 2005 <date> <time>.log). Make sure that you do this install just as you want it to be in the end (same components). Basically, treat it like you would if you were recording an InstallShield script (setup -R). In this file, you should search for "NU\NU.MSI". After you find it, go down about 28-30 lines to find a line that starts with "MSI (s) (DC:20): Command Line: ". (Some of that may be different, the important part is that it is the first line after the "NU\NU.MSI" that you found that starts with "MSI" and contains "Command Line".) In this line, there is a section that starts with "REMOVE", copy all of the text after that into something that you can hold onto for a moment. This is a list of all of the NU components that are not going to be installed as part of NSW. Weird, I know... but that's life with Symantec.

Third, browse to your Unattended folder and open it up to your NSW location. Once there, open the "NU" folder and make a backup copy of NU.MSI (or you can just plan on copying it back from your CD if you mess it up). Now, right click on the NU.MSI file, and select "Edit with Orca".

Now, we need to make two changes to this file to override what the setup program will be passing into it by default during your unattended setup.

Change 1:
Locate the table titled "CustomAction" in the left-hand pane and click on it. In the right-hand pane, right-click and select "Add Row". Enter the following data:

Action: SetRemovedComponents1
Type: 51
Source: REMOVE
Target: <paste the string you copied from the log file here>

Now, add another row that is exactly the same, but has an Action value of SetRemovedComponents2

Change 2:
Locate the table titled "InstallExecuteSequence" in the left-hand pane and click on it. In the right-hand pane, right-click and select "Add Row". Enter the following data:

Action: SetRemovedComponents1
Condition: <leave blank>
Sequence: 150

Now, add another row with the following data:

Action: SetRemovedComponents2
Condition: <leave blank>
Sequence: 950

(We have to enter this stuff twice because I'm too lazy to figure out exactly where the code needs to go to only have it in there once... hey, I've been working on this bugger all week--give me a break! If someone wants to play with it to figure it out, by all means, be my guest.)

Now, save the MSI (File -> Save, or just exit the program) and use the following command line in your installation script (whatever type it may be)

One last thing, and we're set to go. Currently, this is going to have issues with the product key. However, if you enter the product key into the registry first, everything comes out nice and smooth. To do that, enter the following into an empty text file and save it as NSW.REG (replacing the Xs with your key, of course):

For Norton System Works 2005

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000082\00000015\00000022]
"Key"="XXXXXXXXXXXXXXXXXXXXXXXX"

For Norton System Works 2005 Premier

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\CCPD-LC\KStore\00000082\00000016\00000023]
"Key"="XXXXXXXXXXXXXXXXXXXXXXXX"

<add the NSW.REG file to your registry, however you do that>
<PathToNSW>\NSWSETUP.EXE /O REBOOT=ReallySuppress /qb-

Ta da! You should be done and working... give it a try in a VM to make sure.

For those of you who are interested, I install the following components:
Anti Virus
Disk Doctor
WinDoctor
Speed Disk
Explor Shell Extensions

Which leaves me with a REMOVE line of (all on one line, of course):

Image32,Norton_Registry_Tracker,Norton_Registry_Editor,
Wipe_Info,System_Information,Norton_System_Doctor,UnErase_Wizard,
Norton_File_Compare,DOS_Applications,Norton_Optimization_Wizard

Anti-Virus
Now, if you want to disable NAV, you'll have to edit a different MSI file. Unfortunately, NSW blows up if the NAV\NAV.msi file isn't there. I tried making a dummy MSI installer, but NSW threw a fit about that one too. So, we get to rip parts out of the NAV.msi file.

So, open up NAV.msi in ORCA. The first table that you're going to play with is the 'Binary' table. There are two files in here that can be deleted. They are 'Callreginst' and 'Callsttginst'.


Next, go to the 'CustomAction' table. In this table, you need to KEEP the following rows (delete all of the others):
AddVeniceIni
CheckSourceExists
CheckSymEvent
PostInstall
PreInstall
PreUpgrade
RemoveVeniceIni
UIFirstAction
Upgrade

Now, go to the 'InstallExecuteSequence' table and remove all of the entries in it. Yup, every last one (this is what keeps the MSI from actually DOING anything when it is called).

Next, go to the 'SymNestedFeature' and 'SymNestedInstaller' tables and remove everything EXCEPT for the one row in each table that starts with 'this'.

Now, just save the file out and remove everything else in the NAV folder (including any subfolders). You can remove the VIRUSDEF folder from the SystemWorks root as well.

FYI, this technique seems to work as well for NIS, though I can't find a shortcut to LiveUpdate anywhere in my Start menu (accessable through the NIS control panel). Definately don't use this if you're installing *both* NIS and NSW unless you don't want NAV installed at all. If this is the case, leave NIS alone (it will install NAV) and use this technique on the NSW install (which must run *after* NIS). This *should* cause the NSW installer to uninstall NAV and then run the 'custom' MSI that you've edited. No promises though, it's way past my bedtime and I don't know when I'll actually get around to testing it.

Ghost
Open the NORTONGHOSTNT.MSI (and after that one, the GHOST.MSI) file in ORCA and naviate to the 'InstallExecuteSequence' table and remove all of the entries in it. Yup, every last one (this is what keeps the MSI from actually DOING anything when it is called).

Ghost shouldn't give you any hassles now, and won't actually install.

CleanSweep
CleanSweep shouldn't give you any problems if you don't want it installed, because it is unselected by default. However, I had a request by someone who does want it, so here it is.

The easiest way to do it is to actually make it a separate install. Use the command line:

NCS.MSI SYMSETUP=1 /qb-

to launch the installer, and make sure that you do this AFTER installing the main body of NSW (at that will install the common libraries, etc.).

Enjoy, and good luck!

P.S. As a side note, you may get an error or two if you try to uninstall. Just click 'ignore' and everything seems to come out allright. Once, I had a couple of NU shortcuts that didn't get removed, but they no longer pointed to anything <shrug>.

This post has been edited by gosherm: 02 November 2005 - 08:05 PM

[SyKik]

cheers for good work, gonna give it a try

[orei]

hi!!
i used the same process that gosherm tell us in simply mode.. but there is a problem...
so.. i used only the first of the two disk of installation of NSW 2005 premium..

i've copied all the file and the directory except NAV (because i use Kasperky Personal..)..

i've found in the file .log the excactly row for nu.msi...

i've copied the entire part after ERASE= (until the next command..)

i did all the step for the file nu.msi with orca...

insert the rows:

regedit /S %systemdrive%\INSTALL\nsw\nsw.reg
start /wait %systemdrive%\install\nsw\NSWSETUP.EXE /O REBOOT=ReallySuppress /qb-

in the file nsw.cmd

and burn my disk...
but when star the unattended installation of nsw.. i receive an error of installation!!!

why this???

there is only this method for installing norton systemworks???
thanks a lot

[gosherm]

orei, on Sep 29 2005, 10:13 AM, said:

but when star the unattended installation of nsw.. i receive an error of installation!!!

why this???
<{POST_SNAPBACK}>

What is the error message you are receiving?

[orei]

please wait a minute.. i reinstall now the program..

so.. the error is: (i translate for you in eglish from italian language..)

To continue, please insert Norton SystemWorks 2005 Premier CD-ROM.

.\NAV\NAV.MSI


i think that the error come because there isn't NAV directory.. but how can i say to the installation program that i don't want install NAV??

I want to install only:
Norton Utilities (without wipe info and unformat program..)
Norton CleanSweep

thanks a lot

This post has been edited by orei: 29 September 2005 - 03:00 PM

[gosherm]

What is the content that you added to the MSI? And can you post the section of the log file that you got it from?

[orei]

this is the row of the log that i've found..

MSI (s) (38:2C) [14:28:58:578]: Command Line: SYMSETUP=1 ARPSYSTEMCOMPONENT=1 REBOOT=ReallySupress PARENTINSTALLDIR=C:\Programmi\Norton SystemWorks INSTALLDIR=C:\Programmi\Norton SystemWorks\Norton Utilities NU_PROGRAM_MENU=C:\Documents and Settings\All Users\Menu Avvio\Programmi\\Norton SystemWorks Premier\Norton Utilities SUITEINSTALL=1 ADDLOCAL=ALL REMOVE=Wipe_Info,Norton_Registry_Tracker,Norton_Registry_Editor,DOS_Applications,UnErase_Wizard,Nort
on_File_Compare,Image32,Norton_Optimization_Wizard CURRENTDIRECTORY=F:\UTILE\altri programmi\Utiliti di emmergenza\Norton System Works 2005\Norton system works 2005 Cd1 CLIENTUILEVEL=3 CLIENTPROCESSID=3776 CURRENTMEDIAVOLUMELABEL=WXPSP2_0905

i used only this text:
Wipe_Info,Norton_Registry_Tracker,Norton_Registry_Editor,DOS_Applications,UnErase_Wizard,Norton_File
_Compare,Image32,Norton_Optimization_Wizard

in the nu.msi, i've added the text that you wrote in your post

thanks

[gosherm]

Wow... that's cool. So, apparently things get done a bit differently for NAV. I'm going to edit the original post with information about how to not include NAV. Check back in a few.

[orei]

you're a genius!!

thanks a lot!!!

byeee

[orei]

so.. now there is a big big problem... nooooooooooo!!!!!!!

if i install the packet with:

NSWSETUP.EXE /O REBOOT=ReallySuppress /qb-

i receive an answer, that say me that can't do the installation process, because i need to uninstall NSW that i've installed before... but i didn't installed anithing!!!

Instead.. if i start the installation with NWSETUP.EXE... so.. normal... te installation go well...

why??

thanks a lot

[orei]

i've analyzed the problem...

if, when i launch the installation process, there is NAV directory (with your modded nav.msi file.. and with or without all other files..), the process will terminate with an error...

if, when i launch the installation process, there isn't NAV directory (because i've renamed it in NAVe for example..), the process start, but ask me the nav.msi file in the middle of installation.. now i say to the program where is the file, and the installation finish fine!

So.. but if i want a complete unattended installation?? how can i do???

Because i saw that you are a GURU of unattended windows etc.. i've another problem with the last program..
Nero 7 Premium Retail Version (not beta..)

In beta version.. the command /norestart work fine.. and the computer doesn't restart.. but in the new retail version, the command /norestart didn't work..
but the file .msi is the same!!

if you want.. and you can.. this is the topic where i talk about my problem:
http://www.msfn.org/board/index.php?showtopic=56208&st=30

Thanks a lot!!

[SyKik]

Suppose gotta take a better look when I have more time

But is there a way to configure the MSI to install to the %Systemdrive% ? By accident was using it on a mates computer where there was no C:\ (don't ask me why ) and the NSW install method failed, since it automatically tried to install to C:\

[gosherm]

SyKik, on Oct 10 2005, 02:06 PM, said:

But is there a way to configure the MSI to install to the %Systemdrive% ?

@SyKik -- Is that a problem with my custom NAV.msi? [edit]Well, regardless. No more custom MSI from me. You get to edit your own now. Check out the first post of the thread for updated instructions.[/edit]

@orei -- I'll be happy to take a look at Nero when I get my hands on it. I suppose that today's the 26th and I can go see about d/l'ing a upgrade from Ahead now. Of course, this subject will get relocated to an appropriate (existing?) thread. [edit](*Blasted* software developers... the download was *supposed* to be available today, the 26th. But no... it's NOW available on Nov 2. What a pain. Actually, I probably shouldn't blame it on the developers, it's probably somebody in the QA dept. saying 'I don't think we should ship with this minor bug' or something like that. Not that I've ever done that. But then again, at my workplace, my supervisor just tells me (jokingly, of course) to shut up and get to work if I say something like that -- "It's not a bug!")[/edit] <I'll add link here after I post in it.>

@all -- Sorry I've been pretty swamped with work and stuff lately, I should have a bit of time over the next week or so to look closer at this. [edit]Ok. Check the first post, instructions should be working this time around. Let me know if there's still any bugs.[/edit]

This post has been edited by gosherm: 02 November 2005 - 08:02 PM

[SyKik]

gosherm, cheers for the reply mate

safe to ignore me was only a freak one off occurance, worked fine on another comp where the c:\ wasn't the system drive

[X-Savior]

Hi There,

Well, I have followed the new instructions posted. Everything went well to create the new install. I Removed NAV as I like Symantec Corporate Instead (Less Bulky and MUCH faster).

I Will try the install and see if it works without any hitches.

[X-Savior]

Ok, Things went well, except Ghost Still Installed and Cleansweep did not appear.

I used the exact remove stuff from the install, Here is what there was...

REMOVE=Image32,Norton_Registry_Tracker,Norton_Registry_Editor,Norton_File_Compare,DOS_Applications,N
orton_Optimization_Wizard

It should have a few other items on here. I Do not see Ghost listed here as it SHOULD be.
So does anyone have any more info on this? The install worked good. Most important the NAV didn't install. The other big one is No Ghost, Then I will be happy.

I Know I am close but what am I missing? I Followed the instructions EXACT.

[gosherm]

X-Savior, on Nov 2 2005, 01:18 AM, said:

Ok, Things went well, except Ghost Still Installed and Cleansweep did not appear.

Ok, let me get this straight. You DO NOT want Ghost, and you DO want Cleansweep?

Unfortunately, I'll have to wait to address this further until I get home from work tonight... I don't seem to have NSW (the unmangled copy) on my computer anymore, so I'll have to pull it back off the CD. BTW, I assume that since it has Ghost that you are using NSW Premier 2005? (I haven't bought 2006 yet... it probably won't happen until it's free after rebate either.)

[edit]
Well, I went on the assumption that you DO NOT want Ghost and you DO want Cleansweep. The information has been added to the first post -- let me know if there are problems with it, but it seems to work just fine for me.

This post has been edited by gosherm: 02 November 2005 - 08:02 PM

[X-Savior]

Hi There,

Ok, I will check what you posted and try it and get back to you....

Thanks!!!

[EDIT]

Ok, I tried it, and yes I have Premier 2005.

I get to Norton Antivirus, Feature: SysOpt
and it comes up with a message in a Box "Norton Systemworks Premier 2005 configuration has failed. Do you want to try to install again?"

This message did not come up until I made the changes in the two Ghost Files. Is there more to be removed from the Ghost Files?

[EDIT 2]

Ok, I replaced the Original Ghost Files and still same message. I am going to start fresh and make all the changes again.

This post has been edited by X-Savior: 03 November 2005 - 01:22 AM

[X-Savior]

Well, I re-did all the steps layed out to Edit to custom the install and remove NAV. Then Edit to remove Ghost and I Still get the Error when it switches from Norton Systemworks to Antivirus on the previous post.

Any Feedbackon this? Never got this error last night when I tested without changing Ghost Files. But if I replace them with the originals I STILL get the error.

[gosherm]

That's weird. I've never had anything continue to give the error message after replacing the original MSIs.

Ok, try this.

• Reset your VM, preferable back to a "just finished installing XP, nothing else really installed" state if possible (I assume that you're using a VM to test this... if you're doing this on a live box, there's a whole different set of issues that needs to be addressed, starting with using the SymNRT tool to do a complete removal of everything Symantec related).
  
• Put together a clean NSW folder (recopy it from your CD) and make all of the changes you would like to make (including the ones for ghost).
  
• Force MSI logging, if you haven't done it already. Here's the reg file to use:
  

  REGEDIT4
  
  [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
  "Debug"=dword:00000003
  "Logging"="vicewarmup"
  

  
  
• Empty the %temp% folder of all content.
  
• Run the install using your unattended command line.
  
• From the %temp% folder, grab the NSW related log files, and see if you can determine what is causing the error and post at least that, perhaps the whole file (as a d/l or something I guess, as it can be rather lengthy).

[edit]
I just went through this procedure myself, completely reediting the MSI files from scratch with no problems whatsoever. So, if you're still having problems, let me take a look at the log files.

This post has been edited by gosherm: 03 November 2005 - 11:10 AM