VM hosted apps license error during installation

Microsoft virtualization

content

First a few basic terms explained:

  • What is a Virtual machine?
    A piece of software is used to simulate a complete piece of hardware that usually runs in a window, but can also be accessed remotely like a terminal server connection. This “virtual machine” can also be assigned virtual memory or hard disks of freely definable size. Ultimately, however, the entire virtual machine (VM) is a single file. At VMware these are called .VMDK at Microsoft they are .VHD files.
  • Which does ______________ mean Hypervisor?
    Basically, a piece of software must be installed in order to run a virtual machine. This is the hypervisor. In MS, the hypervisor is called “Hyper-V” or “Virtual PC”.
    Type I and Type 2
    Type 2 hypervisor requires a full “host” operating system. Microsoft Virtual PC 2007, for example, is a type 2.
    Type 1 hypervisor is based directly on the hardware. Microsoft Hyper-V is a Type 1.
    Typical functions: USB connection, shared folder to exchange files between host and guest, etc.
  • What is a LUN?
    The term LUN (Loginal Unit Number) also appears again and again in conjunction with the topic of virtualization. LUN is the general term for virtual hard disks or hard disk areas. In modern SANs (Storage Area Networks), LUN addressing makes many virtual hard disks available as disk arrays.

New to this topic?

Then in this skilllocation demo video there is a good explanation of what virtualization actually means, what the difference between Terminal Server and VDI is and to what extent WVD Windows Virtual Desktop fits into it:

DemoVideo: What is the difference between Terminal Server RDS, VDI and WVD?

Microsoft took over this technology when it bought Softricity. The product was then called Softgrid. App-V is included in the Microsoft Desktop Optimization Pack MDOP and is part of the System Center family.

