Hi Jake,

Thanks for the input.  I have done some testing with your suggestions but don't feel it will work for our situation unless I am not using the feature properly, allow me to elaborate a little more.

Instead of moving 1 machine from LocationA to LocationB, let's say I want to move 400 machines from LocationA,C,D,E,F....... etc etc (any random amount from any random location), to LocationB.  I only want 1 instance of 'InstalledPackage' to exist on the machine.

When the 400 machines are installed.  I want to use Deployment Manager to install 'http://transmitter:5282/LocationB/InstalledPackage' to the machines.  I can't use a Deployment with the "Update From" command as I would have to define which Location each machine came from.  Unless there is a way to set up the deployment with a wildcard such that I can say:

(where X represents any possible location ID)

Update http://transmitter:5282/Location'X'/InstalledPackage From http://transmitter:5282/LocationB/InstalledPackage

Is this possible?

This is a regular occurence for us, so I was thinking the easier solution would be that 'InstalledPackage' always gets written to the same channel, that way installing it from DM would always overwrite the same channel folder.

Thoughts?  Thanks.

Hi Jake,

I'm not concerned about where the package is retrieved from.  We currently have approximately 100 repeaters online and are very familiar with the use of the subnet based repeater policy.  My concern is the fact that the only way I can create a deployment that will perform the update from is to specify which channel I want to update and which channel I want to update from.

In my test environment, the only way to make it work successfully was to build a Generic Task Group using an Application Packager command.  In that command I had to specifically reference the channel I want to update, ie. http://transmitter:5282/LocationA/InstalledPackage, and the channel I want it to update from, ie. http://transmitter:5282/LocationB/InstalledPackage.  Although the channel was left in an 'install-pending' state, and didn't actually install.  In my example where I am moving machines frequently, I would have to build 60+ of these deployments to accommodate for our 60+ locations and deploy all of them, not very efficient.

I considered using Policy Manager, but once again, I would have to have 60+ entries to uninstall the channels that aren't from the LocationB folder.  Again, not very efficient.

I appreciate your input.

Thanks.

Custom software that is specific to each office but all have the same URL structure to take advantage of other custom tools running on the machine.

ie.

http://transmitter:5282/LocationA/InstalledPackage

is not the same version of software as:

http://transmitter:5282/LocationB/InstalledPackage

Users can access a tool locally and perform certain functions on a GUI via runchannel scripts that builds the required transmitter URL based on variables defined in the machine, Location being one of them.  The script will contain some generic entry such as:

Install http://transmitter:5282/"MyLocation"/InstalledPackage

This allows us to use the custom tools over and over on any machine regardless of the location, but when we move machines around, and re-define variables such as location, we end up with multiple 'InstalledPackages' in the workspace, which eats up a lot of storage space.