Couple of options come to mind...
- One could implement DFS and have your MSI install from
a DFS link server.
- One could use a drive letter instead of a UNC path for
the source location, and have a separate process that runs
on the workstations (logon script, eg) that maps the drive
letter to one of several servers.
- If you're comfortable editing the MSI, then at the MSI
level, one can create/edit the "SOURCELIST" property and
specify multiple paths. Check
out "
http://msdn.microsoft.com/library/en-
us/msi/setup/sourcelist_property.asp" for more information
on the "SOURCELIST" property. However, this does not load-
balance, it just provides multiple sources, in case the
original source is not available. Implementing DFS is
the "best" option, as this will scale well.
Editing the "SOURCELIST" property does not edit
the "msiFilelist" attribute of the software package
object, which is used to hold the path of the MSI, and any
transforms that should be applied, rather than multiple
paths to MSIs.
Hope this helps!
Curtis Sawin