locked
OSD / ICO Deployment allways throug SMB or HTTP? RRS feed

  • Question

  • Hello,
    I'm building a new design and i'm running into a design issue and I don't know if it is true. So maybe I can get some help here.
    - In my design I have one server with the web management server service and console installed. (with vSphere it is made fail-over across two datacenters)
    - Two management servers, acting both as publishing and streaming servers, load-balanced accross two datacenters and using RTSP as protocol. Using DFS-R for keeping content folder in sync.
    - DB is running on a cluster which is available in both datacenters. 
    - Clients connect using port 554 to the virtual IP of the load-balancer and get their applist.xml published.
    So far so Good!, I see the xml in my log files (in verbose mode).
    But now the client wants to download the OSD/ICO files using RTSP, and here it fails. If I change the address to an UNC path everything works. But I do not want to load-balance the SMB/CIFS. The streaming part of RTSP works also btw. It is only the OSD/ICO files which fail.
    I really good use some advice on this part.
    Kind Regards, Luc
    Friday, May 6, 2011 3:03 PM

Answers

All replies

  • What address are you changin? i.e. where are you changing this address - in the OSD files, on the client or on the Management Server?

     

    By default, the client will download the OSD and ICO files over SMB. You can override this behaviour with the OSDSourceRoot and ICOSourceRoot properties of the client.

    OSDSourcePath and ICOSourcePath act differently to ApplicationSourceRoot - you will need to copy the OSD and ICO files from each package to the location specified by these properties. You can see how this works by updating these properties and viewing a publishing refresh in the App-V client log.

     

    Also see here: http://social.technet.microsoft.com/Forums/en-US/appvserverandmanagement/thread/a11cbcc0-d21c-4b7a-8c07-9859e2b0dec7 

     


    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
    • Marked as answer by Luc Raeskin Thursday, May 12, 2011 9:29 AM
    Friday, May 6, 2011 3:40 PM
    Moderator
  • Publishing Elements (OSDs/ICONs) must be pulled down via HTTP(s) or SMB. The APPLIST.XML will give the location based on how the list was published (via App-V Management Server or Web via ASP.NET)

    Traditional server-based enviroments build this and target to users on demand based on the Application records stored in the database.

     

    As Aaron said, you can override this with the OSDSourceRoot and the IconSourceRoot options.


    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Friday, May 6, 2011 11:50 PM
  • Thanks for the information. What do you think if I just install the IIS role on the two management servers and publish the ICO/OSD through IIS. I don't want to use SMB because it is much easier and efficient to load-balance HTTP than SMB. 

    What do you think of the other part of the design. Any recommendations?

     

    Edit: I'm reading that RTSP also uses dynamic ports in a high range. What is best practise to load balance this?

    Monday, May 9, 2011 8:23 AM
    • Marked as answer by Luc Raeskin Thursday, May 12, 2011 9:29 AM
    Monday, May 9, 2011 9:00 AM
  • For HTTP, sure. How do you plan to load balance - using WLBS or a non-Microsoft/HW solution?
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Tuesday, May 10, 2011 1:02 PM
  • Thanks for the info. I'm planning to use a HW-solution for both HTTP and RTSP. Just thinking how this would size, since i'v combined several services (publish/streaming/distributing OSD/ICO) on 2 servers. Maybe a third or even fourth server is needed.

    1000 app-v applications either published to Citrix XenApp or fat clients. 5000 end-devices

    Wednesday, May 11, 2011 8:46 AM
  • We have many customers doing just that with Cisco/F5/Netscaler/etc. just fine.
    Steve Thomas, SSEE, Microsoft
    App-V/MED-V/SCVMM/SCCM/AppCompat
    http://madvirtualizer.wordpress.com/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”
    Wednesday, May 11, 2011 11:04 PM