Installscript MSI engine DCOM Settings Issue
Hi All,
I am working on a application called as IXOS Clients 6.0.2.This application has pre-requsite of ISSCrip.msi version 7.4.0.377. when i try to install the application via sccm the application installs fine with admin user id but the same installation fails with standard user id eventhough we run the advertisement with admin rights. After a long troubleshooting we came to know that it is not issue with the package but it is the issue with isscript 7.4.0.377 the dcom settings for install shield driver is by default points to interactive user but it should be launching user. I got a script from this site where it changes the dcom settings install shield driver for isscript 7.4.0.377 from interactive user to launching users. Also as per the one the person who psoted it adviced to use this script after costintialize. But when i tried the same application failed to install.
Request your kind help for the same.
Thank You.
Yuvi
I am working on a application called as IXOS Clients 6.0.2.This application has pre-requsite of ISSCrip.msi version 7.4.0.377. when i try to install the application via sccm the application installs fine with admin user id but the same installation fails with standard user id eventhough we run the advertisement with admin rights. After a long troubleshooting we came to know that it is not issue with the package but it is the issue with isscript 7.4.0.377 the dcom settings for install shield driver is by default points to interactive user but it should be launching user. I got a script from this site where it changes the dcom settings install shield driver for isscript 7.4.0.377 from interactive user to launching users. Also as per the one the person who psoted it adviced to use this script after costintialize. But when i tried the same application failed to install.
Request your kind help for the same.
Thank You.
Yuvi
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Why bother with a script?
The correct/easiest route is to create a transform for the ISScript MSI then create a package for that, upon which your actual package depends. You can use a Task Sequence if you like. That way, the IS MSI is available for any other package which requires it. You should do the same for all the various IS engines/drivers. To make your life even easier, they should be part of your build.
The correct/easiest route is to create a transform for the ISScript MSI then create a package for that, upon which your actual package depends. You can use a Task Sequence if you like. That way, the IS MSI is available for any other package which requires it. You should do the same for all the various IS engines/drivers. To make your life even easier, they should be part of your build.
Posted by:
cygan
13 years ago
this issue with dcom has been well documented
have a look at this link
read the options that you have
have a look at this link
read the options that you have
Posted by:
rak171089
13 years ago
Hi
I am very new to packaging but have faced this issue.Try editing the pack with Wise Studio and check the launch conditions tab. If it can be run only as admin there may be a condition AdUsr. Try deleting that conditon and relaunch the application in restricted user.
Tc
I am very new to packaging but have faced this issue.Try editing the pack with Wise Studio and check the launch conditions tab. If it can be run only as admin there may be a condition AdUsr. Try deleting that conditon and relaunch the application in restricted user.
Tc
Posted by:
anonymous_9363
13 years ago
Rakesh, th eproblem has nothing to with administrative privileges versus ordinary user privileges, but the identity used to launch COM applications. Read the article that Cygan linked.
Also note that your advice to edit the package is contrary to best practice if the package is a vendor-supplied MSI. These should always be customised using a transform, applied at installation time.
Also note that your advice to edit the package is contrary to best practice if the package is a vendor-supplied MSI. These should always be customised using a transform, applied at installation time.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
