Weird problem while installing PhotoShop Elements 3.0
Background
========
The customer I workfor at the moment wanted me to make a package for Adobe Photoshop Elements 3.
This package also installs DirectX and Windows Media Format 9 Series Runtime.
They wanted all kinds of settings and wanted to assign the application to a user with Active Directory.
This way the application shows the shortcut in the startmenu and installs the first time the user clicks it.
Since I could not get it to work with the original MSI from Adobe I repackaged it.
Some more info
===========
The package contains a lot of files in C:\Windows Driver Cache\i386.
Also a lot of files in C:\Windows\System32 and C:\Windows\System32\Drivers
I have also a directory RegisteredPackages with a lot of (double) files in it in two directories.
There are files that have to go in the All Users profile (Application Data) and that has to go in the userprofile (Application Data and Local Settings\Application Data)
The only Registry keys I have my doubts about are : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents and what's in it.
Problem
======
When the user logs in, the application is installed instantly without the user ever clicking the shortcut.
When the user logs out and another user with rights to the application logs in, the same happens and the application is installed completely again.
When a 3th user logs in which doesn't have this application assigned nothing happens.
When user 1 or 1 log in again nothing happens too and the application starts and works as it should..
I didn't use the StubPath trick that does this (described elsewhere on this forum).
Does anybody know what may trigger this?
It's quite annoying because when the user wants to log in somewhere else to check something he gets the whole installation again.
I think I left too much in the package but with the ActiveX and the Windows Media Format 9 stuff and the fact that I captured an MSI installation I'm reluctant to remove a lot of this stuff.
I hope someone can help me on my way here.
Marcel
========
The customer I workfor at the moment wanted me to make a package for Adobe Photoshop Elements 3.
This package also installs DirectX and Windows Media Format 9 Series Runtime.
They wanted all kinds of settings and wanted to assign the application to a user with Active Directory.
This way the application shows the shortcut in the startmenu and installs the first time the user clicks it.
Since I could not get it to work with the original MSI from Adobe I repackaged it.
Some more info
===========
The package contains a lot of files in C:\Windows Driver Cache\i386.
Also a lot of files in C:\Windows\System32 and C:\Windows\System32\Drivers
I have also a directory RegisteredPackages with a lot of (double) files in it in two directories.
There are files that have to go in the All Users profile (Application Data) and that has to go in the userprofile (Application Data and Local Settings\Application Data)
The only Registry keys I have my doubts about are : HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\ExceptionComponents and what's in it.
Problem
======
When the user logs in, the application is installed instantly without the user ever clicking the shortcut.
When the user logs out and another user with rights to the application logs in, the same happens and the application is installed completely again.
When a 3th user logs in which doesn't have this application assigned nothing happens.
When user 1 or 1 log in again nothing happens too and the application starts and works as it should..
I didn't use the StubPath trick that does this (described elsewhere on this forum).
Does anybody know what may trigger this?
It's quite annoying because when the user wants to log in somewhere else to check something he gets the whole installation again.
I think I left too much in the package but with the ActiveX and the Windows Media Format 9 stuff and the fact that I captured an MSI installation I'm reluctant to remove a lot of this stuff.
I hope someone can help me on my way here.
Marcel
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
Priapus
18 years ago
Hej Marcel,
As far as I understand the package is assigned to the user. I could imagine when the user logs on to the machine(domain), user name is validated in AD and Group policy is triggered and software is installed
Publishing the software package instead of assigning should solve this problem;
Check this article,
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/a4a077c7-d976-48b1-a3ba-d88d21ebffad.mspx
Cheers
Priapus
As far as I understand the package is assigned to the user. I could imagine when the user logs on to the machine(domain), user name is validated in AD and Group policy is triggered and software is installed
Publishing the software package instead of assigning should solve this problem;
Check this article,
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/a4a077c7-d976-48b1-a3ba-d88d21ebffad.mspx
Cheers
Priapus
Posted by:
ZhuBaJie
18 years ago
ORIGINAL: Priapus
As far as I understand the package is assigned to the user. I could imagine when the user logs on to the machine(domain), user name is validated in AD and Group policy is triggered and software is installed
Publishing the software package instead of assigning should solve this problem;
Check this article,
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/TechRef/a4a077c7-d976-48b1-a3ba-d88d21ebffad.mspx
Hi priapus,
Thanks for your reply.
I checked the article. It says: "User-assigned applications are advertised on the desktop; they appear to be installed on the user’s desktop, but they get installed the first time that the user starts the application, typically from the Start menu.".
It should not automatically install if it is deployed per user. In my case it does install automatically.
I think I have to look at the entry points and components like ActiveX should IMHO be installed per system.
Maybe someone has experience with this program and can give me some further hints.
Kind regards,
Marcel
Posted by:
ZhuBaJie
18 years ago
As is often the case; the solution is dead simple.
I had overlooked the Adobe Gamma Loader in the Startup folder. [:(]
No wonder it installed directly after logging in.
Marcel
I had overlooked the Adobe Gamma Loader in the Startup folder. [:(]
No wonder it installed directly after logging in.
Marcel
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.