지금 지원 담당자와 채팅
지원 담당자와 채팅

Migration Manager for AD 8.15 - Resource Processing Guide

Introduction to Resource Update Distributed Updates in Resource Updating Manager Common Resource Update Workflows Active Directory Processing Exchange Server Processing SMS Processing SQL Server Processing Cluster Server Migration Command-Line Resource Update SharePoint Processing

Pre-installing Resource Updating Manager Agents

Usually, Resource Updating Manager agents are installed to the computers you want to process directly from Resource Updating Manager console. If many computers are involved, this may cause excessive network traffic and slow down resource processing. Also Resource Updating Manager Agents cannot be installed from Resource Updating Manager console to computers with a firewall turned on. To avoid these issues, you can deploy Resource Updating Manager Agents on the computers you want to update using Group Policy, SMS Server and similar tools, or manually.

NOTE: When you deploy Resource Updating Manager Agents via Group Policy, make sure that you have the Full Control permission over the shared folder where the agent setup is located.

If the NetBIOS protocol is not supported in your configuration:

  • Follow the recommended typical scenario as described in Working in a Network Configuration with NetBIOS Protocol Disabled
  • Also you can use legacy registry keys to process the workstations:
    • For RUM agents that are distributed via agent setup: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aelita\Migration Tools\CurrentVersion\Resource Updating Manager (create this registry key if it does not exist)
      Create the RemoteController parameter in the Resource Updating Manager registry key on the computer where RUM console with RUM controller is installed and add the parameter value in one of the following formats: FQDN, IP address or NetBIOS name of the RUM Controller Service server.
    • For RUM agents that are distributed via Resource Updating Manager console: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\QsRUMController\Config
      Create the RemoteController parameter in the Config registry key on the computer where RUM console with RUM controller is installed and add the parameter value in one of the following formats: FQDN, IP address or NetBIOS name of the RUM Controller Service server.

To create agent setup

  1. Log on to the console with an account that has administrative rights over the computers. See the Obtaining Administrative Rights over the Computers topic for more details.
  2. In the Resource Updating Manager console toolbar, click Tools | Create Agent Setup.
  3. Specify credentials for the Migration Manager RUM Agent service account and folder path to save setup files.

After the Resource Updating Manager Agents were successfully deployed to the computers using agent's setup, these computers appear in the right pane of the Resource Updating Manager console. If they were never added to the groups (either from Active Directory or from Network), they stay under the Unconfigured category.

If You Used Aelita Domain Migration Wizard or Aelita Enterprise Migration Manager 5.x/6.x Agents

If Aelita Domain Migration Wizard or Aelita Enterprise Migration Manager 5.x/6.x agents were used to update resources on some computers and were not removed, they will not be overwritten by Resource Updating Manager Agents. You should remove the old agents first (using either Domain Migration Wizard or Enterprise Migration Manager 5.x/6.x) and then install Resource Updating Manager Agents. Domain Migration Wizard 5.x/6.x can use Enterprise Migration Manager agents as well.

 

 

Working in a Network Configuration with NetBIOS Protocol Disabled

This section is intended for network configurations where NetBIOS protocol is disabled. Starting from Quest Migration Manager for Active Directory Product Update 20201020 Resource Updating Manager can work even in a network configuration with the NetBIOS protocol disabled. Product behavior on all computers where RUM console is running depends on a DWORD value of UseNetBIOS in the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aelita\Migration Tools\CurrentVersion\Resource Updating Manager registry key. The table below shows the product behavior depending of the value of UseNetBIOS, or in case this key is omitted.

 

Feature or option

UseNetBIOS=0

UseNetBIOS has any value that is not equal to 0 or this value is omitted in the registry key

Adding computers from AD

Computer’s FQDN name will be added

 

Computer’s NetBIOS name will be added

 

Adding computers from Computer Browser

No option to add (since no Computer Browser when NetBIOS is disabled)

No option to add (the dialog will be empty)

 

Adding computers from migration project

No option to add from migration project (migration project usually contains no computers in the case)

 

Computer’s NetBIOS name will be added

 

Folder name for RUM logs

RUM log folder will be named after computer’s name as it listed in the RUM console without DNS suffix (folder name stays the same even after Moving to target and changing DNS suffix in RUM)

 

RUM log folder will be named after computer’s name as it listed in the RUM console
Select button for a target domain in the Create Move Task dialog

The button is intentionally hidden in the dialog

 

No option to select (The dialog will be empty)

 

Agents deployment

Agents will connect to RUM Controller by its FQDN name.

Agents from MSI packages will be registered by computer’s FQDN name.

Agents will connect to RUM Controller by its NetBIOS name.

Agents from MSI packages will be registered by computer’s NetBIOS name.

IMPORTANT: In case you add or change value of UseNetBIOS, the change takes effect after restarting the QsRUMController service and the Resource Updating Manager console.

