Claire, We faced a similar problem here - we only needed to track about 8 types of CI, and the amount of classes offered in the OotB solution was way over the top (not to mention incredibly confusing in the way SHR:SchemaNames presents those classes to the end user menus).
Given the BMC themselves have considerably trimmed the common data model in CMDB 2.0, if you are using version 1.1 you're probably better off hiding the out-of-the-box classes and creating your own classes extended from Asset Base. With a few tweaks to the data in SHR:SchemaNames, you can get these classes displaying to end users in a friendly manner. We had good customer response when we did that here - we exported our data our from AST:Asset and partitioned it into the 8 classes we wanted and them imported the data from there. Cheers, Matt -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Sanford, Claire Sent: Wednesday, 23 August 2006 4:39 AM To: [email protected] Subject: HelpDesk 6.x - CMDB Are any of you out there using the Help Desk package and struggling with the way they have changed the Asset Tracking part of the package to the CMDB? What did you do to work around it or to use your old data in the new format??? We track 4 major things. PC Scanner Monitor Printer We don't need all of the other fluff and stuff. ARS 6.3 HD 6.0 Oracle Win2003 Thank you! Claire ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org ********************************************************************** The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you have received this communication in error, please notify us immediately by return e-mail with the subject heading "Received in error" or telephone +61 2 93357000, then delete the email and destroy any copies of it. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any opinions or advice contained in this e-mail are subject to the terms and conditions expressed in the governing KPMG client engagement letter. Opinions, conclusions and other information in this e-mail and any attachments that do not relate to the official business of the firm are neither given nor endorsed by it. KPMG cannot guarantee that e-mail communications are secure or error-free, as information could be intercepted, corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. KPMG, an Australian partnership, is part of the KPMG International network. KPMG International is a Swiss cooperative that serves as a coordinating entity for a network of independent firms operating under the KPMG name. KPMG International provides no services to clients. Each member firm of KPMG International is a legally distinct and separate entity and each describes itself as such. Liability limited by a scheme approved under Professional Standards Legislation. This footnote also confirms that this e-mail message has been swept by MIMEsweeper for the presence of computer viruses. See www.mimesweeper.com for more information. ********************************************************************** _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
