locked
App-V package delivery RRS feed

  • Question

  • We have SCCM 2007 Sp2 / R3 environment , . We need to virtualize some applications as they have certain issues running of Windows 7 and run fine on XP. We have been asked to check the Micrsoft APP-V . I started reading about App-v and know how we can use a App-v packed in SCCM 2007 R2. However i have some doubts related to App-V Infrastructure.

     Now that suppose we want to have Office 2010 as an APP-V virtual Application. WHat all do i need.

    Do we have to install App-V Managemedt Server  (We have SCCM so can push policies though it)

    2.Do we have to  have APP-V Streaming server
    3.Do we need to have A App-V client on all our machines that will be running the Sequenced virtual application


    Since the application packeage is created using the sequencer , so if i install the Sequencing Software on Windows XP / 7 / vista and then sequence the application that we want .. Once the app is sequenced and we have the .sft .osd .xml etc files for that appls

    Do we have to mandatorly have them pushed through APP-V Managemnet server  and have a streaming Server.

    Or we can simply take the files and Package them through SCCM and push it to clients .

    The architecture is a littl confusing for me and i do not know what components we need to install to begin testing.

     


    Saturday, April 7, 2012 12:35 PM

Answers

  • Hello,

    1. No

    2. No

    3. Yes

    I suggest you read the whitepapers section - there are several papers that deal with your specific problem (planning and design guide, sccm whitepaper etc etc);

    http://technet.microsoft.com/en-us/appvirtualization/cc843994


    Nicke Källén | The Knack| Twitter: @Znackattack

    • Proposed as answer by RorymonMVP Saturday, April 7, 2012 4:31 PM
    • Marked as answer by Kitaab Sunday, April 22, 2012 6:12 AM
    Saturday, April 7, 2012 1:06 PM
  • It sounds as if you might want to consider running an App-V / ConfigMgr integrated scenario.

    In short, the App-V client is installed on each of the workstations requiring the app. If you go this route, you do not need a management server or streaming server. This set up requires the least amount of administrative overhead. You would sequence your apps using the sequencer, then use ConfigMgr to distribute the apps. The virtual apps can be ran from cache located on the workstation which will allow apps to be ran when/if the workstation is disconnected from the network. You can also stream the apps from the distribution points if you choose to.

    It really comes down to what you/your customer wants. You would need for your ConfigMgr environment to be either Configuration Manager 2007 R2 or Configuration Manager 2007 R3. If you have a business requirement to leverage the additional features of App-V over ConfigMgr integrated, then you will need the additional App-V components (Management servers). Keep in mind, going the non-integrated way typically means you will have to maintain apps in two environments.

    Check out this whitepaper on App-V integration with ConfigMgr:

    http://download.microsoft.com/download/f/7/8/f784a197-73be-48ff-83da-4102c05a6d44/APP-V/App-V_and_ConfigMgr_Whitepaper_Final.docx

    That whitepaper should answer a majority of your questions.

    here's some additional info: http://technet.microsoft.com/en-us/library/cc161957.aspx

    Hope this helps!

    Cheers!



    Thursday, April 12, 2012 5:22 PM

All replies