Explaining Server App-V

Taking a quick approach, Server App-V is a technology that enables the virtualization of server applications, removing the dependency of a server application in a specific Windows Server instance (whether that instance is running in a virtual machine on directly on hardware).

Server App-V represents an evolution of Desktop App-V. This technology includes other aspects in the application virtualization approach, which fits more accurately in servers platforms; for example:

• Server App-V works with a Virtual Environment, but this interacts with the operating system and vice-versa. For example: Virtual services are visible to the OS.
  This is particularly important since we can use monitoring tools, such as System Center Operations Manager, to monitor the functionality of our virtual server application.

• In the sequencing process of an application, Server App-V also detects and includes in the package, several additional components that Desktop App-V does not. The Local Users and Groups that the application might create, IIS applications, COM+ and DCOM components, WMI providers, performance counters and all other components Desktop App-V detects and includes within the package.

• Server App-V appears as a “Private Cloud” concept in the way to offer “Software as a Service” (SaaS) and/or “Platform as a Service” (PaaS). This is the ability to deploy software or a platform without requiring installing it.
  Even though we usually use the concept of “application” in the same way as “software”, the term “SaaS” in Server App-V does not represent the entire scope of the platform. Server App-V includes the possibility to provide “as a Service” platforms like database engines or in the near future Exchange or SharePoint.

• One of the main goals of Server App-V is to have a predictable and repeatable way to deploy server applications.
  Some of the common problems we usually find in organizations are that moving platforms from testing or pre-production to production is never an easy ride – often several inconsistencies might be found.

• Server App-V includes the possibility to separate the configuration of the server application, in order to accomplish scalability in the deployment process. This way, we can have the server application package with the configuration “A” deployed in one server and the server application package with the configuration “B” deployed in another server.

• Server App-V also handles state management operations. This is accomplishing by backing up the current state of an application and restoring it in a separate instance of the application.

• There’s no more streaming processes in Server App-V. Client agents still exist but the interaction with the Server App-V packages can include using just PowerShell Cmdlets or using System Center Virtual Machine Manager 2012.

Windows Azure represents Microsoft’s “Public Cloud”, from which we can use a remote platform to handle software (SaaS), services/platforms (PaaS) and infrastructure (IaaS).

At the moment, Windows Azure is available only to selected clients by a closed beta.

Server App-V is not compatible just yet with the worker roles in Windows Azure, but it will be in the near future.

Reviewing Applications Supported by Server App-V

In this current version, with System Center Virtual Machine Manager 2012 in Release Candidate, Server App-V is oriented to business applications (Dynamics and Web Apps mainly) but it is possible to include others.

Some of the features supported by Server App-V are the following:

• Windows Services: Server App-V includes the possibility to virtualize Windows Services in a different approach than the one we’ve seen in Desktop App-V. With Server App-V, the service is installed and placed in the OS as a normal installation of the server application. This way we can monitor it as any local service.
• Web applications hosted in IIS: We can virtualize web applications entirely (web sites, virtual directories and application pools) on IIS 6, IIS 7 and IIS 7.5.
• WMI: Server App-V Sequencer also captures the WMI providers and/or classes created during an installation.
• SQL Services Reporting Services: Even though SQL Server engine is not supported for virtualization, the applications that install SQL Services Reporting Services (SSRS) are supported.
• COM/DCOM/COM+ objects: These components are registered in the deployment process, this way other applications in the server can access them.
• Local users and Groups: If the application is creating users and/or groups during the installation, the Server App-V Sequencer captures it and maintains, including SID, for next deployments.

Some of the considerations about applications not supported are the following:

• We cannot capture Windows Server Roles. Deploying these kinds of roles is a task performed by SCVMM 2012.
  • We can virtualize Web Apps but we cannot virtualize IIS.
  • In IIS, it is supported to virtualize Web Apps and virtual directories.
  • “Web Deploy” tool is used in this process of deploying Web Apps. For more information about Web Deploy take a look to the following link: “Web Deploy 2.0” http://www.iis.net/download/webdeploy.
• SQL Server is not supported in this version. SQL Server Express is, but there’s no official guideline on how to capture it by Microsoft.
• Device drivers are still not supported in Server App-V.
• Not supported in this release but are priorities for next version: SharePoint and Exchange Server roles.

An important part of understanding Server App-V is to differentiate it from Desktop App-V; in the following section we will review the basics difference between these two platforms.

Differentiating between Server App-V with Desktop App-V

Server App-V and Desktop App-V work similarly, but there are some important differences between the two and we must understand them in order to analyze if Server App-V fits in our environment.

Quick Overview to the Sequencing Process in Server App-V

The sequencing process in Server App-V is quite similar to the process we already know in Desktop App-V. Prior to working with the Server App-V Sequencer, we must remember the basic differences we’ve talked about in the Desktop App-V experience: Isolation, Server App-V packages are not meant to co-exist in the same OS.

We must keep in mind that most of the common operations and best practices are included, like:

• Use the same base OS in the Server App-V Sequencer and client machines. This particular “best practice” appears as a default requirement in Server App-V.
  When a Server App-V application is sequenced, includes by default the roles and features enabled in the sequencer and set those as requirements for the Server App-V Clients.
  If we think about it, makes sense, since we are using server applications which interact with several OS components. Any OS inconsistency should lead us in Server App-V applications malfunctions.
• If possible, sequence your application to a Q:\ drive.
• Use Virtual Machines and snapshot capabilities with the Server App-V Sequencer. And, of course, always sequence a new application with a clean OS image.

Some Other Topics

In Chapter 9 of the “Microsoft Application Virtualization Advanced Guide” we will cover detailed topics and step-by-step processes included in Server App-V. Some additional concepts to review are the following:

• Enhanced details of supported applications in Server App-V.
• Understanding SCVMM concepts like Service Templates and Private Clouds.
• Reviewing Server App-V and SCVMM 2012 integration.
• Sequencing Server App-V applications, taking MySQL as an example.
• Customizing Server App-V packages.

