same question goes with Multicasting and XDD Agents
For the Preferred Server question, yes... as long as your workstation falls within that range it will attempt to connect to the P Server. If it can't find it for whatever reason it will revert back to the core, even if it's in the subnet range.
Alright.. i tried, doesnt work.
I have a task scheduled that picks up the exe from \\server.domain.com\deploy$\Program\Setup.exe. I deployed it to the system that has the IP address that makes it part of the IP address suggested for the Preferred server. When i deploy it, it comes back to the core server and picks up the files.
Do i HAVE to say HTTP://server.domain.com/deploy/program/setup.exe or can i not use UNC paths. Is there any limitation to the use of the UNC path (meaning not using FQDNs)
You mentioned that you tried the preferred server and it doesn't work. Did you put the distribution package files at the location \\PreferredServer\deploy$\Program\Setup.exe? If it can't find it there, it will revert back to the core server.
You can also see in your client log files if it attempted to use a preferred server or not.
Yes, the data has been replicated at the same places.. adn shares are configured teh same way.
Am i supose to use http instead of UNC path? to make the preferred server work?
We have been using preferred servers for some time now and we use web shares not UNC.
A recent change we implemented was allocating the IP segments to our remote servers instead of leaving it up to the chance of a slow network ping, but we left the larger sites with no IP segment range allocated to allow for some redundancy for our remote sites.
Sorry this does not answer all of your questions, but gives a basic working model.
I'll give it a try with http instead of UNC and see how that goes.