Discovery, Inventory and Application Recognition

1,589 views
1,404 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,589
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
63
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Discovery, Inventory and Application Recognition

  1. 1. Discovery, Inventory and Application Recognition December 2011
  2. 2. Webinar Series Automated entitlement based license • 1st webinar (Nov) Level 4 management and optimization; How to get started on Optimized a SAM program • 2nd webinar– (Today) Automated purchased vs. installed Discovery, Inventory Level 3 license reconciliation; SAM processes Continuously & Application Compliant to maintain license compliance Recognition Level 1 Perform purchased versus installed • 3rd webinar– (Jan) Level 2 license reconciliation on an ad hoc Managed License & Contract basis; point in time management Management Levels 2-3 Level 1 • 4th webinar– (Feb) Identify software and hardware installed Installed Strategies for License Optimization Level 4 Enterprise License Optimization Maturity Model2 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  3. 3. Speaker & Agenda • License Management overview • Device Based inventory • Network based inventory • Application Recognition • Additional inventory requirements Vincent Brasseur • Virtualization Director of Product Management, • License examples Flexera Software • Recommendations • Questions and Answers3 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  4. 4. License Management Goals Out of $ Over-Licensed Optimal Compliance $ • Calculate your license position – Reduce non-compliance costs and risks – Eliminate over-spending on software; identify ‘shelfware’ • Manage Licenses and Contracts – Know what the organization owns; understand licensing terms and conditions – Pay for what you need and use – Be audit ready • Meet Organization Objectives – Ensure each installation and use of a software product is licensed – Provide financial forecasting • Optimize the license position – Minimize license consumption – Deliver trend analysis and licensing forecasting4 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  5. 5. License Management Data Software and Hardware Asset Management Inventory Users & Group UserHW/SW data Cost CenterUsage data Business Unit Location HW & SW Assets Financial HistoryRequestPurchases Audit trailContracts 5 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  6. 6. Discovery & Inventory Challenges • Completeness & Accuracy – IT environment is dynamic – Devices are not always connected – Inventory is performed every few weeks • Different OS’s & Environments – Desktop and datacenter have their own challenges – Inventorying the datacenter is usually more difficult – Specific data is needed when virtualization is used • Security and access rights – Inventory requires administrator rights – Difficult to obtain in large organizations6 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  7. 7. Inventory Discovery & Inventory Types • Inventory can be: – Agent based: an agent is physically installed on the device – Agentless: an agent is executed remotely on the device – Remote: no agent is executed on the device; e.g. Oracle db • Device discovery methodologies: – Network discovery – Group Policy / Login script – Manually7 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  8. 8. Inventory Agent & Agentless inventory Available Data Packages Files Registry ISO Tag8 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  9. 9. Device Based Inventory Data Sources Packages • Found in Programs and Features or Add/Remove Programs (Windows), RPM packages (UNIX/Linux)… • Collecting and identifying software products is easy • Challenges: – Cannot be used to track usage – Data can be lost when the software product is repackaged – Discrepancies between installation and package data store – Not all publishers use packages – Product can be running on a machine without installation9 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  10. 10. Device Based Inventory Data Sources Files • Found on the device hard disk • The most accurate data source for identifying software • Challenges: – Requires full disk scan – The volume of files to be collected is large – The identification rules are complex and sometimes inaccurate – Products can be running on a machine without installation10 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  11. 11. Device Based Inventory Data Sources Registry • Can be remotely inventoried • Very accurate data source for identifying software • Challenges: – Need to know what to collect – Many times registry entries are left behind after software removal – Applies to Windows platform only – Products can be running on a machine without installation11 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  12. 12. Device Based Inventory Data Sources ISO 19770-2 Tag • The ISO 19770-2 provides a standard for software identification tags that contain authoritative identifying information for installed software. • The ISO 19770-2 is a XML file with a .swidtag extension … <swid:product_title id="e8_3_2">Adobe Photoshop CS3</swid:product_title> <swid:product_version id="e8_3_3"> <swid:name id="e8_3_3sub1">10.2</swid:name> … <swid:name>Adobe Systems Incorporated</swid:name> <swid:regid>regid.1986-12.com.adobe</swid:regid> </swid:software_creator> … • Challenges: – The adoption of the ISO tag is slow; it does not apply to legacy products – It requires hard disk scan – Few inventory tools capture this data – Product can be running on a machine without installation12 © 2011 Flexera Software, Inc. | Company Confidential
  13. 13. Network Based Inventory Network Discovery and Inventory • Uses port sweep and network protocols (TCP, UDP…) • No agent required • Remote API calls can be performed • Challenges – Need to target the devices to be interrogated – Security issue – Applies to a limited number of software products • Examples: – DNS Server port 53 – Oracle TNS Listener ports 1521/1526 – SQL Server port 1434 – VMware ports 902/44313 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  14. 14. Application Recognition • Software Identification challenges: – What software product is used or installed? – What components are used or installed? – What products need a license? Desktop & Datacenter Recognition Process List of Applications Inventory •Files •Add/Remove Programs •Registry •ISO tag Application Recognition File Rule Application Name = Excel.exe If the file name equals Excel.exe and the version Name = Excel Version = 12.0.6214.1000 starts by 12.* and the publisher contains *Microsoft* Version = 2007 Publisher = Microsoft then the application is Microsoft Excel 2007 Publisher = Microsoft14 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  15. 15. License Management Data Requirements License Metrics Most license metrics can be classified in five main categories: • Device based Per Device, per server, per virtual machine… • User based Per user, named user, accounts, authorized user, external users, UVU (User Value Unit), concurrent users, infrequent users, … • Hardware property based Per core, processor, processor or core points, socket, PVU (Processor Value Unit), RVU (Resource Value Unit), tiered device, virtual memory, processor speed… • Usage based Per amount of time, number of accesses, feature used… • Miscellaneous Enterprise, Site, Per purchase order over 100K, per premium income…15 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  16. 16. License Management & Hardware Asset Management Hardware Inventory Requirements• Processor type• Number of Processors• Processor Speed• Number of cores• Memory• Number of sockets• Computer Model & ManufacturerRelated Data:• Unique Identifier for each device: inventory ID, Network Name• Operating System• Last Logon User• Serial number, MAC Address• Casing16 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  17. 17. Virtualization Application Virtualization • Multiple technologies: Microsoft App-V, Citrix XenApp… • Device inventory will not capture virtualized applications • Two inventory possibilities: – Access rights – Usage • Used in VDI environments • Publishers licensing rules – Microsoft – Adobe – Access rights versus usage17 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  18. 18. Virtualization Example – MS Server Processor Soft Partitioning18 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  19. 19. Virtualization Example – MS Server Processor Soft Partitioning• Hardware: – 1 physical OSE (no SQL) • 1 physical proc w/ 2 cores – 1 virtual OSE (w/ SQL) • 2 virtual procs• Correct calculation: – 2 virtual procs / 2 cores per physical proc = 1 license19 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  20. 20. Virtualization Example – Oracle Processor Soft & Hard Partitioning Discovery and Inventory Process Inventory Oracle Oracle Tool Listener Database SNMP or Port Scanning SQL Queries Oracle Database License • Databases support options and management packs • Options/Management Packs can be inventoried only by database queries • Oracle Processor license is based on the number of processor cores • Oracle Processor License does not support soft partitioning20 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  21. 21. Discovery and Inventory Best Practices • Deploying an inventory solution is challenging • Use existing tools: – Configuration management – Usage monitoring – Environment specific tools – Publisher specific tools • Use all data sources and methodologies – One data source or methodology will not provide all the information • Only use new tools when needed21 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  22. 22. Application Recognition Best Practices • Quantity is nothing • Quality and accuracy are essential • The application recognition solution must: – Be up to date – Support different type of evidence – Allow complex rules; or – Contain the software product name from publishers – Be modifiable on site22 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  23. 23. Recommendations • No tool on the market will provide all the answers • Use what you have today; buy additional tools only when necessary – Assess what data is already available today – Locate areas where additional tools are needed: virtualization, Unix/Linux environments, Oracle, etc.• Use Inventory & App Recognition tools that: – Consolidate data from the multiple sources – Translate raw software inventory into meaningful product titles, versions, editions – Are updated frequently and have broad coverage23 © 2011 Flexera Software LLC. All rights reserved. | Company Confidential
  24. 24. Thank you Please submit your questions via the Live Meeting Q&A form. For more information: www.flexerasoftware.com/ELO Contacts: jemmitt@flexerasoftware.com vbrasseur@flexerasoftware.com24 © 2011 Flexera Software, Inc. | Company Confidential

×