• Deploying Server App-V applications, using SCVMM and PowerShell deployment.

The book is available for pre-order in Pack Publishing website.

I hope you enjoyed the article!

The “Microsoft Application Virtualization Advanced Guide” represents my second App-V book; the previous one “Getting Started with Microsoft Application Virtualization 4.6” was developed a year ago with the basic guidance and step-by-step to get IT administrators started with App-V. This new book is currently available for pre-order in Packt Publishing website (paperback and eBook versions) and hopefully soon enough in Amazon’s (including a Kindle edition).

This advanced book will cover the necessary guidelines and step-by-steps processes to dominate App-V. Starting with detailed description of its architecture, including some rare advanced topics, and moving through the instructions to implement those advanced guidelines. Here’s an overview of the areas we will cover:

• Perform sequencing in complex environments including scenarios where App-V is normally not supported.
• Deploy applications in complex scenarios, including the use of Providers Policies to enforce licensing and other company’s policies.
• Get hands on in how to implement the scripting process within App-V applications and also review how to use App-V command lines.
• Troubleshoot App-V, covering the installation process of this platform, but also normal sequencing issues and deployment problems delivering applications.
• Scale-up App-V implementations by using failover and load balanced scenarios.
• Review App-V integration with VDI (Virtual Desktop Infrastructure) and Remote Desktop Services.
• Integrate App-V with System Center Configuration Manager (SCCM) 2012.
• Understand the new approach appearing in SCVMM 2012 with Server App-V to virtualize servers’ applications.
• Examine 3rd party tools available in App-V to complement your implementation.

Note: We will not cover the topics reviewed in the “Getting Started” book. This version assumes that we’ve already implemented and used Microsoft App-V; presumes that we are looking to optimize our implementation and learn advanced concepts.

And as an exclusive note, here are the chapter’s names to be included in this book:

1. Taking a Deep Dive into App-V.
2. Sequencing in Complex Environments.
3. Deploying Applications in Complex Environments.
4. Handling Scripting and App-V Command Lines.
5. Troubleshooting App-V.
6. Scaling Up App-V Implementations.
7. Integrating App-V with Virtual Desktop Infrastructure (VDI).
8. Integrating App-V with System Center Configuration Manager (SCCM) 2012.
9. Integrating Server App-V with Private Clouds.
10. Appendix A: Reviewing App-V Microsoft and 3rd Party Tools.

In this book, which will contain approximately 450 pages total, I had the great pleasure to work again with Packt Publishing and the same crew of App-V experts that made important contributions in my first book: Aaron Parker, Kevin Kaminski and Nick Källén.

Stay tuned for more news about the book and hopefully a new giveaway copy to all my blog readers! :)

I’ve had the great pleasure to present in October, once again, in one of the main Microsoft events in Argentina, Code Camp 2011. This time with two new tracks: “Desktop of the Future” and “Standardizing Windows Server 2008 R2 images”.

As I mentioned earlier in older posts of mine, Code Camp is an event organized and developed by Microsoft Academics which is held in some important universities of Buenos Aires, this time the selected institution was, as a few years back, Universidad Abierta Interamericana (UAI).

The event contains over 50 tracks presented by students and professionals not only as IT but also as developers. Some of the main topics this year were: Windows Azure, Cloud Computing, SQL Server 2012, Mango and Windows Phone, XBOX and Kinect, VDI, Deployment solutions and so on.

Regarding my topics, the tracks were focused on Virtual Desktop Infrastructure (VDI) integrated with App-V; and a deep dive into Microsoft Deployment Toolkit (MDT) to automate Windows Server’s deployments.

Desktop of the Future

I’ve presented this session (the original Spanish name: “El Escritorio del Futuro”) with Emiliano Estevez, friend and colleague of mine in Algeiba IT where he works as the Services Director.

This track introduces Virtual Desktop Infrastructure (VDI) technology as a result for some current demands in today’s business. By reviewing some of the basic concepts of VDI, we’ve completed the main steps to prepare the Virtual Desktops infrastructure in our company using Hyper-V and Remote Desktop Services (RDS).

We’ve also introduced App-V as the main solution to optimize application management in virtual desktops scenarios, and also with the highly important “Shared Cache” feature to save a lot of money in storage. And finally we had a quick glance about Server App-V, the new technology included in SCVMM 2012 to virtualize server’s applications.

The presentation can be downloaded from this link.

Standardizing Windows Server 2008 R2 Images

This track (the original Spanish name: “Estandarizando Servidores Windows Server 2008 R2”) was presented with another colleague in Algeiba IT, Alejandro Barrionuevo, who’s working as an IT Consultant.

In this session, we’ve reviewed with Alejandro the main benefits of using Microsoft Deployment Toolkit (MDT) 2010, combined with other free tools, to standardize and automate the deployment for Windows Server 2008 R2 OS. We had a quick look about understanding the Solution Accelerators from Microsoft.

We had a detailed look about the process involved in this automation, including some practical demos about using MDT 2010 task sequences, scripts and also editing MDT files used in the deployment process for a complete automated deployment.

The presentation can be downloaded from this link.

I’m introducing a new set of articles in my blog: Interview sessions with some colleagues and technology geeks. In this first article I had the great opportunity to start a quick question and answer session with one of the geekiest App-V guys around the world: Aaron Parker.

Aaron made an important contribution in my App-V book “Getting Started with Microsoft Application Virtualization 4.6”, not only as an official reviewer but with his blog which contains several interesting articles about virtualization using a valuable approach.

You can find more about Aaron following him on Twitter: @stealthpuppy.

Here’s the Q&A session I had with Aaron:

1. To start with the interview, can you give us a quick synopsis about yourself and your experience?

I am a desktop and application virtualization and delivery architect currently working for Kelway in the UK. Previous to my current role I’ve been working on various application virtualization, user virtualization and desktop deployment projects around London. Before coming to the UK, I worked for various VARs in my native Australia where I was doing mostly Citrix XenApp and desktop deployments.

