RM Logo
Technical Rating: 
Support Home PageSupport
Print This PagePrint This Page
Add to 'My Library' Add to 'My Library'

RM Unify Network Provisioning - How to upgrade Network Agent v1 to v2
Published Date : 15 May 2023   Last Updated : 04 Aug 2023   Content Ref: TEC9126101  





Symptoms

You have an existing installation of RM Unify Network Provisioning using RM Unify Network Agent v1. This article explains how to upgrade the Network Agent from v1 to v2 on a: 

  • Vanilla Windows network: Single-site or multi-site RM Unify Network Provisioning
  • Community Connect® 4 (CC4) network: Single-site or multi-site RM Unify Network Provisioning

The upgrade process assumes that you are upgrading the Network Agent on the same server on which RM Unify Network Provisioning is currently configured. This is essential, as the reinstallation uses the existing configuration files.

Do not follow this article if you want to install RM Unify Network Agent v2 on a new server. Instead, please raise a service call with the Cloud Support team or your usual Network Support team for further advice.



Cause

Why should I upgrade to Network Agent v2?
  • New feature for RM Unify Network Provisioning on vanilla Windows networks:
    Write RM Unify deleted information to linked AD accounts. Currently, the Network Agent disables an AD account when its linked RM Unify user account is disabled or when the user has left the RM Unify establishment. This makes it difficult to determine if disabled AD accounts are results of disabled or deleted RM Unify accounts. To assist with this, with Network Agent v2, you can now configure the Agent to populate an AD account attribute with deleted date information when the RM Unify account is deleted, enabling you to query AD for accounts linked to deleted RM Unify users only. Please refer to TEC9141795 in the Other Useful Articles section below for more details.
  • Improved Network Agent auditing messages in the RM Unify Audit log.
  • Compatibility with Microsoft .NET Framework 4.8.
  • Ability to automatically receive future improvements to the Network Agent - no user intervention required and no disruption.
  • As of now, there will be no further development or security update patching of Network Agent v1.

Who can complete the upgrade?
  • Provided the prerequisites are met, you can upgrade the Network Agent yourself regardless of whether RM Unify Network Provisioning was originally installed as part of an installation service completed by RM. 
  • If we currently provide you with a managed service, your existing managed service support team will manage the upgrade.


Requirements

How to identify which version of RM Unify Network Agent is installed?
  1. On the server running the RM Unify Network Agent service, open 'Programs and Features'.
  2. Find RM Unify Network Agent and check the number listed in the Version column.
  3. Network Agent v1 will have a Version number '1.x'. Network Agent v2 will have a Version number '2.x'.

Prerequisites
  1. Microsoft .NET Framework v4.8 on the server where the existing RM Unify Network Agent is installed.
  2. The Network Agent is provisioning users to the parent domain of your Active Directory. If it is provisioning users to a child domain, please contact Cloud Support for additional upgrade steps.
  3. RM Unify user with super admin rights, e.g. rmunifyadmin.
  4. Active Directory administrator account, i.e. membership of Domain Admins and Administrators group.
  5. When upgrading the Agent, password synchronisation between AD and RM Unify will be temporarily unavailable. For this reason, we strongly suggest that you upgrade the Network Agent outside of school hours.


Procedure

Check if .NET Framework 4.8 is installed
  1. On the Network Agent server, run regedit.
  2. Browse to 'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full'.
    Note: If the Full subkey is missing, then .NET Framework 4.5 or later isn't installed and you should proceed to install .NET Framework 4.8.
  3. Select the Full subkey and, in the right-hand window, check the Release REG_DWORD value.
  4. If the value is less than 528040, please proceed to install .NET Framework 4.8.
  5. If the value is 528040 or greater, .NET Framework 4.8 is already installed.

Install .NET Framework 4.8
  1. Download .NET Framework 4.8 and follow the installation instructions from this article: Microsoft .NET Framework 4.8.

Note: You may be prompted to reboot your server as part of the installation.


Upgrade the Network Agent
  1. Sign in to RM Unify as a super admin user.
  2. In the Management Console, click 'Sync users to AD'.
  3. Click Generate Network Agent MSI to download a copy of the RM Unify Network Agent MSI.
  4. Copy the downloaded RM Unify Network Agent MSI to a temporary location on the Network Agent server.
  5. Open Services and stop the RM Unify Network Agent Service.
  6. On the Network Agent server, open Registry Editor and browse to '[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RM\RM Unify Network Agent]'.
  7. Right-click 'UPTBlockUserProvisioning' and select Modify.
    Note: please see Possible Issues section below is key is missing.
  8. Type true and click OK.
  9. Close Registry Editor.
  10. Open 'Programs and Features' and select to uninstall RM Unify Network Agent.
  11. Click Finish.
  12. In File Explorer, browse to where you saved the RM Unify Network Agent MSI and double-click to run it.
  13. Click OK to the window message "Just to let you know, we're going to extend the Active Directory Schema....".
  14. Click Finish.
  15. Using the 'Run as administrator' option, run the RM Unify Provisioning Test Tool to confirm if the three test user accounts can be created successfully. Please see TEC7323785 in the Other Useful Articles section below for more information.
  16. Open Registry Editor and browse to '[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\RM\RM Unify Network Agent]'.
  17. Right-click 'UPTBlockUserProvisioning' and select Modify.
  18. Type false and click OK.
  19. In the RM Unify Management Console, click User Audit, review the entries for any errors and follow up.


Possible Issues

Missing 'UPTBlockUserProvisioning' registry key

When following step 7 from the 'Upgrade the Network Agent' section above, if the 'UPTBlockUserProvisioning' registry key is missing, follow the steps below to manually add the registry key before continuing with the steps to upgrade:

  1. Right-click the RM Unify Network Agent key and select New, String Value.
  2. Set 'Value name' as 'UPTBlockUserProvisioning'.
  3. Set 'Value data' as 'true'.

Note: Set 'Value data' to 'true' if upgrading now, following the steps from this article. Otherwise, set it to 'false' as setting it to 'true' will block user provisioning.



FEEDBACK
Did the information in this article help answer your question?
 Yes
 No
Please add any comments about this article in the box below. If you answered No then it is important you tell us why so that we can change the article if required. We can only respond if you log in to the RM Support website or provide your contact details. Note: If you need help with a technical query, please log a call online or telephone our support team.
Thank you for your feedback, which is sent directly to the RM Knowledge team. We address every message received with the intention of improving our Knowledge Library articles. If you have an unresolved technical issue, please contact RM Support.


If this article has not helped provide a solution then it is also possible to log a call...



Document Keywords: RM Unify network provisioning - how to upgrade Network Agent, rm-install, Active Directory, ad, new user, solution, rmuvnp, rmunp, vanilla, non-cc4, cc4, amend, TEC9126101, v1, v2, version 1, version 2, .net 4.8


Please read - important disclaimer information.
http://www.rm.com/_RMVirtual/Includes/csredirect.asp?cref=&title=Standard Content Disclaimer


Top Of PageTop of page