MSI-based software deployment Error 1327: Invalid drive

[Frederic Pinsonnault]

Environment:

Windows XP Pro workstations in a NT 4.0 domain.
SMS 2.0
Default user profile on the workstation was customized.
The HKCU\Software\...\Explorer\user shell folders values
were changed so that My Documents would point to the path
V:\My Documents for any users that logs in.

The problem is that the SMS software distribution service
uses a local computer account to carry out the software
installation. Because of that, the settings from the
default profile were carried over the SMS Software
Distribution account profile. However, that account is not
really logged on so there is no V: drive mapped for this
account.

Each time Windows Installer tries to install an MSI, it
tries to resolve the pre-defined property
called "PersonalFolder" by querying the HKCU\...\User
shell folders key. Since it points to V:\My Documents,
Windows Installer aborts the installation with the error
msg 1327: Invalid drive V:\.

If I set the default user profile back to default. The
error does not occur.

HERE IS WHERE IT BECOMES INTERESTING!

This error only occured with MSI files that were not
installing MS Office products like Office, Project,
Frontpage or Visio. MSI files that I created using Windows
Installer Editor from WISE or MSI files given by software
manufacturers all suffered from this behavior.

ANY IDEA WHY?

[Richard Threlkeld]

Windows Installer based applications need a valid My Documents folder as you
have outlined below because of the self healing paths that they define in
the registry. I've seen this as well which is why I point the My Documents
path back to the default too before distributing the apps. If you are using
WISE, you can create a custom action and just drag and drop as a quick fix.
This is a known issue by Microsoft although I don't have the article handy.
You can also search on MSI error 1324.

Also, the My Documents folder should also be writeable for it to work
correctly.

--
Richard Threlkeld
rich...@qualcomm.com

"Frederic Pinsonnault" <fred_pin...@hotmail.com> wrote in message
news:077701c309e9$a160a000$3001...@phx.gbl...

[Frederic Pinsonnault]

Thanks for your answer BUT...

That does not answer why MSI installation of MS Products
like Visio, Project and Frontpage do notget the error.

Frederic Pinsonnault
NexInnovations

>.
>

[Richard Threlkeld]

Ok, I think I missed that in your original post.

No idea on why they only apply to those products, I think it's how it's
enumerating certain folders that interact with the installation product when
the MST is created but it's hard to know for sure unless talking to an
Office developer. This issue also occurs with NAV installations as well,
which makes me think it's a property that they are checking for during
installation.

--
Richard Threlkeld
rich...@qualcomm.com

"Frederic Pinsonnault" <fred_pin...@hotmail.com> wrote in message

news:01b801c30a4e$219d4e30$3001...@phx.gbl...