What to do if App-V Sequencer is missing from Windows 10 ADK 1607

When installing Windows 10 ADK 1607, the App-V Sequencer component may be missing. This depending on the Operating System you're installing Windows ADK on. When you need to install the App-V Sequencer from Windows 10 ADK 1607, make sure you install it on Windows 10 1607 as well. Otherwise use the Microsoft Desktop Optimization Pack (MDOP) Setup Media instead.

When running on Windows 10 1511/1507, Windows 8.x, Windows 7 or Windows Server 2012 R2, App-V Sequencer is missing.

When running on Windows 1607, App-V Sequencer will be back again :-) Other components are available then as well.

Hope it helps!

More on App-V in Windows 10 can be found here: Both App-V and UE-V integrated in Windows 10 Enterprise now!

Both App-V and UE-V integrated in Windows 10 Enterprise now!

Within Windows 10 version 1607, both App-V and UE-V are part of the Operating System as Windows features. This instead of inclusion in MDOP, which required a separate download and installation. 

With Windows 10, version 1607 and later releases, Application Virtualization (App-V) is included with Windows 10 for Enterprise and Windows 10 for Education and is no longer part of the Microsoft Desktop Optimization Pack anymore.

The changes in App-V for Windows 10, version 1607 impact already existing implementations of App-V in the following ways:
-The App-V client is installed on user devices automatically with Windows 10, version 1607, and no longer has to be deployed separately. Performing an in-place upgrade to Windows 10, version 1607, on user devices automatically installs the App-V client.
-The App-V application sequencer is available from the Windows 10 Assessment and Deployment Kit (ADK). In previous releases of App-V, the application sequencer was included in the Microsoft Desktop Optimization Pack. Although you’ll need to use the new application sequencer to create new virtualized applications, existing virtualized applications will continue to work.

App-V supports System Center 2016 and 2012 R2. See Planning for App-V Integration with Configuration Manager for information about integrating your App-V environment with ConfigMgr.

Sources:
Getting Started with App-V for Windows 10
User Experience Virtualization (UE-V) for Windows 10 overview
What’s new for IT pros in the Windows 10 Anniversary Update

How to implement Azure RemoteApp (ARA) for business (part 3)

In an earlier blogpost I explained Azure RemoteApp (ARA) functionality and to publish native and virtual (App-V) applications. Now the story continues with some other device experiences. Therefore I installed the Remote Desktop client on a Windows 10 Mobile, Android phone and iPad 3 device. Let's have a look again.

ARA can be used on a variety off devices. Sounds like a cool scenario to use Windows applications on multiple devices.

On a Windows 10 Mobile you need to install Remote Desktop client and logon. As easy as that. All applications published can be started within a RDP session.

On iOS (iPad) you need to install Remote Desktop client and logon. As easy as that. All applications published can be started within a RDP session.

Besides of the Azure RemoteApp RDP client and Windows 10 Remote Desktop client, you can use the Windows Azure RemoteApp website as well. That's the third option I found to access published applications.

Hope there will be still some development on ARA policies (you won't want to use "Save as" on the RDS host within applications), publish specific applications to users and/or groups, and ugly logon screen during logon.

Hope you like my posts so far on ARA functionality!

Check earlier blogposts:
Azure RemoteApp Part 1 and Part 2

How to implement Azure RemoteApp (ARA) for business (part 2)

In an earlier blogpost I explained Azure RemoteApp (ARA) functionality and to setup a virtual machine. Now the story continues with a new ARA collection, build on the virtual machine template created earlier. After that applications are published to make them available.

Steps to take:
Create a new ARA collection. You can choose between:
-Cloud based: Create and manage RemoteApp collections running in Windows Azure.
-Hybrid based: Create a hybrid deployment of RemoteApp that uses VNet to connect to your on-premise infrastructure.
The virtual machine template created earlier must be available now.

Choose the new template created and continue. As you can see it's not that hard to create a new collection. This will take even more time now, so be patience again ;)

When done choose "Configure user access" and "Publish RemoteApp programs" to make them available to end users.

Both native and virtual (App-V) applications will be published now. Just select the ones to publish to end users.

Once the applications have been published and user access has been configured, you can then download the Azure RemoteApp RDP client (or use the Windows 10 Remote Desktop client instead).

After you have been authenticated, you will see your published applications (both native and virtual applications) assigned and published to the user. You can then begin to test virtual application behavior in Azure RemoteApp.

 

They will be added to the local start menu automatically, which is very cool if you ask me :-) Applications are integrated seamless, where you cannot seen if they are installed locally, or added by ARA. No locally installed App-V client is needed as well.

Check the Roadmap too:
-What's coming in Azure RemoteApp
And remember: with added value like the "Ability to publish individual applications to specific users" it will be even better :-)

How to implement Azure RemoteApp (ARA) for business (part 1)

For a customer environment it was needed to offer applications to local devices, without using a local infrastructure. Because Microsoft Cloud is the way to go, I was thinking about Azure RemoteApp (ARA). Let's have a look at the solution and how to implement it for offering applications. It is not that hard to setup.

ARA helps employees stay productive anywhere, and on a variety of devices (Windows, Mac OS X, iOS, or Android). Your company’s applications run on Windows Server in the Azure cloud, where they’re easier to scale and update. Employees simply install Remote Desktop clients on their (Internet-connected) PC, Mac, tablet, or phone and then access applications as if they were running locally. Sounds easy isn't it?

Pro's and cons:
-ARA is available in the old Azure portal only (for now). It will be available in the new Azure portal later this year.
-Applications within a single collection can be offered to specific users or groups only. Not possible to divide them to different users or groups. This will be available in the new Azure portal later.
-Deploying virtual (App-V) applications within ARA isn't supported by Microsoft. It is working, but not a recommended option. This will be supported in future in the new Azure portal.
-Deploying virtual (App-V) applications within ARA is supported in hybrid collections only. When using cloud collections this isn't the case. It is working, but not a recommended option.

Steps to take:
-Open the Azure portal, go to virtual machines and create a new "Windows Server Remote Desktop Session Host" from template. Choose the configuration wanted and wait for it to complete.
-The applications needed can be installed native or may be virtual (App-V) as well. Make sure the App-V Client for Remote Desktop Services is installed too, when App-V packages are used.
-To register App-V packages for later usage, use the following command(s): Microsoft TechNet. Don't start them yet, otherwise delete data in the local VFS Folder (%LOCALAPPDATA%\Microsoft\AppV\Client\VFS) for sure.

When ready start ValidateRemoteAppImage.ps1 on the desktop. This script will check for errors and start Sysprep afterwards. The virtual machine will be stopped afterwards.

Choose to capture the virtual machine afterwards (Capture button).

Go to RemoteApp now and "Add a new template image". The virtual machine captured before must be available now. This will take some time, so be patience ;)

That's it for now. In a next blogpost I will continue creating a new ARA collection, and publish some applications.

Check weblinks:
-Using App-V apps in Azure RemoteApp
-Create a Azure RemoteApp image based on an Azure virtual machine
-Capture an image of an Azure Windows virtual machine created with the classic deployment model
-App-V: On App-V Applications Hosted in Azure RemoteApp

Update 14-7: Change on virtual (App-V) applications. Thanks to @ArjanVroege and @fberson for comments.

ConfigMgr Restart Task fails if client has SUBST-ituted drive

Everytime I'm suprised when I see a new error during deployment in ConfigMgr. Today I have a new one for you. During a default "Restart Computer" step in a task sequence I get the following message. This on a server device running Microsoft App-V Sequencer software.

-Unable to get a handle to device Q: (0x80070005)
-Failed to convert Q: to unique volume id. Code : 0x80070005
-Failed to convert protected paths to unqiue ID. Error code 0x80070005
-Failed to reboot the system. Error 0x(80070005)
-Failed to initialize a system reboot. Permissions on the requested may be configured incorrectly.
-Unknown error (Error: 80070005; Source: Unknown)
-Fatal error is returned in check for reboot request of the action (Restart Computer). Permissions on the requested may be configured incorrectly.
-Unknown error (Error: 80070005; Source: Unknown)
An error (0x80070005) is encountered in execution of the task sequence

Lucky me I found the following blogpost: Microsoft TechNet
It mentions: The workaround we're using is to run a SUBST /D command line prior the restart step to make it work, but i was wondering if this is an accepted bug or limit of the software.

In my case I'm using a "Run Command Line" with "SUBST Q: /D" now to get the job done. No problem anymore during deployment!

Hope it helps!

ConfigMgr 2012 SP1 with App-V 5.0 integration

Today I did some testing with App-V 5.0 integration in ConfigMgr 2012 SP1. Microsoft describes it this way in their whitepaper:
"Configuration Manager 2012 SP1 adds support of App-V 5.0 applications. App-V 5.0 provides benefits over traditional applications as it transforms applications into centrally managed, virtual services that are never installed and do not conflict with other applications. App-V dramatically accelerates application deployment, upgrades, patching, and retirement by eliminating time-consuming processes and simplifying the application management lifecycle."

And some other good lines also:
- Configuration Manager 2012 SP1 was designed to provide the same level application management features that are provided in the App-V 5.0 infrastructure;
- Configuration Manager 2012 offers a rich set of capabilities for managing virtual applications from the Configuration Manager infrastructure. Configuration Manager with App-V integration enhances the virtual application delivery model and provides features that are not available with an App-V full infrastructure model;
- App-V Integration with Configuration Manager is streamlined because Configuration Manager is performing the same tasks that are available with the full App-V infrastructure;
- Configuration Manager provides management of applications from delivery, update, and termination using the application catalog built-in wizards and configurations;
- SP1 for Configuration Manager 2012 reduces the App-V infrastructure to the App-V Sequencer and Client and takes the place of the management, publishing, and streaming components in a typical App-V full infrastructure; 


Figure 1:Configuration Manager with App-V Infrastructure

When having an ConfigMgr installation, no changes are needed at all. You can import App-V packages as applications by default and deploy them to a collection. I created a user collection per App-V package myself, connected with a user group per collection. Deployment of applications is done on the same collection in this scenario. That way management (adding users to a group) can be done in Active Directory, no need to add users in the ConfigMgr console.
 
Here it comes, when deploy a required (mandatory) application to a desktop it will be installed within 5 - 30 seconds after logon. When deploying an application to a already logged on session, nothing is happening. A user policy refresh must be done first, or just logoff and logon again. After that installation is done in 5 - 30 seconds again. I tried both local download and streaming, but no big changes in them. When using local download (which takes longer) the application can be started immediately afterwards. When using streaming (which is way faster) the bits are downloaded when starting the application. I can live with it both ways!

App-V packages visible in Software Center (part of ConfigMgr)

When you want to uninstall an App-V package as application things are really different. Microsoft decided to remove the "Remove this virtual application when it is no longer advertised" option, which was used in ConfigMgr 2007 with App-V 4.6 integration. This was a great option, which removes the App-V package when it was no longer advertised. Much better that way!
 
Page 30 of the updated Configuration Manager White Paper (just click for download) discusses this:
To configure an application to automatically uninstall when a user / system is removed from the install collection, create a collection based on the deployment status of a deployed application then target an uninstall deployment to it.
 
This means you have to create two collections and deployments per App-V package now, one for installing and one for uninstalling the application. This will take a lot of time to create, as it is much more configuration then the option being used before. Microsoft mentions: The uninstall collection query listed only works for systems. The query must be modified when the install collection contains user objects.


User collections in ConfigMgr for installation and removal

I did it another way myself, creating two user collections per application. That way the Microsoft query mentioned is not needed, way to many clicks for me! Just create an Install and Uninstall collection and deployment per application. On the Install collection use a query connected to the specific user group used. On the Uninstall collection include the "All Users and User Groups" and exclude the specific user group used. Do this for all applications used.
 
When a user is removed from the specific user group in Active Directory, it will be synchronized in ConfigMgr within 10 - 15 minutes and installed or removed automatically. Collection membership is refreshed every 5 minutes by default and removal of the application when the "User Policy Retrieval & Evaluation Cycle" is done. 
 
My opinion for now: I'm not convinced of the functionality at the moment, but will keep testing if things get better with a different configuration. For it seems App-V 5.0 is actually slower then 4.6 with an App-V full infrastructure also, so more tuning is needed. It must be easier and faster to remove App-V packages in ConfigMgr to become more successful. Stay tuned for more!

Integration with Configuration Manager 2007/2012

With System Center Configuration Manager (ConfigMgr) 2007 there is many functionality available by default. With ConfigMgr 2012 this becomes even better, even MORE functionality will be in it. With both solutions there is the possibility to extend ConfigMgr with additional functionality. In this blog I will describe the most important ones.

Microsoft Deployment Toolkit (MDT) 2010: Adding new Task Sequences, new options in Task Sequences, new Boot images and all build-in scripts in ConfigMgr. Have a look at this blogpost(s) for more information about this:
http://henkhoogendoorn.blogspot.com/2010/12/mdt-integration-in-configmgr-2007.html
http://henkhoogendoorn.blogspot.com/2011/06/microsoft-deployment-toolkit-mdt-2010.html

Application Virtualization (App-V): Adding App-V streaming functionality in ConfigMgr, so no App-V Management and/or Streaming server is needed anymore. Just publish and update App-V packages from within the ConfigMgr console! Have a look at this blogpost(s) for more information:
http://henkhoogendoorn.blogspot.com/2010/12/configmgr-2007-with-app-v-integration.html
http://henkhoogendoorn.blogspot.com/2011/06/configmgr-2012-beta-2-with-app-v.html

ForeFront Endpoint Protection (FEP) 2010: It is possible to fully manage ForeFront from within the ConfigMgr console. Just deploy the ForeFront clients and manage policies with ConfigMgr. Definition files can be downloaded with WSUS integration in ConfigMgr. More about that on TechNet: http://technet.microsoft.com/en-us/library/cc161958.aspx

User State Migration Tool (USMT) 4.0: With USMT it is possible to store files and/or settings during OS deployment migrations. With hard-link migration it is possible to migrate user accounts, files and settings in less time using megabytes of disk space instead of gigabytes. More about that can be found here: http://technet.microsoft.com/en-us/library/dd560752(WS.10).aspx

Windows Server Updates Services (WSUS): Manage Software updates in ConfigMgr instead of WSUS, with even more control during installation. That way all management can be done in one single console, and additional ConfigMgr functionality as Maintenance Windows can be used. Have a look at this blogpost for this:
http://henkhoogendoorn.blogspot.com/2011/04/patch-management-in-configmgr-2012-beta.html

System Center Updates Publisher (SCUP) 2011: When ConfigMgr and WSUS is used (both together), SCUP can be installed for non-Windows patches. That way patches from HP, Dell, Adobe and Java (for example) can be managed and deployed in WSUS integration in ConfigMgr! How to setup, is explained here: http://blogs.technet.com/b/jasonlewis/archive/2007/11/30/how-to-setup-scup-and-configmgr-2007-to-deploy-custom-updates.aspx

System Center Configuration Manager 2007 Toolkit V2: The Configuration Manager 2007 Toolkit V2 contains 11 downloadable tools to help you manage and troubleshoot Configuration Manager 2007. It can be downloaded here: http://www.microsoft.com/download/en/details.aspx?id=9257

Right Click Tools or SCCM Console Extensions: The Right Click Tools or SCCM Console Extensions installation adds additional functionaly for server and client management. It becomes very handy during management and troubleshooting. More information can be found here:
http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx
http://myitforum.com/cs2/blogs/direland/pages/sccm-console-extensions.aspx

System Center Client Center: This tool is designed for IT Professionals to troubleshoot SMS/SCCM Client related Issues. The SCCM Client Center provides a quick and easy overview of client settings, including running services and SCCM settings in a good easy to use, user interface. Download it here:
http://sourceforge.net/projects/smsclictr/

With these tools more possiblities becomes available in ConfigMgr. Hopefully you have experienced new ideas with these products, and maybe more enthousiastic now to extend ConfigMgr functionality! Stay tuned for more later.

ConfigMgr 2012 Beta 2 with App-V integration

In ConfigMgr 2007 with R2 it was possible to import App-V packages and stream them to the end user. There was also the possibility to choose between streaming or local delivery for that. Have a look at this blog for more information about ConfigMgr 2007 with App-V integration: http://henkhoogendoorn.blogspot.com/2010/12/configmgr-2007-with-app-v-integration.html

Because of multiple reasons there was the choice between App-V integration in ConfigMgr 2007 or using the stand-alone App-V solution. I have selected a few websites with more information about that:

• App-V 4.6 and ConfigMgr 2007 SP2: even better together
• How to integrate App-V with SCCM without losing the features you care about
• Integration App-V and SCCM
• SCCM / App-V hybrid architecture
• App-V - Introduction, Components and SCCM Integration
• SCCM and App-V Integration Whitepaper

Personally I think that the combination of ConfigMgr 2007 and App-V is quite good, only it's better to keep them seperate. This because it's a bit slower in ConfigMgr and there's no publishing functionality in it. That way you must decide where to put the shortcuts in the App-V package, during sequencing. Also all shortcuts will be displayed on the desktop or in the start menu after publishing; no changes on that possible.

The advantage of putting App-V packages in ConfigMgr 2007, and using a Distribution Point (DP) for streaming is integration. No need for having App-V Management and/or Streaming servers that way. Just configure the (existing) ConfigMgr server and deploy all your applications from one platform! The only App-V installation needed is the Sequencer for creating App-V packages. Instead of multiple App-V servers, more Distribution Points are recommended then.

Now have a look at the combination of ConfigMgr 2012 Beta 2 and App-V. In ConfigMgr 2012 things are quite different. Open the ConfigMgr console, Select Application Management, rightclick on that and choose Create Application. There are four (4) choices now, with Microsoft Application Virtualization in here also. Just import a already sequenced application here.

When looking in the Applications screen there are no orange App-V icons anymore. On every application there are tabs for Deployment Types and Deployment (first known as advertisement). On deployment types there are new Content settings seen:

• Persist content in the client cache
• Enable peer-to-peer content distribution
• Load content into AppV cache before launch

Default settings for fast or slow/unreliable network boundary:

• Fast > Download content (changed to Stream content in my environment)
• Slow/unreliable > Do not download (changed to Download content in my environment)

On the Publishing tab, which is also new in ConfigMgr 2012, shortcuts can be selected. Keep in mind that the location (desktop and/or start menu) cannot be set, so still this must be decided during sequencing. The shortcuts that will be displayed on the desktop or in the start menu can be selected now!

For streaming App-V packages from Distribution Points no further configuration is needed in ConfigMgr 2012. Distribution Points have streaming functionality by default now. For App-V integration on the desktops an App-V 4.6 SP1 client is needed. No further configuration is needed on that also. Sometimes the Cache will be placed on another drive, and the Cache size will be enlarged. The file type extensions will be automatically associated to the new applications.

New applications available from ConfigMgr 2012

File type extensions are automatically associated

That's all you need to have for App-V integration in ConfigMgr 2012. Because off better user support in ConfigMgr 2012, App-V integration will be a more interesting choice now!

ConfigMgr 2007 with App-V integration

With ConfigMgr 2007 Release 2 (R2) it is possible to add App-V packages to the ConfigMgr console, and advertise them to ConfigMgr clients. With that functionality, no additional App-V Management or Streaming server is needed anymore. Now there is one solution for managing and publishing MSI-based & Virtual-based applications! I will explain in this blog what to configure in the ConfigMgr console, and how the App-V packages will be published to the ConfigMgr clients.

How it works?

ConfigMgr 2007 supports running sequenced applications created using the App-V Platform. App-V packages are running on ConfigMgr 2007 clients without having to install applications on the computer. Target computers must be running Windows XP (or above) to run virtual application packages. After you create a sequenced application using the App-V Sequencer, you must import the package into ConfigMgr 2007 and deploy the App-V package to ConfigMgr 2007 clients.

First you must make sure you are running ConfigMgr SP2 and R2 or R3 for having fast App-V package delivery. While Release 2 (R2) is needed for App-V functionality, Service Pack 2 (SP2) is needed for fast App-V package delivery. Because with ConfigMgr SP1 it could take up to 10 - 15 minutes for having the App-V packages available, while with SP2 there is almost no delivery delay! With ConfigMgr SP2, delivery can be as fast as with App-V streaming server, which is a great feature!

Client setup

On the computer there is a ConfigMgr client and a App-V client needed. There is no additional configuration on the App-V client needed. You need to enable Virtual Application Deployment in ConfigMgr, and ConfigMgr configures the App-V client for you. Any existing policies will be overruled. Best practice is to put the ConfigMgr client and App-V client in the Task sequence, which is used at deployment. Otherwise App-V delivery is not possible.

ConfigMgr 2007 setup

I will describe here which configuration is needed in the ConfigMgr console. These are all needed for having App-V functionality in ConfigMgr 2007.

Warning: this approach will affect every App-V client with the ConfigMgr client connected to the site. This because App-V management in ConfigMgr will overrule the existing App-V configuration.

In the ConfigMgr Distribution point properties (General) choose for "Allow clients to transfer content from this Distribution point using BITS, HTTP, and HTTPS"

In the ConfigMgr Distribution point properties (Virtuall Applications) choose for "Enable virtual application streaming"

At last, in the Advertised Programs Client Agent properties (General) enable "Allow virtual application package advertisement"

Because ConfigMgr supports two types of App-V delivery (streaming and local delivery), you need the above setting. Streaming delivery is simular to App-V streaming server and uses HTTP(S). Local delivery does "download and execute" the App-V package using BITS (same as MSI-based applications). With local delivery the App-V package will be saved on the computer, and is alltimes available (same as MSI-based (installed) applications)! Streaming is recommended on (VDI) desktops or fat clients.

App-V packages

In the ConfigMgr console you can add MSI-based & Virtual-based applications. I will describe the steps for adding App-V packages here.

Right-click on Software Distribution - Packages and choose for New > Virtual Application Package. Find the XML file, and add the App-V package.

Create an (sub)Collection for every application you want to advertise. Create a Active Directory group for every application, and add it to the collection.



Create an advertisement for every application you want to distribute, and add it to the collection with the same name. Choose for the following settings:

• Schedule: Mandatory assignments (occurs on current date/time)
• Distributing points: Stream virtual applications from Distribution point
• Interaction: Allow users to run the program independently of assignments

While sequencing choose for leaving icons in the Start menu and/or on the Desktop. This because no App-V Publishing server will be available, and users will see no icons to start the application.

Results on the computer

When all of the above steps has been set, App-V delivery will be available. On the ConfigMgr client there will be a policy refresh everytime you logon. At that point the App-V package will be available after 5 - 30 seconds. This will depends on sizing and configuration of the ConfigMgr server.

Again more functionality becomes available in the ConfigMgr console!