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.

Here's what I use for mine. It's the d/l from the VMTN subscription, but I imagine that it's the same (don't know why it's an exe rather than an msi). CALL :BuildPackage "Installing VMWare 5.0.0-13124" ^ "%AUTOPATH%\System\VMWare\VMware-workstation-5.0.0-13124.exe /s /v/qb" ^ "*REGEDIT /S %AUTOPATH%\System\VMWare\VMWare.reg" type %PACKAGE_LOG% >> %XPCD_LOGFILE%

Lucky for you, I'm a good artist . Here's a solution that I just developed and wrote up for an Office 2003 Silent without enterprise version. (I put it in a new thread because it's a fairly definitive solution, and it will be easier for people to find it there rather than in a "do you know" thread. Nothing personal, I promise )

Finally, a solution for installing Office 2003 Silently without having an enterprise edition. 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. First, on your office CD, grab the "PRO11N.MSI" (may be something slightly different (including STDsomething) depending on the actual version, I imagine that this should work for all strains of Office 2003) and stick it somewhere on your harddrive. Second, right click on the MSI file, and select "Edit with Orca". Now, we just need to delete a few fields, nothing terribly difficult--just the sections telling you that you can't do the install quiet, and that you can't use transforms. Locate the table titled "AdminExecuteSequence" in the left-hand pane and click on it. In the right-hand pane, click on the row that has "SkuredQuiet" in the first column, and hit DEL on your keyboard. Next, locate the table titled "InstallExecuteSequence" and select it. In the right-hand pane, delete the row that has "SkuredQuiet" in the first column and the row that has "SkuredCIW" in the first column. Save the file, exit, and put the modified MSI back with the rest of your office installation source (whether that means burning it to disc or just sticking it on your HDD somewhere). Whala. You're done. As a side note, this was not actually all that difficult to figure out, and if you run into other "I won't let you do this because I don't feel like it" issues with this installer, here's how I figured things out. First, I created my MST using the ORK as explained in the Office 2003 Unattended Guided. Next, I ran the install trying to do quiet and with that MST transform. Then I looked at the logfile the MSI left, and just above where it dumps all of the properties, there was a line that said "MSI (s) (C4:EC) [16:59:59:171]: Product: Microsoft Office Professional Edition 2003 -- Quiet-mode installation is supported only in Enterprise versions of Microsoft Office 2003." And just above that, was a line that said "Action start [time]: SkuredQuiet." Well, removing all references to "SkuredQuiet" produced a new error message in the same location that said something about not being allowed to use a transform. So, I found that the "Action start [time]:" line immediately before that new error was for "SkuredCIW." Remove that, and it worked just fine. So, if there are more problems, just keep following that pattern to remove the offending section. As always, keep a backup handy (though I recken that you should have the original CD to work from, eh?). Enjoy!

Not that I'm particuarly aware of. However, you only need the administrative install if you are going to slipstream the updates (which, AFIK, means that any subsequent updates have to be installed as administrative updates, and not from the Office Update website). Personally, I like the ability to use the Office Update website, so I don't do an administrative install by choice. I just install (currently) Office 2003 sp2 & the latest Outlook Junk Mail Filter immediately after the Office install. Probably takes a little bit longer for the actual install, but well worth it in my opinion. If you follow the guidelines for an unattended install located at MSFN's Office 2003 Unattended - Advanced Method, you will be able to configure everything you want to (including product key, etc.) for your unattended install. Here's the code from my CMD file. Call :BuildComponent "Installing Office related software" type %COMPONENT_LOG% >> %XPCD_LOGFILE% CALL :BuildPackage "Installing Microsoft Office 2003 Professional (Access, Excel, Outlook, Word)" ^ "%AUTOPATH%\Office\Office2003\setup.exe TRANSFORMS=Unattended.MST /qb-" type %PACKAGE_LOG% >> %XPCD_LOGFILE% CALL :BuildPackage "Installing Office 2003 Service Pack 2" ^ "%AUTOPATH%\Office\OfficeUpdates\Office2003SP2-KB887616-FullFile-ENU.exe /q" type %PACKAGE_LOG% >> %XPCD_LOGFILE% CALL :BuildPackage "Installing Other Office Updates" ^ "%AUTOPATH%\Office\OfficeUpdates\office2003-KB906173-FullFile-ENU.exe /q" type %PACKAGE_LOG% >> %XPCD_LOGFILE% CALL :BuildPackage "Installing Microsoft Office Profiles" ^ "*pushd '%ProgramFiles%\Microsoft Office\Office11'" ^ "proflwiz.exe /r D:\Matthew\Computer\Outlook\Matthew.OPS /p" type %PACKAGE_LOG% >> %XPCD_LOGFILE%

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.

I think that we've all been there and done that. I spent about five hours debugging my unattended script this weekend because of sill typos SET x=y NOT SET x = y AND If a Then ( echo b [c] ) Else ( echo d ) NOT If a Then ( echo b (c) ) Else ( echo d ) Stupid nested parens, that one took the longest.

Maybe it's just too early in the morning for me, but I don't understand the question. If you are burning everything within the Professional\ subfolder to your DVD, then the contents of the $OEM$\$1\Install folder will be copied to %systemdrive%\Install (which is typically C: and therefore, C:\Install) during the DOS (bluescreen) portion of the install. Is your boot drive something other than C:? Are you getting errors (such as file not found)?

@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]

