Deploy App-V 5.0 Client Configuration VIA GPO on Windows Server 2012

-

Deploy App-V 5.0 Client Configuration VIA GPO on Windows Server 2012


 Things you should know before begin deploying client:
  • Active Directory Knowledge on OU, Groups and GPO’s.
  • Scripting in Power Shell is a plus.
  • Well understanding when deploying GPO’s, such as time it takes to apply and if you want to deploy this policy to machines or users.
  • I recommend Create an OU named _MS_ Application_ Virtualization to assign policies only to that OU and no affect the whole users of your AD.

1. Assign App-V Client Configuration via Group Policy

a. Install MDOPADMXTemplate.msi, you could found at Microsoft site http://www.microsoft.com/en-us/download/details.aspx?id=35516
b.  If you want to use ADMX you should have Windows Server 2008 R2 or later.
c.  Import the MDOPADMXTemplate.msi in Group Policy Access.
d.  Now go to Group Policy Management on the Root domain controller.
clip_image002
e. Expand you Active Directory hierarchy, and Search your  OU _MS Application_Virtualization or as you named before. 
f.  Create a New Policy Linked to _MS_Application_Virtualization OU. 
g. I recommend you to use a clear name for that policy as  “AppvClient Configuration” click OK, then Edit.
clip_image004
clip_image006
h. Where is my App-V  ADMX ?
i. Go to   > Computer Configuration > Policies > Administrative Templates > System > App-V > Publishing
clip_image008
i. Click on Publishing Server 1 to assign the configuration as show in the below image.
clip_image010

Then of this step just go to client computers and made an GPUPDATE /force or just restart the machine.

 
 
 
Thanks for watching if you need more info write me an e-mail or comment.




app-v 5 client gpo deploy

 appv 5 step by step

 app-v infrastructure
app-v 5 client configuration
appv 5 admx

Comments

Post a Comment

Popular posts from this blog

How to create a NIC Teaming on Windows Server 2012 UPDATED !

-
Image
CLICK ON THE BELOW LINK FOR THE UPDATED POST   How to Create/Configure a NIC Teaming on Server 2016/ 2012 Physical or VM's How to create/ enable a NIC Teaming on Windows Server 2012 /R2 NIC Teaming Overview NIC Teaming, also known as load balancing and failover (LBFO), allows multiple network adapters on a computer to be placed into a team for the following purposes: Bandwidth aggregation Traffic failover to prevent connectivity loss in the event of a network component failure  This feature has been a requirement for independent hardware vendors (IHVs) to enter the server network adapter market, but until now NIC Teaming has not been included in Windows Server operating systems. More Info: Windows Server 2012 R2  http://technet.microsoft.com/en-us/library/hh831648.aspx NIC Teaming Step  by Step I've made this tutorial on a Hyper-V 2012 Virtual Machine with Server 2012 R...
Read more

Update Rollup 3 for System Center 2012 R2 Service Manager

-
Update Rollup 3 for System Center 2012 R2 Service Manager   Issues that are fixed in this update rollup Service Manager The Microsoft Systems Center 2012 Operations Manager configuration item (CI) connector does not retrieve disk mount point information for the Service Manager database. When a service request is created from a request offering in the console and when every user prompt is of the Simple List prompt type, the console shows options from all simple lists in each user prompt. When you try to close a customized change request, you cannot close the change request, the task throws an error, and the close is not actioned. MPSync job failures that are logged to the event log do not contain enough information to allow for a quick diagnosis of the problem. All Service Manager workflows may stall when any invalid XML characters (control characters) are used in a work item property. Using the "Set Fi...
Read more