2. In all the experience you have regarding virtualization, how could you explain application virtualization for someone who had never heard about App-V or any other similar platform?

Application virtualization is really just another application deployment method. Where it differs from traditional deployment methods is its ability to make the desktop more dynamic rather than a monolithic blob that we’ve had to deal with in the past. Application virtualization allows us to deliver applications on demand and to users, where ever they are, rather than physical devices.

3. Why do you think that application virtualization did not appear massively just yet in organizations?

Many organisations still look at desktop deployment the old way, i.e. create a static, monolithic SOE, and have failed to recognise the benefits in approaching desktop virtualisation in layers. Small organisations that are still using imaging products such as Symantec Ghost and have stuck with OEM licenses, may find that change can be costly – if their current approach works, why change?

It has also been disappointing to see a lack of support from application vendors for application virtualization in general. Companies such as Attachmate should be applauded for supporting their products under App-V. Momentum requires application vendors to do more than they have currently (which is next to nothing).

Note:
In case you are wondering why there are terms like “organizations” and “organisations” in the same text, this is regarding the American and British spelling differences; both are valid.

4. Can you name the top reasons of why application virtualization must be considered in any organization?

If you’re interested in creating a user-centric model of your computing resources (both hardware and software) then the desktop needs to be broken down into layers to make it dynamic. Application virtualization is just one of those layers. A dynamic desktop is more flexible and allows us to deliver applications based on identity and context.

5. Do you think that Virtual Desktop Infrastructure (VDI) + Application Virtualization represents the future of desktops?

In the short term – yes, But I also think that VDI (as in a hosted virtual desktop based on a Windows client OS) has limited use cases – it suits only 10 to 20% of users. Coming from an SBC background, I know that I can deliver a desktop from the data centre, cheaper, faster and more efficiently with SBC (TS, RDS, Citrix XenApp, Quest vWorkspace etc).

In the long term – no. Windows as we know it today won’t be around forever. It will evolve along with new application architectures that will render today’s desktop model obsolete.

6. With all the possibilities regarding application virtualization (App-V, ThinApp, XenApp, and so on), do you think that there’s one among all that stands out or depends on each scenario?

Absolutely depends on your scenario – the choice of application virtualization product is often not a technical one (as much as we’d like it to be).

7. Regarding Microsoft’s App-V, which are the features included in the latest version that you like the most?

The 4.6 SP1 Sequencer has some great features around sequencing workflow, recommendations before sequencing, displaying what was excluded post sequencing and sequencing templates. These features help to produce better quality packages.

8. Even though there’s no official word from Microsoft, which are the features that you think may (or want to) include the App-V 5.0 version?

I would like to see isolation as something that we could turn off and on. Isolation of a virtual application is great for the majority of cases; however being able to remove isolation as a per-package behaviour would allow use to virtualise many more applications.

I hope you enjoyed this article and I’m pretty sure I’ll get back with some more interviewers and Q&A sessions.

Not so much for a recent, but still I think represents as great news: The App-V book, “Getting Started with Microsoft Application Virtualization 4.6” is available in Kindle version, in Amazon site of course.

So for all those geek Kindle owners (I’m not one, unfortunately) there’s a chance to take a great look to my App-V book using Amazon’s device.

And seems that the availability of the Kindle version also keeps pushing the popularity of the book, since in Amazon.com is ranked as a top seller book in Microsoft section.

#83 in Amazon.com:

Also in Amazon.co.uk (#58):

A few weeks ago I had the big pleasure to visit the US (New Jersey and New York), courtesy of a company which invited me to coach an App-V training course in their facilities. I had a wonderful experience and in this post I would like to share with you the technical and non-technical approach, experience and more I had in those 8 days.

The App-V training course and workshop intended to provide not only all the basic knowledge regarding App-V, but to also give a complete guidance and step-by-step process in App-V installation, deployment, sequence and maintenance.

The Request

The original request appeared in my inbox in 2010, the idea appeared simple right away, they’ve said:

“We are looking for an application virtualization solution for our main company app; we are very interested in App-V but we have no experience handling this technology. We need a complete overview of the platform, understand how to use it and apply it in our scenario”.

So, we’ve started talking about their expectations, getting a deeper understanding about the company app, the scenario where it should be deployed, etc.

App-V Training Course Program

After a bunch of e-mails and phone calls about getting all the information about the scenario, application involved, and general expectations, the training course program looks something like this:

Here’s a detailed look about each day approach:

Day 1 – Overview and Preparing the Environment

• Since the attendees had mix knowledge about general IT concepts, I decided to take a quick look about some key components: Active Directory, IIS, SQL Server, virtualization concepts, cloud service models, etc.
• Understanding App-V components, features, benefits and implementation models.
• Prepare the entire environment in the “hands-on” section of the day. Full-Infrastructure
• Reviewing automation techniques for deploying the App-V client.

Day 2 – Sequencing Applications

• Getting started with the sequencing process, understanding the phases involved and best practices.
• Sequence simple applications to understand sequencing.
• Deep review about company’s application: Environment, requirements, restrictions, integration with the OS and other applications, common use cases, etc.
• Start with the sequencing process of the company’s application.
• Publishing and deploying App-V packages to client machines.

Day 3 – Advanced Options in Sequencing

• Deeper look in the sequencing process. Handling Feature Block 1, security descriptors to protect some files within the App-V package.
• Troubleshooting applications sequencing and deployment process. Understanding log files and common errors.
• Reviewing Dynamic Suite Composition. Even though company’s application does not require any other package, the concept of interconnecting virtual apps is still important.
• Handling Active Upgrade. Reviewing different type of modifications in an existing package: Editing or upgrading.

Day 4 – Deployment Methods

• Reviewing how to size and selecting the environment for a desired App-V implementation.
• Understanding the RTSP/S and HTTP/S streaming. How to fit each in the desired scenario.
• Since the application usage required the scenario with users connecting from different geographic places to a same server, we’ve reviewed necessary steps for publishing App-V to External networks outside the organization.
• Step-by-step processes for implementing HTTP/S streaming.
• A complete Hands-On for App-V Standalone scenario.

Day 5 – App-V and RDS | Securing the Environment

• Understanding the Remote Desktop Services, RDS, role in Windows Server 2008 R2 (formerly known as Terminal Services).
• Reviewing RemoteApp. Similarities and differences with App-V; pros and cons; and understanding when RemoteApp is best suited.
• Hands-on using company’s application with RemoteApp.
• How to integrate App-V into an existing Remote Desktop Services scenario.
• Reviewing Virtual Desktop Infrastructure (VDI) scenarios, integration with App-V and the shared cache feature.

The Result

The result of the course / workshop was great, the attendees had the chance to understand and implement App-V in their scenario and I could interact with an interesting requirement and deployment.

[geekyComment] Not only I enjoyed preparing and coaching this App-V workshop [/geekyComment] thanks to the great hospitality I also had the chance to visit New York City and a bunch of touristic places.

Just hangin’ in Times Square :)

