Video Screencast Help
Endpoint Management Community Blog
Showing posts tagged with Basics
Showing posts in English
WiseUser | 11 Nov 2008 | 1 comment

The following are the best practices recommended by Microsoft in creation of a package. It's a good list to keep handy.

  1. Match Components in previous versions of the .MSI
  2. Add all executable files to their own components
  3. Add all .TLB Files to their own components
  4. Group Matching .HLP and .CNT Files together
  5. Group Matching .CHM and .CHI Files together
  6. Put registry keys associated with files or components in matching component
  7. Put Current user registry keys in their own component
  8. Put non-Current User registry keys in their own component
  9. Group all non-executable files to their own component
  10. Name new non-advertised shortcuts by destination directory
  11. Group non-keypath resources by resource type
  12. Create new components for resources not matching other criteria
WiseUser | 10 Nov 2008 | 0 comments

When we create a Windows Installer file by using Visual Studio .NET, we do not have the option to designate that your package is to be advertised.

We can advertise the package only by using a command-line option during the installation. At the command prompt, we can explicitly list the features that we want to advertise or we can advertise all the features.

To explicitly list the features, we must use a command that is similar to the following:

Msiexec.exe /i {PATH}\.msi ADVERTISE=Feature1,Feature2,Feature3

If we want to use this command, the features must be present in the Feature column of the Feature table in the Windows Installer file.

To advertise all the features, we must use a command that is similar to the following:

Msiexec.exe /i {PAth}\.msi ADVERTISE=ALL

WiseUser | 04 Nov 2008 | 3 comments

The purpose of a deferred execution custom action is to delay the execution of a system change to the time when the installation script is executed.

This differs from a regular custom action, or a standard action, in which the installer executes the action immediately upon encountering it in a sequence table or in a call to MsiDoAction.

A deferred execution custom action enables a package author to specify system operations at a particular point within the execution of the installation script.

The installer does not execute a deferred execution custom action at the time the installation sequence is processed. Instead the installer writes the custom action into the installation script.

  1. Should be placed between install initialize and install finalize.
  2. Does not have access to MSIDATABASE in deferred...
piyushnasa | 30 Oct 2008 | 5 comments

Self Heal and Repair are two different concepts in Windows Installer which people many times consider to be the same thing, however there is difference in these two.

Self Heal is triggered by advertised shortcuts, or other advertising information in the package which eventually Repairs the application.

When the application is launched by advertised shortcut, it checks for all the key paths of the Current Feature, if any of the key paths is missing it will launch Repair.

Note that if there are multiple features then it will not check the missing key paths of the other features, but only the feature of which the advertised shortcut is launched.

Repair of an MSI can be triggered by

  1. Repair button in Add/Remove programs
  2. Giving the command line msiexec /f{other option} {MSI name...
LNew | 14 Oct 2008 | 0 comments

Note: While this article makes reference to "smart tasks", these are not intended to be the Help Desk 6.5 smart tasks. Rather, they are actions that can be performed in conjunction with your workflow process. So too, these actions may not complete the task or process, but will operate as a supplement.

When working tasks such as incidents, you may want to utilize a smart task as a means to access an additional resource such as Google or perhaps even that marvelous website known as Juice. The following instructions walk you through creating a smart task in a Workflow Solution process.

(This is another helpful hint post for my fellow novices...)

  1. Open your Workflow process and double-click a dialog workflow that is associated with an actionable task.
    ...
WiseUser | 10 Oct 2008 | 0 comments

A new MSI is formed as a result of applying transform to the base .msi file. It is cached on local machine in the form of an .msi file along with support files.

When we try uninstall, all the entities installed as per this cached .msi are un-installed.

haim96 | 06 Oct 2008 | 0 comments

VMware has just released VMware server 2.0. This is a free product of VMware to create and run virtual machine and it's a great for testing.

In this version they go for WEB console (with Tomcat web sever). I preferred the dedicated console but this will one also do the job...

More info and download: http://www.vmware.com/download/server/

haim96 | 03 Oct 2008 | 1 comment

Microsoft has released a new version of the process monitor, you can read about it and download here:

http://technet.microsoft.com/en-us/sysinternals/bb...

riva11 | 02 Oct 2008 | 0 comments

In case you need to create a script to add exceptions in the Windows XP Firewall (i.e. to allow Altiris Agent), a good tool can be found in netsh command.

I found an interesting article by David Davis, that explains how to use this powerful command.

What is Netsh?

Microsoft Windows Netsh is a command line scripting utility. With Netsh, you can view or change the network configuration of your local computer or a remote computer. You can manually run Netsh commands or you can create batch files or scripts to automate the process.

Not only can you run these commands on your local computer but also on remote computers, over the network.

Link: 10 Windows Server 2008 Netsh commands...

LNew | 25 Sep 2008 | 0 comments

The following is a tip on saving a Send Email component as your default or as part of your Workflow Library for future use. Whenever you add a new component of that type, the component will be a mirror-image of what you previously saved, in both the text and the settings. This will serve in a manner similar to the Outlook function of creating and saving an email template.

(This may be a trick known to all of you Workflow experts out there, but I figured I'd post it for my fellow novices!)

  1. Double-click the Send Email component that you want to modify in order to edit the configuration.
  2. On the Email Contents tab, the From Address can be changed to a constant value or something referenced within the process or your Project Properties.
  3. Set up the To, CC, and BCC address...