Code Library: Microsoft Virtualization

Showing posts with label Microsoft Virtualization. Show all posts

THE FIVE WINDOWS SERVER 2008 TERMINAL SERVICES ROLE SERVICES The TS role is split into five parts called role services. Each role service performs its own unique function and each is explained in this section.

Terminal Server
A server with the Terminal Server role service installed is referred to as a terminal server. It hosts the Remote Desktop sessions and the Windowsbased applications that are made available to your users.

TS Licensing
Each connection to a terminal server requires a TS client access license also known as a TS CAL. There are two types of TS CALs: TS Per Device CALs and TS Per User CALs. If Per Device licensing is chosen, you will need to purchase a CAL for each device in your enterprise that may be used to access your TS infrastructure. This can be a more economical choice if you have more users than computers in your enterprise. Per User licensing requires you to purchase a CAL for each user that may access your TS deployed applications or desktops. This is often the choice made by companies whose employees need to make a TS connection from a variety of different machines. It is highly recommended that you consult with a Microsoft licensing specialist when deciding which path is right for you. TS CALs are managed by a TS Licensing server, and you are required to have at least one in any TS infrastructure. If you implement a large TS environment with multiple terminal servers, it is recommended that you install TS Licensing on a separate server. However, if you are implementing a TS environment with a small footprint or just for testing you can install TS Licensing on a server running the Terminal Server role. For more detailed information on the installation and configuration of TS Licensing you can go to http://go.microsoft.com/fwlink/?linkid¼85873.

TS Session Broker
The TS Session Broker serves two purposes in a TS environment with a farm of terminal servers. The first is TS Session Broker Load Balancing. When this feature is enabled, the TS Session Broker monitors the number of TS sessions open to each terminal server and directs new session requests to the server with the fewest open sessions. This allows for an even distribution of sessions across all servers in a farm. The second function provided is the ability to ensure a TS user is automatically
reconnected to their active session, if one exists. TS Session Broker tracks information on all open sessions within the farm, recording which user sessions reside on which terminal server. This allows a user to pick up where they left off if their session is unexpectedly disconnected. More detailed information on the installation and configuration of TS Session Broker can be found at http://go.microsoft.com/fwlink/?linkid¼92670.

TS Gateway
By leveraging TS Gateway, a TS environment and computer with Remote Desktop enabled can be configured to be accessible by authorized users over the public Internet without the need for an additional secure method to access your internal network such as a Virtual Private Network (VPN) connection. This is done by establishing an RDP over HTTPS connection from an Internet connected computer over port 443 versus the standard RDP port 3389. Security settings for this access are configured via TS Gateway Manager and include the ability to define several parameters, such as authorized Active Directory user and computer groups, accessible network resources, device and disk redirection, and acceptable authentication methods like passwords or
smart cards. For TS Gateway installation information and a step-by-step installation guide, you can go to http://go.microsoft.com/fwlink/?linkid¼85872.

TS Web Access
TS Web Access makes available from a web browser the applications you publish with the traditional TS methods, such as RemoteApp programs and virtual desktops. You can choose to limit the access to the TS Web Access Web site to your local intranet or use it with TS Gateway as another way to enable your users to access TS applications from across the public Internet.

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

Presentation virtualization (Terminal Services) Presentation virtualization is a buzz phrase that refers to the features and functionality delivered by Windows Server 2008 version of Terminal Services (TS). With TS you can publish an entire Windows desktop just as in previous versions of TS. This enables your users to make a Remote Desktop connection to a terminal server accessing a fully functional desktop environment. In addition, by leveraging a subcomponent of TS called TS RemoteApp, you can publish individual applications that appear to be running locally on the desktop, but are actually running in your data center on a terminal server.

The value of the TS approach to application deployment is realized in multiple areas. In an enterprise with remote locations utilizing slow links back to a centralized data center, this technology can substantially reduce the bandwidth used across slow Wide Area Network (WAN) circuits. This is because only the keyboard and mouse input along with display information is transmitted keeping the data flow between the TS server and the data source exclusively over the data center Local Area Network (LAN).

