locked
App-v 5.0 SP3 questions RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    We have App-v 5.0 SP2 on terminal servers (with some APp-v 5.0 packages) and are about to do a rollout of App-v. I have my App-v 5.0 SP2 hotfix 3 package ready but there is a SP3 now.

    My questions:

    -major one: what's my biggest benefit for upgrading, is there a major bug fix or new feature?

    -can we just upgrade the terminal servers without impact (apart from some down time): all previous packages will still work?
    -if we update the sequencer first, can I publish SP3 packages to SP2 clients (are they compatible)?
    -some Windows 7 clients already have SP2, will they have an impact when upgrade to SP3

    Please advise.
    J.

    Jan Hoedt

    Friday, January 30, 2015 11:19 AM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jan,

    SP3 brought about some significant changes for App-V, in particular increased flexibility of connection groups, runvirtual for the user and improvements to the sequencer. For a full breakdown of what's new read here: http://virtualvibes.co.uk/everything-you-need-to-know-about-app-v-5-0-sp3/

    https://technet.microsoft.com/en-us/library/dn858700.aspx

    Its mainly a feature release however there are some bug fixes in there too.

    SP3 is fully backwards compatible with non-SP3 packages. This is the order in which you should upgrade:

    • App-V Server
    • Sequencer
    • App-V client or App-V Remote Desktop Services (RDS) client
    • Connection groups

    Friday, January 30, 2015 4:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi folks,

    Kindly help with an issue related to publishi of app.

    Chked/observed one thing that at the publishing server, as we are publishing the apps  from the console : http: localhost:81 / Console.html.

    while chking the IIS  > sites >MS App-V publishing server > manage  website > browse , then the XML file launches via IE doesnt contain the package  info then and there , it takes smart 10 mins or so, despite being the package n publishing server being same. So cant see real time effect. (shown below before package info)

    ------------------------------

    <?xml version="1.0"?>

    -<Publishing Protocol="1.0">

    <Packages/>

    </Publishing>

    ----------------------------------

    however  if we stop/ start the publishing server then it gives the published info then n there . (even in 2 secs)

    (shown below post 10 mins OR stop > start manage website/publishing  website)

    -----------------------------------------------------------

    <?xml version="1.0"?>

    -<Publishing Protocol="1.0">

    -</Package>

    <Package PackageUrl="" VersionId="backslash backslash xxxxxxxxx App-V 5 Content>vSphere 6.0>vSphere Client 6.0.appv" PackageId="xxxxxxxxxxxxxxxxxxx"/>

    </Packages>

    -<NoGroup>

    <Package PackageId="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"/>

    </NoGroup>

    </Publishing>

    -----------------------------------------------------------------------

    Is this the normal behaviour , like to wait for 10 mins even on the same package server?

    or is this some IIS issue related to refreshing ?

    how can this be fixed ? Guess this causing delay to the package to be published at the client end .

    Expertise please advice/help.

    thanks,

    Niks

    Tuesday, July 7, 2015 3:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi guys,

    Found answer for my asked query.

    i tweaked the  publishing server refresh interval to 10 secs , which was set to 600 secs (by default), at the mgmt server.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Server\PublishingService
    PUBLISHING_MGT_SERVER_REFRESH_INTERVAL = 5 (common value used for test environment

    this helped in instant publishing/ unpublishing of apps at client end .

    also changed some iis settings  : IISM>application pool >AppvPublishing>  ad settings>Under General> startmode to Always Running.

    Hope this helps to other as well.

    But still post unpublishing the app, can see the cached folder under  VFS folder, at client's machine.

    thanks,

    Niks

    Wednesday, July 8, 2015 11:47 AM