[ Send this article ]
Your message has been sent.
How would you like to send this article:
[ Save this article ]
Save this article to your account for easy access.
This article has been saved to your account.
Go to my account
This article has been emailed to your Kindle.
Send this article
Complete the form below to send this article, Installing the App-V Sequencer, Client and Streaming Server, to a friend (or to yourself). We will never share your details (or your friend's) with anyone. For more information, read our Privacy Policy.
by
Augusto Alvarez | January 2011 |
Enterprise Articles Microsoft
Even though most of the initial and common errors are related to the Management Server, an incorrect deployment of the rest of the components could result in hours of troubleshooting effort. After reviewing and understanding the components and models available for implementation, a good point to remember is that often you can combine options to fulfill your business requirements.
Also, with automatic deployments you get the chance to optimize the time you are investing in mechanical procedures and also deliver outstanding provisioning times. In this article by Augusto Alvarez, author of Getting Started with Microsoft Application Virtualization 4.6, you will cover:
- Installing the App-V Sequencer
- Installing and configuring the App-V Desktop Client
- Installing the App-V Streaming Server
| Read more about this book |
(For more resources on Microsoft, see here.)
Installing the App-V Sequencer
After reviewing the requirements and recommendations you can see that the App-V Sequencer installation is pretty straightforward. The procedure is as follows:
- Once you run the installation file, you should get the notification for missing requirement, in this case Microsoft Visual C++ 2005 SP1 Redistributable Package (x86). Click on Install.
- On the first wizard page, click on Next.
- Accept the License Terms and click on Next.
- Select the installation path for the App-V Sequencer binaries. Click on Next.
- Click on Install and the installation process will start.
- After the installation completes, you can automatically launch the application where you can see the new and refreshing interface.
Installing the App-V Client
The installation of the App-V Client component is also very simple and intuitive. The only consideration before starting the installation is that should already have the proper cache size defined.
- Once you start the installation, a few prerequisites will be installed.
- On the first page of the wizard click on Next.
- Accept the License Terms and click on Next.
- Select Custom setup type and click on Next.
- Accept or modify the installation path for the App-V Desktop Client.
- Verify that the data locations used by the App-V Desktop Client, including the drive letter that will be used, are the same as the ones selected for the App-V Sequencer. Click on Next.
- Now you can select the cache size used by the client to store the loaded applications.
The default is the maximum size of 6 GB (6144 MB) or you can use the Use free disk space threshold option, where you can set the value for minimum hard disk space available.
Click on Next.
- On this page you can set the behavior of the Runtime Package. The only recommended option to change from the default selection is marking the On Publishing Refresh on Automatically Load Application.
The Application Source Root option, here left blank (default), is used when you want to override the streaming location of the .sft files (this location is set in the .osd of the App-V package). If you set a path in the Application Source Root, the applications will look for the SFT in that location instead of the one they are receiving in the OSD. This option is another alternative when you are using slow links to avoid transmitting large amounts of data.
Also take note that you can use the auto-load options. In this example Automatically load previously used applications has been selected.
- On the next page you can configure the server you are receiving the packages from and the communication method used. In this case, the server's name is appv-server and the type of communication is Application Virtualization Server, using the RTSP 554 protocol. Click on Next.
- On the last page, just click on Install.
- After the wizard completes, you can use the App-V Client Management Console to verify the Publishing Servers options.
| Read more about this book |
(For more resources on Microsoft, see here.)
Installing the App-V Streaming Server
The App-V Management Server can already perform application streaming, making the App-V Streaming Server an optional component to install.
One of the most appropriate scenarios for the App-V Streaming Server is branch offices. The streaming process requires high bandwidth to deliver applications, so using an App-V Streaming Server near client computers is usually the best option.
Working with the App-V Streaming component gives you the possibility to customize the type of connections you are going to allow from client machines. Let's take a look at the step-by-step installation.
- Running the installation file, at the first page click on Next.
- Accept the License Terms and click on Next.
- Complete the Customer Information and click on Next.
- Verify the installation path for the Streaming Server binaries. Click on Next.
- On the Connection Security Mode page, as you are not using secure connections, click on Next.
- The TCP Port Configuration uses the default port in this case. Click on Next.
- Provide the location for the content folder. Remember that this folder will be the place where App-V packages will be stored, so it could be a good idea to use a secondary drive. Click on Next.
- In the Advanced Settings page, customize the settings for the App-V Streaming possibilities with the following values:
- Max client connections: 1000.
- Number of core processes: 5.
- RTSP thread pool size: 50.
- Connection timeout: 60 seconds.
- Core timeout: 120 seconds.
- RTSP timeout: 30 seconds.
- Enable User authentication and Enable User authorization: As the App-V Streaming Server uses NTFS file permissions, by enabling these two options you can control whether the server checks and enforces those ACLs (Access Control Lists) or not.
- Cache block size: 512 KB.
- Maximum cache size: 512 MB.
- Package update: 1800 seconds (30 minutes).
- On the last page, click on Install.
- Once the installation is complete it will ask for a reboot. This is not exactly a requirement, but actually a recommendation for system performance.
- After the reboot, there are two post-installation tasks necessary (the same as in the App-V Management Server installation):
- Sharing the content folder the same as in the previous installation.
- Use Windows Firewall with Settings to add two inbound rules for the executable files, sghwdsptr.exe and sghwsvr.exe, both located in C:\Program Files (x86)\Microsoft System Center App Virt Streaming Server\App Virt Streaming Server\bin\ folder.
- Sharing the content folder the same as in the previous installation.
Summary
In this article you have had the chance to start working directly with the App-V platform, with the main procedures for the installation.
Further resources on this subject:
- FAQ on Virtualization and Microsoft App-V [article]
- Microsoft Application Virtualization: Managing Dynamic Suite Composition [article]
- Microsoft LightSwitch Application using SQL Azure Database [article]
- Microsoft WCF Hosting and Configuration [article]
- Microsoft Enterprise Library: Security Application Block [article]
About the Author :
Augusto Alvarez
A full time computer geek. Working as an IT Manager, coordinating and managing IT areas; envisioning, designing and implementing client-driven solutions. Also working with Microsoft Academics and Technet, collaborating on different technological events.
Books From Packt
|
|
|
Post new comment