Problem with admin image
Hi all,
I had create admin image of office 2003 msi, this admin image installs fine in normal user mode, but when i create a admin image of repackged application and try to install in same normal user mode it throws error, My problem is how to make admin image install in user mode , I can't tell that .msi cannot be installed in user mode because office 2003 is installing in same user mode.
Thanks in advance
Rana
I had create admin image of office 2003 msi, this admin image installs fine in normal user mode, but when i create a admin image of repackged application and try to install in same normal user mode it throws error, My problem is how to make admin image install in user mode , I can't tell that .msi cannot be installed in user mode because office 2003 is installing in same user mode.
Thanks in advance
Rana
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
Inabus
15 years ago
As VBScab will say, use processmon as this will no doudt show an "access denied" type error, you will basically have to relax the seucurity permissions on either a registry key or directory / file I would think.
P
P
Posted by:
clyrigham
15 years ago
Raka, What is the information your log file is showing?
After you determine if the problem is a security issue, if you prefer you may run your installation using a runas administrator... ...
A lot of times I had the same problem with sercurity permissions and I perfomed a Script using AutoIT to run with Local Administrator privileges ...
After you determine if the problem is a security issue, if you prefer you may run your installation using a runas administrator... ...
A lot of times I had the same problem with sercurity permissions and I perfomed a Script using AutoIT to run with Local Administrator privileges ...
Posted by:
anonymous_9363
15 years ago
ORIGINAL: clyrigham...which is fine and dandy if the installation is being carried out "locally", but what if Raka is packaging for external clients?
After you determine if the problem is a security issue, if you prefer you may run your installation using a runas administrator... ...
@Raka, As you know HKCR is an almalgam of HKLM\Software\Classes and HKCU\Software\Classes. I suspect that your package is trying to write to HKLM\Software\Classes whereas your Office package is using HKCU\Software\Classes.
How are you installing these packages, per-machine or per-user?
Posted by:
raka1903
15 years ago
HI VBScab,
I was trying to install the package as Per machine, When i tried to install the package Per user, the registries issue cleared, now i am getting errors related to files, cannot create files under C:\windows\System32
Regards,
Rana
I was trying to install the package as Per machine, When i tried to install the package Per user, the registries issue cleared, now i am getting errors related to files, cannot create files under C:\windows\System32
Regards,
Rana
Posted by:
anonymous_9363
15 years ago
The reason for that is that the account you're using has insufficient rights to that folder.
Posted by:
clyrigham
15 years ago
I agree with you, VBScab!
Raka... just some comments:
If you are installing via AD, you need to publish or assign the package using authoritative privileges...
If you are installing via SMS, you need to ensure the System Account Context is perfoming the installation or if you really want to use the User Context you will need to use the Elevate Privileges Script.
Thanks and Regards
Raka... just some comments:
If you are installing via AD, you need to publish or assign the package using authoritative privileges...
If you are installing via SMS, you need to ensure the System Account Context is perfoming the installation or if you really want to use the User Context you will need to use the Elevate Privileges Script.
Thanks and Regards
Posted by:
raka1903
15 years ago
Error 1406: Could not write registry in CLSID, insufficient access
Regards,
Rana
Regards,
Rana
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.