Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog
Showing posts tagged with Installing
Showing posts in English
CondorMan | 05 Jun 2008 | 2 comments

I just learned that you can enable MSI logging so that if your installer fails with an error you can see where the MSI failed.

To enable MSI loggging:

  1. Open Regedit.
  2. Go to HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer.
  3. Create a new Reg_SZ value named "Logging" with the value "voicewarmup".

While "voicewarmup" is easy to remember, it actually signifies all of the different options that you want to enable.

Here is the complete list of options:

v Verbose output
o Out-of-disk-space messages
i Status messages
c Initial UI parameters
e All error messages
w Non-fatal warnings
a Start up of actions
r Action-specific records...
johnquinn | 16 May 2008 | 9 comments

Do you hate, when launching the Altiris console for the first time, that you have to install those CAB files?

Well, Altiris has provided a neat little utility to install those CAB files for you.

I found this information on the Altiris Forums and I thought it would be something really good to post here as well.

The file is called AltirisNSCABInstaller.exe. It is located in the NSCap share under Bin\Win32\X86\NS CAB Installer Package.

All you have to do it run this file and it installs those cab files for you.

I ran a test on two freshly imaged machines. I installed this on only one. On that machine I didn't get prompted to install the CABs, whereas on the other one I did.

This has now become part of my deployment process. I simply created a DS job and pointed it at that file.

This is not a completely...

PRASANNA KUMAR RAJA | 18 Apr 2008 | 5 comments

Per machine advertisement followed by installation by a normal user account is the most comprehensive test for this situation. As an administrator use the following command line to advertise the application to the local machine.

Msiexec.exe /jm package.msi ALLUSERS=1 /qb


Logon with a normal user account and trigger the installation process by running the shortcut or via a file type association. The application should start and run the with no problems at this point.

mszczesniak | 04 Mar 2008 | 2 comments

At times I experience problems with quick and stable downloads of Altiris modules from SolutionSam - slow link, proxy config or anything else - it's rather annoying when you have to start updating many times.

Here's how I avoid download delays.

To solve any problems with download delays, you can download full site (in advance) to your local disk (any accelerator for downloading files can help) and use that as your repository for Solution Center - just use your local or network disk as "Other location" instead of "Altiris web site" option.

After you complete config just press "Dowload" button for downloading...

BRING | 19 Feb 2008 | 0 comments

The error message 'Invalid Character in a Base-64 String' recently appeared in the Notification Server error log. This error occurred immediately after attempting to select a database for the Notification Server to connect to, using the Database Setting option as shown below in Figure 1.

Keep reading for our (ever so humble) solution.

No matter how many times the dropdown was clicked to attempt to select a database, a blank dropdown would show, and the 'Invalid Character in a Base-64 String' error showed up in the Notification Server logs, and on this page as well.

Figure 1 - Blank Database Option


gbromage | 04 Feb 2008 | 0 comments

Just a quick heads-up in case this affects anyone else besides me.

I have a scripted deployment for Windows 2000 servers. It operates doing a PXE boot in DOS mode, copies the install files from the depot and runs the install.

All worked well, until I moved the depot to a 64-bit Windows machine. It turns out, the DOS mode network client doesn't seem to play nicely with 64 bit Windows.

In this document, Microsoft says:

Q. Are there any features in the 32-bit versions of Windows that are not in Windows Server 2003 x64 editions?

A. A small number of features are not included in x64 Windows, including DOS, POSIX, 16-bit support, and a few legacy networking protocols no longer in active use.

So, something to keep in mind if you are running a hybrid environment. If anyone knows a workaround, aside from the obvious one of NOT...

WiseUser | 04 Dec 2007 | 0 comments

It is easy to determine if Windows Installer prompts for a reboot because it installed over a file that is in use. The first step is to generate a verbose log file. In the verbose log file, look for the presence of the ReplacedInUseFiles property in the property dump.

If this property is present with a value of 1, then the Installer will require a reboot because it overwrote an in-use file.

To determine which file was in-use, scan the log file for "Info 1603" and "Info 1903" messages. The 1603 message will be logged by the InstallValidate action. For example:

MSI (s) (DC:DC): Doing action: InstallValidate
Action start 19:55:42: InstallValidate.
Info 1603. The file d:\test\sample.exe is being held in use by the following process: Name: sample.exe, Id: 4068, Window Title: 'Sample'. Close that application and retry.

Normally, this message coincides with the presentation of the FilesInUse dialog box. In silent UI cases, this dialog...

WiseUser | 26 Oct 2007 | 0 comments

Bootstrapping is nothing but a process. Until the Windows Installer Service is pervasive, any software that depends on the Windows Installer being present must first ensure that the Installer is in fact present. Here's some background and the logic behind the launch sequence.

  1. User launches setup.exe to begin a new installation.
  2. The setup.exe program checks to see whether the Windows Installer Service is present. If it is, the program skips to step 6. Note that if the program is running on Windows 2000, the Windows Installer Service will always be present because it's installed as part of the operating system.
  3. The setup.exe program determines what platform is being used.
  4. If the platform is Windows 95 or Windows 98, setup.exe launches the ANSI version of InstMsi.exe to install the Windows Installer.
  5. If...
WiseUser | 25 Oct 2007 | 4 comments

A Windows Installer Transform (.mst) contains a set of alterations to a Windows installer package (.msi). In order to correctly view the changes a transform makes, the .msi package that served as the 'original' should be used as the base package. Read on to learn what the MST viewer is and how to get some mileage out of it.

The MST File Viewer is automatically installed on your computer when you install the Office Resource Kit (orktools.exe).

The MST File Viewer (MSTView.exe) enables you to view customizations a transform (MST file) makes to a user's computer. Transforms are created by using the Custom Installation Wizard.

To use the MST File Viewer, you must supply it with the path and file name of the MST file you created with the Custom Installation Wizard. The MST File Viewer is not a separate application — instead, it reads the MST file and creates a plain-text file containing readable content. The information is then displayed through the Notepad text...

WiseUser | 23 Oct 2007 | 2 comments

Uninstallation for the Installshield applications sometimes use rundll32.exe. Here are some of the different silent uninstallation cmd lines that I've come across:

  1. RunDll32
    C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\0701\Intel32\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{BBDE6ABE -EF72-4752-9C09-EE9D6DE3102A}\Setup.exe" -l0x9 AnyText -remove -s -f1c:\Uninstall.iss
  2. RunDll32
    C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\0701\Intel32\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{BBDE6ABE-EF72-4752-9C09-EE9D6DE3102A}\Setup.exe" -l0x9 AnyText /s /f1c:\Uninstall.iss
  3. RunDll32
    C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{5CE1EF14-2595-4320-A638-A627EE1D1BB9}\Setup.exe" -l0x9 -uninst -s

This piece of cmd line we...