Last week I installed a fresh new App-V environment. With this short blogpost I want to share 2 configuration ‘note-to-selfs’ which I encountered during the installation and configuration. Both are really obvious configurations but it took me some time to discover the solution. So also for my own reference I want to describe them on my blog.
In this blogpost, I want to describe how the new MDM Group Policy functionality can be used to configure your Windows 10 workstation. With the Windows 10 Creators Update we’ve the possibility to deploy and apply Group Policy objects through the MDM channel. This means that the policy configuration support in Windows 10 will be expanded to allow access of select Group Policy administrative templates (ADMX-backed policies) for Windows PCs via the Policy configuration service provider (CSP). In this blogpost, I want to use this new functionality to activate and configure the App-V client on a Windows 10 MDM Managed workstation.
This is the last part in the blog series about App-V support in Azure RemoteApp. In the first part I discussed the use of a standalone App-V deployment with Azure RemoteApp. The second part discussed the use of the full App-V infrastructure in combination with Azure RemoteApp. This last part will focus on deploying App-V applications through System Center Configuration Manager (ConfigMgr). This blogpost will describe the steps needed to add your RemoteApp instances to ConfigMgr and the steps needed to deploy the App-V applications.
In the first post of this blog series I explained how App-V standalone can be used inside Azure RemoteApp. This blogpost will cover the use of the full App-V infrastructure to publish and stream the applications to the Azure RemoteApp instances. Since a domain joined Session Host server is a prerequisite this can only be done through a Hybrid Azure RemoteApp deployment. This blogpost will not cover the installation of the App-V environment itself. This is well described on TechNet. You can find the information here. If you use an external SQL server install the database component first on the SQL server before starting the installer on the App-V Management Server. Continue reading
In this series of blogposts I want to describe the different ways of using App-V with Azure RemoteApp. Azure RemoteApp is a cloud service delivered through Microsoft Azure. With Azure RemoteApp you can publish native Windows applications to your ‘Universal Workplace’. Azure RemoteApp has clients for almost all Windows operating systems and also for iOS, Mac OS X and Android. With this broad support of clients Azure RemoteApp provides the flexibility to publish native Windows Applications to almost all platforms. Azure RemoteApp is the cloud implementation of the on-premise RDS RemoteApp technology. Application Virtualization is used in most of the Desktop Virtualization environments, as there is limited information available on the support of App-V in combination with Azure RemoteApp I want to share this information in the following series of blogposts:
- Part 1: Azure RemoteApp with standalone implementation of App-V
- Part 2: Azure RemoteApp with full infrastructure implementation of App-V
- Part 3: Azure RemoteApp with ConfigMgr 2012 R2 SP1 implementation of App-V
In these series I want to describe the steps which I have taken to enable App-V in Azure RemoteApp en want to discuss the advantages en disadvantages of the implementation. This part will continue with describing the standalone implementation of App-V.
This week Microsoft released App-V 4.5 SP2. The release notes introduced the following new functions:
- Support for Office 2010: App-V 4.5 SP2 now supports the virtualization of Microsoft Office 2010.
- Support for Database Mirroring: App-V 4.5 SP2 now supports Microsoft SQL Server Database Mirroring.
- Customer Feedback and Hotfix Rollup: App-V 4.5 SP2 also includes a rollup of fixes to address issues found after the App-V 4.5 SP1 release.
The support for database mirroring is a very interested new function. But how about database mirroring on my App-V 4.6 infrastructure. I looked at the version of my App-V 4.6 server, the version was 184.108.40.20640. So technically it’s also possible to install the servicepack on my 4.6 infrastructure. I give it a try:
I looked in my database on which version my server was runnning. I did the following query:
SELECT hostname,version FROM dbo.SERVERS;
The result was:
Hostname: ###### ——- Version: 220.127.116.1140
Below the steps I did:
1. Download the patch from here
2. Unzip the download file and start the setup_upgrade.exe from the Management Server folder
3. On the welcome screen click Next
4. Accept the terms and click Next
5. Choose your option on the Windows Update screen and click Next
6. Note that the access to the Management Server will be disbabled and click Next
7. Check if the database information is correct and click Next
8. Click Next
9. Click Upgrade
10. After the Upgrade restart the Management Server
After the restart I ran the query again:
Hostname: ###### ——- Version: 18.104.22.16880
The result is that my 4.6 App-V Management Server is upgraded with a 4.5 SP2. Very nice logic, but it works. Now it’s time for in dept testing!!
Issue: The SoftGrid Management Console on the Virtual Application Server may be unable to connect to itself by name and produced error 0000C802 when launched. The console does launch successfully when referenced as “localhost” or by it’s IP address.
Cause: The browser on the computer (IE) is configured to use a proxy server.
Resolution: Either remove the proxy server or configure an exception to bypass the proxy for this connection.
Additional Information: Accordng to KB930469this error could be caused by one or more of the following:
- The port specified is invalid
- The World Wide Web Publishing Service is not running
- The default web site is not running
If you check all of these and still experience the issue then it may be caused by the browser being configured to use a proxy server. After eliminating the conditions from KB930489 as possibilities, check your Internet Explorer configuration settings by going to Tools -> Internet Options -> Connections -> LAN settings. Here you can either disable the proxy server, or if you do not use dotted names (e.g. myserver versus myserver.local) try enabling ‘Bypass proxy server for local addresses’. If this is enabled, any server name that does not have a dot in it will be considered local, therefore the proxy will be bypassed. If this fails or is not an option in your environment, you can add an exception for the server via the same page by selecting the Advanced button.