Hi all,
Not sure how possible this is, but are you able to have two App-v package repositories in separate locations? Our current infrastructure means that a chunk of our users are at a satellite location, with access to their own set of servers for daily tasks (print, file etc).
We're in the middle of an App-v rollout, with most of the structure for it housed at our main office: management server, SQL databases, main publishing server etc. We have a secondary publishing server at our satellite offices, which functions as intended
on the port set up (the xml schema is visible when viewing from a client machine), and we've rules in place to allow contact through the firewalls.
Unfortunately this has given me a lot of trouble, and while the publishing server itself works, client machines at the secondary site are unable to receive apps (0x74F00F0C-0x80070005). They should, in theory, obtain apps from their local repository (appsrv2), but the xml schema still shows the app location as appsrv1. I'm sure that their failure is down to permissions based on the error codes, which makes sense as our users there wouldn't be able to access servers here so directly, even with a folder permissions change (domain users are already authenticated to access repositories).
Is there a way I can point client machines at our satellite office to their own, local repository on appsrv2? Using the existing one up here would cause issues with link load, which is already stressed as is. I have a feeling it may require a second management server but I would hope not.
Thanks,
Dusty.