Active setup and repair problem
Hello,
I have a strange issue so I would like to ask some help.
The situation is the following:
I use active setup in my MSI package to deploy custom office template files, like C:\Documents and Settings\<username>\Application Data\Microsoft\Templates\Normal.dotm and C:\Documents and Settings\<username>\Application Data\Microsoft\Excel\XLSTART\book.xltm
I have installed the package on a clean XP build. It works fine, every user has these files after logged in.
The problem:
I have installed this MSI on a test machine with corporate image, the Active setup seems worked, but the files not in the user profile. I have modified the active setup command to create log file. In the log file, it seems the active setup try to deploy these files to the account's profile who is installed the MSI. The normal repair did the same...
So the problem on corporate image:
- install msi as administrator
- log in as user
- active setup try to install these files to the administrator profile however a normal user is logged in..
- command line or ARP repair also do the same...
I do not know what is wrong on my corporate image, the MSI with active setup is fine...
Thanks in advance,
Zoltan
I have a strange issue so I would like to ask some help.
The situation is the following:
I use active setup in my MSI package to deploy custom office template files, like C:\Documents and Settings\<username>\Application Data\Microsoft\Templates\Normal.dotm and C:\Documents and Settings\<username>\Application Data\Microsoft\Excel\XLSTART\book.xltm
I have installed the package on a clean XP build. It works fine, every user has these files after logged in.
The problem:
I have installed this MSI on a test machine with corporate image, the Active setup seems worked, but the files not in the user profile. I have modified the active setup command to create log file. In the log file, it seems the active setup try to deploy these files to the account's profile who is installed the MSI. The normal repair did the same...
So the problem on corporate image:
- install msi as administrator
- log in as user
- active setup try to install these files to the administrator profile however a normal user is logged in..
- command line or ARP repair also do the same...
I do not know what is wrong on my corporate image, the MSI with active setup is fine...
Thanks in advance,
Zoltan
0 Comments
[ + ] Show comments
Answers (13)
Please log in to answer
Posted by:
navnathz
13 years ago
First log in as user(e.g. userA) on your corporate image bafore installing application.
Then come back to admin and install your application.
Login in as user(e.g. user A)
I hope it will solve your issue.
BYE
Navnath
Then come back to admin and install your application.
Login in as user(e.g. user A)
I hope it will solve your issue.
BYE
Navnath
Posted by:
weicznerz
13 years ago
Hi Navnath,
thanks for your quick reply. Unfortunately, I have tried this before, but didn't help.
Thanks,
Zoltan
thanks for your quick reply. Unfortunately, I have tried this before, but didn't help.
Thanks,
Zoltan
Posted by:
anonymous_9363
13 years ago
Navnath, that's not really a practical solution, is it? This is a corporate deployment.
Zoltan, show us what your MSI is using to set up the AS part.
Zoltan, show us what your MSI is using to set up the AS part.
Posted by:
weicznerz
13 years ago
Hello VBScab,
my Active Setup command is the following:
msiexec.exe /fauvs [ProductCode] /qn
I usally use /fomus. At this MSI I have tried a lot of combination.
my Active Setup command is the following:
msiexec.exe /fauvs [ProductCode] /qn
I usally use /fomus. At this MSI I have tried a lot of combination.
Posted by:
anonymous_9363
13 years ago
Check out the switches for repair on MSDN.
Most people would probably use just '/fup' for an AS "repair".
Most people would probably use just '/fup' for an AS "repair".
Posted by:
weicznerz
13 years ago
Thanks. Yes, I have tried it before. I think there is no problem with AS, because on clean XP build work perfect. One of my friend has tried at his company, worked too...
I have used AS at other MSI packages, they had worked fine.
I have used AS at other MSI packages, they had worked fine.
Posted by:
weicznerz
13 years ago
I have upload my active setup log file to here
I hope you can download by the blue "download now" button. Anyway, there is in log:
... Property(S): USERPROFILE = C:\Documents and Settings\a\"
...Property(S): LogonUser = a
So the Active Setup run under the account "a".
But the file copy wants to copy file to admin profile: [:(] I do not know why
...MSI (s) (30:8C) [13:10:31:984]: File: C:\Documents and Settings\Administrator\Application Data\Microsoft\Templates\Normal.dotm; Won't Overwrite; Won't patch; Existing file is unversioned and unmodified - hash matches source file
I hope you can download by the blue "download now" button. Anyway, there is in log:
... Property(S): USERPROFILE = C:\Documents and Settings\a\"
...Property(S): LogonUser = a
So the Active Setup run under the account "a".
But the file copy wants to copy file to admin profile: [:(] I do not know why
...MSI (s) (30:8C) [13:10:31:984]: File: C:\Documents and Settings\Administrator\Application Data\Microsoft\Templates\Normal.dotm; Won't Overwrite; Won't patch; Existing file is unversioned and unmodified - hash matches source file
Posted by:
mekaywe
13 years ago
What are the values of below properties inside msi/mst ? are they hardcoded ?
1. TEMPLATES
2. EXCEL
3. XLSTART
4. USERPROFILE
1. TEMPLATES
2. EXCEL
3. XLSTART
4. USERPROFILE
Posted by:
weicznerz
13 years ago
From the Directory table:
"Directory" "Directory Parent" "DefaultDir"
TEMPLATE MICROSOFT TEMPLA~1|Templates
XLSTART EXCEL XLSTART
EXCEL MICROSOFT Excel
USERPROFILE TARGETDIR .:USERPR~1|UserProfile
There is no hardcoded in msi.
Thanks!
"Directory" "Directory Parent" "DefaultDir"
TEMPLATE MICROSOFT TEMPLA~1|Templates
XLSTART EXCEL XLSTART
EXCEL MICROSOFT Excel
USERPROFILE TARGETDIR .:USERPR~1|UserProfile
There is no hardcoded in msi.
Thanks!
Posted by:
pjgeutjens
13 years ago
Zoltan,
a few questions:
- what is the value of the ALLUSERS property in your package?
- what are you using as the key path for the component containing the user files? Also in what feature did you put the component and what's its relation to other features?
- what is the target directory for said component?
Rgds,
PJ
a few questions:
- what is the value of the ALLUSERS property in your package?
- what are you using as the key path for the component containing the user files? Also in what feature did you put the component and what's its relation to other features?
- what is the target directory for said component?
Rgds,
PJ
Posted by:
weicznerz
13 years ago
Hello PJ,
Here are my answers:
ALLUSERS=1
I have only one feature. The user files are separated two components, both of them have file keypath. The component of book.xltm has the destination [AppDataFolder]Microsoft\Excel\XLSTART, the other has [AppDataFolder]Microsoft\Templates.
Thanks,
Zoltan
Here are my answers:
ALLUSERS=1
I have only one feature. The user files are separated two components, both of them have file keypath. The component of book.xltm has the destination [AppDataFolder]Microsoft\Excel\XLSTART, the other has [AppDataFolder]Microsoft\Templates.
Thanks,
Zoltan
Posted by:
pjgeutjens
13 years ago
Zoltan,
try giving the components a registry keypath in HKEY_CURRENT_USER, something along the lines of HKCU\Software\MySoft\UserFilesInstalled = 1
Another thing that comes to mind is this: do the users have access to the original install location from which you ran the MSI? since you're propagating files, the cached version in <WinDir>\installer won't suffice (it gets stripped of the files it contains), users will need to access the original msi.
Rgds,
PJ
try giving the components a registry keypath in HKEY_CURRENT_USER, something along the lines of HKCU\Software\MySoft\UserFilesInstalled = 1
Another thing that comes to mind is this: do the users have access to the original install location from which you ran the MSI? since you're propagating files, the cached version in <WinDir>\installer won't suffice (it gets stripped of the files it contains), users will need to access the original msi.
Rgds,
PJ
Posted by:
weicznerz
13 years ago
PJ,
I have changed the kepaths for both components from file to HKCU registry entries. It works now on corporate image too! [:D] Thanks a lot!
I have changed the kepaths for both components from file to HKCU registry entries. It works now on corporate image too! [:D] Thanks a lot!
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.