Modifying Software Installation path

[Lee]

Hi,

I want to move our current appdeploy folder to a DFS share. All apps
deployed via GPO are currently set to install from
\\%servername%\apps\%appname%.msi.

The new DFS share will be

\\eu\dfs\apps

I have modifed the msi-filelist attribute on one of my apps to point to the
new DFS share, and removed the package from the old share, now the package
will not install andI get the following error in event log:

ID 102

The install of application Previous Version Client from policy 45Software
Deploy Policy failed. The error was: The installation source for the
product is not available. Verify that the source exists and that you can
access it.

I have triple checked the path is correct.
Tripled checked Authenticated users has access to all DFS shares and NTFS
security on those shares and folders within.
Ran gpresult -z on the PC which shows the installation path pointing to the
DFS share.

Any other ideas why this isn't working ?

TIA

LM

[Brian Desmond [MVP]]

Lee-

You will need to remove the application assignment and reassign it with the
new path. This will trigger an uninstall/reinstall on every workstation
affected by the policy.

--
--
Brian Desmond
Windows Server MVP
desm...@payton.cps.k12.il.us

Http://www.briandesmond.com

"Lee" <l...@nowehere.com> wrote in message
news:e70cRfnm...@TK2MSFTNGP09.phx.gbl...

[Lee]

Brian,

That sucks, we are talking over 1000 users and about 10 packages.

When I change the msi-file list attribute to my new path, it reflects this
in the policy package, so I don't see why it shouldn't work.

Can you explain the reason why this doesnt work because redploying all the
apps is not an option.

Thanks

LM
"Brian Desmond [MVP]" <desm...@payton.cps.k12.il.us> wrote in message
news:uB3ZMsqm...@TK2MSFTNGP15.phx.gbl...

[Darren Mar-Elia]

Lee-
The reason is that the msifilelist attribute on the packageRegistration
object is not the only place where the package path is held. Its also
embedded in the application avertisement script (.aas file) in the GPT
(SYSVOL) portion of the GPO, and its stored in the registry on each
workstation where the app was deployed. So the problem of changinge deployed
app paths is a tough one. I'm working on a utility that lets you change the
path without redeploying the app--by regenerating the AAS file with the new
path, but the challenge is that you still have to touch each individual
workstation that has the package(s) deployed to change the path(s) in the
registry--otherwise you lose the ability for app to remove/update/patch
itself.

--
Darren Mar-Elia
MS-MVP-Windows Management
http://www.gpoguy.com

"Lee" <l...@nowehere.com> wrote in message

news:%23Lv%23PTrmE...@TK2MSFTNGP10.phx.gbl...