Software deployment settings

[chekmate1984]

Hi all

 

We had target tracker deployed from our old file server via GPO. Few weeks ago we deployed the update via GPO. Noticed its uninstalling the old one and is failing as the MSI is pointing to the old file server.

 

As result the new install is failing. Is there way round this than manual install?

[pantscat]

So - the old location isn't there anymore?

 

A rough work around would be to put in a CNAME for the old file server hostname, point it to the new file server and hey presto!

[LeMarchand]

Not had to do this, but I'd try setting the older version to redeploy from the new server and the new version to update it. You may need to fiddle in the below?

 

 

That said, I can remember having problems last time we changed servers and I don't think I'd have thought to consider the last installation's location! Probably no probs as server and shares were still active for some time.

 

Ninja'd by @pantscat's more elegant solution.

Edited July 8, 2022 by LeMarchand

[jmak]

Not had to do this, but I'd try setting the older version to redeploy from the new server and the new version to update it. You may need to fiddle in the below?

 

 

Fiddling below can get you in all kinds of trouble....

 

(Sorry, it's Friday)

[mavhc]

Always use DFS to deploy, then the server it's on doesn't matter

[pantscat]

^ This - very elegant.

[jthompson]

CNAME aliases are best avoided, as Kerberos gets upset with them.

 

Better (and simpler?) to add a new alias onto the new file server using PowerShell:

 

netdom computername fileservernew /add:

 

where fileservernew is the hostname of the new server, fileserverold is the hostname of the old one and internal.school.org is the AD domain.

 

That will take care of all the required DNS entries for you as well.

 

Simples.