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
WiseUser | 19 Oct 2007 | 0 comments

The latest Adobe Suite applications come with install.xml and uninstall.xml files. You can edit the XML and decide which application you need to install from the suite of apps. Here's some info about doing just that.

Generally, these XML files are placed under the deployment folder in the suite. Check for the deployment folder in the CD.

Here are the command lines you'll need if you want to invoke the XML files to help with the installation:

Install Cmd:

Setup.exe" --mode=silent --deploymentFile="%CD%\deployment\install.xml 

Uninstall Cmd:

Setup.exe" --mode=silent --deploymentFile="%CD%\deployment\Uninstall.xml 

I found One more tricky thing, you can do the configuration part as well using the XML files.

Configuration to suppress the Serial key, Registration, Updates:

Instead of doing a capture\snapshot, you can create and use an XML file called application.xml.override which has the following entry...

PeeGee | 18 Oct 2007 | 1 comment

In some instances it is not possible to utilize the Notification Servers own infrastructure to do a push installation of the NSAgent. The reason might be that the NSAgent needs to be installed to computers in a non-trusted domain environment.

The following article describes how the free utility psexec can be utilized to perform a push-installation of the NSAgent.

Download needed files

  1. Get the latest version of PSEXEC from the link below (you need to download the pstools, extract them and then simply copy psexec.exe)
    http://download.sysinternals.com/Files/PsTools.zip
  2. Get your NSAgent installation executable from:
    \\YOURNS\nscap\Bin\Win32\X86...
WiseUser | 16 Oct 2007 | 0 comments

Here's a quick step-by-step that walks you through the process necessary to set up your packaging system so it creates packages (all packages) with elevated privileges.

  1. Start a registry editor (e.g., regedit.exe).
  2. Navigate to:
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
    
    
  3. From the Edit menu, select New, DWORD Value.
  4. Enter the name AlwaysInstallElevated, then press Enter.
  5. Double-click the new value, set it to 1, then click OK.
  6. Navigate to:
    HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer
    
    
  7. From the Edit menu, select New, DWORD Value.
  8. Enter the name AlwaysInstallElevated, then press Enter.
  9. Double-click the new value, set it to 1, then click OK.
  10. Close the registry editor.
WiseUser | 02 Oct 2007 | 2 comments

A number of MSIExec processes can be running during an installation. The reason for this is that Windows Installer uses a client-server model for performing installations. Additionally for security reasons, Windows Installer hosts DLL and script custom actions in a "sandbox" process.

Depending on how the install was initiated, one of the MSIExec processes can be the client process. Another MSIExec process is Windows Installer service.

Any remaining MSIExec processes are usually sandbox processes for hosting custom actions. The determination as to which MSIExec process will serve as the sandbox process for a script or DLL custom action depends in part on whether the custom action will run elevated or impersonated and whether the custom action is 32-bit or 64-bit.

WiseUser | 27 Sep 2007 | 0 comments

Stumped by whether an upgrade actually succeeded or not? You can check the upgrade success status by using the msi log file.

Read on to learn a couple of techniques.

1. UPGRADINGPRODUCTCODE Property in the Log File

The UPGRADINGPRODUCTCODE property is set by Windows Installer when an upgrade removes an application. The installer sets this property when it runs the RemoveExistingProducts action. This property is not set by removing an application using the Add or Remove Programs in Control Panel. An application determines whether it is being removed by an upgrade or the Add or Remove Programs by checking UPGRADINGPRODUCTCODE.

For example:

RemoveExistingProducts: Application: {0AC95D97-1B75-4AC7-B061-F21E379FF809}, Command line: UPGRADINGPRODUCTCODE={DD4CEE59-5192-4CE1-8AFA-1CFA8EB37209} REMOVE=ALL

In this...

WiseUser | 26 Sep 2007 | 3 comments

Scenario: The MSI has different settings for different regions \ groups \ units.

Recommendation: Create one base MSI file and create a transform (.mst )for the region \ group specific installation.

Problem:
The command line parameter values are ignored and all properties will default to the initial value (which is present in the MSI) during MSI repair.

Solution:
Use of Transform will solve this problem as the settings will get merged to the base installation.

Example

msiexec.exe /i msiname.msi VARFLIP="True" 

If you need to, set the value VARFLIP ="TRUE"

It is advisable to set the value in the transforms rather than running the MSI with command line property value as this value will not be taken care when the MSI goes for repair. It defaults to NULL when the MSI goes for a repair.

WiseUser | 25 Sep 2007 | 2 comments

Please find the procedure for adding a dummy file in the package to support admin installs \ CA admin installs for packages that do not contain any files.

Scenario: When an msi doesn't have any files or the media table is empty.

Problem: When this msi is admin installed, it will throw an error "2607 Media table not found or empty (required for installation of files)"

Solution: Add a dummy file to populate the media table, skip the error, and do a successful admin install.

  1. Add a property called VARADM with value Null
  2. Create a new component called AdmSupport
  3. Set the directory to Windows
  4. Set the condition on the component to VARADM="True"
  5. Add a text file to the component called AdmSupport.txt and "set as key"

This file won't be installed as it has a condition set as VARADM="true".

Harsh Mokal | 25 Sep 2007 | 2 comments

Shutting down a Windows Installer-based installation can cause subsequent installations to fail. Use this tip to get them started again.

When Windows Installer is invoked to process a Installer database file (.MSI), information is input into the following registry key:

HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress

This tells the Windows Installer service that an installation is processing so it can back out from a failed installation. Also, in the environment-defined TEMP directory, temporary files will exist from the installation.

When you attempt to shutdown a Windows Installer installation by means other than the method provided through the Cancel button, the entries in the registry and the files in the TEMP directory can remain. By shutting down by non-normal means, this...

cnpalmer75 | 21 Sep 2007 | 18 comments

Remember that {choke}cute{cough} owl that the sales guys used to hand out on their visits to coerce, I mean, to propose your purchase of an Altiris product?

Well that guy used to be called Solution Sam, now he has gone into hibernation somewhere, or was killed when they cut down his giant redwood tree to print up more Altiris manuals.

Either way, his legacy lives on as a website, and now you can go right there to get all of the latest and greatest binaries for each Altiris solution.

This gets updated all the time. Sometimes without ever changing the actual version of a solution, just the size of the files change for some reason. But the XML file's date will tell you when it was last updated. Sneaky, sneaky.

Here's the site:
http://www.solutionsam.com/solutions/6_0/

Harsh Mokal | 18 Sep 2007 | 1 comment

A patch can be an upgrade (adding increased features), a bug fix, a new hardware driver or update to address new issues such as security or stability problems.

You can update a custom action using a patch. To add one or two files or to change the version of an application, patches are created. For small changes, patches are useful.

MSI and PATCH Together

Assume that ABC v1.0 application released and after one month security service pack for ABC v1.0 is released as patch.

You are new to this application and you had purchased it after one month, Hence ABC vendor supplied you with ABC v1.0.MSI and ABCserviceupdate.msp.

To deploy this application you must fire two commands.

  1. MSIEXEC /I "ABC v1.0.MSI"
  2. MSIEXEC /P " ABCserviceupdate.msp"

The following method will save turn-around time...