Location Mapping in Hardware workflow not working when multiple IP addresses found from SCCM
Is there a way of selecting the most recent IP adress from the information from SCCM without tweaking SCCM?
Our Computers inventory hardware every 7 days, I want this to be every day, but since it remembers all the IP addresses in the inventory data, the location for the connected hardware asset will not be update anymore.
I want the location to be update daily, because this is what happens within our Company, employees are always travelling over the world.
Is this possible?
Best Answer
-
pzerger Partner Adept IT Monkey ✭✭Getting only the "primary IP" is tough largely due to lack of consistency across environments. This MS thread has a query I have used for this purpose with success in a couple of situations. https://social.technet.microsoft.com/Forums/systemcenter/en-US/b5f720f0-48ae-4793-81b5-114d28831857/sccm-sql-query-ip-address?forum=configmgrgeneral.
With the Cireson Asset Import Connector, you could actually use this query to bring the data in directly to the class of your choice, as long as it's in a sealed MP. No custom automation required.6
Answers
Currently, AM will throw warnings it its logs if 2 or more IPv4 addresses are detected from ConfigMgr.
A work around would be to leverage the SCSM workflow framework or Orchestrator to to overwrite the ConfigMgr IP data for network adapter related to a Computer CI. This assumes that you have a mechanism to determine which IP address is the correct one at that time from the ConfigMgr data.
Have you (Cireson) got any response from MS's on this?
This is a tricky one though, and based on the information given by Allen above I think one possible solution is to have the computer itself update its IP through a secondary means. Depending on your use of Azure automation, the computer could run a Powershell script regularly to trigger a simple webhook with some data to update the network adapter data for that machine is SCSM.
Ive done something like this previously and it's definitely something our services team is capable of helping with.
If if you need something more on prem (computers are always inside the network) you could have the machine update a csv and use the AM import connector to update the information from there.
The he options are many!
Jon, what are your requirements?
But in our environment we lose track of almost 25% of laptops because they never connect to the corporate network anymore. Since SCCM isn't available from the internet ( a 5 year old wish to get this implemented ) I have no source, a simple Azure based webhook would be great for this and I actually see a good idea for a new Cireson App
Thanks for thinking with me and there is 1 thing I'll check and that is the order of the reported IP adresses, it might just be the order in which they were discovered.
I'll get back on this.
We'd just like the best way to have an ootb updated IP-adress on the CI in SCSM
Much of the brainstorming above will help even though I'd like to be able to rely on the feed from SCCM as a starting point before moving over to workarounds. In ootb SCSM this doesn't provide much value but becomes much more important when transforming SCSM to an ITAM tool.
As Cireson ITAM feels like the most demanding add-on-solution for SCSM I think that Cireson has good opportunities to feed MS with enhancement requests for this kind of functionality.
We'd want to use this functionality for workflows when an owner (likely a manager) wants to identify all the PC's in his/her department.
Some PC's will need additional info to be found and will then need to be identified via the last IP.
With the Cireson Asset Import Connector, you could actually use this query to bring the data in directly to the class of your choice, as long as it's in a sealed MP. No custom automation required.