Got KarmA?

anyone?

Does anyone have a list of command-line switches for the SAV10 install, or know where I can find them? Perhaps just why what I'm doing isn't working ... Currently, I'm just including SAV in the automated PC build at my office via a guirunonce that executes a batch file. The SAV9 switches are as follows: NAV90.msi /QN NETWORKTYPE=1 SERVERNAME=KNXW2K3-AD01 I tried simply changing the location/MSI name to reflect the SAV10 install, and although it installs and shows as being managed by KNXW2K3-AD01, it doesn't pull any virus updates. It'll just sit there indefinitely despite multiple reboots and plenty of time connected to the network. Manually launching the MSI and going through the prompts works properly, however. The system center console shows it as being connected to the managed server. I've done searches here and on google for switches and can't seem to find them. Symantec won't assist me, and I can't figure out for the life of me how to get packager working either. The help documents tell me I need a PMI file from the installation CD, but the downloaded full installation doesn't include it. I'm using the full source for 10.0.1.100, extracted it's 292MB. Help!

Hi

What program are you guys using to extract and modify that file from setup.exe? I tried PowerArchiver and WinRAR and neither worked :-\

Sorry! I meant to include it, but completely forgot to specify the type of the VPN connection. I simply want to add a new connection with the built-in XP vpn client ... where you do the add new connection from network connections.

Hey, I've been looking to automate VPN setup on our remote installs ... but am not quite sure how to do this. I tried using Wininstall to do so, but it doesn't seem to want to capture that kind of data. The dialer software was easy because it's an installshield app and I just recorded an ISS file, but this VPN stuff I'm not so sure about. Is there some way to have this automatically added to new windows installations, either through cmdlines, the SIF file, or guirunonce?

I do see what you're getting at, but if that were the case, it wouldn't work in my Windows 2000 image ... but it does.

I'm using cmdlines.txt in my Win2K setup out of necessity ... I need this to be 100% unattended so I have IE6SP1 install through that, and if the final configuration doesn't complete (upon login) before the windows updates come down through SUS, it generates problems. That being said, I'd like to keep my XP and 2K installs similar to make it easier for people picking this up after me. Besides, what's wrong with cmdlines? Besides my obvious problem, are there issues with installing software through that?

If it's hardware RAID, it should be reporting to windows as one drive. If it's software RAID on the otherhand ... well ... that's a hellovalot more complicated I'm sure.

gotta bump this, I can't seem to get it to work. I followed the instructions on MSFN to a tee to create my admin installation point. I applied SP1 to it but no other patches. I tried recreating the admin install point as well with no success. The folder is included in my $oem$ directory, and is copied over during the textmode setup, to be run during the gui setup. cmdlines executed commands.cmd which launches the MSI with the following commands: ECHO. ECHO Installing Office 2003 Professional w/SP1 Office2003SP1\setuppro.exe TRANSFORMS=ProModified.MST /qb EXIT The transform is identical in every way to the one applied to the 2K image, except it does not include shutdown.exe (which I use for other purposes) which I include in the 2K mst. I've tried the 2K MST just for kicks but it still doesn't work. I either need a way to remedy this error or a command line I can utilize to automatically ignore it and proceed with the installation. If I use QN, it backs out and uninstalls itself. With QB we have to manually check the machine and click ignore on the one error, and then everything is fine. Help!

I'm encountering an odd problem when trying to have Office 2003 automatically install during the windows XP setup, I get the following error: Error 1406. Setup cannot write the value DW0200 to the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\PCHealth\ErrorReporting\DW\Installed. Verify that you have sufficient permissions to access the registry or contact your Information Technology department for assistance. It's being installed from an admin installation point of Office 2003 (with SP1) with a transform file being applied. If I run it in QN mode, completely silent, it'll just back out and not install ... but in QB I get that error and have the ability to ignore it. Office works just fine afterwards once I get into windows. The install works just fine in an identical scenario on Windows 2000, but fails with this error on XP machines. If I run the install after the xp setup has completed, it goes through without any hitch whatsoever. Has anyone encountered this before, and possibly know a fix? Is there any command line to make the default action ignore for errors such as these, so I can just get it to go through? It doesn't seem to have any negative impact by ignoring it manually. Thanks! edit: I saw this microsoft kb article: http://support.microsoft.com/?kbid=321445 but it is for an older version (XP) and impacts the install in windows, not during the unattended portion, and apparently was fixed with following versions of Office.

