/build/static/layout/Breadcrumb_cap_w.png

Change per-machine to per-user

Hi,

I need to deploy Adobe Photoshop Elements 8 with a GPO to some of our users. As i'm not that experienced with repackaging and deploying software i hope to find some help over here.

Elements 8 comes with a setup.exe, which executes msiexec /i "Adobe Photoshop Elements 8.0.msi" TRANSFORMS=1043.mst SERIALNUMBER=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx NOT_STANDALONE=1. I made a new mst file including the two properties and created a new per-machine gpo including the msi and two mst files. When i tested the deployment the application is installed and everything works as intended.

After a few days a user told she wanted to use the applications in other offices too, so i changed the per-machine gpo into a per-user gpo. I tested the per-user deployment and noticed that the installation starts, but crashed after about 30 second. The logfile in c:\windows\temp states that admin rights are required to install the application.

How can i change the installation from per-machine to per-user?

0 Comments   [ + ] Show comments

Answers (17)

Posted by: anonymous_9363 14 years ago
Red Belt
0
Is there a check for 'IsAdmin' or 'Privileged' in the MSI?
Posted by: TalkingMarble 14 years ago
Orange Belt
0
When i open the msi together with the mst in orca and perform a search, both items are not found.
Posted by: MSIPackager 14 years ago
3rd Degree Black Belt
0
Check the launchconditions table.

Failing that, have you got the appropriate group policies in place to allow end user to install managed software with elevated rights?

http://msdn.microsoft.com/en-us/library/aa367561(VS.85).aspx
Posted by: TalkingMarble 14 years ago
Orange Belt
0
Elevated privileges have been enabled in computer and user settings in the gpo.

The launchcondition table has three entries:
-AdminUser
-NOT_STANDALONE=1
-VersionNT>=501 OR VersionNT64>=501
Posted by: AngelD 14 years ago
Red Belt
0
Remove the AdminUser LaunchCondition entry
Posted by: anonymous_9363 14 years ago
Red Belt
0
Remove the AdminUser LaunchCondition entry ...in your transform, of course.
Posted by: TalkingMarble 14 years ago
Orange Belt
0
I removed the AdminUser launchcondition in the 1043.mst file and now the application installs when the user logs on.

Because i only want the application to install when the user actually uses it, i also tested the deployment without the option "Install at logon" in the gpo. An event in the eventviewer stated the package installed, but in the "all programs" menu there is no icon available to install/start the application. How can i solve this?
Posted by: AngelD 14 years ago
Red Belt
0
Did you advertise or publish it?
Posted by: TalkingMarble 14 years ago
Orange Belt
0
I assigned it.
Posted by: AngelD 14 years ago
Red Belt
0
oops, yeah that's what I meant :)

Are any of the shortcuts advertised?
Posted by: TalkingMarble 14 years ago
Orange Belt
0
No shortcuts are advertised.
Posted by: AngelD 14 years ago
Red Belt
0
Then set one of the shortcuts as advertised, launch the shortcut after the user has logged in and watch for the magic to happen.
Posted by: MSIPackager 14 years ago
3rd Degree Black Belt
0
To be honest, if you need help with finding launch condittions you are really going to struggle to get thia vendor app advertising!

Better to publish the app so that users can install it via ARP when they want it.
Posted by: TalkingMarble 14 years ago
Orange Belt
0
I thought about publishing the app too, but users are not allowed to access ARP.

How do i set one of the shortcuts to advertise? I opened the msi with orca but i don't now which option(s) exactly to adjust.
Posted by: AngelD 14 years ago
Red Belt
0
Make sure the file (the shortcut should launch) is set as keypath for the component holding the file.
In the Shortcut table; find the shortcut entry, change the Target column field value to the feature holding the component specified in the Component_ column field.
The shortcut should now be installed as advertised.
Posted by: TalkingMarble 14 years ago
Orange Belt
0
I opened the msi and mst file with orca and made the adjustments as suggested by AngelD, but still no shortcut is advertised.

I did the following:
-i looked in the file table for the filename the shortcut should launch (photoshop elements 8.0.exe) and copied the values from the file and component columns
-in the component table i searched for the component value from photoshop elements 8.0.exe and put the value the file column from photoshop elements 8.0.exe in the keypath column.
-went to the shortcut table and copied the value from the component column from the shortcut which should be advertised
-in the featurecomponent table i found the component from the shortcut and copied the value from the feature column (photoshop_elements)
-back in the shortcut table i change the value from the target column for the shortcut to be advertised to photoshop_elements
-generate a new mst file and edited the gpo in order to use the new mst
-tested the deployment

I checked everything twice, but fail to see what i did wrong.
Posted by: MSIPackager 14 years ago
3rd Degree Black Belt
0
Honestly, getting this vendor MSI to advertise is going to be difficult. Adobe products are notoriously awkward. Not saying it can't be done but there are many tips and tricks to get it working. Vendors typically don't support advertising as it's too much like hard work for them in the first place.

I'd suggest you try and get the "Add New Programs" tab at least enabled from the Add or Remove Programs applet - after all, the reason it's there is to allow end users to install centrally published apps...

I'm sure this can be achieved via group policy, while still hiding "Change or Remove Programs" and "Set Program Access and Defaults" tabs.

Cheers,
Rob.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