Asset Management Suite

Hi everyone,

Looking for some insight as to why my AMS environment isn't setting the primary asset owner based on the primary user for some computers.

Things to note:

- Machines that have missing asset owner, do have a primary user for the current month.

- Machines that have missing asset owner, have checked in with inventory successfully on a routine basis.

-  No error occurs when i manually run the Asssign Owner Job from with NS.

- There are no duplicate users in the database for the user that should be the primary asset owner.

- AMS / NS 7 are on the latest versions of both.

For the life of me I can't figure this out, there are some machines that just plain out will NOT set the primary owner for the asset.

Has anyone exeprienced this issue or might know a resolution for it?? I've checked everything I possibly know to check... So it is either a bug or I am missing something extremely straight foward...

I've just noticed a bit more info:

The reason that the primary user isn't being set properly on some machines is due to the fact that the AD connector isn't properly importing the "userID" and "Domain" fields from our AD structure.. even though both of these are present.

  I do have the default column mappings selected in AD import rule to bring in both of these items based on the proper attributes. Might anyone know why these wouldn't be populating?

If I manually set the UserID and domain information inside of the asset USER then, automagically the primary owner gets set to the asset. So obviously the job is using these two as a primary key to relate back to the actual user inside of NS.