This is a known issue with the Windows Installer. When using group policy
software deployment, an advertise script is created on the sysvol (.aas file).
The advertise script contains a set of opcodes that describe the actions that
the Installer must perform in order to put the appropriate entrypoints on the
client machine. These entrypoints are the COM registration, file extension
activation, and shortcut entrypoints.
Because the advertise script is created on the deployment machine, the data it
contains is influenced by the state of the deployment machine. While in some
cases the Installer will use a marker in the script so that it can install to
the appropriate location on the client machine (an easy example is the shortcut
itself which uses the shell folder ID (CSIDL) to represent the starting point
for the shortcut directory), it doesn't do the same in all cases. This is true
of the working directory value which will be resolved to a full path based upon
the deployment machine.
That's why you see the behavior.
Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<
http://www.microsoft.com/windows2000/community/centers/management/msi_faq.m
spx>
Biaudet Sébastien said:
When I distribute my msi package with a GPO the shortcut in the desktop, his
working directory isn't good. It take value C:\ also when I install the
package without GPO, the working directory take the [TARGETDIR] value.
Whyyyyyyyy
Biaudet Sébastien.
