Deployment and Imaging Group

Our company is looking to move forward with Asset Management in ITMS 7.5 HF4.  With regard to Location, we are looking to find out what other companies has set for this.  Ultimately we want to find where a computer in, maybe not a granular as desk location but for or proximity.  Any help would be appreciated.

I have had customers go as granular as Cities, as they then associate Department objects with them.

I'd consider how you are going to maintain the location of individual assets. Unless you have systems in place to track every PC as its moved then you probably want to stick to Locations you can automatically assign computers to by subnet using a Task. Then you could add a few sub locations that will be assigned manually. So you might have a location for "Fourth Floor" when you have a subnet that covers the whole fourth floor, and maybe a sub location "Fourth Floor storeroom" if you maybe put spare PCs in a specific room when their Status is set to "Stock". But you are asking for trouble if you try and split the fourth Floor into "Fourth Floor East" and "Fourth Floor West" if you have to track those manually. If you create a Task to assign Location by subnet you might want to only run it against Desktops, you don't necessarily want laptops changing location all the time. One other point is that, if you change the filter that any of the CMDB Tasks are scheduled to run on you need to create a new Schedule for the task and stop the old one.

We have a very unique environment.  We do have subnets for floors but we also have subnets that cross floors and buildings.  Finally our wireless is on 1 subnet that is throughout our enterprise through 2 counties.  We might have to go by town and then break down by floor.  On the plus side we have our north, south, east floors with specific department numbers which we can break down even more by floor.

But if you have multiple locations across subnets with active computers you'll have to track every computer manually as it's moved between different wings of floors.

Wireless isn't generally such a problem as machines using it are usually not tied to a location anyway.
 

We use Active Directory OUs to set the location.

Another option would be to alter your computer naming scheme to append a location code.  I've had customers who have some elaborate naming conventions that can include locations and even departments.