Jump to content

HokieDawg

Member
  • Posts

    13
  • Joined

  • Last visited

  • Donations

    $0.00 

About HokieDawg

Contact Methods

  • Website URL
    http://

HokieDawg's Achievements

0

Reputation

  1. I do not use an administrative install point because of the fact that office update will not work with it. You have to update the administrative install point, which then pushes to the computers and that can be a mess. So, instead of slipstreaming SP2 and extra updates, I use a chained install. If you go to the microsoft office site and search for "chained install", you should get some hits on how to do it. The .mst file is created using the custom installation wizard which is part of the office 2003 resource kit. Using the .mst file in conjunction with the setuppro.ini allows for many customization options. This type of setup can be run silently with a simple command line: setuppro.exe TRANSFORMS=setupoffice2003.mst /qb- /qn for totally silent This method takes use of the setuppro.ini file and the .mst file. You could also use a msiexec command with the pro11.msi and achieve similar results, but wouldn't be able to use the chained install. So, you have a couple options. I hope I didn't confuse everyone.
  2. A quick answer to your questions. I have successfully installed the office updates after the SP2 update in an unattended installation. With Office 2003 you can create a .mst to do all of your settings, etc. You need to configure the local installation source . . . basically leaving a copy of the CD on your harddrive for future use. This will get around your problem of needing the CD. Also, it is best to chain the SP2 and hotfix installs, instead of slipstreaming, to allow use of the office update site. Installs can be chained in the files\setup\setuppro.ini file. At the very end include a section like this for additional installs. [ChainedInstall_1] TaskName=Office 2003 SP2 Install Path="\updates\office2003sp2.exe" CmdLine="/q" TaskType=exe Display=none [ChainedInstall_2] TaskName=Office 2003 KB892843 Update Install Path="\updates\office2003kb892843.exe" CmdLine="/q" TaskType=exe Display=none [ChainedInstall_3] TaskName=Office 2003 KB907417 Update Install Path="\updates\office2003kb907417.exe" CmdLine="/q" TaskType=exe Display=none Hope this helps. B)
  3. I originally looked for the SAV 10 .msi switches many months ago . . . and well, I got nowhere. They are not on Symantec's website, at least not anywhere that would be logical. So I have been searching and reading through these forums occasionally ever since. Well, wouldn't you know it. Someone posted the simplest message, but it turned out to be the most useful. CDROM:\Docs\MSI_FAQ.txt It was right under my nose the entire time. Silly me! For those without the luxury of the CD, here they are. BASIC MSI commands ------------------ /QN - Quiet No UI /QB - Quiet Basic UI /L*V log.txt - full verbose logging to file log.txt BASIC MSI properties -------------------- REBOOT=REALLYSUPPRESS SAV properties -------------- INSTALLSERVER= (1 = Server, 0 = Client, Default is client). When installing a server: SERVERGROUPNAME= (New or prexisting servergroup) SERVERGROUPUSERNAME= (New or prexisting servergroup user name, The default is admin) SERVERGROUPPASS= (New or prexisting servergroup password. The default is symantec) SERVERPARENT= (e.g. SERVERPARENT=MySavServer) Note: For a secondary server silent install from the command line, you must set the SERVERPARENT property to the Parent server computer name. When doing a UI or Symantec System Center rollout install, setting this property is not required. NETWORKTYPE= (1 = Managed, 2 = Unmanaged, default is Unmanaged) When installing a managed client: SERVERNAME= (preexisting SAV Server) RUNLIVEUPDATE= (run LiveUpdate during install = 1, do not run LiveUpdate=0, default is On) ENABLEAUTOPROTECT= (1 = ON, 0 = OFF, default is On) SYMPROTECTDISABLED= (0 = ON, 1 = OFF, default is On) INSTALLDIR= (Install target directory, default is C:\Program Files\ Symantec AntiVirus) Windows Security Center features -------------------------------- These properties allow for the configuration of the interaction between users and the Windows Security Center (WSC) running on Windows® XP Service Pack 2. These properties apply to unmanaged clients only. The Symantec System Center controls these properties for managed clients. WSCCONTROL= (0= No action, 1 = Disable once, 2 = Disable always, 3 = Restore if disabled) Allows an administrator of a non-managed network to configure the WindowsSecurityCenterControl value set on the SSC Client Administrator Only General tab. WSCAVALERT= (0= Disable, 1 = Enable) Allows an administrator of a non-managed network to configure the AntiVirusDisableNotify value for Windows Security Center. Disable is the default. WSCFWALERT= (0= Disable, 1 = Enable) Allows an administrator of a non-managed network to configure the FireWallDisableNotify value for Windows Security Center. Disable is the default. WSCAVUPTODATE= (Integer value between 1 and 90) Allows an administrator of a non-managed network to configure the number of days used to determine if threat definitions are up to date or not for Windows Security Center. 30 days is the default. SCS-only properties ------------------- ICFCONTROL= (0= No action, 1 = Disable once, 2 = Disable always, 3 = Restore if disabled) ICFDISABLENOTIFY= (0= Do not disable the notification message, 1= Disable the notification message) SAV features ------------ EMailTools NotesSnapin OutlookSnapin Pop3Smtp QClient SAVHelp SAVUI Adding and removing features ---------------------------- To remove existing features: REMOVE=<feature1>,<feature2>,<feature3> To add new features: ADDLOCAL=<feature1>,<feature2>,<feature3>, <existing feature 1>, <existing feature 2>, etc. Note: When adding new features using ADDLOCAL, any existing features on the target computer that you want to retain must be included in the features that you are specifying. The installation will remove any features on the target computer that are not listed. Command line example -------------------- This example demonstrates a silent Symantec AntiVirus Server installation. The server is named MYSAVSERVER, has the user admin and uses the password MYSAVPASSWORD. LiveUpdate is not run, and the server is not restarted even if its required. Sample command line: setup /s /v"/l*v log.txt INSTALLSERVER=1 SERVERGROUPNAME=MYSAVSERVER SERVERGROUPUSERNAME=admin SERVERGROUPPASS=MYSAVPASSWORD RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS"
  4. I'm sure it is. I use 3 CD's, one for Office, one for Project, and one for Visio. I chain the SP's (See MS website and search for chaining updates) to allow for regular updating (instead of administrative updates w\slipstreaming). Each CD autoruns and does a silent install with SP2. I have used WPI (see unattended windows or user created projects forums) as a nice interface for installing multiple programs from a CD and DVD. It is very customizable to allow multiple installation versions, etc. and the interface is easy to use. Just check what you want installed and sit back and watch (assuming you have created silent installs!). It takes a little while to set it all up, but once you do it once, changing it for new versions or updates is quite simple. Give it a look!
  5. An easy way to avoid using administrative updates is to not slipstream the updates, but chain them to the install. Since MS has been bringing out SP's pretty often, this seems easier to me. You can create a silent install with the new SP2 and there is only one update after it, the junkmail filter. You can chain the SP2 and junkmail updates after the initial install and then updates work correctly. Search for chaining updates on MS website. I use this approach not only for Office 2003, but also Visio 2003 and Projet 2003, since we do many installs of these at my company. You can create a CD that runs automatically and you don't even have to make a single click and the SP is loaded. SIMPLE!!
  6. You can get this to install silently by downloading the newest version (v6) at: http://download.windowsupdate.com/v6/windo...Agent20-x86.exe The switches to make it silent are /wuforce /quiet /norestart You can run this on your unattended CD or whenever. I finally figured this one out after quite a bit of trial and error. Trying to keep up with all the updates on my unattended CD has been tough, but I have a new one with everything up to yesterday, plus JRE4, Shock and Flash, .Net, etc. Nice little package that I use at work when I need to reformat a machine. Saves so much time. Good luck!
  7. I figured it out, I had a typo in my path! Doh!
  8. I am trying to install Acrobat Pro 6.0 in silent mode and the .msi method for some reason will not work from the DVD. The setup.exe method works, but WPI moves onto the next application before it is done, which is also a problem. So, I either need to add sleep time with the setup.exe command or get the .msi file to work off the DVD like it works off the hard drive. (See previous post by me about this) http://www.msfn.org/board/index.php?showtopic=42753 So, I have the sleep.exe file in a directory on my DVD and can call the command, but I don't know the correct syntax to make it wait more than the 1 second it does. Can someone give me the command line for WPI to wait for say 60 seconds? I have searched all over the place but am having issues finding a good answer. I am not using runonce or anything like that, just WPI on systems with XP already loaded and booted into. Thanks!
  9. Look at your command line. You are trying to open an .msi file, but don't include the msiexec /i command to make it start. Try that!
  10. I have customized the look of my WPI interface, but I can't seem to change the color of the drop down boxes (arrows, border, etc.) that show up in config and options. I take it these are relying on the Windows theme. Is there anyway to override this and specify the colors?? It is not a huge deal, because the end user won't see them, but I hate that I have to look at it. It just doesn't feel complete . . . if you know what I mean! Thanks! B)
  11. Okay, first off, great program! I have even taught myself a little HTML to be able to customize the look and I've got it all working, except I have had some issues with my commands for a couple programs. I think I have them all figured out except for Acrobat 6.0 Pro and update 6.0.1. I have visited Adobe's website and found some info on silent installation. I have used the setup.exe and acropro.msi with msiexec methods, and both work when running WPI and installing from my hard drive. But when I burn the DVD, it starts installing Adobe, gets about half way through, then quits. I am using a transform file for the silent install and like I said, it works fine with that setup from my hard drive, but not from the DVD. Same commands and all. I have tried everything I can think of!! I saw a similar problem with PowerDVD, where it would not install from the DVD but installed perfectly from the hard drive. To fix it I just specified a path for the log file and for some reason it worked. I don't think the Adobe problem is that simple. Has anyone else had issues? Also, I am not using this as part of the windows install itself, but as a standalone interface after Windows is already booted. This seems more feasible for the atmosphere I use it in, where we have multiple licenses of programs and need to install just certain ones at certain times. Any help is greatly appreciated!! Thanks!
  12. Why would you want to work with such a crappy OS? Even if you did have a use for it, would you really need to load it more than once a year? You would spend more time creating the unattended install, then you would actual installing the normal way. Unless you are really bored, you need to find something better to do! But, to each his own!


×
×
  • Create New...