NOTE: Application Virtualization (App-V) and User Experience Virtualization (UE-V) are now an integral part of Windows 10 Enterprise and Windows 10 Education (what else was that? You can find it here: https://www.skilllocation.com/microsoft -desktop-optimization-pack-mdop /).

The idea is not to install an application locally, so that data is written to the operating system environment (e.g. registry). Instead, the application is virtualized, i.e. executed in its own virtual bubble. This isolates it from the operating system, but also from other “bubbles”, so that at the beginning not even the clipboard could be used between App-V applications. (This was fixed with Dynamic Virtual Application Interaction).

With App-V, a user can access their applications from any desktop (roaming user environments).

The applications are deployed on demand or streamed to the desktop, but appear as if they were actually installed locally. So there is no difference in perception for the user.

App-V requires an App-V server infrastructure to support App-V clients. You need the following App-V components:

  • App-V server. The App-V server provides functions for App-V management and publishing of virtualized apps, as well as app streaming and reporting services. All of these services can be run on one server or individually on multiple servers. For example, you can set up multiple streaming servers. App-V clients contact App-V servers to determine which apps are published for the user or device. Then they run the virtualized app from the server. (App-V Server is available free of charge as part of the Windows 10 Assessment and Deployment Kit)
  • App-V sequencer. The App-V sequencer is a typical client device used to sequence (capture) apps and prepare them for hosting by the App-V server. You install apps on the App-V sequencer, and the App-V sequencer software determines the files and registry settings that are changed during the app installation. The sequencer then captures these settings to create a virtualized app.
  • App-V client. The App-V client must be activated by the App-V server on all client devices running apps. These are the Windows 10 Enterprise E3 devices.

There are two types of App-V clients to choose from: the terminal server client and the desktop client.

In any case, the client must be installed on every desktop or terminal server on which virtual applications are to be provided.

The client takes up relatively little storage space. It installs a driver and is displayed as an icon in the system tray. The client compiles a list of available virtual applications from the App-V management server and allows them to start. App-V supports the HTTP and HTTPS protocols for streaming over the Internet as well.

All data sent to the client is in a local cache file on the device, and each subsequent application start is from the local cache, which avoids additional network traffic. And the application is also available offline.
However, the client enables the virtual application to access the local file system when files are saved and edited, and it also enables the application to interact with local services (e.g. printing), provided the user has the appropriate permissions on the local system.

When the App-V application is started, the App-V client checks whether there is a newer package and streams it back to the system. However, the entire package does not have to be transferred; only the updated deltas or innovations are applied to the running applications. However, any changes that a virtual application makes to files on the local system and registry are redirected to the virtualized environment so that the host device remains unchanged.

In order to take advantage of App-V, virtual application packages must be created. This is where the App-V sequencer comes in. The sequencer is a wizard-based tool that guides you as a “packer” through the process of installing an application and transforming it into a virtual application.

App-V can be combined with the Microsoft System Center Configuration Manager (2007 and higher).

Microsoft Application Virtualization (App-V) 4.6 (February 2010) offers the following improvements and new features for the App-V Desktop Client, Client for Remote Desktop Services and App-V Sequencer:

  • Support for 64-bit applications: supports sequencing and execution of 32-bit and 64-bit applications on 64-bit versions of Windows 7, Windows Vista, Windows XP, Windows Server 2008, Windows Server 2008 R2, Windows Server 2003 and Windows Server 2003 R2 . For more information about the supported operating systems, see Application Virtualization Deployment Requirements.
  • Support for Windows 7 and Windows Server 2008 R2: provides support for Windows 7 and Windows Server 2008 R2. This includes support for Windows 7 features such as the taskbar, jump lists, AppLocker, BranchCache, and BitLocker To Go.
  • Extends global reach and localization: provides support for 12 additional languages.
  • Support for Virtual Desktop Infrastructure (VDI) system: Read-only, shared cache memory enables optimized server disk storage in VDI scenarios.
  • Optimized sequencing: optimized sequencing wizard and support for sequencing 32-bit and 64-bit applications.

App-V 5.0 (November 2012) came with the following functional enhancements:

  • IT diagnosis and monitoring: App-V 5.0 includes a better way to report information about computers running the App-V 5.0 client and virtualized packages.
  • Consistent programmability: Using PowerShell 3.0, App-V 5.0 includes a comprehensive programmability solution for packaging, client and server operations.
  • Simple and efficient client console: App-V 5.0 includes a modern client console to simplify the scenarios for technicians for support for key users and support at level 1.

App-V 5.0 SP2 (1.5.14) improves application publishing and updates. It also optimizes the App-V application. According to Microsoft, it should facilitate tests and rollouts of new versions of virtual apps.
NOTE:
Microsoft names Applicationsthat can only be achieved with greater effort or not allow it to be virtualized at all. The following list should also apply to other virtualization products:

  • Applications that one Install system-level driverssuch as a printer driver or a USB device driver
  • Applications that Boot services to install
  • Applications that COM + use
  • Applications that MAPI virtualization require
  • Applications where the Licensing tied to the hardware is, e.g. dongle

Competitive products: VMware ThinApp, Symantec Altiris SVS, Citrix XenApp.

App-V version overview

App-V is an excellent solution for companies that bring incompatible applications to Windows 7/8 / 8.1!

A new Microsoft study on application virtualization found that Microsoft App-V customers reduced application lifecycle management time by 27 percent.
This corresponds to a saving of US $ 82 per PC per year compared to companies without application virtualization. The study also showed how Microsoft App-V can deliver applications faster and more efficiently.

App-V with Office 365 and Office 2013/2016

With Office 2013/2016 and the corresponding services in Office 365, App-V is introduced as a key technology for deployment. Office on Demand or Click-to-Run or Click-to-Run allow quick provisioning, even over the Internet, without having to install Office locally. No separate App-V infrastructure or MDOP is required.

Users can work with the applications after around 2 minutes before the entire Office suite has been streamed to the PC (hence the term streaming analogous to videos that are already running before they are fully loaded). Office 2013 uses a customized version of application virtualization so that functions can be loaded when they are called.

Office Side-by-Side then means that no previous versions of Office need to be uninstalled in order to be able to use the new Office. There is now also support for the integration of existing Office add-ins, adjustments, macros and earlier Office file formats.

The low test effort to check application compatibilities speaks in favor of this provision method.

VDI is a centralized desktop deployment architecture that allows companies to centralize the storage, execution, and management of a Windows desktop in the data center.

The client operating system runs in a virtual machine on the server (server-based virtualization); communication with the end device takes place via remote desktop protocol, as with a terminal server connection.

Therefore, the question arises again and again whether an RDS-CAL is required. You can find the answer here: https://www.skilllocation.com/rds-und-vdi

Another possibility is to deploy the virtual desktop machines on client hardware (client-hosted virtualization or offline desktop).

Since Windows 7 can already boot from a .VHD file (which contains the virtual machine), new scenarios for efficient desktop deployment arise. Here are instructions on how to install a .VHD boot (not from us).

Windows 8 has Hyper-V with it (from the PRO Edition).

Windows Server 2008 R2 comes with VDI Services, on the one hand, it defines the possibility of managing virtual machines centrally (only on Hyper-V) and a connection broker (at Terminal Services this service was called the Session Broker). The connection broker has the task of assigning an instance of a virtual machine to a requesting user and organizing load distribution accordingly.

This demo video is one of oursLearning snacksYou can download it in different versions (e.g. without a soundtrack and without the skilllocation logo).

The idea is to save administrative costs through central management. But it must be clear: the machines can only be managed centrally if they are identical and correspondingly high server resources are required.

  • As of July 1, 2010, Windows Client Software Assurance customers no longer need to purchase separate licenses for the Windows operating system within a VDI environment. Access rights to the virtual desktop are then included in Software Assurance.
  • Also since July 1, 2010, customers of Windows Client Software Assurance and new customers of Virtual Desktop Access licenses have been given access to their virtual Windows desktop and Microsoft Office applications using VDI technology for secondary, external devices such as home PCs and kiosks .

With Service Pack 1 for Windows 7 (and Windows Server 2008 R2) two new features are added:

  • RemoteFX: Video, 3D, Aero etc. Finally full graphic support for remote desktop connections. The execution takes place on the server. This is where the VDI theme is driven again.
    With Windows 8 RemoteFX is expanded again: http://blogs.msdn.com/b/rds/archive/2012/11/26/remotefx-features-for-windows-8-and-windows-server-2012.aspx
  • Dynamic memory: Here you can now specify min and max RAM values ​​for virtual machines. This also guarantees that no more RAM is used than is available (with proper planning), so that it does not have to be swapped out onto the disk, which in turn results in a loss of performance.
  • The Windows XP mode no longer requires hardware virtualization technologies such as Intel VT or AMD-V integrated in processors.

Competitive products:

  • VMware View (formerly VMware VDI, currently: Version 4.5) is one of the leading solutions here.
  • Citrix Xen Desktop is not a competitor!

VMware View currently requires Infrastructure 3, the current vSphere 4 is only supported with version 4.

  • Distributed Resource Manager: can dynamically outsource virtual desktops to additional physical servers depending on the load. Cannot MS currently (but may be superfluous due to optimal planning)
  • RDP: View uses the RDP developed by MS but enriched by WyseTCX. Alternatively, HP RGS is also possible.
  • Thinprint: Use of local and network printers without installing drivers. Corresponds to EasyPrint from MS.
  • View Manager: Connection Broker

Virtualization for desktops

Sometimes desktop virtualization is also understood to mean that a virtual machine can be created and executed on a desktop client, i.e. without central management.

Operating systems in virtual machines are suitable for testing in isolated environments, for increasing security when surfing the web, or for simply being able to run programs that are not available for the main system.

In the case of Microsoft, this would be the old version Microsoft Virtual PC 2007 or the new Microsoft Windows Virtual PC. Both are free. Windows Virtual PC only runs on Windows 7 and supports USB 2.0, copy & paste between host and guest, 3D graphics, shared folders, multithreading for guests, seamless integration of guest applications into the host's start menu. (See also XP mode!).

There are competitors here:

  • VMware Workstation 6.5
    max 2 virtual CPUs, seamless mode, P2V, headless mode (no surface of the VM),
  • Parallels Workstation 2.2. (approx. 50 US $)
    Can SharedFolder as well as Copy & Paste between host and guest, but e.g. no snapshot function, only USB1, no 3D graphics
  • Parallels Workstation 4.0 Extreme
    3D graphics, up to 16 virtual CPUs; but currently only in a package with the HP Z800 workstation
  • VirtualBox from SUN
    OpenSource, USB 2.0, 3D graphics, up to 32 virtual CPUs, SharedFolder, Copy & Paste,

In the days of Windows Vista, the “V” stood for Vista, but that changed with the appearance of Windows 7.

Windows VECD is a device-based Annual subscription, which enables your customer's company to license virtual copies of Windows 7 (or earlier operating system versions) for a variety of application scenarios.

VECD provides two basic delivery options: Static and dynamic. Customers with less stringent administration can opt for a static deployment. Customers with well-managed environments can also take advantage of dynamic topologies.

  • Static provision: In the static mode, each user has his own, dedicated virtual machine on the server - there is a one-to-one assignment of virtual machines and users. The more users there are, the more virtual machines are required. Virtual machines are stored on a SAN or NAS and run on the server. Desktops are displayed on a PC or thin client, depending on the situation.
  • Dynamic provisioning: There is only one master image in a dynamic infrastructure. Instead of having to manage many dedicated images, this one image is automatically made available to users when required. This makes it easier to manage the virtual machines and dynamically provide desktop environments - which helps you to reduce maintenance and support costs.
    The dynamic mode of VECD works with a master VM image in a SAN or NAS and for the users individual application images (via App-V). When a user enters a virtual machine, the master image is replicated and executed on the server.

VECD can be used on the one hand for PCs and on the other hand for thin clients and means that the customer pays a license fee for running a virtual machine or instance of Windows 7.

New from July 1st, 2010:
Starting July 1, 2010, Windows Client Software Assurance customers no longer need to purchase separate licenses for the Windows operating system within a VDI environment. Access rights to the virtual desktop are then included in Software Assurance.

With Enterprise Desktop Virtualization, operating systems are set up as centrally managed virtual machines on the server. This makes updates easier and employees have access to their workstation from anywhere, even when they are on the move with their notebook.

MED-V is included in the Microsoft Desktop Optimization Pack MDOP.

Virtual PC and MED-V together

Together with Virtual PC 2007, MED-V (formerly Kidaro) offers a client-hosted desktop virtualization solution.

MED-V expands Virtual PC with four additional components:

  • serves as a central repository for virtual images and as a delivery system for the creation, testing, provision and updating of virtual images
  • offers central management and monitoring for the entire life cycle of the virtual machines (e.g. an expiry date can be defined for the VM)
  • enables policy enforcement and data transfer control to be used by an endpoint agent
  • offers a seamless user experience, the applications are displayed as shortcuts in the start menu and local printing is possible.

An icon for MED-V appears in the Windows notification area. But you don't see a virtual machine running because the applications themselves are integrated as windows.
The virtual machines are created with Virtual PC and then uploaded to the repository on the server via the MED-V management console.

MED-V and Windows 7
The handling but also the architecture of MED-V are strongly reminiscent of Windows Virtual PC and the XP mode of Windows 7 and also serve the compatibility problem. So mainly Windows XP VMs on Windows Vista or Windows 7 hosts will be used.
And that's right, version 2 of MED-V also supports Windows 7. This means that its Windows XP mode can also be administered centrally.

MED-V and Windows 8
MED-V is still included in the MDOP, although XP mode is no longer available under Windows 8. Virtual machines are now provided with Hyper-V clients and can be managed centrally via e.g. SC VMM. MED-V may still be required for old Windows 7 clients and XP mode.

With Windows Server 2008 R2, Terminal Services will be renamed to Remote Desktop Services. There are several reasons for this.
In addition to Terminal Server Sessions and Remote Applications (RemoteApps), hosted desktops are now also available.
New in Hyper-V 2.0 is the ability to make desktops available in a virtual environment.

  • RemoteApp: The entire desktop is no longer transferred here, ie. the user no longer sees two start buttons, etc., but only the application is displayed locally in a window. This is transparent for the user. The application is integrated in the taskbar, start menu and systray, but runs as a remote app on the server.
  • RD Easy Print: Thanks to improved integration, it is now possible to print locally without the printer driver having to be installed on the Terminal Server.
  • RD WebAccess: All approved applications are displayed on a special website and can be started from there.
  • RD gateway: Sessions can be started over the Internet (tunneled over HTTPS, so a VPN connection is no longer necessary)
  • RDC RemoteApp and Desktop Connections (RDP-Client 7): a new function in Windows 7, via which RemoteAppps and Hosted Desktops are automatically displayed directly in the start menu of the user. (RDC also comes for Windows XP and Windows Vista).
  • over Media redirection the server forwards multimedia data unrendered and unprocessed directly to the client, which plays the data with the local hardware, which relieves the server and increases quality.
  • Remote audio: transmits microphone inputs from the client so that VoIP is also possible or the sound of the server to the local sound card.
  • Multi-monitor support: Windows 7 allows up to 10 monitors to be used in RDS sessions.
  • Graphic improvements: Aero-Glass also in the session.

Microsoft has bought Calista Technologies, which will integrate further graphics improvements into the RDP protocol.
If customers already have increased requirements for the graphics system within Remote Desktop, then add-on solutions from Quest “EOP” or Wyse “TCX” or Ericom “Blaze” are available.

Incidentally, the TS CAL is now also called RDS CAL.

Hyper-V virtualizes the system resources of a physical computer and thus represents a virtualization platform that enables customers to consolidate multiple operating systems on one physical server.

The graphic is from a Microsoft partner program twelve-page and German-language partner guide server virtualization.

Typically, Hyper-V is used to virtualize server computers. If Hyper-V is used together with Virtual Desktop Infrastructure (VDI), Hyper-V is used to virtualize client computers.

Hyper-V is an integral part of the x64-based versions of Windows Server 2008 and higher. But it is also available as a standalone server: Microsoft Hyper-V Server and can run 32-bit and 64-bit virtual computers.

Requires hardware with virtualization support: Intel VT or AMD-V, which shouldn't be a problem on the server side, as most servers have been delivered this way for years.

Hyper-V is SAP certified, more information here.

The Federal Office for Security in Information Technology (BSI) has certified the Microsoft Windows Serer 2008 Hyper-V role according to the Common Criteria EAL 4 standard. Info here.

Managed by Microsoft System Center Virtual Machine Manager VMM Hyper-V brings additional benefits:

Hyper-V supports the Cross-platform approach: Linux systems can run as virtual machines and be managed by the VMM, but Windows servers virtualized with VMware can also be managed under one interface. There is also the free of charge Linux Integration Services 2.1 for Windows Server 2008 Hyper-V R2to improve support for Linux-based virtual machines. This version of Integration Services for Hyper-V supports Novell SUSE Linux Enterprise Server 10 SP3, SUSE Linux Enterprise Server 11, and Red Hat Enterprise Linux 5.2 through 5.5. The 2.1 release includes driver support for synthetic devices, fastpath boot support for Hyper-V, time synchronization, integrated shutdown, Symmetric Multi-Processing (SMP) support for up to four processors, heartbeat and pluggable time source. The drivers are available in different languages.

Microsoft itself has also consolidated and centralized its data centers through server virtualization. There is an English-language case study on this: How Microsoft IT Reduced Operating Expenses Using Virtualization.

This is not a product or tool, but a description of a reference architecture, i.e. a specification of what an optimized installation and configuration should look like. Since Microsoft itself does not manufacture any hardware in the server area (“fabric”, storage, network components, storage or housing), manufacturers have pre-installed their hardware with Microsoft Hyper-V and deliver them as ready-made solutions or private cloud infrastructures. The customer only has to copy his virtual machines onto it.

Further information here: http://www.microsoft.com/en-us/server-cloud/private-cloud/fast-track-trial-buy.aspx

Competitive products or providers who also rely on Hyper-V:

  • VCE and vBlock
  • HP Converged Systems
  • Cisco UCS and Cisco / NetApp FlexPod
  • Dell ActiveSystem
  • EMC Vspex Reference Architecture
  • Fujitsu vShape and Integrated System Cloud ReadyBlocks
  • Hitachi Data Systems: Unified Compute Platform
  • IBM PureFlex System
  • Oracle Virtual Compute and Exalogic Elastic Cloud
  • Nutanix and Simplivity
  • Simplivity Omnicube
  • Huawei FusionCube

Convert VMware to Hyper-V

Microsoft Virtual Machine Converter 3.0 MVMC
For the import of virtual machines from VMware vSphere or ESX (i) from version 4.1 to Hyper-V there is a free one Virtual machine converter. This converts the file format (as a guest system Windows Server from 2003 or Windows 7 or higher) and its functions are quite limited. With Double-Take Move, Vision Solutions has developed a solution that migrates complete VMware servers to Hyper-V during operation, including system status, attributes, compression and encryption settings.