Page Comparison

...

There are ways to get around the issue however if the CMDB import populates the "Global Windows User" dataclass with the domain name and user id of the user being imported.

The Arellia suggests that the following three sql scripts will assist with the User Resource import without Resource Keys being populated issue:, and should check with your Symantec Support Representative before testing or applying any changes.

select * from Inv_Global_Windows_Users GWU
WHERE EXISTS
	(select 1 from ResourceKey RK where RK.KeyName = 'name.domain' and RK.KeyValue= (GWU.UserId + '.' + GWU.Domain)
	and RK.ResourceGuid != GWU._ResourceGuid)

...