Asset skipped devices and other issues.
For asset tracking, we want to track all of our user workstations as well as all of our servers (mostly VMs.) For workstations, we import all of our inventory into Asset Management when we receive the hardware. We set the Asset Name, Serial Number and HW Asset ID to the serial number of the system. Now when we deploy a workstation, the hardware asset already exists when SCCM scans it for the first time. The Asset workflows go and rename the the asset to match to computer name, this has been working perfectly fine for us so far.
However, when we deploy a server the serial number is not known ahead of time. In that instance, we want Asset Management to create the hardware asset for us after the SCCM connector runs overnight. This is not happening right now. The Hardware sync log indicates that it is not the most recent computer with that SID (it is just a blank SID,) so it never makes the asset.
If I go into the HW Sync workflow settings and uncheck the box next to "Before creating, check for existing windows computer..." then it will create the HW assets for the items I am missing. However, we rename computers frequently so I think that turning that off would just introduce a new set of problems.
We are only importing computers from our SCCM connector. Our AD connectors do users only. I forget why we had done it that way, but I think it was recommended to not import computers from both locations.
Is it possible to have the Assets created automatically for our servers in this scenario?
Should we be using an AD connector for computer objects? What happens if we are also running the SCCM connector?