GPO App Deployment - Changing Locations.

[boomam]

Hi.
About 3 months or so ago i started blasting apps out, where possible, via GPOs.
The deployment share "\\server\gpsins" is on our main DC/file server. I want to move the apps to another server, a modified nas, so the paths would be "\\nas1\gpsins".
Im happy going into each GPO and removing/re-adding the new paths to the programs, but what i want to know is: Will all the machines start installing the software again, or will it not bother as its previously installed?

Thanks in advance all. .

[sahmeepee]

Bad news! It'll reinstall. In a few moments, someone will be along to chastise you for not using DFS!

[localzuk]

You should've used DFS! :P

But yes, it will re-install as it will think they are new versions of the software.

[boomam]

Why should i have used DFS?

It wasnt really an option to begin with, the NAS was a later addition, and whoever setup the DC before i started didnt have DFS installed/configured on it.

[cookie_monster]

Take a look at this link.

http://www.windowsdevcenter.com/pub/...04/05/dfs.html


@ localzuk

Do you find DFS usefull in other situations as well?

[boomam]

Take a look at this link.

http://www.windowsdevcenter.com/pub/...04/05/dfs.html


@ localzuk

Do you find DFS usefull in other situations as well?

Hmm. Interesting,
So DFS is basically a virtual filesystem, where i can change paths as nessessary, tranparenty to the rest of the network?

Im wondering how it can get me around this problem though?
I can setup the existing DC/File server as the DFS root, and add several folders on the NAS as par of the DFS, but the programs would just want to re-install wouldnt they?
Therefore negating the need for me to use DFS in the first place. .

[techyphil]

Very interesting, glad I read that myself before I went down that route. Atm I do all unattended installs etc after a Install of Windows XP.

Cheers guys

[ChrisH]

Having software installs look at an old file source is an absolute pita and can cause all sorts of propblems. DFS is the best solution although I dont think it's 2 clever using 2 different sources sometimes.

[cookie_monster]

Is it possible to fool packages by using a DNS alias if you move them to another location?

[sahmeepee]

Im wondering how it can get me around this problem though?
I can setup the existing DC/File server as the DFS root, and add several folders on the NAS as par of the DFS, but the programs would just want to re-install wouldnt they?
Therefore negating the need for me to use DFS in the first place. .

Although we don't use it here yet, my understanding is that you can set up a root which you access via \\yourdomain\installpoint\ much like you can probably type \\yourdomain\netlogon right now to get at the netlogon folder which actually lives on your DCs.

That way you can have a "virtual" location which never changes and so that software won't be reinstalled. Of course, it's a bit late now - you'd want to have the DFS set up prior to the original software installation.

[ChrisH]

Is it possible to fool packages by using a DNS alias if you move them to another location?

You can do this but you also need to add a little tweak to the registry to allow the machine to answer to the old servers name using the normal \\server\share format.

[cookie_monster]

Can you provide a bit more info on that please ChrisH?

[ChrisH]

This KB article has the info you just have to disable the strict name checking:

http://support.microsoft.com/kb/281308

[cookie_monster]

Oh yes i've actually read that before, thanks for jogging the grey matter.

[boomam]

This KB article has the info you just have to disable the strict name checking:

http://support.microsoft.com/kb/281308

So this will allow me to change file locations without redeployment?