TS can enable you to extend the useful life of client computers by moving the heavy processing off of the aging client equipment and onto your terminal servers. This allows you to implement newer more intensive applications without having to perform an expensive and time-consuming enterprisewide PC upgrade project. Along a similar line, performing an upgrade of a TS deployed application is accomplished from your centralized data center location. This can eliminate the need to visit all of the client computers in your enterprise to upgrade a locally installed program. Depending on the circumstances (numbers of computers and remote locations, etc.) this can save your company a considerable amount of money and you a considerable amount of time.

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

NEW FEATURES IN APP-V 4.5 AutoLoad packages
One of the new features in Version 4.5 of App-V is the AutoLoad settings in the registry. These settings are created during the client installation and can be adjusted. By default, when a user logs on, the client attempts to load all previously used applications in cache. This ensures all features for are available locally on the computer. For mobile users, this option enables them to leave the network and still be able to use any application that has previously launched. However, this does not give them access to published applications that have not launched before. The AutoLoad options can be modified to download all applications published for a user and can also be triggered by a background publishing refresh.

Application streaming with Streaming Servers
Another new component in Version 4.5 is the Streaming Server. The Streaming Server does not provide the publishing refresh process. It relies on another resource to perform this operation. The publishing refresh process is achieved by implementing a Management Server to handle the publishing refresh and using the Application Source Root (ASR) setting on the client to point to the Streaming Server. You can also use the manifest.xml file created during sequencing to script the package publishing using SFTMIME. These options provide flexibility in remote office scenarios. Streaming Servers implement authorization via NTFS permissions.

Application streaming with File Servers
A file server can deliver packages in an App-V infrastructure, but like the Streaming Server, it cannot provide the publishing refresh process to the clients. As previously noted, this is accomplished by providing a Management Server for the publishing refresh process. This file server could be an actual server or a powerful desktop. File servers implement authorization by using NTFS permissions.

Application streaming with IIS
IIS can also be used for streaming. However, like the Streaming Server and the File server, it cannot provide the publishing refresh process to the clients. The client supports a publishing refresh over an HTTP/HTTPS connection. However, App-V currently has no Web-based publishing refresh service. So the IIS streaming option would require a Management Server to publish applications. IIS Servers implement authorization by using NTFS permissions.

Stand-alone mode with MSI
The App-V Sequencer supports creation of an MSI during the sequencing process. The stand-alone option does not have a formal publishing or streaming procedure. The MSI contains the ICO, OSD, and Manifest. xml files that are necessary for publishing the application on the machine and importing the SFT file into the App-V client cache. However, the package file (SFT) is not created as part of the MSI. It should be placed in the same directory as the MSI to successfully complete. You can place SFT files on a file server. In this scenario, the administrator uses the SFTPATH parameter to specify an alternate location of the SFT file. This removes the requirement that the SFT file to be in the same directory as the MSI. In Stand-alone mode the package will be published and the SFT file contents will be loaded into the client cache completely.

Streaming mode with MSI
Another option is to use MSI packages and choose to stream the SFT file from an alternate location. In this configuration the package is published, but the SFT file is streamed to the App-V client cache. The process of streaming the SFT file is done by default as part of the installation of the MSI, but could optionally be configured to happen when the user launches the application the first time. This mode enables the features of streaming, such as Active Upgrade. The following registry key value must be set on the client to enable Streaming Mode supporting MSI deployment:

HKLM\SOFTWARE\Microsoft\Softgrid\4.5\Client

» Configuration\AllowIndependentFileStreaming ¼ 1

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

CREATING AN APP-V PACKAGE Microsoft’s best practices for sequencing applications, walk you through the steps of creating an App-V package, and explain the various options for publishing that application.

Before sequencing, familiarize yourself with installation and use of the target application. Failure to fully understand the configuration and functionality of the application prior to sequencing may lead to an inefficiently sequenced package; one that may not work all. Specifically,

