Per-user managed installations vs unmanaged installations
Kroese, Ramon
When I clear and set the sourcelist of a installed msi product
(assingmenttype=0) which was installed per-user (Allusers=2) the source list
isn't updated in the Per-user unmanaged context
(HKCU\Software\Microsoft\Installer\Products\<Compressed
ProductCode>\SourceList\NET). Instead the SID of the user added under the
registry key
'HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Managed\' and the
new sourcelist is added in the per-user managed context
(HKLM\Software\Microsoft\Windows\CurrentVersion\Installer\Managed\<User
SID>\Installer\Products\<Compressed ProductCode>\SourceList\).
I have searched the internet and the 'Microsoft Platform SDK for Windows
Server 2003 SP1' for more information about per-user managed installations
but it is scarce.... What is the consequense of this? Will windows installer
use the per-user managed sourcelist or the per-user unmanaged sourcelist?
Another problem I have is that I can't change the PackageName of the
installed product to reflect the new situation/source. The only way is to
directly write to the registry key PackageName. Will this cause any
problems???? In the past we have changed the sourcelist and/or
LastUsedSource registry key directly without any problems. Users, which
travel with a laptop for instance, would get the installation sources from a
local server in stead of the server at the other end of the country (and
maybe behind a slow link). I have tried to change the PackageName with the
API function MsiSourceListSetInfo and with the SourceListInfo property of
the Windows.Installer.Product object. Both ways did not change the
packagename.
Who can provide me with some more information????
With kind regards,
Ramon Kroese