Follow

How do I add machines in ProfileUnity machine-based license

Product: ProfileUnity

Product Version: 6.5 and above

Expires on: 365 days from publish date

Updated: February 22, 2017

 

Problem: How do I add machines in ProfileUnity machine-based license

 

Resolution:

 

ProfileUnity machine license supports machines that are in an organizational unit (OU) or in a container (CN).  It also support multiple OUs and CNs (although the use of CN is rare), which is useful when the computers are scattered.

 

The license requires the distinguished name of the OU or the CN.  First, you need to identify where your machines are.  Open Active Directory User and Computer and access your AD.  Browse to the location where your computers are.  Make sure that Advanced Features under View is selected before you right click on the object itself.  Select Properties in the pop-up menu and you will see the object's properties.  Click on Attribute Editor and look for distinguishedName.  Copy the name and we will add it to the license.  If you have multiple locations, repeat the same process until you obtain all distinguished names of the objects.

 

Once you have all the distinguished names, you will need to modify your license.  Open your license file (profileunity.lic) with Notepad.  You should see the last line look like this:

$scriptstart_license_ou = "CN=Computers,DC=MyCompany,DC=MyCorp; OU=Employees,DC=MyCompany,DC=MyCorp"

** If you see the option that is not $scriptstart_license_ou but $scriptstart_license_group, you DO NOT have a machine-based license, and you CANNOT continue with this process.  Please reach out to your account manager or Liquidware Labs support first before you move forward.

 

Replace the value inside the quote with the distinguish names of your OU or CN.  If you have multiple OUs and/or CNs, add everything in one single string separated by a semicolon.  The result may look like this:

$scriptstart_license_ou = "CN=Computers,OU=Atlanta,DC=example,DC=com; OU=VDI, OU=Boston,DC=example,DC=com; OU=XenApp,OU=Chicago,DC=example,DC=com"

 

Once the changes are made, save the changes, and copy the new license to your INI or license location specified in your ProfileUnity GPO.

 

 

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

0 Comments

Please sign in to leave a comment.