The contest ended in February, but I didn’t have the chance to publish the winner in my blog so I decided to take a moment and share with all blog readers the happy winner for the App-V book.

Ian Walters from Webster, NY received a few weeks ago the book and kindly is sharing with us a quick pic. Thank you Ian!

For all those who didn’t get the chance to win this time, remember that the book is still available in the following sites:

• Packt Publishing
• Amazon.com
• Amazon.co.uk
• Lehmans

Thank you all for participating!

As a celebration since my App-V Book: Getting Started with Microsoft Application Virtualization 4.6 has just been published, I want to give away a free paperback version among my blog readers.

Here’s the deal:

• All you need to do is email me at augusto@augustoalvarez.com.ar with the subject: “App-V Book”.
• Include in the email body your full name plus the address where you would like for us to send the copy.
• I’ll close up the contest on February 25. All the emails sent until that date will be included in the election, which will be completely random.
• I’ll notify the winner in the following days and we’ll ship a free copy of “Getting Started with Application Virtualization 4.6”.

For more information about the book and the free chapter available for download, check this last post of mine.

To avoid any problems, here are some disclaimers:

• Only one email by person will be included. Do not use different mail accounts to participate several times.
• Emails that don’t include person’s full name and address will not be considered valid.
• We’ll cover the expenses regarding shipment but we are not responsible for extra fees or taxes other countries may include in the package.

Remember that the book is available in the following stores: Packt Publishing; Amazon.com; Amazon.co.uk and Lehmans.

Good luck!

My book “Getting Started with Microsoft Application Virtualization 4.6” has been finally published by Packt and the pre-order waiting game is over :)

This App-V book is available in the following stores and in the following links:

• Packt Publishing
• Amazon.com
• Amazon.co.uk
• Lehmans
• Bookware

Sample Chapter

Also, as a preview of this book, you can download a sample chapter for free!

Chapter 7: Managing Dynamic Suite Composition (DSC)

This chapter provides a complete overview and detailed procedure for using Dynamic Suite Composition in App-V 4.6. A complete explanation about DSC and how these virtual dependencies are being handled by App-V, naming also some considerations and restrictions about its implementation.

App-V Book Overview

As a quick overview of the book, here are some of the topics this book will provide:

• Understand App-V components and its architecture.
• Explore the new and important features of App-V 4.6.
• Set up App-V Management and Streaming Servers to facilitate the centralized management of applications.
• Install App-V Sequencer, Desktop Client, and Remote Desktop Services (Terminal Services) Client to set up the entire environment for application virtualization deployment.
• Prepare and configure different models and implementations of App-V.
• Sequence and publish simple applications, as well as highly complex applications such as Microsoft Office 2010.
• Understand and implement Dynamic Suite Composition (DSC) for interconnected virtual applications.
• Integrate App-V with System Center Configuration Manager (SCCM) to optimize the infrastructure.
• Secure the App-V Environment to ensure safe communication between the server and the clients.
• Install and configure App-V for Remote Desktop Services (Terminal Services) to simplify application deployment and integration.

For more information, check this previous post of mine.

More News Coming Soon

I’m hoping that within the following weeks I’ll giveaway one App-V book (paperback version) among blog readers, so stay tuned!

Also, I would like to share some special thanks included in this book but definitely worthwhile to mention them in this post:

• PacktPublishing crew
• Aaron Parker
• Kevin Kaminski
• Nicke Källén

Finally the writing process is complete, and my App-V book is just around the corner: “Getting Started with Microsoft Application Virtualization 4.6”. The book is available for pre-order in Pack Publishing website and in Amazon.

An overview about what we will cover:

• Publish, deploy, and manage your virtual applications with App-V.
• Understand how Microsoft App-V can fit into your company.
• Guidelines for planning and designing an App-V environment.
• Step-by-step explanations to plan and implement the virtualization of your application infrastructure.

As an exclusive note, here’s the list of chapters that will be included (chapter’s name could vary in the final release.):

1. Introducing Application Virtualization in a Virtualized World.
2. Understanding App-V Architecture.
3. Preparing your App-V Environment and Installing App-V Management Server.
4. Deploying the App-V Sequencer, App-V Desktop Client and Streaming Server.
5. Taking the Initial Steps in the Sequencing Process.
6. Sequencing Complex Applications.
7. Managing Dynamic Suite Composition.
8. Integrating App-V with System Center Configuration Manager 2007 R2.
9. Securing your App-V Environment.
10. Reviewing App-V for Remote Desktop Services (Terminal Services).

Here’s also a summary about what you will learn in this book:

• Understand App-V components and its architecture.
• Explore the new and important features of App-V 4.6.
• Set up App-V Management and Streaming Servers to facilitate the centralized management of applications.
• Install App-V Sequencer, Desktop Client, and Remote Desktop Services (Terminal Services) Client to set up the entire environment for application virtualization deployment.
• Prepare and configure different models and implementations of App-V.
• Sequence and publish simple applications, as well as highly complex applications such as Microsoft Office 2010.
• Understand and implement Dynamic Suite Composition (DSC) for interconnected virtual applications.
• Integrate App-V with System Center Configuration Manager (SCCM) to optimize the infrastructure.
• Secure the App-V Environment to ensure safe communication between the server and the clients.
• Install and configure App-V for Remote Desktop Services (Terminal Services) to simplify application deployment and integration.

This book represents a lot of months of hard work and I’m hoping it will cover all of the common topics for any IT professional who wants to start working with Microsoft Application Virtualization, understanding the basic concepts, and receive the guidelines for installing, configuring and deploying the entire App-V environment, and of course achieve the abilities to master Application Virtualization in complex scenarios.

The book will be available in the paperback as well as in eBook version.

The official release date for the book is not available just yet, but you’ll be hearing the confirmation soon enough; including the special acknowledgements for a lot of people who I had the chance to work with in the writing process of this book.

For more information and pre-order, access the detailed description for “Getting Started with Microsoft Application Virtualization 4.6”.

Other posts in this series:

Implementing App-V – Part I: Introduction to Application Virtualization

Implementing App-V – Part II: Choosing and Preparing the Environment

Implementing App-V – Part III: Integrating Clients

Ok, we had a good look about the entire App-V platform so far: Explanation about application virtualization and the components involved in App-V (Post I); installation of the App-V Server including some troubleshooting tips (Post II); integrating App-V client components, testing the default application and some troubleshooting about this process as well (Post III).

Now it is time to sequence some real applications and deliver them to clients. As always, I’m going to start with an easy one, so you can see all the tricks involved to get the things working. But first, we must prepare the App-V Sequencer machine.

As we’ve seen in Post I, the main component involved in the sequencing process is the App-V Sequencer.

Sequencer Quick Checklist

• Use the same base operating system for both, Sequencer and Target (client) machines. Microsoft does not support using different type of OS between these two. Off the record: I’ve used many applications that worked perfectly when this requirement was not fulfilled.
• The Sequencer machine must have a second partition available. The common use for this one is to assign the Q:\ drive letter.
• Sequencer and Client machine must have the same Windows Installer version.
• In the Sequencer machine ensure that the directories %TMP%, %TEMP% (user temporal data) have sufficient space, since the application use this directory to store temporal sequencing data.
• Before sequencing an application you should close all other programs, including Antivirus.
• As a recommended best practice, use VirtualPC or any other type of virtual machine for the App-V Sequencer. Combine this using snapshots or differencing disks to always have available a fresh OS to deploy applications. 

For more information about the sequencing process and requirements, check the Sequencing Guide from Microsoft and also the Sequencing Best Practices.

App-V Sequencer Setup

Once you’ve checked all the requirements mentioned above, the installation process is quite simple and straight forward.

App-V Sequencer main window:

Sequencing Applications Step-by-Step

As I mentioned earlier my first pick will be a simple application, this will allow us to get familiarized with the sequencing process. I want to start showing the App-V compatibility with some non-Microsoft applications, I’ll be using Mozilla Firefox.

1. In the App-V Sequencer program window select “New Package”.

2. A new wizard will start, select the package name “Firefox”.

3. In the next window you are ready to get started with the applications installation and capture, so you can start creating the installation folder in the Q:\ drive.

Within this folder, the application will store all the program files and the sequencer will use them to package the application.

Note: You don’t need to place the installer inside this folder.

4. Click on “Begin Monitoring” to start the installation process.

5. The capture process will start by selecting the folder in the Q:\ drive.

6. Once you’ve selected the folder, the virtual environment will start to load, wait for the “Monitoring started. Please begin installation” message appears.

7. Locate the installer and start the installation process.

8. In the installation process, the main step will be in the destination folder option that the program use to place the program files. Select the folder you’ve selected to be monitored. In my case: Q:\Firefox.

9. Once the installation is complete and you verified that the program was installed correctly, get back to the sequencer window and click on “Stop Monitoring” and click on “Next”.

10. In the next window you can add some more files inside the package. This can help you if you are using customized applications, that need to load local files.

In my case I don’t need any.

11. In the next window, the sequencing process detects the applications that compose Mozilla Firefox, in my case the Firefox standard app and the Firefox safe-mode.

You can add new ones, remove the detected and modify the components involved: File type associations and icons.

For every application shown here, we will need to make a small change. Click on each application in the right list, and select the “Edit” option. In the “OSD File Name” you will probably see a long name, like “Mozilla Firefox 1.9.1.3523.osd”.

You need to change this one removing all the spaces in the name, like “Firefox.osd”.

Change this in all applications involved and click on “Next”.

12. The next step is optional, where you can launch the applications for a final check that they are working properly. Click on “Next”.

13. Sequencing process is complete. Click on “Finish”.

14. The package is ready for the final customization regarding the application deployment.

In the App-V Sequencer window, select the “Deployment” tab and change the Protocol option to “RTSP” (this will automatically change the Port to 554), and in the Hostname option select the name of the App-V Server, in my case “appv-server”.

In the Operating System list, you can add all the baselines where this application can become available. And note also the option to generate an MSI package, that you can use it with the App-V Stand Alone mode (explained in Post I of this series) and/or System Center Configuration Manager (SCCM) integration with App-V.

15. Before saving the package, you can explore other options within the Sequencer, like the registry files that are modified by the application.

Once you are done, click on save this package locally.

With the project saved, you can check on the files created and verify that the OSD files were not created with names composed by blank spaces.

Adding the Package to the Server

Now that the package has been sequenced and created, it is time to add it to the server.

1. Copy the files created in the App-V Sequencer to the “content” folder in the App-V Server.

2. In the App-V Server, open the App-V console. Right click in Applications and select “Import Applications”.

3. Select the SPRJ file for the Mozilla Firefox and click “Open”.

