Chat now with support
Chat mit Support

Migrator Pro for Active Directory 20.11.2 - User Guide

Upload Logs Result Codes

This table includes result codes for BT-UploadLogs PowerShell jobs.

Result Code Error Rollback Possible
32 (zip folder) could not be created. No
64 Failed to Zip log files on computer. No
128 Upload failed to contact the server. Please verify the URL (url) is correct and BITS is enabled. No

SQL Repermission Tool

Use the SQL Repermission Tool to update a SQL Server’s Source AD Windows Authentication Group Login permissions and their associated database users for the Target domain to which the user and group objects have been migrated.

Prior to re-permissioning SQL servers, accounts must be migrated and Mapping Files created using Migrator Pro for Active Directory.

  1. Open the SQL Repermission.msi file included in the installation.
  2. Run the installer on the Migrator Pro for Active Directory Server or any machine that will have access to the SQL Server instance and databases to be re-permissioned.

  3. The Welcome screen appears. Click Next to continue.

  4. The "Ready to Install the Program" screen appears. Click Install to begin the installation.

  5. When the installation completes, the "InstallShield Wizard Completed" message appears. Click Finish to close the wizard.

  6. Copy the map.usr and map.gg files created using Migrator Pro for Active Directory to a folder on the same machine.

  7. Launch the SQL Repermission Tool from the Apps screen or the Start menu.

  8. Select the SQL Logon Method. If SQL Server Authentication is selected, enter the Username and Password. If Windows Authentication will be used, you must be logged onto the machine with an account that has access to the SQL Server instance and databases to be re-permissioned.

  9. Click on Browse to select the SQL Server instance to be re-permissioned.

  10. Select the SQL server instance from the list and click on OK.

  11. Click on the Connect button. If connection is successful, the Logging message should read “SQL Server Connected” and there should be databases available to pick from in the drop-down list.

    Note: If the login information is incorrect, the following error will be received. The credentials to connect to the SQL server instance should be corrected, and then the Connect should be retried.

  12. Once successfully connected to the SQL Server instance, in the drop down select either <ALL> or a specific database that needs to be re-permissioned.

  13. Click on the Generate SQL button. If the Open script in Notepad option is left checked, the results will be displayed when completed.

  14. The Logging information will display the name of the SQL file created in the directory that the application is located.

  15. If the option to open the file in Notepad was not checked, navigate to where the file was saved and right-click and choose Open with Notepad.

  16. The results of the process can be reviewed prior to actually executing it on the SQL Server instance.

  17. When the SQL file has been reviewed, either open the file in SQL Server Management Studio or create a new Query in SQL Server Management Studio and copy/paste the contents of the file into the Query.

  18. Execute the Query and the new target credentials will be created.

Installing and Configuring SQL Server Reporting Services

Installing SQL Server Reporting Services

These instructions are for existing SQL Server installs where reporting services are being added.

  1. Load the ISO into the DVD drive.
  2. Open My Computer.
  3. Double-click on the DVD drive to run the SQL Server Installation Center dialog.
  4. Select Installation from the left.
  5. Select New installation or add features to an existing installation.
  6. Click the OK button on the Setup Support Rules page if everything passed.
  7. Click the Install button on the SQL Setup Files page.
  8. Click the Next button on the Setup Support Rules page if everything passed.
  9. Select Add features to an existing instance of SQL Server (verify your instance is shown).
  10. Click the Next button.
  11. Check the Reporting Services box and click the Next button.
  12. Click the Next button on Installation Rules.
  13. Click the Next button on Disk Space Requirements.
  14. Click in the Account Name field and select NT AUTHORITY\NETWORK SERVICE.
  15. Click the Next button.
  16. Click the Next button on the Reporting Services Configuration to Install, but do not configure the report server option.
  17. Click the Next button.
  18. Click the Next button on Installation Configuration Rules page if everything passed.
  19. Click the Install button on the Ready to Install page.
  20. If you have a green checkmark on the 'Complete' page, click the Close button.
  21. Close the SQL Server Installation Center dialog.