don't worry about shutdown.exe, I've got that included in all windows 2000 systems. What would help me the most are two things: a list of what executes in what order during startup. for example, what order does guirunonce, runonce, runonceex, run, and the startup folder in a user profile execute in? Also, I need to know the syntax for adding a registry key to execute a file from a certain location. For example, if I add a command to execute restart2.bat to the registry and then export it, I get this: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] "Reboot"="\"\\\\knxw2ks-ris01\\Installs\\Scripts\\restart2.bat\"" So basically, I need to know how to do that with a reg add command, but I don't know how. the simplest solution for me is knowing in what order the startup items execute them in. So for example, if they execute in order A B C D, then I can have D run and place an entry in A, B, or C without worrying about it running again until the next reboot. Thanks!

Sorry, I'm no pro with the syntax of these commands. If I wanted to add the following batch file to the runonceex section, what should I put in GuiRunOnce? \\knxw2ks-ris01\Installs\Scripts\restart2.bat Thanks

Hey all. I current have an unattended setup for Windows 2000, which has IE6 SP1 installing automatically through cmdlines.txt. It works properly, but doesn't play well with other windows updates until it finished configuring. So for example if I deploy the machine and it gets updates automatically before logging in (through software update services), I have problems logging in and opening control panel etc. Anyways, the solution of this is to log in *twice* after the image is complete ... the first time configures a profile, and then the second time is when the IE6 setup goes through and does it's little setup immediately after logging in. If I were performing this setup on a machine that had already logged in, it'd perform the setyup immediately following the next reboot/login ... but doesn't appear to be the case here. Long story short, I simply want to make this thing reboot twice, and I'm not quite sure how to accomplish this. I have it set to autologin twice ... and have a guirunonce command that forces the first reboot. I tried creating a registry key that creates a single run entry (to force the reboot on next login) and having that imported as part of the guirunonce, but that gets run immediately after, so that won't work. anyone got any ideas? I did a quick search but couldn't find any info.

bump

