Importance of content share on Streaming servers in branch offices
We have our AppV publishing/mgmt server in our central office and the content is being served using a DFS share that replicates across our branch offices. We had setup a AppV streaming server in one of our branch office and copied all data in publishing server content share to streaming server as suggested by the setup document. As we are using DFS share which is commonly accessible across the sites (say \\foo.com\microsoft\appvcontent), we disabled the content share on both publishing server and streaming server as the virtual apps are supposed to be streamed by DFS. Everything went fine till this state but when we virtualized a new application and copied it to just DFS share, it works perfectly fine on clients that are local to our publishing server but the clients in branch offices that are configured to talk to streaming servers fail to launch the application with generic "...not found..." message. We could see that client is communicating to both local streaming server and DFS share but it fails to launch. When we copy the virtual app into the content share of branch streaming server (note that content folder is not shared here), it starts working fine.
Just wondering if this dependency is expected behavior or we are missing something?
There are no answers at this time