Does anyone else think this may be useful to have? The way it works right now is that if you use an HTTP path in the package it will only try to use an HTTP path when it tries to go to a preferred server and the same goes for UNC paths. This becomes an issue when you use a Gateway which requires HTTP paths and when you dont have many preferred servers that can run a web service. If we set everything to UNC then when a client is in Gateway mode it can't access packages. We have over 500 portable NAS devices that are used as preferred servers. The NAS boxes will support web services but it doesn't work quite as nice as IIS does on a server. If the client had the ability to try both methods, HTTP and UNC, then it would allow it to almost always find a good path to the package. If anyone thinks this would be useful please vote http://community.landesk.com/support/ideas/1580. This was actually someone elses ER but is exactly what we need and it also adds flexibility that others may also see useful.
So nobody sees any benefit from this?
I am searching a way to be able to force some of our DMZ servers to use HTTP instead of UNC while keeping the UNC way (more faster) on our core LAN. Is there a way to force some agents to use HTTP ? or fallback to HTTP if UNC is not available ?
Any help will be welcomed.
I gave you 5