Hi guys.
So i have a client that needs teh following...
adverts for the app-v to be deployed to the user for optional install.
Using KMS server all defualts.
UserA has a PROJECT STANDARD license only.

Now they need it so when UserA logs into the machine he can run his project and only use the PROJECT STANDARD license.
When hes gone UserB logs into the machine and can run up his PROJECT PROFESSIONAL license.
and so on back and forth for these users logging in and out.

so how do i make this work considering that for project standard....
- msiexec /i offvirt.msi PROJECTSTD=1 USEROPERATIONS=1
- then install the sequenced project standard app-v product

and for project pro i have....
- msiexec /i offvirt.msi PROJECTPRO=1 USEROPERATIONS=1
- then install the sequenced project pro app-v product

Now ....because they want it to be user based adverts only...can the above be done so that when UserA logs in and runs his project he only gets the Project STD version, and then we he logs out and UserB logs in he gets his Project Pro version? ( all on the same machine this is )

Im really confused about how this can work :(
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.



Jut append the properties to a single command-line and then base the advertisements to the user. This works for Project, but not Visio
Visio will always choose the highest licensing model due to the fact that they have a single media-set, whereas Project has two different media sets and the specific media set will only adopt the licensing it was inteded for
Answered 07/20/2011 by: nucko
Senior Purple Belt

Please log in to comment
Thanks Nucko.
That sort of helped....only one advert for the officevirt.msi needed ( still dont know how to link these to the users single advert for ProjectSTD or ProjectPRO)

The next issue im having is as follows...
Both seperate installs on clean machines each time of ProjectSTD App-v and ProjectPRO App-v work fine ( no issue here [:D] )
So from a fresh machine...
When UserA logs in and runs his advert to install his ProjectSTD App-V, it installs sweet and works well.
If UserB then logs in later and runs his advert to install ProjectPRO App-V, it says it installs sweet...but there are no shortcuts for him!

And the issue is replicated if UserB logs in first and installs, and then UserA logs in 2nd ( UserA's shortcuts will not be there!!!! ).
ARGHHHH! help!
Answered 07/26/2011 by: dbowe
Orange Belt

Please log in to comment
Ok so i solved that issue.
Selecting the sequencer File Type to "User Data" seemed to make the shortcuts stick in the users profiles.

I have another problem now where Project Standard seems to be the stuck on the machine.
After installing Project Std by UserA, the app reports via help/about that it is indeed Std for UserA
Then when i log in as UserB and install Project Pro it reports its Pro for that user.
But it dosnt stick for UserB, as when he logs out and logs back in it is now Project Std.

Anybody know what i need to do to make the Project Pro stick for the user its advertised to?
Answered 07/26/2011 by: dbowe
Orange Belt

Please log in to comment
Ok so i solved this one to! just wanted to share what fixed it for me...

In the Files tab on the right is some options to do with application data/user data and override.
These are self explanitory options..i just mashed about with the options for what i thought were user-specific (ie the project.lnk file etc - will post a bit more info when im near my docos ).

The other thing i did was to make sure the proxy information was correct and to deploy the officedeployment kit twice...
- once with the "PROJECTPRO=1 PROJECTSTD=1"
- and then installed the office deployment kit with the proxy settings
Answered 07/28/2011 by: dbowe
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity