Re: Asset Management - Manual add software, license
Still not getting a license connect. Here's what I tried: Redefined Quickbooks software as a Product CI type. Updated the categorization in the license certificates. Created five software instances (Product CI), QuickBooks-1 to 05. Created five laptops (Computer System CI), related them to people (Dependency - Used By), added software, one to each, using Component (Child) relationship. Each laptop now shows two child relationships, dependency to a person and component to a product (QuickBooks). Back to SAM console, opened license certificates, created 'Attached To' relationships between license certificates and products (software) - all five product CIs are listed as Related CIs on the console, but the deployed numbers are still 0. Ran compliance only job - Found nothing at all - No CIs with certs, no CIs without certs, all four lines are 0s. Set job to do review and connect again - Found 5 CIs with no certs. Back to SAM console, the job disconnected all five product CIs again from the license certifications. Something is still throwing off the license engine. Again, is there anywhere in the documentation that explains what the License Engine uses to connect so I can check these details myself? The Product CIs and license certificates have the exact same categorization. Why isn't it accepting the 'Attached To' relationship I create manually? Do I have to use the license engine in order to confirm these connections (set the deployed values)? In this example, three specific items of software are supposed to be attached to one license cert, and two to another - if the license engine just maps whatever matches, how will I make sure it doesn't choose the wrong ones? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mori, Toshiyasu Sent: Wednesday, January 04, 2012 1:41 PM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Logan, 1. Please relate People to parent CI (Computer System) not Software Asset CI with Used by role (then you should see Person is associated to the Computer System Relationships table, RLE rule checks Person relationship when work with Per copy license type). 2. CI Type BMC_Application is not Software Asset CI Type it doesn't support RLE engine rule, you should choose either of CI Types from System Component - Product, Package, Operating System, Patch, System Software, System - Software Server as Software CI. 3. if you use Purchase Line item UI to create line item, it will give you message to select Contract and/or license certificate when CI Type was chosen Software Asset CI. Toshiyasu Asset management QA lead, BMC Software --- Toshiyasu Mori (Charles) ITSM QA Engineer, Service Support Dept Room 2403, 91 E. Tasman Dr, San Jose, CA 95134, U.S.A Tel: 1-408-571-7270 Fax: 1-408-571-7001 BMC Software www.bmc.comhttp://www.bmc.com/ toshiyasu_m...@bmc.commailto:toshiyasu_m...@bmc.com From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: Wednesday, January 04, 2012 10:00 AM To: arslist@ARSLIST.ORG Subject: Asset Management - Manual add software, license ** We will be using an outside product for procurement, so I am testing the process of adding software and licenses on ARS/ITSM 7.6.4. Following the instructions in the Asset Management User guide, I have created Application CIs and related them to users, and created a software contract and license certificates, and I have used the 'Search for Existing Record to Relate' function on the 'Software Assets' tab of the license certificates to relate the software CIs (Application CI type). But this does not change the deployment numbers on the certificate. When I run the license engine job (does a full check on all CIs for this company), it removes this relationship and states that the CIs have no certificates. What do I need to match to have the license engine link the Application CIs to the certificates? Certificates Company: PQ-GIO Status: Executed License Type: Per copy Related to Product Category: Manufacturer: Intuit, Inc. Product Name: QuickBooks Market Version: 12.0 Cat 1: Software Cat 2: Application Cat 3: Third Party Application CIs
Re: Asset Management - Manual add software, license
The license certificate and CI's need to have the same Company value as well as matching categorisations. You don't need to relate the certificates to the CI's, the engine will do that for you. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: 05 January 2012 16:37 To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Still not getting a license connect. Here's what I tried: Redefined Quickbooks software as a Product CI type. Updated the categorization in the license certificates. Created five software instances (Product CI), QuickBooks-1 to 05. Created five laptops (Computer System CI), related them to people (Dependency - Used By), added software, one to each, using Component (Child) relationship. Each laptop now shows two child relationships, dependency to a person and component to a product (QuickBooks). Back to SAM console, opened license certificates, created 'Attached To' relationships between license certificates and products (software) - all five product CIs are listed as Related CIs on the console, but the deployed numbers are still 0. Ran compliance only job - Found nothing at all - No CIs with certs, no CIs without certs, all four lines are 0s. Set job to do review and connect again - Found 5 CIs with no certs. Back to SAM console, the job disconnected all five product CIs again from the license certifications. Something is still throwing off the license engine. Again, is there anywhere in the documentation that explains what the License Engine uses to connect so I can check these details myself? The Product CIs and license certificates have the exact same categorization. Why isn't it accepting the 'Attached To' relationship I create manually? Do I have to use the license engine in order to confirm these connections (set the deployed values)? In this example, three specific items of software are supposed to be attached to one license cert, and two to another - if the license engine just maps whatever matches, how will I make sure it doesn't choose the wrong ones? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mori, Toshiyasu Sent: Wednesday, January 04, 2012 1:41 PM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Logan, 1. Please relate People to parent CI (Computer System) not Software Asset CI with Used by role (then you should see Person is associated to the Computer System Relationships table, RLE rule checks Person relationship when work with Per copy license type). 2. CI Type BMC_Application is not Software Asset CI Type it doesn't support RLE engine rule, you should choose either of CI Types from System Component - Product, Package, Operating System, Patch, System Software, System - Software Server as Software CI. 3. if you use Purchase Line item UI to create line item, it will give you message to select Contract and/or license certificate when CI Type was chosen Software Asset CI. Toshiyasu Asset management QA lead, BMC Software --- Toshiyasu Mori (Charles) ITSM QA Engineer, Service Support Dept Room 2403, 91 E. Tasman Dr, San Jose, CA 95134, U.S.A Tel: 1-408-571-7270 Fax: 1-408-571-7001 BMC Software www.bmc.com http://www.bmc.com/ toshiyasu_m...@bmc.com From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: Wednesday, January 04, 2012 10:00 AM To: arslist@ARSLIST.ORG Subject: Asset Management - Manual add software, license ** We will be using an outside product for procurement, so I am testing the process of adding software and licenses on ARS/ITSM 7.6.4. Following the instructions in the Asset Management User guide, I have created Application CIs and related them to users, and created a software contract and license certificates, and I have used the 'Search for Existing Record to Relate' function on the 'Software Assets' tab of the license certificates to relate the software CIs (Application CI type). But this does not change the deployment numbers on the certificate. When I run the license engine job (does a full check on all CIs for this company), it removes
Re: Asset Management - Manual add software, license
I did get the license engine to match up - I had updated the Market Version to be Pro / 12 instead of matching the 'Model/Version' value of Pro / 12.0 in keeping with the documented best practice so that I could have several versions (Pro /12.1, Pro / 12.2, etc.) that were all considered the same as far as licensing was concerned. Once I updated the 'Related Product Categorization' in the License Certificate, the engine did match certs to products. But this brings me back to the primary questions and the reason I wanted to do this manually: The engine did not match them correctly. Here is the situation: We have two 3-person license certificates ...-421 and ...-665, based off the same software contract. We have five users currently licensed, three on ...-665 and two on ...-421. Who (which product CI) goes on which (certificate) is already set in our records and needs to be set the same in Remedy. In the Asset Mgmt. User guide, it says that you can manually attach certs to products in this way, and then run the license engine. I manually attached the certs to the products as above, the correct three on ...-665 and the correct two on ...-421. When I run the engine job, instead of using the connections already there, it destroys those, then drops all five products onto the ...-665 cert, pushing it out of compliance. Is this normal? Isn't there some way to tell the engine to just validate what is already there? If I have five different certificates, each bought at different times for different people, how do I keep the license engine from randomly distributing these entries every time it runs??? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Thursday, January 05, 2012 11:49 AM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** The license certificate and CI's need to have the same Company value as well as matching categorisations. You don't need to relate the certificates to the CI's, the engine will do that for you. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: 05 January 2012 16:37 To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Still not getting a license connect. Here's what I tried: Redefined Quickbooks software as a Product CI type. Updated the categorization in the license certificates. Created five software instances (Product CI), QuickBooks-1 to 05. Created five laptops (Computer System CI), related them to people (Dependency - Used By), added software, one to each, using Component (Child) relationship. Each laptop now shows two child relationships, dependency to a person and component to a product (QuickBooks). Back to SAM console, opened license certificates, created 'Attached To' relationships between license certificates and products (software) - all five product CIs are listed as Related CIs on the console, but the deployed numbers are still 0. Ran compliance only job - Found nothing at all - No CIs with certs, no CIs without certs, all four lines are 0s. Set job to do review and connect again - Found 5 CIs with no certs. Back to SAM console, the job disconnected all five product CIs again from the license certifications. Something is still throwing off the license engine. Again, is there anywhere in the documentation that explains what the License Engine uses to connect so I can check these details myself? The Product CIs and license certificates have the exact same categorization. Why isn't it accepting the 'Attached To' relationship I create manually? Do I have to use the license engine in order to confirm these connections (set the deployed values)? In this example, three specific items of software are supposed to be attached to one license cert, and two to another - if the license engine just maps whatever matches, how will I make sure it doesn't choose the wrong ones? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email
Re: Asset Management - Manual add software, license
Logan, 1. SAM console Certificate and related CIs (or Unrelated CIs there are three tables in the Console) is only supporting RLE engine running results not manually adding Software Asset CIs (no matter what relationship type, Attached To, or other relationship type), that is as design. You should use license engine to confirm the connections (relationships). 2. Please choose license Job type to ALL instead of COMPLIANCE if haven't gotten any CI connection before. 3. Asset Management document have listed trouble shooting about not found CI connection or compliance status (deploy number) results are not expected. Please double check these (1)Make sure Software Asset CI records (Product) has the same Company as License Certificate and License Job (2)Make sure that license type using in License Certificate is the same as License Job (e.g. Per copy) (3)Make sure the License Certificate status is Active and Connect to Engine flag changes to Yes in Certificate form, and save the changes. (4)Make sure that License Job qualification covers what you want (you can leave product name, market version, tier 1, 2, 3 fields empty so RLE engine will check, make connection and calculate deploy number in a large scope of CI may take a little longer). 4. You can verify log to check connection but the log is more use for trouble shooting (error identification). Charles From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: Thursday, January 05, 2012 8:37 AM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Still not getting a license connect. Here's what I tried: Redefined Quickbooks software as a Product CI type. Updated the categorization in the license certificates. Created five software instances (Product CI), QuickBooks-1 to 05. Created five laptops (Computer System CI), related them to people (Dependency - Used By), added software, one to each, using Component (Child) relationship. Each laptop now shows two child relationships, dependency to a person and component to a product (QuickBooks). Back to SAM console, opened license certificates, created 'Attached To' relationships between license certificates and products (software) - all five product CIs are listed as Related CIs on the console, but the deployed numbers are still 0. Ran compliance only job - Found nothing at all - No CIs with certs, no CIs without certs, all four lines are 0s. Set job to do review and connect again - Found 5 CIs with no certs. Back to SAM console, the job disconnected all five product CIs again from the license certifications. Something is still throwing off the license engine. Again, is there anywhere in the documentation that explains what the License Engine uses to connect so I can check these details myself? The Product CIs and license certificates have the exact same categorization. Why isn't it accepting the 'Attached To' relationship I create manually? Do I have to use the license engine in order to confirm these connections (set the deployed values)? In this example, three specific items of software are supposed to be attached to one license cert, and two to another - if the license engine just maps whatever matches, how will I make sure it doesn't choose the wrong ones? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mori, Toshiyasu Sent: Wednesday, January 04, 2012 1:41 PM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Logan, 1. Please relate People to parent CI (Computer System) not Software Asset CI with Used by role (then you should see Person is associated to the Computer System Relationships table, RLE rule checks Person relationship when work with Per copy license type). 2. CI Type BMC_Application is not Software Asset CI Type it doesn't support RLE engine rule, you should choose either of CI Types from System Component - Product, Package, Operating System, Patch, System Software, System - Software Server as Software CI. 3. if you use Purchase Line item UI to create line item, it will give you message to select Contract and/or license certificate when CI Type was chosen Software Asset CI. Toshiyasu Asset
Re: Asset Management - Manual add software, license
If you create a new license contract with the same categorisation as one that exists then you should have been given the option to relate them together. This takes care of situations where you may have bought some licenses then later bought some more for the same software. If you do this then the engine will relate the CI's it finds to the first certificate and, when the number related equals the number on the certificate, relate the rest to the second certificate. You can't specify exactly which CI's connect to which certificate but you can specify which order the related certificates are used in (e.g. the one with the cheapest maintenance rate first) From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: 05 January 2012 18:06 To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** I did get the license engine to match up - I had updated the Market Version to be Pro / 12 instead of matching the 'Model/Version' value of Pro / 12.0 in keeping with the documented best practice so that I could have several versions (Pro /12.1, Pro / 12.2, etc.) that were all considered the same as far as licensing was concerned. Once I updated the 'Related Product Categorization' in the License Certificate, the engine did match certs to products. But this brings me back to the primary questions and the reason I wanted to do this manually: The engine did not match them correctly. Here is the situation: We have two 3-person license certificates .-421 and .-665, based off the same software contract. We have five users currently licensed, three on .-665 and two on .-421. Who (which product CI) goes on which (certificate) is already set in our records and needs to be set the same in Remedy. In the Asset Mgmt. User guide, it says that you can manually attach certs to products in this way, and then run the license engine. I manually attached the certs to the products as above, the correct three on .-665 and the correct two on .-421. When I run the engine job, instead of using the connections already there, it destroys those, then drops all five products onto the .-665 cert, pushing it out of compliance. Is this normal? Isn't there some way to tell the engine to just validate what is already there? If I have five different certificates, each bought at different times for different people, how do I keep the license engine from randomly distributing these entries every time it runs??? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Thursday, January 05, 2012 11:49 AM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** The license certificate and CI's need to have the same Company value as well as matching categorisations. You don't need to relate the certificates to the CI's, the engine will do that for you. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: 05 January 2012 16:37 To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Still not getting a license connect. Here's what I tried: Redefined Quickbooks software as a Product CI type. Updated the categorization in the license certificates. Created five software instances (Product CI), QuickBooks-1 to 05. Created five laptops (Computer System CI), related them to people (Dependency - Used By), added software, one to each, using Component (Child) relationship. Each laptop now shows two child relationships, dependency to a person and component to a product (QuickBooks). Back to SAM console, opened license certificates, created 'Attached To' relationships between license certificates and products (software) - all five product CIs are listed as Related CIs on the console, but the deployed numbers are still 0. Ran compliance only job - Found nothing at all - No CIs with certs, no CIs without certs, all four lines are 0s. Set job to do review and connect again - Found 5 CIs with no certs. Back to SAM console, the job disconnected all five product CIs again from the license certifications. Something is still throwing off the license engine. Again, is there anywhere in the documentation that explains what
Re: Asset Management - Manual add software, license
Logan, A small correction, in (3) change status of License Certificate to Executed (not Active as it doesn't provide such status value, sorry) and make sure Engine connection is Yes and save the update. Toshiyasu From: Mori, Toshiyasu Sent: Thursday, January 05, 2012 10:07 AM To: arslist@ARSLIST.ORG Subject: RE: Asset Management - Manual add software, license Logan, 1. SAM console Certificate and related CIs (or Unrelated CIs there are three tables in the Console) is only supporting RLE engine running results not manually adding Software Asset CIs (no matter what relationship type, Attached To, or other relationship type), that is as design. You should use license engine to confirm the connections (relationships). 2. Please choose license Job type to ALL instead of COMPLIANCE if haven't gotten any CI connection before. 3. Asset Management document have listed trouble shooting about not found CI connection or compliance status (deploy number) results are not expected. Please double check these (1)Make sure Software Asset CI records (Product) has the same Company as License Certificate and License Job (2)Make sure that license type using in License Certificate is the same as License Job (e.g. Per copy) (3)Make sure the License Certificate status is Active and Connect to Engine flag changes to Yes in Certificate form, and save the changes. (4)Make sure that License Job qualification covers what you want (you can leave product name, market version, tier 1, 2, 3 fields empty so RLE engine will check, make connection and calculate deploy number in a large scope of CI may take a little longer). 4. You can verify log to check connection but the log is more use for trouble shooting (error identification). Charles From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: Thursday, January 05, 2012 8:37 AM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Still not getting a license connect. Here's what I tried: Redefined Quickbooks software as a Product CI type. Updated the categorization in the license certificates. Created five software instances (Product CI), QuickBooks-1 to 05. Created five laptops (Computer System CI), related them to people (Dependency - Used By), added software, one to each, using Component (Child) relationship. Each laptop now shows two child relationships, dependency to a person and component to a product (QuickBooks). Back to SAM console, opened license certificates, created 'Attached To' relationships between license certificates and products (software) - all five product CIs are listed as Related CIs on the console, but the deployed numbers are still 0. Ran compliance only job - Found nothing at all - No CIs with certs, no CIs without certs, all four lines are 0s. Set job to do review and connect again - Found 5 CIs with no certs. Back to SAM console, the job disconnected all five product CIs again from the license certifications. Something is still throwing off the license engine. Again, is there anywhere in the documentation that explains what the License Engine uses to connect so I can check these details myself? The Product CIs and license certificates have the exact same categorization. Why isn't it accepting the 'Attached To' relationship I create manually? Do I have to use the license engine in order to confirm these connections (set the deployed values)? In this example, three specific items of software are supposed to be attached to one license cert, and two to another - if the license engine just maps whatever matches, how will I make sure it doesn't choose the wrong ones? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Mori, Toshiyasu Sent: Wednesday, January 04, 2012 1:41 PM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** Logan, 1. Please relate People to parent CI (Computer System) not Software Asset CI with Used by role (then you should see Person is associated to the Computer System Relationships table, RLE rule checks Person relationship when work with Per copy license type). 2. CI Type BMC_Application is not Software Asset CI Type it doesn't support RLE engine
Re: Asset Management - Manual add software, license
Thanks Peter, that did work. Hopefully specifying the certificate a user is on won't be an issue. (I was able to go into the certificates and use the 'Manage Groups' On a related note, now that I understand how critical 'Market Version' is - Am I missing it on the Data Management tool spreadsheets for 7.6, or do I have to go in an set it manually for the software after I load it in? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Thursday, January 05, 2012 1:17 PM To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** If you create a new license contract with the same categorisation as one that exists then you should have been given the option to relate them together. This takes care of situations where you may have bought some licenses then later bought some more for the same software. If you do this then the engine will relate the CI's it finds to the first certificate and, when the number related equals the number on the certificate, relate the rest to the second certificate. You can't specify exactly which CI's connect to which certificate but you can specify which order the related certificates are used in (e.g. the one with the cheapest maintenance rate first) From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: 05 January 2012 18:06 To: arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** I did get the license engine to match up - I had updated the Market Version to be Pro / 12 instead of matching the 'Model/Version' value of Pro / 12.0 in keeping with the documented best practice so that I could have several versions (Pro /12.1, Pro / 12.2, etc.) that were all considered the same as far as licensing was concerned. Once I updated the 'Related Product Categorization' in the License Certificate, the engine did match certs to products. But this brings me back to the primary questions and the reason I wanted to do this manually: The engine did not match them correctly. Here is the situation: We have two 3-person license certificates ...-421 and ...-665, based off the same software contract. We have five users currently licensed, three on ...-665 and two on ...-421. Who (which product CI) goes on which (certificate) is already set in our records and needs to be set the same in Remedy. In the Asset Mgmt. User guide, it says that you can manually attach certs to products in this way, and then run the license engine. I manually attached the certs to the products as above, the correct three on ...-665 and the correct two on ...-421. When I run the engine job, instead of using the connections already there, it destroys those, then drops all five products onto the ...-665 cert, pushing it out of compliance. Is this normal? Isn't there some way to tell the engine to just validate what is already there? If I have five different certificates, each bought at different times for different people, how do I keep the license engine from randomly distributing these entries every time it runs??? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG]mailto:[mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Thursday, January 05, 2012 11:49 AM To: arslist@ARSLIST.ORGmailto:arslist@ARSLIST.ORG Subject: Re: Asset Management - Manual add software, license ** The license certificate and CI's need to have the same Company value as well as matching categorisations. You don't need to relate the certificates to the CI's, the engine will do that for you. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG
Asset Management - Manual add software, license
We will be using an outside product for procurement, so I am testing the process of adding software and licenses on ARS/ITSM 7.6.4. Following the instructions in the Asset Management User guide, I have created Application CIs and related them to users, and created a software contract and license certificates, and I have used the 'Search for Existing Record to Relate' function on the 'Software Assets' tab of the license certificates to relate the software CIs (Application CI type). But this does not change the deployment numbers on the certificate. When I run the license engine job (does a full check on all CIs for this company), it removes this relationship and states that the CIs have no certificates. What do I need to match to have the license engine link the Application CIs to the certificates? Certificates Company: PQ-GIO Status: Executed License Type: Per copy Related to Product Category: Manufacturer: Intuit, Inc. Product Name: QuickBooks Market Version: 12.0 Cat 1: Software Cat 2: Application Cat 3: Third Party Application CIs Company: PQ-GIO Status: Deployed Product Categorization - Tier 1: Software Tier 2: Application Tier 3: Third Party Product Name: QuickBooks Model/Version: Pro / 12.0 Manufacturer: Intuit, Inc. Financials - Cost Entries: License Certificate listed, Association Type Secondary, with the correct LC# Note that when I didn't have the market version set, I couldn't put in the related product categorization on the certificate, the most I could get was the Manufacturer and the Product Name. When this was all that was set, the License Engine run would say either the CIs had no certificates or that they had multiple (some of each), with no rhyme or reason that I could discern for which it picked. Any idea what I am missing here? Is there anything that documents that basic steps and requirements to manually enter a new piece of software and a license for it? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Asset Management - Manual add software, license
Logan, 1. Please relate People to parent CI (Computer System) not Software Asset CI with Used by role (then you should see Person is associated to the Computer System Relationships table, RLE rule checks Person relationship when work with Per copy license type). 2. CI Type BMC_Application is not Software Asset CI Type it doesn't support RLE engine rule, you should choose either of CI Types from System Component - Product, Package, Operating System, Patch, System Software, System - Software Server as Software CI. 3. if you use Purchase Line item UI to create line item, it will give you message to select Contract and/or license certificate when CI Type was chosen Software Asset CI. Toshiyasu Asset management QA lead, BMC Software --- Toshiyasu Mori (Charles) ITSM QA Engineer, Service Support Dept Room 2403, 91 E. Tasman Dr, San Jose, CA 95134, U.S.A Tel: 1-408-571-7270 Fax: 1-408-571-7001 BMC Software www.bmc.comhttp://www.bmc.com/ toshiyasu_m...@bmc.commailto:toshiyasu_m...@bmc.com From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Logan, Kelly Sent: Wednesday, January 04, 2012 10:00 AM To: arslist@ARSLIST.ORG Subject: Asset Management - Manual add software, license ** We will be using an outside product for procurement, so I am testing the process of adding software and licenses on ARS/ITSM 7.6.4. Following the instructions in the Asset Management User guide, I have created Application CIs and related them to users, and created a software contract and license certificates, and I have used the 'Search for Existing Record to Relate' function on the 'Software Assets' tab of the license certificates to relate the software CIs (Application CI type). But this does not change the deployment numbers on the certificate. When I run the license engine job (does a full check on all CIs for this company), it removes this relationship and states that the CIs have no certificates. What do I need to match to have the license engine link the Application CIs to the certificates? Certificates Company: PQ-GIO Status: Executed License Type: Per copy Related to Product Category: Manufacturer: Intuit, Inc. Product Name: QuickBooks Market Version: 12.0 Cat 1: Software Cat 2: Application Cat 3: Third Party Application CIs Company: PQ-GIO Status: Deployed Product Categorization - Tier 1: Software Tier 2: Application Tier 3: Third Party Product Name: QuickBooks Model/Version: Pro / 12.0 Manufacturer: Intuit, Inc. Financials - Cost Entries: License Certificate listed, Association Type Secondary, with the correct LC# Note that when I didn't have the market version set, I couldn't put in the related product categorization on the certificate, the most I could get was the Manufacturer and the Product Name. When this was all that was set, the License Engine run would say either the CIs had no certificates or that they had multiple (some of each), with no rhyme or reason that I could discern for which it picked. Any idea what I am missing here? Is there anything that documents that basic steps and requirements to manually enter a new piece of software and a license for it? Kelly Logan, Sr. Systems Administrator (Remedy), GMS ProQuest | 789 E. Eisenhower Parkway, P.O. Box 1346 | Ann Arbor MI 48106-1346 USA | 734.997.4777 kelly.lo...@proquest.commailto:kelly.lo...@proquest.com www.proquest.com ProQuest...Start here. 2010 InformationWeek 500 Top Innovator P Please consider the environment before printing this email. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender, and delete the message from your computer. _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
