How can I change Domain, UserId, and Email Address in the Altiris Database using Connector Solution and Microsoft Active Directory Import Rules?
Important: To reduce Altiris Database corruption, All changes to the Altiris Database must be made through the Altiris Console or other Altiris provided tools such as Altiris Connector Solution, Altiris CMDB Solution, OR Microsoft Active Directory Connector.
Altiris cannot support Altiris Databases that have been modified by manually changing the databases tables because all the needed modifications may not be made.
If you have manually modified the altiris database and are having problems with the altiris system, you will need to use a backup of the last known working database.
Scenario: The company has changed its name and domain from “smallcompany” to “bigcompany”, and has also changed its user names (“UserId” in Altiris and “User login name” in Active Directory) and email convention standards. Before the change, the company used the user’s first initial and last name for the username (“UserId” in Altiris, “User login name” in Active Directory) and email address, but now the company is using a unique employee number for the username, and the unique employee number and the new company name for the email address. For example, John Doe’s username was “jdoe”, but will change to his employee number “E12345”. His email address was “[email protected]”, but will change to “[email protected]”.
The Altiris Administrator wants to update the user information in the Altiris Database and Altiris_Incidents Database to the new conventions and standard while maintaining the integrity of the data.
The Altiris Administrator also wants to be able to use the Microsoft Active Directory Import rules to update information about the users and add new users to the Altiris System without creating a separate, new record for people already in the Altiris system.
In this case study, we are going to:
Disable Microsoft Active Directory Import Rules if they are enabled
You don’t want an Active Directory Import to run while you are updating the data in the Altiris Database because, if the information was changed in the database and the Active Directory Rule ran, duplicate records could be made for the same resources.
Create a .csv file to be a place holder for the data source information
For this case study, create a new, empty file called AltirisUserDB.csv at C:\Temp\Export.
Create the data source
Create a Resource Import/Export Rule
Modify the .csv file to change the User ID, Domain, and Email information using Excel or other editor
Modify the Data Source to Allow Imports
Edit the Resource Import/Export Rule to Allow Imports
Test the Rule
Run the Rule
Verify that the Information was updated in the Altiris Database
Allow the Altiris Incidents Database to Import Data from the Altiris Database
The Helpdesk/Incidents data will be updated to the new information in the Altiris Database based on a schedule, which by default is set to run every hour. Because the Helpdesk/Incidents data is updated using the user resource guid as the key (which was not changed), the corresponding data in the Altiris_Incidents database will be updated without duplicates being made.
(Optional) Update Active Directory Import to the new Active Directory (that has the new username/domain)
If you want to use the Microsoft Active Directory Import, modify the Microsoft Active Directory Import rules to use the new domain.
Because the Altiris Database has been updated with the new domain and new user information, when the Active Directory Import rule is run, the rule will compares Domain and UserId information in Microsoft Active Directory with the Domain and UserId information in the Altiris Database. Because the Altiris Database already has a record for the users with the new Domain and new UserId, duplicate records will not be created for those users. If other information for the user has been changed in Active Directory, that information will be updated in the Altiris Database. New users in Active Directory will also be added to the Altiris Database.