4. In the General Information window, accept the default options and click on “Next”.

5. In the “Published Shortcuts” select the shortcuts that the clients will have created.

6. In the “Access Permissions” select the group that will load this application. In my case, I’m using Domain Admins.

7. In the “Summary” window, click on “Finish”.

And now you have the application ready in your App-V Server to be deployed.

Testing the Application

After completing the importing wizard, the application is ready to be deployed in the client machines.

Access the client machine, and if you want to avoid the process of log-off and log-on to test it, locate the App-V Client console (C:\Program Files\Microsoft Application Virtualization Client\SftCMC.msc), select “Publishing Server” and click on “Refresh Server”.

The new icons will appear in the desktop or in the places you’ve selected.

Mozilla Firefox starting

Troubleshooting App-V Published Applications

The most common error about App-V applications I’ve experienced are regarding the firewall exceptions discussed in the Post III of this series. But, there’s also another problem that appears related to the package it self.

If the package that you’ve created, the OSD file name uses spaces between, like “Mozilla Firefox 1.9.1.3523.osd”:

Then most likely when you try to deploy this application, after importing it in the server, you’ll get these errors:

“The package requested could not be found in the system data store or the files associated with this package could not be found on the server”. “Error code: 4513CDC-1690150A-20000194”

To fix this, you’ll need to regenerate the sequenced application as shown above, editing the application information and remove any blank spaces in the OSD file name.

More Resources

• Microsoft Application Virtualization 4.5 Resource Kit Tools
• [Case Study] Sequencing Applications for Deployment at Microsoft
• App-V Sequencing Guide

Other posts in this series:

Implementing App-V – Part I: Introduction to Application Virtualization

Implementing App-V – Part II: Choosing and Preparing the Environment

Implementing App-V – Part III: Integrating Clients

Other posts in this series:

Implementing App-V – Part I: Introduction to Application Virtualization

Implementing App-V – Part II: Choosing and Preparing the Environment

Implementing App-V – Part IV: Sequencing Applications

We’ve already talked about Application Virtualization and some common scenarios (Post I), talked about the existing models in App-V and how to install the App-V Management Server (Post II); now it’s time to work with the App-V clients.

I was considering to not include this post and go directly to sequencing applications, but most of the errors and blocking issues that appear in App-V are related on not having a environment properly installed.

The process will start with the App-V Desktop Client installation.

App-V Desktop Client Installation

Select a client machine that will receive some of the sequenced applications and you shouldn’t have any problem with this installation, pretty straight forward:

1. Double click on the installer and most likely you will be needing to install a few components before starting.

2. The wizard starts and click on “Next”.

3. Accept the License Agreement.

4. Select your option for Microsoft Update.

5. Select “Custom” installation option.

6. Accept the default installation path.

7. Data Location, the default preferred drive letter by convenience is used the letter “Q” (avoiding to collide with possible network drives).

8. Then you can select the cache size that the client machine will use. Every time that the client downloads applications, it will use the local cache for every time the application needs to be loaded again in the session. You can use the default option provided.

9. On Runtime Package Policy Configuration use the default options adding the “On Publishing Refresh” option inside “Automatically Load Application”.

10. On "Publishing Server” complete the options used for your App-V Server. And since I won’t be using SSL for the communication, I’m selecting the type “Application Virtualization Server” and “Port” 554.

11. Click on “Install” and we are ready to go.

Testing the Default Application

As we’ve seen it before, once you install the App-V Management Server a default application is installed.

We are going to use it to validate that our environment is ready to go and start sequencing applications. Unfortunately you will need a few steps before publishing the application:

1. First of all, re check the configurations mentioned in Post I of this series:

- Ensure that the Application Management Server service has started.

- The content folder (C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\content\) must be shared with proper permissions: “Everyone” the “Read & Execute”, “List folder contents” and “Read” access.

- If you have the firewall enabled, ensure that you enable the exceptions for inbound connections with the programs sghwdsptr.exe and sghwsvr.exe. Both located in “C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\bin\”.

To make a first quick check about the connectivity, you should always start using “telnet appv-server 554” to ensure that the ports are open between the hosts.

What Happens If I Don’t Complete The Requirements?

If any of those are not in place, the error code that you should be receiving when you try to access an application is: “The Application Virtualization Client could not establish a connection to the Application Virtualization Server” “Error code: 4513CDC-19D06A0A-10000004”.

And in the Event Viewer you’ll see a bunch of warning messages and one error: “The Application Virtualization Client could not connect to stream URL ‘RTSP://appv-sequencer:554/application‘” along with the same error code.

2. With all that in place, time to get the application ready. Access the App-V Management console, open the Default Application Properties. In the General tab, the OSD and Icon path must be using a UNC path, like in my case: “\\appv-server\content\”.

3. Shortcuts tab will let you decide where you want to insert the client’s shortcuts.

4. Access Permissions: Here you can select all the domain groups that will have access to this application.

5. Edit the DefaultApp.osd file that is stored within the content folder mentioned. Look for the “Implementation” area and replace the name of the server using the current name of the actual server.

6. Login to the client machine using credentials that belong to the group you just gave access to the application. You will see the Default Applications shortcuts already in place, double click the shortcut.

And there you have it, your environment is ready to receive and launch applications.

Note:

Remember that by default, the applications are refreshed once the user logins to the client computer.

If you want to avoid this process, in the client computer access “C:\Program Files\Microsoft Application Virtualization Client” folder and double click “SftCMC.msc”. Inside “Publishing Servers” right-click the name of the server and select “Refresh Server”.

With that, any update on the applications published should be shown in the client.

In a few days more, I’m publishing the fourth part of the series: sequencing applications.

Other posts in this series:

Implementing App-V – Part I: Introduction to Application Virtualization

Implementing App-V – Part II: Choosing and Preparing the Environment

Implementing App-V – Part IV: Sequencing Applications

Other posts in this series:

Implementing App-V – Part I: Introduction to Application Virtualization

