Follow

Why add .Net 4.5.2 to systems when using ProfileDisk and DIA.

Product: ProfileUnity-FlexApp

Product Version: 6.5

Expires on: 365 days from publish date

Updated: Oct 6, 2015

 

Problem:

Why add .Net 4.5.2 to systems when using ProfileDisk and DIA.

 

Symptoms:

ProfileUnity leverages many aspects of the .Net library to complete it's function.  For DIA and ProfileDisk in ProfileUnity 6.5 it's required that .Net 4.5.2 is present on the systems

 

 

Possible Resolution(s):

 

For Non-Persistent

You can add this to the base by completing Windows updates, then shut down, snapshot and recompose.

 

For Persistent VM's or Physical machines

In ProfileUnity 6.5 there is a  new ADMX template this can be added as part of a new Computer GPO applied to OU.

To add the new ADMX template follow instructions on the Installation on configuration guide.

http://www.liquidwarelabs.com/content/pdf/documents/support/Liquidware-Labs-ProfileUnity-Installation-Guide.pdf

 

GPOadd1.png

Select the bit level appropriate for VDI desktops

GPOadd2.png

 

Edit Auto Install .Net and select enabled.

For persistent machines, please reboot to apply the GPO

For Non-persistent VDI it would be more effective to add to the parent image then recompose

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.