Sign in
Microsoft.com
 
Application Virtualization TechCenter
 
 
 
Application Virtualization TechCenter > Microsoft Application Virtualization (App-V) Forums > App-V Clients > Slow launch of applications
Ask a questionAsk a question
Search Forums:
 

AnswerSlow launch of applications

  • Thursday, January 08, 2009 12:57 PMKim Morgan Ellis Fiva Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I've sequenced and testet some applications, but the launching is extremly slow.

    When I launch a package that is about 500MB it uses about 10 miniutes to stream.

    Standard App-V 4.5 setup and installed on a new 2008 server.

    The clients are 4.5 on Windows 2003 with latest SP.

    If I use RTSP (554) it streams in about 5 seconds.
    If I use RTSPS (322) it strems in about 10-15 minutes.

    Is there a way yo speed up the streaming of new apps, when the app finally is streamed the lanuch is fast.

    Copying the project from the app-v server to the 2003 server manually is fast.


    Kim
     

Answers

All Replies

  • Friday, January 23, 2009 7:09 PMTim ManganMVP, AnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

     Why are you using RTSPS?  Unless it is to expose connections outside the corporate firewall without use of a VPN, then there is very little use of RTSPS.

    Also, since you seem to be streaming to a 2003 server, I will mention that it is generally considered best practice to "pre stream' to terminal servers (sftmime /load).

     
  • Friday, March 27, 2009 11:46 AMKim Morgan Ellis Fiva Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Now special reason other that it's what Microsoft has set as deafult.

    We sequence 100+ applications a week and I want to aviod the extra work it is to change to the old protocol when sequencing.

     
  • Thursday, April 02, 2009 2:25 PMTim ManganMVP, AnswererUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Sign In to Vote
    0
    Sign In to Vote

    Since you don't need RTSPS, you should probably remove it if concerned about speed.  RTSPS is providing encryption and, in 4.5, authentication of the server itself.  Since the traffic on this link is pretty much the SFT blocks, you really don't need the encryption.  And personally, I am not concerned about someone putting up a rogue App-V server somewhere inside my enterprise and hacking DNS to deliver rouge apps. 

    I believe the decision by Microsoft to default this setting was simply an ill conceived idea that this setting fell under the "secure by default" mandate.  Of course, they didn't make IE default to use https: addressing by default, did they?

    If you don't want to edit all those OSDs, you can instead push out an ASR override to the regisrty of the clients.  If the osd says "rtsps://fooServer/..." you set the ASR to "rtsp://fooServer" and it will override the appropriate parts of the OSD string.

     

    • Proposed As Answer byznack Thursday, April 16, 2009 6:26 AM
    •  
     
  • Thursday, November 05, 2009 8:32 AMKim Morgan Ellis Fiva Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    I think this is solved in App-V 4.5 SP1.

    I've reverted to using RTSP, but I saw in the buglist that "slow RTSPS" is fixed.