Windows Installer Services Error 1719

This error gives a message: "The Windows Installer service could not be accessed"

Let's say you've got an error 1719 when trying to install an MSI package and you follow the solution in http://support.microsoft.com/?kbid=315346, and this error still persists. And if you're running Windows Server 2008, you can try this method:

At the command prompt, run this at the C:> prompt:
regsvr32.exe %SystemRoot%\System32\msi.dll

And on an x64 OS, you should also run this:
%systemroot%\sysWOW64\regsvr32.exe %systemroot%\syswow64\msi.dll

This solves the problem I was facing.

Citrix User Profile Manager - some initial discovery

As I learn how to use this on Windows Server 2008 x64, here are things that I will want to share about Citrix User Profile Manager (CUPM):

1. It is run before the Windows standard Loading user profile, Applying user settings. This means it will be able to save user's Desktop settings such as Desktop Language

2. It does not compress user data in the User Store (the location where the saved profile will be stored). This is not configurable. Compressing user profile and saving a single compressed instance across a network has the benefits of reduced network bandwidth usage and reduce the chances of profile corruption.

3. Only 1 configuration per server. Let's say you have SAP Client and Microsoft Word loaded on a Citrix XenApp server and they are both published. The 1 configuration limit means if you want to just load SAP Client and load only SAP Client-related settings for a session, you must load the whole profile including profile settings for Microsoft Word

4. It is able to read Active Directory User Account Object attributes - e.g. Profile path - to use as the location for the user store. Or you can save the user store in user's HOMEDRIVE environment variable. The default settings in CUPM is to save the User Store in user's Windows folder on the HOMEDRIVE. User Environment Variables are not possible because CUPM runs before Windows' Loading User Profile action is processed

5. Configurations can be done through the AD Group Policy Object, or the local INI file, or the combination of both. GPO settings have the priority

6. To use this effectively, the server should be configured to use Local Profile only. This can be set in the Policy Editor or the Group Policy Object in AD

7. CUPM has the option to delete the cached local profiles when users log off. This will be useful in a Terminal Services environment

8. This can be used anywhere, not only for servers running Citrix XenApp

These are just some of my initial thoughts.