/bundles/itninjaweb/img/Breadcrumb_cap_w.png
Does anyone know how to do this?

Thanks
0 Comments   [ - ] Hide Comments

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.
Answer this question or Comment on this question for clarity

Answers

0
This is done by simply going into the GPO, right-clicking the application, and choosing the option to "Redeploy application".
Answered 02/06/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
Thanks for the info, and if it comes down to it, we may end up doing that. However, we were really looking for a way to just repush it to one machine. Sorry for not being more specific.

Thanks
Answered 02/06/2006 by: BlueFlameKeg
Senior Yellow Belt

Please log in to comment
0
Unfortunately you can't redeploy it to only one computer via Active Directory.

The only method I can offer is to remotely start the process on this one computer and run the neccessary command-line to reinstall the application.

eg: msiexec /i "application.msi" REINSTALL=ALL REINSTALLMODE=vomus etc etc
Answered 02/06/2006 by: brenthunter2005
Fifth Degree Brown Belt

Please log in to comment
0
I've encountered this issue before...

I think that we removed a registry key that marked what software had been installed by GPO and that forced a reinstall, as if the machine didn't know it had it installed.

I'll have to poke around the registry a bit.

Anyone else know about this?
Answered 02/06/2006 by: CedricMordrin
Senior Yellow Belt

Please log in to comment
0
Found it...
We have a batch file template that we used when we experimented with GPO pushes.

It first calls msizap.exe to remove the specified product code
then it deletes the appropriate key under HKLM\Software\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt\
then runs gpudate and forces a reboot

when the machine reboots it will pull the software down via GPO.


Hope this helps...
Answered 02/06/2006 by: CedricMordrin
Senior Yellow Belt

Please log in to comment
0
Hey that worked. Thanks!
Answered 02/06/2006 by: BlueFlameKeg
Senior Yellow Belt

Please log in to comment
0
You can just put a Deny on the policy for that computer; reboot; remove the Deny
Answered 02/08/2006 by: YatesAG
Senior Yellow Belt

Please log in to comment