» What are all of the application components needed to complete the installation of the application?

» What updates such as adding new files to the package will need to be performed while sequencing?

» What postinstallation configuration steps need to take place while sequencing?

» How is the application commonly used by its target users?

When sequencing on Windows Vista or Windows 7, configure the User Account Control (UAC) as it will exist on the target desktops. Disable the UAC if it is disabled on your target client machines.

Always use the Comments field in the sequencer to include details about the package you may want to reference in the future. This allows the sequencer to maintain a log of your actions.

Always sequence to a unique, 8.3 directory name. This applies to both the Asset and Installation directories. (‘Q:\MYAPP’ and ‘Q:\MYAPP.001’ are correct, ‘Q:\My Application’ is incorrect.)

Sequence to a folder in the root of the drive, not to a subdirectory (‘Q:\MYAPP’ is correct; ‘Q:\’ is incorrect; ‘Q:\Temp_Junk\MYAPP’ is incorrect). If the suite has multiple parts, install each application in a subdirectory of the Asset Directory. For example, if a package contains a primary application with the Java Client, use Q:\AppSuite as the Asset Directory; sequence the application to Q:\AppSuite\APP; and sequence the Java Client to Q:\AppSuite\JavaClient.

Use globally unique paths and Package names across the set of application sequencings. For example, place multiple Microsoft Office sequencings in the same Asset Directory name. Use a standardized naming scheme that can be incremented, for example, Q:\OFFXP.v1 or Q:\OFFXP.001.

Launch, configure, and test the application during the installation phase. Often this requires performing several manual steps that are not part of the application installation process, such as configuring database connections, copying updated files, etc. Launch and use the application multiple times in order to ensure that all of the most common features are utilized and captured properly by the sequencer. For example, run the application to get past any registration or initial pop-up dialog boxes. Some applications perform different tasks on first launch, second launch, and sometimes subsequent launches. Multiple launches ensure relevant application code makes it into Feature Block 1 during the execution phase. Use the Application Wizard to launch each executable in a suite of applications; do not just browse to their location under All Programs. Doing so may result in the sequencer failing to grab the proper first launch data for the primary feature block.

Some applications have the option to Install on First Use for certain components. Do not sequence applications with this option selected.

Disable any Auto Update features. Some applications have the ability to check a Web site or a server for the latest application updates. Leaving this feature enabled will not break the application, but it may affect version integrity should the application ever be resequenced to apply updates.

There are applications that cannot or should not be sequenced, and there are limitations within App-V. The following list of applications that SHOULD NOT be sequenced is provided by Microsoft:

» Applications (when sequenced) that are over 4 GB in size. If the application is too large the sequencer will not save the application. It will attempt to compress the file.

» Applications that start services at boot time. App-V requires a logged in user initiate the launch of an application.

» Applications that require device drivers. App-V cannot virtualize drivers, but it may be possible to bypass this issue and install the driver locally on the target computer, outside of the App-V package.

» Applications required by several applications for information or access. For example, a program that launches another program. Normally you want to include both programs in the same suite. However, this is not always possible. This is especially true if one of the reasons you are deploying App-V is to avoid application conflicts. Remember that the virtual “bubble” can see the OS and what is installed on it but the OS can neither see the “bubble” nor interact with it.

» Applications that are a part of the operating system, such as Internet Explorer.

» Applications that use COMþ. COMþ is dynamic and initiates at runtime. The sequencer cannot capture this information.

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

INSTALLING THE APP-V SEQUENCER Before installing the Sequencer on a workstation or server, there are some items that you must be aware of, and may want to configure in advance. Microsoft’s support requirement since version 4.2 of App-V has been to sequence and publish on “like” operating systems. This means that creating a sequenced package on Windows XP and then publishing that package to Vista, and vice versa is not supported. You should plan to have a sequencer workstation or server for every operating system you plan to publish applications to. For example, to publish to a Server 2003 operating system, you must create the package on a Server 2003 operating system, including service pack and hot fix level. Although you may be able to sequence on one operating system and publish to another, the practice is not supported.

