mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-07 18:17:22 +00:00
51 lines
2.3 KiB
Markdown
51 lines
2.3 KiB
Markdown
---
|
||
title: Maintaining App-V 5.1
|
||
description: Maintaining App-V 5.1
|
||
author: jamiejdt
|
||
ms.assetid: 5abd17d3-e8af-4261-b914-741ae116b0e7
|
||
ms.pagetype: mdop, appcompat, virtualization
|
||
ms.mktglfcycl: deploy
|
||
ms.sitesec: library
|
||
ms.prod: w10
|
||
ms.date: 06/16/2016
|
||
---
|
||
|
||
|
||
# Maintaining App-V 5.1
|
||
|
||
|
||
After you have completed all the necessary planning, and then deployment of App-V 5.1, you can use the following information to maintain the App-V 5.1 infrastructure.
|
||
|
||
## <a href="" id="move-the-app-v-5-1-server-"></a>Move the App-V 5.1 Server
|
||
|
||
|
||
The App-V 5.1 server connects to the App-V 5.1 database. Therefore you can install the management component to any computer on the network and then connect it to the App-V 5.1 database.
|
||
|
||
[How to Move the App-V Server to Another Computer](how-to-move-the-app-v-server-to-another-computer51.md)
|
||
|
||
## <a href="" id="determine-if-an-app-v-5-1-application-is-running-virtualized-"></a>Determine if an App-V 5.1 Application is Running Virtualized
|
||
|
||
|
||
Independent software vendors (ISV) who want to determine if an application is running virtualized with App-V 5.1 or above, should open a named object called **AppVVirtual-<PID>** in the default namespace. For example, Windows API **GetCurrentProcessId()** can be used to obtain the current process's ID, for example 4052, and then if a named Event object called **AppVVirtual-4052** can be successfully opened using **OpenEvent()** in the default namespace for read access, then the application is virtual. If the **OpenEvent()** call fails, the application is not virtual.
|
||
|
||
Additionally, ISV’s who want to explicitly virtualize or not virtualize calls on specific API’s with App-V 5.1 and above, can use the **VirtualizeCurrentThread()** and **CurrentThreadIsVirtualized()** functions implemented in the AppEntSubsystems32.dll module. These provide a way of hinting at a downstream component that the call should or should not be virtualized.
|
||
|
||
## Got a suggestion for App-V?
|
||
|
||
|
||
Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). For App-V issues, use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
|
||
|
||
## Other resources for maintaining App-V 5.1
|
||
|
||
|
||
[Operations for App-V 5.1](operations-for-app-v-51.md)
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|