Symantec Management Platform (Notification Server)

Hello.

I'm currently trying to test the use of DFS (Distributed File System) with software deployment (you might want to check this post regarding official support of DFS).

In order to really test this, I need to make sure that the client downloads the package from the DFS Namespace and not the NS.

Is it possible to configure the solution so downloading the package from the NS is only used as last resort regardless of an eventual speed test?

I can see in the package.xml file in my packages that the NS is always listed as the first server, so I guess it's natural that it tries that server first if the client doesn't have a previous speed test cached.

Thanks in advance.

/MiGe

I've tried to remove the "Read" permission on the virtual directory in IIS for a specific package so it cannot be downloaded from there, but the agent still want's to download the package from the NS even though there's an alternate download location available.

The alternate location is listed in the "Source location" list and the client can browse the location.

What is needed for the client to move on to the next location in the list?

I let the client keep retrying downloading the package, and after 5 unsuccessful attempts, the client contacted the NS server again to get the package info (GetPackageInfo.aspx).

The NS then returned a list of all available package servers and the client then downloaded the package from one of those servers. The original alternate download location mentioned in my prevoius post, is NOT listed as a source location after the last update!

So again; What is needed for the client to move on to the next location in the list? If it never moves on to the next location in the list, what's the point of having multiple sources?