Implementing App-V – Part III: Integrating Clients

Implementing App-V – Part IV: Sequencing Applications

After the first post about App-V and application virtualization technologies we had a nice review about the platform. So, if you feel like this type of technology can add some value to your organization, let’s start playing around.

Before you begin, let’s talk about the available models in App-V that will help you choose the strategy according to your platform. The architecture is prepared to support almost any scenario, including low-bandwidth branches offices or even offline deployments.

App-V Models

Stand-Alone Mode

This is the minimalist mode of App-V with no infrastructure required but the machine that packages the application, “sequencer” from now on, and the App-V Desktop Client.

Sequencing the application adds all the necessary files into one package and generates an MSI file that you can use to deploy manually, by group policy or using SMS/System Center Configuration Manager.

This mode is focused when you have several offline users (do they even exist at this point?), or when you have already SCCM deployed and you don’t want to add a App-V Server.

Streaming Mode

This model it is also focused on platforms that do not want Management Servers. The components present here are the streaming server, sequencer to package applications and the App-V client.

The Streaming Server as the name says it, streams the applications to the clients on demand. The server does not use a SQL database, the permissions are set and maintain based on ACLs (access control lists).

You can use it on low-bandwidth links like branch offices to optimize the application deployment.

Full Infrastructure Model

The full model contains the full set of components in App-V: Management Server, Sequencer, Streaming server and App-V Client. In most cases, the streaming server it is completely optional since the application streaming can be executed from the Management Server, delivering applications on demand to users.

Using a Management Server will add the applications shortcuts publication within the process of deployment. And includes more features for reporting, using a SQL database.

Applications in this model are associated to security groups in Active Directory. And you can also manage centrally the applications licenses.

We are going to focus this set of posts in a Full Infrastructure Model, using a Management Server, Sequencer and a App-V Desktop Client.

Enough with the explanations, let’s get to work.

Installing App-V Management Server

The process it is a little tricky, but we’ll try to set clear all the necessary requirements before running the installation wizard.

Pre-Requisites

This is the list of minimum requirements:

• Windows Server 2003 SP1 or superior
• IIS 6 role installed with ASP.Net
• .Net Framework 2.0
• MMC 3.0
• SQL Server 2005 Express SP2

Before proceeding with the installation take a closer look to what are the SQL and IIS configurations necessary that we are going to review next.

Here’s the environment that I’ll be using:

• Active Directory and DNS platform in place.
• Windows Server 2008 (32-bit)
• IIS 7 role installed with ASP.Net
• SQL Server 2005 Express SP2.

SQL Special Considerations

The SQL Express can be installed with the default options, but, as I mentioned it before, there are a few SQL configurations that needed to be set before the App-V installation process:

1. Open SQL Server Surface Area Configuration Tool from the SQL Server Start Menu folder.

2. Click on Surface Area Configuration for Features.

3. Inside of “CLR Integration”, click the option for “Enable CLR Integration”.

4. Inside of “OLE Automation” click “Enable OLE Automation”.

5. Close “Surface Area Configuration for Features”.

6. Click “Surface Area Configuration for Services and Connections”.

7. Inside “Remote Connections” select “Local and Remote Connections” and set “Using both TCP/IP and named pipes”.

8. Restart the SQL Server services to apply all changes.

IIS Considerations

Since I’m using Windows Server 2008 and IIS 7 for the Management Server installation, there are a few considerations about it.

• Install ASP.Net feature with all pre-requisites.
• Windows Authentication feature enabled.
• IIS 7 Management Tools with Management Service and IIS 6 Management Compatibility features installed.

Step-by-Step App-V Management Server Installation

One completed the pre-requisites and considerations, let’s start with the installation.

1. With the App-V installation media, double click the setup executable.

2. Welcome page, click on “Next”.

3. Accept the License Agreement and click on “Next”.

4. Select “Custom” setup type.

5. Here you can modify installation components (not recommended) or change the installation directory. Click on “Next”.

6. Select the SQL Server instance where the database will be stored. In my case, I’m using the same server with one instance. Click on “Next”.

7. Select “Create a new database”. Maintain the suggested database name “APPVIRT”. You can also modify the location for the database files. Recommended for this type of server to store the database on a different hard drive than the operating system.

8. Leave deselected the option for “Use enhanced security”. You can set secure connections with this server, that will require of course for a certificate. Out of the scope in our case.

9. Leave the default value for the RTSP (Real Time Streaming Protocol): 554.

10. Select the group that will have full access to the App-V Management Server console. In my case, I’m selecting only “Domain Admins” to give access. This option can be modify later.

11. Select the provider group, that by default will have access to the enabled applications. In my case, I will select only “Domain Admins” and later personalize each application for each group.

12. Select the folder where the applications packages will be stored. Leave the default “C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\content\”. Click on “Next”

13. On the “Ready to Install the Program” window click on “Install”.

After a few moments you will have the App-V Management Server fully installed.

14. Recommended: Reboot the server.

IMPORTANT: If any of the pre-requisites and considerations mentioned above are not completed, you will receive a message like this when you start the installation:

“Error 25109. The installation program could not create the configuration data store. Please see the installation log file for more information”

Post-Installation Procedures

There are basically three more tasks to execute after the App-V Management Server installation is completed to guarantee the proper functionality:

1. Once the server is rebooted, you will need to verify the “Application Virtualization Management Server” service. If you are running on a virtualized environment, you will need to manually start the service.

2. Share the “content” folder created for the applications packages (by default C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\content\). Give to “Everyone” the “Read & Execute”, “List folder contents” and “Read” access.

3. If you have the firewall enabled, ensure that you enable the exceptions for inbound connections with the programs sghwdsptr.exe and sghwsvr.exe. Both located in “C:\Program Files\Microsoft System Center App Virt Management Server\App Virt Management Server\bin\”.

Note: If these firewall exceptions are not in place, you will also have problems with App-V clients trying to receive and execute the application packages. We’ll check that later.

