{
	"id": "cbe928a2-24ce-41a0-aa88-d73159b925a7",
	"created_at": "2026-04-06T00:10:15.156177Z",
	"updated_at": "2026-04-10T03:21:54.618416Z",
	"deleted_at": null,
	"sha1_hash": "d160a368834a10eba3f268acf7326bd4c5458339",
	"title": "Getting Started with App-V (Windows 10/11) - Microsoft Desktop Optimization Pack",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 47756,
	"plain_text": "Getting Started with App-V (Windows 10/11) - Microsoft Desktop\r\nOptimization Pack\r\nBy aczechowski\r\nArchived: 2026-04-05 13:32:30 UTC\r\nApplies to:\r\nWindows 10\r\nWindows 11\r\nImportant\r\nThe Windows App-V client is in fixed extended support. For more information, see App-V client support.\r\nMicrosoft Application Virtualization (App-V) for Windows delivers Win32 applications to users as virtual\r\napplications. Virtual applications are installed on centrally managed servers and delivered to users as a service in\r\nreal time and on an as-needed basis. Users launch virtual applications from familiar access points and interact with\r\nthem as if they were installed locally.\r\nStarting with Windows 10 version 1607, App-V is included with the Windows 10 for Enterprise edition. If you're\r\nnew to Windows client and App-V, you'll need to download, activate, and install server- and client-side\r\ncomponents to start delivering virtual applications to users. To learn what you need to know before getting started\r\nwith App-V, see the Application Virtualization (App-V) overview.\r\nIf you're already using App-V, performing an in-place upgrade to Windows 10/11 on user devices automatically\r\ninstalls the App-V client and migrates users' App-V applications and settings. For more information about how to\r\nconfigure an existing App-V installation after upgrading user devices to Windows 10/11, see Upgrading to App-V\r\nfor Windows from an existing installation.\r\nImportant\r\nYou can upgrade your existing App-V installation to App-V for Windows from App-V versions 5.0 SP2 and higher\r\nonly. If you are using an earlier version of App-V, you'll need to upgrade your existing App-V installation to App-V 5.0 SP2 before upgrading to App-V for Windows.\r\nTo learn more about previous versions of App-V, see MDOP information experience.\r\nGetting started with App-V for Windows (new installations)\r\nhttps://learn.microsoft.com/en-us/windows/application-management/app-v/appv-getting-started\r\nPage 1 of 3\n\nTo start using App-V to deliver virtual applications to users, you'll need to download, enable, and install server-and client-side components. The following table describes the App-V for Windows client components, what they\r\ndo, and where to find them.\r\nComponent What it does Where to find it\r\nApp-V server\r\ncomponents\r\nApp-V offers five server components that\r\nwork together to allow you to host and\r\npublish virtual applications, generate usage\r\nreports, and manage your App-V\r\nenvironment. For more information, see\r\nDeploying the App-V Server.\r\nIf you're already using App-V 5.x, you don't\r\nneed to redeploy the App-V server\r\ncomponents, as they haven't changed since\r\nApp-V 5.0's release.\r\nThe App-V server components are\r\nincluded in the Microsoft Desktop\r\nOptimization Pack (MDOP) 2015\r\nISO package that can be downloaded\r\nfrom the following locations:\r\nIf you have a Microsoft Visual\r\nStudio subscription, use the Visual\r\nStudio subscriptions site to\r\ndownload the MDOP ISO package.\r\nIf you're using Windows client for\r\nEnterprise or Education, download it\r\nfrom the Microsoft M365 admin\r\ncenter.\r\nFor more information about\r\ninstalling and using the server\r\ncomponents, see Deploying the App-V Server.\r\nApp-V client and\r\nApp-V Remote\r\nDesktop Services\r\n(RDS) client\r\nThe App-V client is the component that runs\r\nvirtualized applications on user devices,\r\nallowing users to interact with icons and file\r\nnames to start virtualized applications.\r\nStarting with Windows 10 version\r\n1607, the App-V client is\r\nautomatically installed.\r\nTo learn how to enable the client, see\r\nEnable the App-V desktop client.\r\nApp-V sequencer\r\nUse the App-V sequencer to convert Win32\r\napplications into virtual packages for\r\ndeployment to user devices. Devices must\r\nrun the App-V client to allow users to\r\ninteract with virtual applications.\r\nInstalled with the Windows\r\nAssessment and Deployment kit\r\n(ADK) for Windows client.\r\nFor more information about these components, see High Level Architecture for App-V.\r\nIf you're new to App-V, it's a good idea to read the documentation thoroughly. Before deploying App-V in a\r\nproduction environment, you can ensure installation goes smoothly by validating your deployment plan in a test\r\nhttps://learn.microsoft.com/en-us/windows/application-management/app-v/appv-getting-started\r\nPage 2 of 3\n\nnetwork environment. You might also consider taking a class about relevant technologies.\r\nGetting started with App-V\r\nWhat's new in App-V provides a high-level overview of App-V and how it can be used in your organization?\r\nEvaluating App-V provides information about how you can best evaluate App-V for use in your organization.\r\nHigh Level Architecture for App-V provides a description of the App-V features and how they work together.\r\nOther resources for this product\r\nApplication Virtualization (App-V) overview\r\nOperations for App-V\r\nSource: https://learn.microsoft.com/en-us/windows/application-management/app-v/appv-getting-started\r\nhttps://learn.microsoft.com/en-us/windows/application-management/app-v/appv-getting-started\r\nPage 3 of 3",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://learn.microsoft.com/en-us/windows/application-management/app-v/appv-getting-started"
	],
	"report_names": [
		"appv-getting-started"
	],
	"threat_actors": [],
	"ts_created_at": 1775434215,
	"ts_updated_at": 1775791314,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/d160a368834a10eba3f268acf7326bd4c5458339.pdf",
		"text": "https://archive.orkl.eu/d160a368834a10eba3f268acf7326bd4c5458339.txt",
		"img": "https://archive.orkl.eu/d160a368834a10eba3f268acf7326bd4c5458339.jpg"
	}
}