Microsoft Picture Manager
I am attempting to install Microsoft Picture Manager by itself without effecting the current installation of Office 2000.
I have used the following command
msiexec /i "\\sbtlif01-test\dfs\off2003\PRO11.msi" ADDLOCAL=OISFiles /qb
This installed picture manager fine however treated it as an upgrade and therefore removed the current Office 2000 components. Has anyone installed picture manager by itself and if so how??
I obviously know that I can go down the route of doing a setup capture by itself but did not think that this would be the correct method.
I have used the following command
msiexec /i "\\sbtlif01-test\dfs\off2003\PRO11.msi" ADDLOCAL=OISFiles /qb
This installed picture manager fine however treated it as an upgrade and therefore removed the current Office 2000 components. Has anyone installed picture manager by itself and if so how??
I obviously know that I can go down the route of doing a setup capture by itself but did not think that this would be the correct method.
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
craig16229
18 years ago
Have you tried creating and applying a transform (using ORK2003) that specifies not uninstalling previous versions of Office apps?
Craig --<>.
Craig --<>.
Posted by:
MDG534621
18 years ago
Craig,
My problem with this is that I can produce a transform that does this, and it works fine when there is not an exisiting installation of Office on the PC.
If however there is an install of Office 2000 on the PC then the install does not do a straight custom install. It also does a typical install, any ideas??? Has anyone seen this before???
Thanks
My problem with this is that I can produce a transform that does this, and it works fine when there is not an exisiting installation of Office on the PC.
If however there is an install of Office 2000 on the PC then the install does not do a straight custom install. It also does a typical install, any ideas??? Has anyone seen this before???
Thanks
Posted by:
craig16229
18 years ago
Hmmm. Okay. I will see if I can reproduce this behavior. Your previous post didn't mention anything about a transform, so I assumed you were not using one.
Craig --<>.
Craig --<>.
Posted by:
MDG534621
18 years ago
Craig,
Just so that you are aware I seemed to get around this issue by modifying the following property.
NOFEATURESTATEMIGRATION="1"
This will ignore the typical setup behaviour and carry out an application installation exactly as instructed within the MST.
Thanks for you help
Marc
Just so that you are aware I seemed to get around this issue by modifying the following property.
NOFEATURESTATEMIGRATION="1"
This will ignore the typical setup behaviour and carry out an application installation exactly as instructed within the MST.
Thanks for you help
Marc
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.