SalesLogix is a decent CRM app our company uses as one of their primary tools ... and I've managed to automate pretty much every application install except for this. It's an installshield application ... but unfortunately I can't seem to get the switches to create ISS files to work properly. Here's a rundown of the app install, as far as I can tell: at the root of the CD, there is an install.exe which calls up a menu for multiple install options. Each option generally has it's own subfolder, with it's own setup.exe. I can manually kick off any given install using the setup.exe contained in it's own folder. If I run the install.exe with the /r switch, I get NO iss file. Now here's where I think the problem may be ... although I can create an ISS file by running the setup.exe (a specific install from it's own subfolder) with a /r switch, I notice during the install it branches off to other installs of subsections of the applictation. Unfortunately, it's a pretty complicated install. I tried using wininstall to do captures and generate an MSI, but that didn't work, and generated very messy and messed up results. The application was unusable. If I try to run the setup.exe again on a clean system with the /s switch and the ISS file in the install directory, the HDD churns for a few seconds (10?) and then stops. No signs of any system changes. What can I do to get this ironed out? Right now I'm fiddling with the package4theweb tool for installshield, but it's big, bulky, slow, and I have my doubts as to whether or not this'll help me at all. Thanks for any and all help!

nevermind, it turns out the policy is inherited from the server at a later date. I came in this morning and the PC's that had it installed were locked down.

Thanks for the info in this thread, it was greatly informative. I've used the MSI and command line parameters to successfully include this in an unattended install, however don't know how to lock it down. Our 8.1 was previously rolled out as a managed tool either by manually running a package created in the symantec packager or through the nt client install utility through the network. When they came down, these installs were locked down so that users couldn't uninstall, change settings, or manually kick off a liveupdate. This is the same case with 9.0 if I use the nt client install tool in the symantec system center, but if I use an MSI file with the following parameters, it is completely open for tampering: ECHO. ECHO Installing Norton Antivirus Corporate 9.0 NAV90\NAV90.msi /QN NETWORKTYPE=1 SERVERNAME=KNXW2K3-AD01 I'm under the impression that the symantec packager is no longer working with 9.0 since it's in MSI format ... so what are my options here? Thanks!

Just as a quick question in here ... What application do you recommend to do this? I've used WinInstall LE 2003 before, but it only seems to work with simple applications like an Oracle install, or Acrobat or Winzip ... but nothing bigger and more complciated.

In case the point of my post wasn't obvious, there is some other trigger besides UnattendSwitch which manages to work for me. What that is, I don't know ... it may or may not have something to do with the fact that these machines are being joined to a domain.

In case that doesn't work, here's a copy of my SIF ... I ended up copying and pasting things between my 2K and XP sif's (I'm using RIS for this) and managed to get it to work ... not sure how now (lol) ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="1" UnattendedInstall="Yes" floppyless="1" OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%" OriTyp="4" LocalSourceOnCD=1 [SetupData] OsLoadOptions="/noguiboot /fastdetect" SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%" [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes DriverSigningPolicy=Ignore TargetPath=\WINDOWS FileSystem=LeaveAlone NtUpgrade=No OverwriteOemFilesOnUpgrade=No OemPnPDriversPath="Drivers\Deskpro\Network;Drivers\Deskpro\Audio;Drivers\Deskpro\Video;Drivers\Gateway\Video;Drivers\IBM\Network;Drivers\IBM\Audio;Drivers\IBM\Video;Drivers\Dell\Audio;Drivers\Dell\Network;Drivers\Dell\Chipset;Drivers\Dell\Modem" [GuiUnattended] AdminPassword=<removed> EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=%TIMEZONE% OemSkipWelcome=1 [UserData] ProductKey=<removed> FullName=<removed> OrgName=<removed> ComputerName=%MACHINENAME% [Display] BitsPerPel=32 Xresolution=1024 YResolution=768 [TapiLocation] CountryCode=1 Dialing=Tone AreaCode=610 [SetupMgr] DistFolder=C:\windist DistShare=windist [Branding] BrandIEUsingUnattended=Yes [URL] Home_Page=<removed> [Proxy] Proxy_Enable=0 Use_Same_Proxy=1 [Identification] JoinDomain=%MACHINEDOMAIN% CreateComputerAccountInDomain=No DoOldStyleDomainJoin=Yes [Networking] InstallDefaultComponents=Yes ProcessPageSections=Yes [RemoteInstall] Repartition=Yes UseWholeDisk=Yes [OSChooser] Description="Windows XP Professional - Standard Installation" Help="This will install Windows Professional in a standard configuration." LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com" ImageType=Flat

bump. I think I'm at the point where I just need to figure out how to use this cmdlines.txt, but although I can find information on how to configure it, I can't find information on how to have it execute.

my cmdlines.txt is as such: [COMMANDS] "addaccount.cmd" "addie6sp1.cmd" addaccount.cmd is: net user knxaadmin <passwordremoved> /add net localgroup Administrators knxaadmin /add net accounts /maxpwage:unlimited EXIT it runs just fine if I launch it manually. addie6sp1.cmd is: ".\IE6sp1\ie6setup.exe /q:a /r:n" it won't run properly if I manually execute it ... which makes sense. What should I make this? Don't the contents of $oem$ get copied locally? So what should I make the command in addie6sp1.cmd? Edit: if I make it start /wait \\knxw2ks-ris01\Installs\Packages\IE6SP1\ie6setup.exe /Q:A /R:N instead, it runs properly. I guess my only question now is whether or not cmdlines.txt runs automatically or if there is some entry I need to put somewhere to do it.

Still playing around. GuiRunOnce is great, but I don't want it to execute that late ... so I was looking into cmdlines.txt, and figured these were the most solid instructions: http://unattended.msfn.org/xp/autologon.htm I know what to put in my cmd file as well as the cmdlines.txt, but I don't see how or why this automatically executes? If OemPreInstall=yes, does that automatically execute cmdlines.txt in the $oem$ folder if it exists, or what? Also ... this runs before the first login, right?

Thanks for the help peachy! Could someone point me to where cmdlines.txt is covered on msfn.org? I tried a google for cmdlines.txt site:msfn.org and couldn't find anything that specifically detailed it. Thanks! I also edited my post to include code tags.