And yes, you can now open the “Application Virtualization Management Console” and start working with the platform.

Make sure that you deselect the “Use Secure Connection” if you didn’t install a certificate for App-V.

Other Resources

As an interesting option to evaluate your App-V Management Server environment is the Microsoft Application Virtualization Best Practices Analyzer.

It verifies general configurations in your Management and/or Streaming Server 4.5, and notify about possible anomalies as a diagnostic tool. Requires the presence of Microsoft Baseline Configuration Analyzer to generate the reports.

In this example, the warning generated is about the database been stored in the same place as the Management Server.

I’ll be reviewing in the next posts how to prepare clients and applications to be deployed by App-V. I’ll be using Microsoft Office 2007 as the sequenced application.

Other posts in this series:

Implementing App-V – Part I: Introduction to Application Virtualization

Implementing App-V – Part III: Integrating Clients

Implementing App-V – Part IV: Sequencing Applications

Cheers!

Other posts in this series:

Implementing App-V – Part II: Choosing and Preparing the Environment

Implementing App-V – Part III: Integrating Clients

Implementing App-V – Part IV: Sequencing Applications

Virtualizing applications it is not a very common requirement for most administrators or companies. These solutions doesn’t seem like a “must” in any given environment, but why? One of the main reasons it’s related to the benefit/cost equation it’s not quite clear for most of us.

With these posts I’ll try to give a small introduction to the technology, explain the environment, provide a step-by-step deployment for App-V and the benefits that could apply to your organization.

What is Application Virtualization?

Application virtualization represents the technologies that permits to remove the complexity of deploying and maintaining applications for desktop users by providing:

• Applications centralized management. Facilitates the process of deploying, updating and removing applications. 
• Removing potential conflicts on desktop clients. Each application deployed using this type of technology runs in a isolated environment.
• Capability to capture a set of interconnected applications into a single package to be distributed among clients.

Common Scenarios

Let me give you a few common scenarios where application virtualization applies:

Scenario A

Problem: You are using a company’s application that requires some special configurations every time that is deployed, and that is also interconnected with other applications (for example: A local database engine, Java Runtime Environment or some other particular requirement). It demands you several hours every week to support end-users for deploying or troubleshooting configurations.

Solution: Providing application virtualization you can guarantee end-users to always have the same configuration deployed, no matter when or where; since you only need to configure it once and then wrap up the entire set of applications into one package.

Scenario B

Problem: You have a dynamic base operating system image that changes constantly, there are several type of base images according to the users, and you not have deployed Microsoft Deployment Toolkit (MDT) combined with System Center Configuration Manager (SCCM) to maintain images. You have two options: Manually and locally change the desktop image on every client by installing or removing applications; or providing end-users with local administrator privileges to achieve some kind of auto-management (don’t get me started on that).

Solution: Implement application virtualization with a clean base image will help you to minimize the impact every time there’s a change. With a centralized management of the applications you can make all the necessary changes and implement those instantly. Adding also granularity on the type of images, special applications can only be distributed to selected group of users.

Did you read the scenario problems and feel like “been there, done that”? Then you definitely should continue reading these posts.

Existing Platforms

There are several platforms provided to achieve application virtualization, the most common are:

• Microsoft Application Virtualization (App-V). Formerly known as SoftGrid.
• VMWare ThinApp.
• Citrix XenApp.
• Symantec Software Virtualization Solutions (SVS).

To name a few differences among them:

• ThinApp is the only one that supports 64 bits OS deployments.
• App-V, SVS and XenApp use a set of kernel mode drivers and supporting services to manage virtualization process. ThinApp includes the entire virtual environment directly into the application package.

This set of posts will be focused on reviewing the components and process within an App-V environment. As well as providing an step by step deployment.

App-V Components

App-V is the solution provided by Microsoft to achieve a secure, scalable and high performing applications deployment. Here’s a quick review about which components are involved.

App-V Management Server

In charge of delivering sequenced applications on-demand to selected clients. Any Management Server needs a SQL data store (multiple Management Servers can access the same data store) where it retrieves information like application assignments, records and permissions within the App-V management environment.

App-V Management System

Composed by the App-V Management Console and the App-V Management Service. It represents the communication channel between the MMC and the SQL data store, controlling any read/write requests to the database. It can be installed together with the Management Server or in a separate computer with IIS.

App-V Sequencer

In charge of producing the application package. It is basically a tool installed on a computer (preferred using the same OS as App-V clients) that captures the installation of the applications to generate the package, that consists in several files: Open Software Description (.osd file that links other files); sequenced application file (.sft file); icon files (.ico); XML manifest and a project file (.sprj). Optionally an MSI file can be included for offline deployments, but we’ll see how to do that later.

App-V Streaming Server

This server will have a the role of streaming applications to the clients where these do not have an acceptable connection to the Management Server, like a branch office. Streaming applications is the only functionality enabled for this server, and it represents, on most cases, as an optional role to be installed.

App-V Client

Installed on the end-user operating system, interacts with the App-V Server. Manages package streaming into cache and publishing refresh. Stores user-specific information related to the virtual applications in each user profile, so every time the client reboots the machine, the virtualized applications conserves last changes made. This client it is also represented with “Terminal Services” version, the only obvious reason is that the applications are published using Terminal Services virtual desktop.

Here’s a graphical description of the entire App-V environment

Resources

Here are some of the recommended resources you can find about the technology

• Application Virtualization 4.5 Documentation
• Microsoft Desktop Optimization Pack Home Page
• Microsoft Application Virtualization 4.5 Resource Kit Tools
• App-V Team Blog
• Planning and Deployment Guide for the Application Virtualization System

On the next posts I’ll use more practical examples and show you how to deploy an entire environment for virtualizing application. Stay tuned.

Other posts in this series:

Implementing App-V – Part II: Choosing and Preparing the Environment

Implementing App-V – Part III: Integrating Clients

Implementing App-V – Part IV: Sequencing Applications

Cheers!