In addition to operating system, service pack, and hot fix level, you will also want to include any applications that are a part of your base image. For example, if Adobe Reader is a part of your base image, you should include it in the building of your sequencer workstation. This is especially important if you include the Microsoft Office suite on your base image. Some applications install differently if they see that Microsoft Office is
already installed.

If you plan to package applications that include ODBC DSN settings, you will want to create one on the sequencer workstation prior to sequencing a package. The registry key associated with the ODBC setting will become virtualized and prohibit the packaged application from seeing any ODBC DSN settings on the base client machine.

The following locations can be checked to determine ODBC information was captured:

» Search for odbc.ini: It will be located in the VFS\%CSIDL_WINDOWS% folder
» HKLM\Software\ODBC\ODBC.INI\ODBC Data Sources
» HKCU\%SFT_SID%\Software\ODBC\ODBC.INI

You will want to include a printer as part of the Sequencer base image as well. Printer configurations are handled like ODBC settings. So it is necessary to include a printer device in the sequencer PC image.

You will need to set up your sequencer machine with at least two primary partitions. The first partition, C:, should have the operating system installed; format it as NTFS. The second partition, Q:, is used as the destination path for the application installation. It should also be formatted as NTFS.

The sequencer uses %TMP%, %TEMP%, and its own scratch directory for temporary files. These locations should be large enough to accommodate the full installation size of the application being packaged. The sequencer uses the scratch directory to temporarily store the files generated during the sequencing process. The location of the scratch directory can be seen by launching the sequencer and browsing to Options | Tools and then clicking the Paths tab. You can improve performance by configuring the temp directories and the scratch directory to reside on different physical hard drives.

Before you begin to sequence an application, you will want to shutdown other programs that may be running. Ensure no scheduled tasks are running, or will begin running, during the sequencing process. Disable the following programs before starting a sequencing job:

» Windows Defender
» Antivirus Software
» Disk defragmentation software
» Windows Search
» Microsoft update
» Any open Windows Explorer session

