How can I change MSI path within a deployed GPO?

Question

Does anyone know how to change the path to the MSI on a GPO that's currently deployed (without redeploying it)?

Currently we have 30 or so packages pushed from a server via GPO assignment but we need to move the packages onto a different server - but as most the packages are sizeable and/or were initially packaged by my predecessor in such a way that the product requires manual per-machine fine-tuning to function, I do not want to pull and push them (redeploy them).

Based on what I've googled, I tried the following: Using ADSIEdit to modify the MSIFileList Attribute path on an existing (linked software assigning) GPO, and even though the settings on the GPO show the new path I want when I do this, the GPO no longer pushes the MSI, and the AppEvent Log cites:

"The install of application <productname> from policy <gpo name> failed. The error was : The installation source for this product is not available. Verify that the source exists and that you can access it. "

However, if I redeploy the package within the GPO, it pushes fine - but this of course entails removing and reinstalling the package on all current end-user machines which is precisely what I'm trying to avoid.

I'm pretty sure I'm up a creek without any pants on, but if anyone's nailed this problem I'd love to here about it.

Answer

I have faced this requirement many times. Unfortunately the only solution is to redeploy the application.
 I don't know if any other software distribution tools have an option for this. That will be interesting to know.

Answer

Hi Guys
 
 I am now facing the same issue of trying to move the source without all the apps re-installing.
 
 Does anyone have a workaround to this ?
 
 Cheers
     Shaun

Answer

It's been suggested in the past to use adsiedit, if you feel comfortable using it...

Answer

I've worked on this problem extensively. I'm pretty convinced it can't happen. ADSIedit can indeed modify the path, but then the GPO breaks until you select redeploy - which defeats the purpose of modifying the path in the first place since you could just as easily remove and readd the software to the GPO and get the same results.  Though if anybody ever cracks this one I'll be interested to here a solution.

Answer

I have had the same problem, I ended up renaming the Server.  But I heard that if you put the Software directories on DFS then they are not Tied to a server.
 Is anyone doing it that way?

Answer

Most of our packages reside on a DFS linked share. The GPO is unaware that the path is a DFS path and not an absolute path. For example, if the source path in your GPO is \your_domain\data\packages\package.msi then the GPO for all intents and purposes "thinks" there's a server named "your_domain" with a share called "data". The implementation of DFS is of course a great thing, and if your packages reside in a folder of a DFS linked share then you're free to migrate that DFS linked share to any other server and provided the DFS link points at that share then your GPO is none the wiser and everything is golden.
 
 But the issue being discussed here is that some people (myself for example) have some packages deployed from a non-DFS linked share and therefore if they need to physically move their packages to another share then there's no way to update the GPO's source path and have the GPO still deliver the software without necessitating a redeployment of the GPO - which of course results in the complete uninstall and reinstallation of the package on the end-user's machine.

Answer

Hi Guys
 
 DFS "should" prevent this issue, but ironically in my case, the customer did use DFS, but named it / setup it up inappropriately, so it is actually the DFS name I am trying to change !
 
 I am raising this is a support call to Microsoft so I'll let you know if they come back with anything. 
 
 There is this article that provides some hints from the web that I haven't tried yet, but from what people have said on this forum, doesn't sound like it's going to work either.
 
 http://diaryproducts.net\about/operating_systems/windows/move_software_package_to_another_gpo
 
 Cheers
    Shaun

Answer

Hi Folks,
 did anybody ever solve this problem? I am currently dealing with this issue and I'm not very keen on redistributing to 120 clients.
 Help or information would be great.
 C.

Answer

I gave up, I couldn't find a way to do it without causing a redeploy.

Answer

I'll have to search for the utility tomorrow when I have more time but MS has a filer server migration tool that might help. Basically it will setup a shere on a new server and configure AD to answer for the old server and share.  If this is something that sounds like it may help, email me and I'll try to find the info for you.

Answer

hi guys, i've found the answer :
 http://www.gpanswers.com/community/viewtopic.php?t=1118

Answer

That's awesome! Thanks for following up on this. We looked for a way to do that many years ago when AD was still relatively new, but there was no solution. 
 
 I will definately be filing this one away.
 
 Tom

Answer

The solution at gpanswers.com worked for me but it ended up redeploying to everyone in the OU that used that GPO. Going the ADSI Edit route and changing the path in the msiFileList entry worked fine for me and did not redeploy to existing members of the OU and installed the software when computers were added to the OU.

Answer

Gordho,
 
 In your situation was the GPO in a managed state? Meaning, was "Uninstall if out of scope" enabled?

Answer

It's been 7 long years. Has anyone managed to crack this puzzle?
I too would like to move my install points from a $ share to a new DFS setup without redeployment...