Specifying the Processing Scope

Before you start resource processing, the processing scope should be determined. You should create collections and include the computers you want to process. A collection contains computers and defines processing settings for them.

By default, you can work only with those collections that were created in the Resource Updating Manager console on the current computer. To gain access to collections created from other instances, disable the View | Show only collections created from this computer option in the main menu.

Creating Collections

To create a collection, in the left pane of the Resource Updating Manager console, right-click the Collections node and select Create Collection. Specify the collection name and an optional description, then add the computers you want using the Included Computers dialog box. The created collection node will appear under the Collections node in the console management tree.

Adding Computers to a Collection

To add computers to a collection, right-click the collection node and use the options in the Add Computers sub-menu.

To add computers from Active Directory

  1. Right-click the collection node and select Add Computers | From Active Directory.
  2. In the Add Computers from Active Directory dialog box click Browse.
  3. In the Select Location dialog box that appears expand the tree, browse to the container where computers you want to process are located, and then click OK. The list of computers located in the selected container will be displayed in the Computers list.
  4. Select the check boxes next to the names of computers you want to add to the processing scope or click Select All.
  5. Click OK to close the dialog box.

To add computers from the network

  1. Right-click the collection node and select Add Computers | From Computer Browser.
  2. In the Add Computers from Computer Browser dialog box select the domain from the Domain drop-down list. The list of computers located in the specified domain will be displayed in the Computers list.
  3. Select the check boxes next to the names of the computers you want to add to the processing scope or click Select All.
  4. Click OK to close the dialog box.

To add computers from a file

  1. Right-click the collection node and select Add Computers | From Text File. You are prompted to add computers listed in an import file prepared in advance.
  2. In the file selection dialog box, select the import file and click Open.

The import file is a text file with two tab-separated columns. Every line should contain a computer you want to process, in one of the following formats:

  • NetBIOS name with an optional domain NetBIOS name in the second column
  • FQDN
  • IP address

You can write your comments in the file after the * character.

Example:

*This is a comment

\\ComputerName1 NetBIOSDomainName

\\ComputerName2

ComputerName3 NetBIOSDomainName

ComputerName4

computername5.domainname.corp

12.34.56.78

Note: Import files exported from Resource Updating Manager console in Migration Manager version 8.3 and earlier are also supported.

To add a specific computer

  1. Right-click the collection node and select Add Computers | Single Computer option.
  2. Specify the name of the computer you want to add and the domain that the computer is a member of.

To add computers from an existing migration project

  1. Right-click the collection node and select Add Computers | From Migration Project. You are prompted to specify computers included in a migration project.
  2. In the Add Computers from Project dialog box select the check boxes next to the migration scopes that you need.
  3. Click OK to load all the computers in the selected scopes.

After computers are added to the collection, they appear in the right pane of the Resource Updating Manager console.

Specifying Preferred Master Browser

Resource Updating Manager cannot perform the Add Computers from Network and Add Computers from File operations (excluding cases when domain name is specified for all computers in the import file) if the information about domains in the network is not complete on the Computer Browser servers.

You can set a Preferred Master Browser or the domain in which it is located to use the specified Preferred Master Browser later for enumerating domains in the network.

Take the following steps:

  1. Run Registry Editor and browse the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aelita\Migration Tools\CurrentVersion\Resource Updating Manager registry key (or the HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Aelita\Migration Tools\CurrentVersion\Resource Updating Manager registry key on a computer running a 64-bit version of Microsoft Windows). If this key is absent from the registry, create it.
  2. Create a new PreferredMasterBrowser string value in the key. Specify either the NetBIOS name of Preferred Master Browser or NetBIOS name of the domain in which Preferred Master Browser is located, as follows:

DomainName

or

\\PreferredMasterBrowserName

NOTE: When specifying a domain name, do not add two backslashes before it. However, you must type two backslashes (\\) before the name of Preferred Master Browser. Any time you edit the registry, you must restart Resource Updating Manager console.

Removing Computers from a Collection

To remove a computer from a collection, right-click the computer in the right pane of the Resource Updating Manager console and select Remove.

Discovering Computers

Before starting to process computer resources, Resource Updating Manager discovers the computers included into the processing scope and collects various statistical information, including the following:

  • Operating system installed
  • Operating system architecture
  • Last logged-on user

NOTE: Discovery may not detect users logged on remotely through Remote Desktop Services.

Also, Resource Updating Manager provides information about computer status and task results.

To view computer information, right-click a computer and select View History. The following information is displayed:

  • List of performed tasks
  • Task operation date and time
  • Computer status
  • Error description (if any)
  • Resource Updating Manager Agent status
  • Last operation date and time

To view the information about a specific task, go to the Task tab in the right pane in the Resource Updating Manager console, then right-click the task and select View Results.

Importantly, Resource Updating Manager agents are installed on the computers as part of the discovery process.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택