SCSM to Device42 connector
Completed- We need a connector so we can have SCSM query Device42 on a schedule and copy/update records (assets) on SCSM. So you are correct, create if it does not exist and update if it does exist. However, what would be even better would be if Device42 sees a filed already populated, don’t update it (as the data from SCCM, the other connector, would be more recent)
- You are right, connector queries should be based in name
- I’m not sure we can provide you with a mapping, but see attached how the DB from SCSM looks like with just the SCCM connector
- We basically would like to get things like name, asset number, type of asset (server, Vm, blade, etc), location, Environment (prod, dev, uat)
-
Connector for SCCM is now available: http://www.device42.com/integrations/sccm/
0
Please sign in to leave a comment.
Comments
1 comment