All components for the App-V Sequencer are available through the Microsoft Volume Licensing Site (https://licensing.Microsoft.com). The link is called “Application Virtualization Hosting for Desktops 4.5” and can be found under the Windows section. Once downloaded, extract the files or burn the ISO to a CD.

1. Using the media you just downloaded in the previous step, browse to. . . | App-V | Installers | Sequencer and click Setup.exe.

2. The setup wizard prompts you to install the Microsoft Cþþ Redistributable Package, Microsoft MSXML, and Microsoft Application Error Reporting if they are not already installed. Click Install.

3. Once the prerequisites have been installed (or if they were already installed), you are taken to the Welcome page for the Application Virtualization Sequencer. On the Welcome page click Next.

4. Read and accept the license agreement, and then click Next. Doing so takes you to the Setup Page. Leave the installation path at its default setting and click Next.

5. Click Install to begin the installation of the App-V Sequencer.

6. When the installation completes, click Finish. The Sequencer will now start.

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

App-V SYSTEM REQUIREMENTS You will notice the system requirements for the App-V Sequencer and Client are very similar to a typical end-user workstation.

➤ App-V Sequencer Requirements
o Processor—IntelW PentiumW III, 850 MHz or faster. The sequencing process is a single-threaded process; it does not take advantage of dual processors.

o Memory—256 MB RAM or greater. A 500 MB page file is recommended.

o Hard drive—Two physical drives, 20-GB minimum each. (Install the operating system and local applications on one drive, and use the second drive as the target for your virtual applications.) It is recommended your disk drives should be at least three times as large as the largest application you will sequence. If you have only one hard drive, you must use at least two NTFS volumes to partition it.

o Operating system (this must be the same as the clients)—The Sequencer runs on the following operating systems:
- Windows XP Professional (SP2 or SP3)
- Windows Server 2003
- Windows Vista
- Windows Server 2008 with Terminal Services
- Windows 7

App-V Client requirements
Now we will discuss two App-V client requirements: App-V Desktop Client and App-V Terminal Services Client.

App-V Desktop Client
» Processor—See recommended system requirements for the operating system you are using.
» RAM—See recommended system requirements for the operating system you are using.
» Disk—30 MB for installation and 4096 MB for cache.
» Windows XP Professional (SP2 or SP3) 32-bit
» Windows Vista RTM/SP1 (Business, Enterprise, or Ultimate) 32-bit
» Windows 7

The following software prerequisites are installed automatically if the setup.exe method is used. For setup.msi install program, these must be installed first. Microsoft recommends using setup.exe.

» Microsoft Visual Cþþ 2005 SP1 Redistributable Package (_86)—For more information about installing Microsoft Visual Cþþ 2005 SP1 Redistributable Package (_86), see http://go.microsoft.com/fwlink/?LinkId¼119961.

» Microsoft Core XML Services (MSXML) 6.0 SP1 (_86)—For more information about installing Microsoft Core XML Services (MSXML) 6.0 SP1 (_86), see http://go.microsoft.com/fwlink/?LinkId¼63266.

» Microsoft Application Error Reporting—The install program for this
software is included in the Support\Watson folder in the self-extracting
archive file.

App-V Terminal Services Client
» Processor—See recommended system requirements for the operating system you are using
» RAM—See recommended system requirements for the operating system you are using (also depends on the number of users and applications)
» Disk—30 MB for installation and 2 GB for cache
» Windows Server 2003 (Standard, Enterprise, or Datacenter, SP1 or later) 32-bit
» Windows Server 2008 (Standard, Enterprise, Datacenter) 32-bit
» Windows 7

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

WHAT IS AN APP-V PACKAGE? An App-V package is the next generation of an application installation. Apart from some specialized scenarios, most applications prior to the introduction of App-V were simply “installed” on a user’s workstation and the state of the installation remains largely static unless the user or their network administrator choose to force the application to upgrade,
update, etc. An App-V package is much more dynamic in that it can be
custom designed to

» Reside completely on a user’s workstation
» Partially on a user’s workstation and partially on a server
» Completely on a server only allowing access to the application from the user’s workstation
» And many variances in-between.

This approach allows you to efficiently maintain an App-V package. For example, an App-V package can be designed to install completely on a user’s workstation and still regularly “check-in” to the App-V infrastructure to look for updates, and then apply those updates in the background without impacting the user’s experience of the application.

Isolating an application addresses application compatibilities that otherwise would make it impossible to run two applications on the same workstation. An example of this is two different applications, each requiring a different version of the Java runtime. Prior to App-V, installing both applications on the same desktop caused pain and frustration. App-V allows you to package an application together with its prerequisites, and then stream the collective package to a workstation without the need to actually “install” anything on the user’s workstation. You can do this for any or all applications, including two different versions of the same program.

Application Virtualization Sequencer
The Sequencer is a wizard-based tool; App-V administrators will come to
use and appreciate more than any other function in the App-V world. The
Sequencer is used to create App-V sequenced applications and produce an
application “package.” A package consists of several files, including

» A sequenced application (.sft) file
» Open Software Description (.osd) “link” files
» Icon (.ico) files
» A manifest xml file that can be used to distribute sequenced applications with electronic software delivery (ESD) systems
» A project (.sprj) file

The Sequencer can also be used to build Windows Installer files (.msi) for deployment to clients configured for stand-alone operation. The .sft, .osd, and .ico files are stored in a shared content folder on the Management Server and are used by the App-V client to access and run sequenced applications.

Application Virtualization Client
The App-V Client is required on endpoint devices receiving applications from the App-V environment. It allows for management of package streaming on the client device; such as how much local cache is to be used by the application. It also manages how often the application checks in for any changes, and any user-specific configuration settings.

Source of Information : Elsevier-Microsoft Virtualization Master Microsoft Server Desktop Application and Presentation

Code Library

Categories