The WinOps Blog

L'installation en mode stand-alone correspond à une infratsructure AppV sans infrastructure associé (Serveur AppV). Le sequencer génère un fichier MSI qu' il est alors nécessaire de pousser sur les postes clients pour charger l' application AppV par d'autres moyen (SMS...).

En version AppV 4.5 le mode d'installation silencieux et le paramétrage a changé. Il est présenté dans le guide Technet suivant:

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

Guide : App-V Application Publishing and Client Interaction

Les clés de registres suivantes doivent être mise en place pour que le mode Stand-alone complet fonctionne:

HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client

· Network\Online = 0

· Configuration\RequireAuthorizationIfCached = 0

· Configuration\AllowingStreamingFromFile = 0

· Permissions\ToggleOfflineMode = 0 (Recommended)

· Network\LimitDisconnectedOperation = 0 (Recommended)

Pour rappel:

Le MSI généré par le sequencer ne contient pas le fichier SFT. Il  contient les scripts, icônes, etc... permettant de charge rl'application dans le cache du client AppV. I s'accompagne donc du fichier SFT dans un mode complet stand-alone.

Pour information :

Un mode semi stand-alone est disponible. A savoir un outil (SMS, autre...) pousse le MSI uniquement sur le poste client. Le client AppV enregistre la référence de l'application, mais n'a toujours pas l'application. Deux choix:

- Streaming depuis un SC AppV Streaming Server. On a alors la configuration suivante:

Msiexec.exe /i \\PathToMsi\packagename.msi MODE=STREAMING OVERRIDEURL=\\\\server\share\package.sft LOAD=FALSE /q

HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client

· Configuration\AllowingStreamingFromFile = 1

- Import depuis un share où le fichier SFT est stocké. On a alors:

Msiexec.exe /i \\PathToMsi\packagename.msi SFTPATH=\\server\share\package.sft /q

Extrait de Microsoft Application Virtualization Version 4.5 Trial Guide :

The Microsoft Application Virtualization Sequencer has an option to create an .msi file that automates the addition of the virtual application. The .msi file can be used by an ESD system to automatically publish the shortcuts and FTAs and to load the application into cache. It can also be used directly on the client in standalone mode. Standalone mode requires the client to go into offline mode, which allows only.msi-based updates of the virtual applications; streaming is not allowed while in offline mode. This mode is meant for rarely connected users who need the power of virtualized applications, but do not have access to a server. A Group Policy administrative template (.adm) is available at http://go.microsoft.com/fwlink/?LinkID=121835 to manage these settings centrally through group policy.

Configuring the Client for Standalone Mode

Perform the following steps on the Microsoft Application Virtualization client:

1. Click Start | Administrative Tools | Application Virtualization Client.

2. In the console tree, click Applications.

3. Right-click Word Viewer 2003 and click Delete.

4. Click Yes to confirm and close the Application Virtualization Client.

5. Open the Registry Editor.

6. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SoftGrid\4.5\Client\Configuration (Figure 29).

7. In the details pane, double-click RequireAuthorizationIfCached.

8. In the Value data field, type 0, and then click OK.

Figure 29. Configuration for standalone mode

9. In the console tree, under Client, click Network (Figure 30).

10. In the details pane, double-click AllowDisconnectedOperation.

11. In the Value data field, ensure the setting is 1, and then click OK.

12. In the details pane, double-click Online.

13. In the Value data field, ensure the setting is 0, and then click OK.

Figure 30. Network

14. In the console tree, under Client, click Permissions (Figure 31).

15. In the details pane, double-click ToggleOfflineMode.

16. In the Value data field, type 0, and then click OK.

Figure 31. Permissions

17. Close the Registry Editor.

18. Open the Services applet in Control Panel and restart the service named “Application Virtualization Client” so that these changes will take effect.

19. Copy WordViewer2003.msi and WordViewer2003.sft from the files in the WordViewer2003 folder sequenced earlier in the guide to the client computer.

20. Double-click WordViewer2003.msi.

21. In the Word Viewer 2003 Setup Wizard (Figure 32), on the Welcome page, click Next.

Figure 32. Word Viewer 2003 Setup Wizard Welcome page

22. On the Installation Complete page, click Close.

23. Click Start | Programs | Word Viewer 2003. The application will launch an Open dialog box.

24. Click Cancel, and then close Word Viewer.

ou alors on crée un package directement via un tools fournit par MS:

The App-V 4.6 client has been tested extensively with pre-4.6 sequenced packages.

If you have 4.5 RTM packages which use MSI for deployment, then they will have to be updated (4.5 CU1 and SP1 MSIs are not affected by this). There are three ways to update your 4.5 RTM packages: 

1. Use the MSI transform that we have placed on Microsoft Download Center.
2. Use App-V 4.5 CU1/SP1 or App-V 4.6 Sequencer to open your package and generate a new MSI 
        a.    Open the package in “Edit a Package” mode on the 4.6 Sequencer
        b.    Select the  Deployment tab
        c.    Check the “Generate Microsoft Windows Installer (MSI) Package” option
        d.    Save package
3. Use the App-V 4.6 Command-Line (CLI) Sequencer to overwrite your MSI with a new one: SFTSequencer /Open:"package.sprj" /MSI. You can get more information about opening a package in CLI here.