Systems Management

why you said violates the VMWare WS license. we install vmware only on people we have license for

im playing we upgrdae code because with notepad++ i was needed to have the same upgrade code but not the same product code to be able to upgrade version and work at application launch

Thanks

we install vmware only on people we have license forYou should be installing per-machine. What happens if your licensed user logs in on another machine? GP will install VMWare on that machine. You now have two installations and only one license. Oh wait...hang on...that never happens, does it?

As for futzing ProductCode and UpgradeCode...because you kludged one product in this way, it suddenly becomes Best Practise?

im installing per user not per machine .......

and by the way i don't need some one who just give his opinion on everything like violate this and that ... if you can't help me then just don't respond

that was the second time you respond with this kind of answer ....

im controlling my license very tight so i just need advices if it fesable or not ...

I tried to help you with post #4.

Now, re-reading your question, you seem to be under the impression that changing the upgrade and/or product code will change GP behaviour to upgrade an application at launch-time. Why would you think that? As I mentioned, GP installs at workstation start-up (if it's a per-machine install) or when a user logs in (if it's a per-user install). That's it. If you want to trigger an upgrade at application launch, you need to change the app's shortcut to launch a script which checks if 7.01 is installed and, if not, execute the upgrade command line.

There...now that's twice I've said pretty much the same thing. Feel free to ignore me if you want but it won't change the answer.

One thing I haven't mentioned is that if you're trying to use the upgrade functionality of GP, i.e. using the 'Upgrade' tab - don't. Over the years, I've learned that whilst it sometimes works, it's generally more trouble than it's worth. Either use GP's "out of scope" method to uninstall the previous version or just add a new GP for 7.01 and let it upgrade 7.00.

i did what you mention at last and when i run the 7.01 it ask to remove the 7.0 before

all soft i create for now work well as per user the people go to the add new software section and chose what they want let say filezilla and it was installed...

thanks

by the way you are wrong cause i chose the option publish

1. Methods of deployment
Group Policy supports two methods of deploying a MSI package:

•Assign software - A program can be assigned per-user or per-machine. If its assigned per-user, it will be installed when the user logs on. However, if its assigned per-machine then the program will be installed for all users when the machine starts.
•Publish software - A program can be published for one or more users. This program will be added to the Add or Remove Programs list and the user will be able to install it from there

Is it feasible? Unlikely, since (hopefully) your users do not have the required privileges to install applications.

well they are admin on there machine

it work but at user log on i want to do the same but at application lauch

Thanks

You can't use GPO to install at application launch, as the trigger events (i.e. workstation start-up or user log-in) have already fired at that stage.

I suppose you *could* alter the shortcut target to be a script (which checks for the latest version, etc.) but then you'd have to engineer a new self-healing/repair entry-point, etc.

Also, VMWare WS is already in MSI format so why would you need to mess with ProductCode and UpgradeCode?

Lastly, you say that user log-in is triggering the install? That means you're installing per-user which a) must be interesting and b) probably violates the VMWare WS license.