Systems Management

Having been burnt twice with different packages at a previous client, I now never use GP's 'Upgrade' facility. Move your users out of the old group into the new one. That, of course, presumes that you set your GPOs to uninstall apps when the object falls out of scope. If not, you should probably edit the new version's MSI/MST to uninstall the old app.

If the latter is what you're describing, then you should take a verbose log of the new install to determine what's happening.

yeah dude will second vbscab - we're constantly distributing msi's and never "upgrade" and I also successfully deployed versions of paint.net uninstalling/installing later versions since about the very version you're starting from in our company. paint.net isn't a massive install and doesn't take very long for it to remove itself and then re-install again.

vbscab

what do you mean by
Move your users out of the old group into the new one. That, of course, presumes that you set your GPOs to uninstall apps when the object falls out of scope. If not, you should probably edit the new version's MSI/MST to uninstall the old app.


and in the msi i set in the upgrade table the upgrade code the same as the old version
do you have some screen shot of the step i need to do ?

Thanks

In every environment I've worked in which used GP for deployment, GPOs were set to uninstall the linked applications if the object (generally an AD group) was out of scope. That means, if machines or users are removed from the group associated with the GPO, the application gets uninstalled on start-up or log-in. Similarly, when machines or users are added to the group, the app gets installed. For example, lets say I have FooBar v1.00 and I have MachineA and MachineB in a group SW-FooBar_1.00 which is associated with a GPO. When those machines start up, FooBar v1.00 gets installed.

Now I have to upgrade FoorBar to v2.10, but only on MachineA for now. So I create a new GP and associate a new group, SW-FooBar_2.10 with it. When we're ready, I move MachineA from SW-FooBar_1.00 to SW-FooBar_2.10. Next time MachineA starts up, FooBar v1.00 gets uninstalled and FooBar v2.10 gets installed.

No need to futz with the Upgrade table...

woah this is deja vu territory vbscab [;)]

- the other alternative kerm007 is to right mouse on the package in the GPO to remove the package, and select uninstall the software immediately, which isn't that immediate but next re-boot following policy processing having caught up with the workstations software will uninstall. You can then add the new package to the same GPO just make sure your old MSI package hangs around in your deployment share so it's available until all the required machines have the old veriosn removed.

search for mine and vbscabs posts in the forums we've had discussions about this before [8D]

hi

i already try that in lab and my test pc didnt have the old version remove even after reboot.

what we do is we have a big gpo for all free software like filezilla,notepod++ etc and the other softwares not free we create a special gpo for it.


as for this :
Now I have to upgrade FoorBar to v2.10, but only on MachineA for now. So I create a new GP and associate a new group, SW-FooBar_2.10 with it. When we're ready, I move MachineA from SW-FooBar_1.00 to SW-FooBar_2.10. Next time MachineA starts up, FooBar v1.00 gets uninstalled and FooBar v2.10 gets installed.

you deploy your software via computer base but here the system admin what to use the per user i'm right ?

Great...another client who thinks his software licenses allow per-user installs... Do be sure to ask your Finance Director if he's aware of exactly how much a visit from FAST will cost his company, won't you? At my last client, the savings gleaned from cleaning up "illegal" installations paid for a complete desktop hardware refresh...and I'm not talking about tens of machines but thousands. One example: Microsoft Project. Number of licenses? 30. Number of installed instances? 270. Oops...

Also, you need to check the licenses for the "free" software. Most will explicitly prohibit commercial use. Sorry.

As for how to proceed, you just need to substitute the machine names with user IDs. When you say you have special GPOs for paid-for software, I presume you mean you have each package in its own GPO? That's good, because you can limit the scope to an AD group.

@squeakstar: I'd forgotten about the right-click context menu for removing a package. Of course, that course of action is probably only valid once all the "old" users have been migrated.

as for the paid softwares let say adobe if i have 10 licenses im allowing only the 10 peoples we have license for to install it.


on the exemple you deploy the software computer base ?

thanks

on the exemple you deploy the software computer base ?I'm sorry, I don't understand your question.

what i mean is on the exemple to use the assign method instead of publish and you assign it per computer or user ?

thanks

ORIGINAL: VBScab

@squeakstar: I'd forgotten about the right-click context menu for removing a package. Of course, that course of action is probably only valid once all the "old" users have been migrated.



Oh yeah doing it the right way by computer is so engrained the fact he was doing per user slipped me by.

Kerm - the fact people can install the software means the people can install the software anywhere they sit which also equates to the fact you could end up with more copies of software around the office than you have licences for - are your users going to be thoughtful enough to remove their installed software when they leave their desk??? Probably not!

Do your users even swap desks, because for 99% of the time i'm thinking GPOs by computer are the most logical way to go for installing software, so get migrating.

Paint.net defo works in GPOs by machine, if you either remove the old copy when machines fall out of scope or by using the remove software option then re-deploy new version! You may even find upgrading works but thats a bad habit so leave it out!

I've never used publishing, always assignation. A previous client used per-user installs (hence their licensing nightmare because they DO have hot-desking users) but I would always recommend per-machine.

they don't sit at any place they want all of them have there own pc ....

...there ya go then get your GPOs tidied and cross-over to distrubuting by machines !!!!

Thanks

one more question

how can i check why the update was not working ?

Thanks

windows error logs.. erm symptoms.. no idea - move forward! [;)]

Google "group policy msi logging". Or you could do worse than start your search on AppDeploy. Maybe start at the 'Group Policy' forum!