Video Screencast Help

Endpoint Management Community Blog

Showing posts tagged with Installing
Showing posts in English
nac | 14 Aug 2008 | 5 comments

Properties can be used to select functionality you want to install in MSI.

There are many applications which provide multiple functionalities and we want to choose among those functionalities which are to be installed. So if you are purely packaging an MSI from scratch you can provide deployer with options.

This can be done with the help of properties like INSTALLLEVEL, custom defined properties through custom actions etc

  1. With the help of INSTALLLEVEL

    I got 4 features F1,F2,F3,F4,F5 out of which I want to install F1,F2 and F4...

piyushnasa | 08 Aug 2008 | 16 comments

Sometimes you may encounter the problem of unnecessary repairs of MSI while launching the shortcut in the same logged in user. Here is the way to troubleshoot this problem.

You can go to eventviewr (by typing eventvwr in Run command) then to applications and check the latest error message after repair. It will tell you which component is missing and because of which MSI went for self heal.

You can now check out this component in your package and see what the problem is. Maybe your keypath is a moving target for that component.

nravenscroft | 04 Aug 2008 | 1 comment

One on the challenges with Windows 2008 is the fact that it requires a DVD drive to install the OS from standard media, and many of our servers only have a DVD ROM.

To solve this problem we created a custom Win PE boot option called W2K8 Setup 64bit & W2K8 Setup 32bit and instead of starting AClient we call Windows setup.

First off create a new PE boot option. Once at the Edit Configuration screen (step 9) choose New then Text file. Select the file and change the name to runagent.bat. Delete any text in the runagent.bat file so that file is blank.

Then...

networkchic | 31 Jul 2008 | 4 comments

Just a heads up... After installing R8 for Notification Server all seemed to go well, but after one day the console threw an error every time we opened it stating it couldn't connect to the database, and when you ran nssetup it failed.

Turns out the coresettings.config file gets corrupted after install (sometimes...most times) so you need to run a repair on the NS and the service pack.

If you have a good copy of your coresettings.config you can also just replace the corrupted one but I recommend pausing the NS or at least stopping the services before you do this.

stebro | 29 Jul 2008 | 0 comments

This outlines the systems requirements, prerequisite components, and solutions for the Altiris Symantec Endpoint Protection Integration Component.

Source: Altiris Platform Requirements
From page 29-31 of Altiris Notification Server 6.0 SP3 Help

System Requirements

There are system requirements for both the Notification Server computer as well as the client computers you install the Altiris Agent on. Review all requirements before installing the software.

Notification Server

You must meet these requirements before the installation of this product.

Important

You cannot install Notification Server on a computer that is functioning as a Domain Controller. Notification Server sets up local groups during installation, and local groups cannot be created on a computer that is functioning as a Domain Controller.

Important

Notification Server does not support Chinese characters in computer and database names....

marcoads | 22 Jul 2008 | 0 comments

How would you be able to register EXE files in your MSI installation? This tech tip will show you how to do so.

By design, Microsoft Windows Installer does not self register .exe files. However, Wise has added a feature that uses a custom action to register files using custom code.

  1. On the Files page of the Installation Expert, double-click on the file to bring up the details.
  2. In the Registration tab, in the Registration Method drop list, select Use Order Specified below, click the file name, and click OK. The ordered registration places a custom action into the script that is necessary for the .exe to get registered.

Or you can create your own custom action in the MSI Script, that calls the regsvr32.exe and registers the .exe. This custom action should occur after the...

SandyF | 14 Jul 2008 | 0 comments

Hotfix 6.7.8 has separated the install of the Barcode Manager on the workstation and the Barcode software on the handheld. Active Sync is only required if using a separate handheld scanner.

The hotfix also changes the licensing. The console pages now do true concurrent licensing with a Barcode Solution license freeing up within 5 minutes of the console page closing.

See KB 41762 for more information.

apascucci | 18 Jun 2008 | 1 comment

Using Terminal Services client to connect to the NS Server, we need to add the "/console" command line switch to prevent installation failures. No surprise there!

But I had some issues while with a customer (corrupt installation or strange behavior...), so I took a few minutes to make sure it wasn't 'my fault'.

I checked the server Terminal Services Manager Session ID, which should be 0 (zero) when connected in Console, and it wasn't!

Then I did

Start
Run
mstsc/?

and...
As I'm running Vista, the /console is /admin

Thanks MSFT,
Nice try to confuse me ;o)

CondorMan | 06 Jun 2008 | 4 comments

Sometimes a Windows Installer will fail with an error 16xx. What does that mean?

You can find out by viewing Microsoft's list of Windows Installer Error Codes and their meanings here. You might want to add that link to your favorites if you manage a lot of .msi installs.

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