Not able to see computer objects in Modeling section of DMA project (NETIQKB52435)

  • 7752435
  • 02-Feb-2007
  • 30-May-2007

Resolution

fact
Domain Migration Administrator 7.x

symptom
Not able to see computer objects in Modeling section of DMA project

symptom
Can't find computer objects when modeling data

symptom
Computer modeling not working

symptom
Computers imported from a .csv not showing up in database modeling

cause

When computers are selected by importing a CSV file, Domain Migration Administrator (DMA) incorrectly adds/updates the ObjectName and SamAccountName column in the Model table of the project's database by adding an extra dollar sign ($$). 

The entries for each computer accounts' records show up as computerName$$. The double dollar sign is a mistake and should not appear anywhere in the table as this causes the computer to appear missing from the Modeling:Edit Computer data interface.



fix

This is a known issue with Domain Migration Administrator (DMA).  However, keep in mind that Microsoft Windows 2000/XP or later machines cannot be renamed and migrated at the same time. This limits the usability of the modeling functionality. However, if the modeling functionality is necessary to direct machines to a different OU, or you are migrating Microsoft Windows NT 4.0 machines, you can use the following process:

  1. Using Microsoft Access, open the projectName.mdb file (\Program Files\NetIQ\DMA\Projects\projectName\projectName.mdb).
  2. Select Tables.
  3. Double-click the Model table.
  4. Remove the trailing dollar sign ($) from the end of the ObjectName value and SamAccountName value for the computer accounts.

An alternative way to do this is to perform a Find/Replace on the ObjectName and SamAccountName columns to find the double dollar sign ($$) and replace it with a single dollar sign ($). This will remove all double dollar signs from the ObjectName and SamAccountName columns.

  • If you have computer names that actually contain a dollar sign, you will not be able to use this process and will need to update the values manually.
  • If you have users and computers that have the same name, you will not be able to use this process, as it will attempt to create a duplicate of the PrimaryKey value of SourcePath for the SelectedObjects table. 

Furthermore, computers and users of the same name cannot be migrated in the same project



Additional Information

Formerly known as NETIQKB52435

Feedback service temporarily unavailable. For content questions or problems, please contact Support.