I am running into a significant amount of service oriented issues and wondering if anyone else has workarounds.

1. If you have a workstation (Dell in our case) and search for the service tag under assets it will not return any matches.
       a. If you switch the search field to workstation it does however work - resulting in a loss of time by having to        switch multiple areas to search.

2. If you have a existing piece of equipment in inventory (Laptop name corpmjdoe) and issue a replacement that has the same name a .xml file import wipes out all the asset information even though they have different service tags. Why is computer name a primary key in this case?

3. Why is it that only workstation has every field that you could ever want for information - but this information does not exist for any other pingable assets?
      a. Since licensing is based on pingable asset why is this info being withheld?
      b. Is there any documentation that shows the SNMP mapping and what fields they correspond to within SD?
           - I get different answers depending on the support tech.
      c. How do others troublshoot routers/printers/other equip when:
            -IP does not show for anything other than workstation, how do you have your staff ping/support/troubleshoot devices such as routers & printers?

4. Any request gets attached to the first asset a user has. So if 10 assets are assigned to a requestor then 100's of calls will be assigned to that asset. There is no management option to set to none and allow tech or requestor to choose asset  on ticket creation. Tech can manually change it through a 7-11 step process. We would prefer to globally set all requests to 'none' and have user/tech choose asset after investigation.

5. Attaching assets to sites. Takes up to and over 1 minute per asset.
When you add an asset and goto assign it to a location it builds a query that query is takes way to long. I only have 60 locations with 15 departments. The SD system attaches each department to each site so we end up with 900 entries. Assigning assets to sites is painstaking.

6. CSV imports of assets. - Even if you have the office field match up when the asset is imported it does not attach it to the site. So you manually have to attach them anyway - even if the site matches within the csv.

This is critical to our organization as each type of asset router, printer, terminal etc. is attached to a SD site. So when a user requests something our centralized support can pull up their information and site.

Requester: I am having trouble with my printer...
Tech: No problem, just let me ping that...oh wait I need you to goto the printer hit the config button, scroll to network, read me the IP ...etc but WAIT I can tell you you need cyan toner soon!

I have been asking for over a year and every time a canned response is provided (Feature enhancement) and wondering if anyone else who uses the asset module has these same issues.

-Joe