I just had a <sarcasm>great</sarcasm> experience to add to the list of why to use an unattended disc. I routinely access my home PC from work. Last night, however, just before I went to bed, the blasted thing got into a continuous reboot cycle. This morning, before walking out the door, I booted my PC from my unattended disc, and about 20 minutes after getting to work the computer is back up and running.

I find that it definately saves me time. If I do a full system install from scratch without my unattended DVD, it takes me from 12-14 hours (plus about 3-5 hours checking for updated software, plus 2+ hours installing Norton & Microsoft patches... nasty reboot cycle). With my unattended DVD, it takes me 3-5 hours checking for updated software and changing my install script (doesn't usually take much time to *change* an item, it's when it's a *new* item that it can get nasty). To then install, it takes about an hour, including installing software that I don't have automated yet and any post-install tasks such as relocating the IE cache, changing the swap file settings, etc. If I don't bother doing any of the updates, it takes me about an hour to be up and running again. Can't really beat that. (Not to mention, that I can just stick the disk in, walk away, come back after dinner and it's up and running -- try having that experience with a "clean" install.) Actually, I do. After getting everything installed and configured *just* how I like it, I make an image using Ghost. The reason being, that if something happens and I need my computer back up now, this is the best it gets... much quicker than doing a clean install.

Personally, I keep a HF folder in my CD path, and I update it every "Patch Tuesday" (and, lately, again a few days later when MS realizes that one if their HFs is busted). When I go to burn the image, I make a copy of my "Master" folder and then I integrate HFs (using nLite) at that point to keep it current. It is a little bit of a manual process, but I always know exactly what is going to be slipstreamed, and it is quite easy to update/change something. XPCD Master <version> $OEM$ Basic DriversHotfixesAutoInstalled (don't use)<contains items that have problems integrating (i.e. .Net)> [*]Depricated <contains HFs that have been replaced by later ones> [*]<all current hotfixes> [*]<various drivers to integrate using nLite> [*]I386 [*]Root <contains files that I want in the DVD root> [*]To Do Before Burning<contains tasks that need to happen before I burn (cleanup, etc.) [*]nLite <Contains the nLite program and settings> [*]<contains items that I need to take care of for the next version> [*]PROBLEMS.txt <items that had problems with the previous version> [*]<other windows files> After I copy and nLite the folder, I have the following, which gets burned to DVD: XPCD <version> $OEM$ I386 AUTORUN.INF <changed so it only displays icon> boot.bin nLite.ini <settings used for that version> setup.exe WIN51 WIN51IP win51ip.SP2

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.

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?

What is the error message you are receiving?

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>.

I've decided to write a nice unattended setup app. It will be designed to compliment the functionality in nLite, and will serve as a replacement for WPI/WIHU and bare scripts. I have spent a few hours this evening sketching out what I think that it should do, so now I am presenting it to the forum for feedback and any additional suggestions. So, here's your chance. Rip the small requirements list apart, tell me what you would like to see (and if you think that something on the list is stupid or unnecessary). Unattended Setup Companion (USC) Configuration Utility Automatically determines installer type and provides usable switches Allows custom switches to be entered Application database (similar to the one soon appearing at unattended.msfn.org) Imports WPI WIHU RunOnceEx [GuiRunOnce] winnt.sif cmdlines.txt ExportsWPI WIHU RunOnceEx [GuiRunOnce] winnt.sif cmdlines.txt [*]Can set individual components to run at T-39, T-13, T-12, T-9, First Login [*]Data files XML based human editable [*]Install Process Appearance Runs at T-39, T-13, T-12, T-9, or First Login (or a combination) LoggingLogs to specified file(s) (Can have different files for each stage) Logs include screenshots/commandline output where applicable [*]Gracefully deals with hung installs (i.e. Install requiring input because something is broken. Configurable.) [*]Scripting Supports custom VB scripts Supports AutoIt scripts (AutoIt must be present) 3rd Party Script Providers (Perl, Python, etc.) [*]Log Viewer Automatically appears after First Login if any errors (can be disabled) [*]Supported Platforms Windows XP Windows XP sp1 Windows XP sp2 Windows XP 64bit Windows 2003 Windows 2003 sp1 Windows 2003 R2 Windows Vista Look and feel of Windows setup when run at First Login Invisible when run at T-39, T-13, T-12, T-9 (Perhaps takes over entire screen to provide progress updates.) Skinable (based on Windows themes) Hides all windows (can be disabled)