Configuring SQL Server Reporting Services

  1. Click Start > All Programs > Microsoft SQL Server > Configuration Tools.
  2. Click on Reporting Services Configuration Manager.
  3. Click the Connect button.
  4. Select Service Account from the left.
    • Verify Network Service is set for the built-in account.
  5. Select Database from the left.
    • Click the Change Database button.
    • Verify 'Create a new report server database' is selected and click the Next button.
    • Set your security type and click the Next button.
    • Leave the defaults. Verify 'Report Server Mode' is set to 'Native' (Reporting will fail to work if not in Native Mode)
    • Click the Next button.
    • Click the Next button.
    • Click the Next button and it will begin to configure the database.
    • Click the Finish button.
  6. Select Web Service URL from the left pane.
    • Click the Apply button.
  7. Select Report Manager URL from the left pane.
    • Click the Apply button.
  8. Click the Exit button.

Your Report URLs

Browseable URL

http://<servername>/Reports

or

http://<servername>/Reports_InstanceName (if SQL Server is installed as an instance)

Web Service URL

http://<servername>/ReportServer

or

http://<servername>/ReportServer_InstanceName (if SQL Server is installed as an instance)

Verifying the Report Server URL

The Report Server URL is needed when installing the Reporting feature. Use the following steps to verify the correct URL to use.

  1. Open up Reporting Services Configuration Manager.

  2. Provide the SQL Server Name and Report Server Instance name and click Connect.

  3. In the left folder navigation, select Web Service URL.

  4. The Report Server URL appears in the Report Server Web Service URLs section.

Creating a Linked Exchange Account

This process supports customers that require completing their AD migration before their Exchange migration by creating a linked Exchange account. This allows users to log into their mailbox that still resides in the source Domain, using their target credentials.

After an account has been migrated, the computer ReACL’d and Cutover to the target, follow these steps in order to link the target account to the Exchange mailbox still residing in the source.

  • In the Migrator Pro for Active Directory Console:
    1. Run the Action on the migrated user accounts “Enable on Target/Disable on Source”.
    2. Execute Sync in Migrator Pro for Active Directory for that Directory Sync Pro for Active Directory Synchronization Profile.
    3. Run the “Mark as Migrated” Action on the above user accounts.
    4. Filter on the “Migrated” column as “True” and verify only the accounts to be actioned are in the grid.
    5. Export the Migrator Pro for Active Directory Grid to a CSV.
  • On the Source Exchange server:
    1. Download the script file to a local directory and rename BT-ConvertMBX-to-Linked.ps1. The script can be obtained by contacting Support.
    2. Copy the updated CSV created from export of the Migrator Pro for Active Directory grid to the same local directory.
    3. Run the following Exchange PowerShell command – replace items in red date with actual data.

.\BT-ConvertMBX-to-Linked.ps1 –InputCsvPath c:\temp\Export.csv –OutputFolder c:\temp\outputlog –SourceDomainDC E2E-DC1.DOM1.E2E.dom –SourceDomainGC E2E-DC1.DOM1.E2E.dom –TargetDomainController QA-E2E-DC1.QA-Dom1.QA-E2E.dom

Results:

Log output will also be created in the directory specified in the PowerShell command.

Verification:

  • Check the following AD attributes:
    1. msExchMasterAccountSid of the source account should contain the target account objectSID value.
    2. Check that the legacyExchangeDN on the both the source and target account has not changed.
  • Check the mailbox using Outlook
    1. Log in to computer using target account.
    2. Launch Outlook.
    3. Outlook should launch without prompting for credentials (should us pass-through authentication).
    4. Check that any additional proxyaddress’ are still present on the source user mailbox.
    5. Spot check in Outlook for the retention of signatures, tool bar edits, etc.

Additionally:

  • Once all of the above has been completed and verified, migrate the mailbox to the target Exchange and verify that it is still accessible.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen