Asset location field does not update when user location changes

[theroz]

We have users in our company who move to different locations. When there location field for their user record is updated to the new location, the asset location field does not change. However, if I in-assign and re-assign the asset to the same user, the location field updates to the user's new location. I thought maybe there was a bug in our Kingston instance, but this appears to be an out of box function because I can duplicate it in a dev instance on ServiceNow. Is there a fix in place or planned to address this issue of not having the asset location change when the assigned to user location changes?

[Uncle Rob]

This is on purpose.  The location of an asset is far more important than the user it's associated with, and you can't universally assume that moved user = moved assets.  Consider:  If I move from the NY office to the London office, are they shipping my desktop PC?  More likely they're just reclaiming it and giving me another one over there.  

Back in the day, my solution was to front the move process in ServiceNow.  This workflow involved a task to check / update asset information.

[theroz]

Thanks for the reply. So to correct any mismatches....can I just bulk update the Assigned to location field to match the user location if necessary?

[Uncle Rob]

As a ServiceNow resource, I wouldn't hazard a guess nor a suggestion.  It's an asset management question for an asset manager.  You can't just a global assumption on the data like that.

Asset management deals in all the unreliability of real life.  I *suspect* that assets have to be validated as actually existing at the locations you expect them to be in.  Otherwise the asset is *lost*.