Change the resource/asset-type of an asset

Linne,
I would create a brand-spanking new resource type for Switch and another one router, both of these should inherit from network device. Then I would create any resource associations that are needed, but not inherited for the resource types. Then when you go to import you should be able to import as "Router" or "Switch"

Cheers,

John Golembiewski
Midwest Practice Principal
ITS Partners
Jgo@itsdelivers

You could create a new data class to associate to that Resource type. The steps to do it are rather easy.
Using the old console go to your "Configuration" tab.
Then navigate to "Resource Settings" > "Data Classes" > "User Defined"

Right-Click and select "New Editable Data Class"

Name it something like "Extended Network Device Type"

Pick a Tab Name or leave it General.

Add an Attribute. (In this case I'd choose Static List)

Give your values "Switch" and "Router" (it's also a good idea to change your Maximum Length to the number of characters on your longest entry)

Once you've saved that Data Class browse to the Network Resource on the Configuration Tab.

Mine is located in "Resource Settings" > "Resource Types" > "Asset Types" > "IT" > "Network Resource"

Click the "Add Data Classes" button and go from there.

I would only track them as two separate resource types if you had distinctly different data that needed to be tracked. If you're just tracking the same things, like ownership, location, rack info, and such for both of them I'd follow this solution I mentioned above.

Hi John,

I already created the new ressource types (on the base of network device) and I am able to import NEW assets as switch or router.

BUT I want to modify already existing routers and switches which are at the moment "network devices" to the new ressource type switch and router.

How can I do that?

Linne

Hi MBHarmon,

I think I know what you mean. I do the same with the peripherals and work there with a static list with entrys like "USB-stick, Docking station" etc.

I did this, because I want to be able to differ peripheral-assets via one value.

But, wouldn't it be a better way to create a new asset type for switch and router? Isn't it easier to handle? Are there arguments, what's best practice?

Cheers
Linne

Here are your options... All of these are given with the assumption that what is currently in Network Devices are all "Routers" or "Switches" or enough of them could be lost...

1. Delete everything from Network Devices and start from scratch.
2. Export and then re-import the assets:
   1. Create a report of all "Routers" or "Switches" that are mislabeled as Network Devices.
   2. Create an Export to grab all Data Classes of devices that are on that report.
   3. This is a decision point... you could either let Duplicate Asset merging cure all of your woes later today OR delete the "Routers" or "Switches" that are mislabeled as Network Devices. Depending on your environment I think both are valid options.
   4. Run an import on the Data you exported in Step 3 into it's appropriate Resource Type.
   5. If all went well, take a break. You've earned it.

John Golembiewski
Midwest Practice Principal
ITS Partners
Jgo@itsdelivers

In the middle of my coffee break there were a few responses to the post... so the first I would like to respond to:

From mbharmon:

I would only track them as two separate resource types if you had distinctly different data that needed to be tracked. If you're just tracking the same things, like ownership, location, rack info, and such for both of them I'd follow this solution I mentioned above.

Completely agree. Good point!

from linne:

But, wouldn't it be a better way to create a new asset type for switch and router? Isn't it easier to handle? Are there arguments, what's best practice?

Better way for separating "Switch" and "Router"? Not sure. For reporting purposes I would think you could get the same information from either creating new resource types or from creating a drop down to signify type. This leaves usability, I would strongly suggest that you query your Asset Administrators to see what they would like. Either answer is easy to maintain, at this point it is more a matter personal choice. :)

NOTE: You might want to test out reporting on this both ways before you make your final decision.

Cheers,
John Golembiewski
Midwest Practice Principal
ITS Partners
Jgo@itsdelivers

The best practice as it was put to me at Manage Fusion in April was to decide if I was going to track different inforamtion. If it logically fit into a resource type and I didn't need to track anything differently I should use a data class to make the differentiation on a report.

NOTE: You might want to test out reporting on this both ways before you make your final decision.

That's a great point too. It really does just all come down to reporting and making sure you're reporting works the way the business unit needs it to.

@jgo
"I would strongly suggest that you query your Asset Administrators to see what they would like. Either answer is easy to maintain, at this point it is more a matter personal choice. :)"
--> I nearly do everything on my own with altiris. I'm respsonsible for the NS and implement the Inventory, Patch Mgt, Asset Mgt and now the Software Delivery. A few colleagues work with the assets or deliver patches, but that's it. So I often have to decide, which way is the best and that's not ever easy.

@MBHarmon
I understand the message. If the values are the same, I shouldn't create another asset type. In my case I need some different informations. If I differ the routers and switches only with a data class I would have to modify many reports and the standard reports for example would't differ too, if the asset is now a router, switch etc. So I think I create to different asset types. I think both ways could be best practice? Do you think too?

Cheers
Linne