Brainware ITAM Review Tools Day
•Download as PPTX, PDF•
0 likes•403 views
Brainware presentation at the ITAM Review Tools Day
Recommended
Recommended
More Related Content
What's hot
What's hot (8)
Viewers also liked
Viewers also liked (17)
Similar to Brainware ITAM Review Tools Day
Similar to Brainware ITAM Review Tools Day (20)
More from Martin Thompson
More from Martin Thompson (20)
Recently uploaded
Recently uploaded (20)
Brainware ITAM Review Tools Day
- 1. brainwaregroup Products and Services Barry Johnson Business Development Manager - brainwaregroup © 1989-2014 brainwaregroup 1
- 2. Agenda Introduction to brainwaregroup Overview of our products Reference customers for SAM Whistle stop demo Tool selection and shortlisting advice Summary © 1989-2014 brainwaregroup 2
- 3. Facts brainwaregroup Spider LCM GmbH Brainware Solutions AG Brainware Founded 1989 Leading provider of: IT Lifecycle Management Contract Management 100% self-financed ~ 70 employees Offices Zug (HQ) Zurich Bern Hamburg Essen Munich Frankfurt South Africa Japan UK © 1989-2014 brainwaregroup 3
- 4. Products IT Management Contract Management SW Management Mobile Management Product Competences Groups IT Management Contract Management © 1989-2014 brainwaregroup 4
- 5. Technology Management Organisation Management Spider IT Lifecycle Management Asset Mgmt Licence Mgmt Recognition Service Article Catalogue Solution Portfolio OS Installation SW Distribution SW Packaging Patch Management Replication Remote Control Inventory Software Kiosk Change Mgmt IMAC MDM Solution Columbus System Management Spider Contract Management Professional Contract Mgmt Enterprise Contract Mgmt © 1989-2014 brainwaregroup 5
- 6. Some SAM References 6 month implementation covering multiple complex server metrics 10’000 servers with complex metrics 20’000 clients (growing) Multiple mandators International implementation/rollout Asset Management & Licence Management 85’000 devices (client & servers) Multiple discovery systems Multiple legal entities International implementation/rollout 6 month project 40’000 devices (client & servers) Additional licence services International implementation/rollout EMEA/NORAM 65’000 devices (client & servers) Additional licence services International implementation/rollout EMEA/NORAM 50’000 devices (client & servers) © 1989-2014 brainwaregroup 6
- 7. Spider Licence 6 LIVE © 1989-2014 brainwaregroup 7
- 8. Tool selection and shortlisting advice Barry Johnson Business Development Manager - brainwaregroup © 1989-2014 brainwaregroup 8
- 9. “I don’t need to know everything, I just need to know where to find it, when I need it” - Albert Einstein © 1989-2014 brainwaregroup 9
- 10. Examples of challenges your tools must overcome First example – technical data collection design Considering the following network, what design choices would you make around which tools to implement and what challenges do you foresee with this client’s network? FL, USA Datacentre 10.11.x.x Nottingham, UK Datacentre 10.10.x.x MPLS 100Mb 100Mb SCCM Primary Site WAS WA, USA Office 10.1.x.x SCCM Primary Site NYC NY, USA Office 10.2.x.x 10Mb 50Mb London, UK Office 10.3.x.x Edinburgh, UK Office 10.4.x.x SCCM CAS Firewall - ports allowed 80, 443, 62000 Local Server, ZA 10.12.0.1 2Mb Services running: DHCP DNS AD DS Johannesburg, ZA Office 400 Sales People 169.254.x.x 200 Callcenter Desktops Various speeds © 1989-2014 brainwaregroup 10
- 11. Another set of different challenges Second Example – Licensing Requirements A company has a requirement to ensure that they have the right number of licences for their datacentre. The technologies in use are all running in virtual machines: Microsoft 100 Windows Server 2012 servers 14 SQL 2012 Servers (400 internal employees & SQL Servers being accessed externally) Oracle 4 servers running Database 11g, each running with Partitioning and Spatial Red Hat 14 Enterprise Linux The virtualisation platform is VMware and the technical team has specified that they will use 20 dual processor hosts with 6 cores per processor All Oracle products will run on the RHEL OS DRS will be used across the VMware hosts for load balancing and HA for physical host redundancy. Two SANs will also be in place to load balance the storage based on performance. What best practice guidance would you give to contribute to the above design to optimise the licensing requirements against the tech spec? © 1989-2014 brainwaregroup 11
- 12. What are some key toolset requirements? Metering Why: for saving money on the desktop estate Interaction with other systems Why: data will be required from external systems such as other inventory sources, AD, ERP systems, licence tracking tools such as ILMT etc. Ability to override the system Why: licensing rules in any system will not be correct in all cases and so the ability to override automatically determined values is crucial. Working with various qualities of inventory data Why: it’s not always practical to redeploy an estate with an agent ‘because the licence tools guys said so’. However, if you have some flexibility to do further additional analysis afterwards and enhance the data, this can be preferable. Detail oriented Why: Some vendors need to know the installation language, the edition, version or all of the above > make sure the tools find this detail and can manage it © 1989-2014 brainwaregroup 12
- 13. What are some key toolset requirements? (cont..) Contract management Why: linking licences to their contracts might be important to know when renewal negotiations need to take place. Ideally a system should allow document management too to keep everything in one place. Report on non-discoverable apps/usage Why: not everything can be automatically audited, but it doesn’t mean it’s not important (e.g. CALs, cloud software usage etc.) Customisation beyond ‘out of the box’ experience Why: no client is exactly the same and some requirements so adding fields like project reference codes, internal contract references etc. is a must. Even configuring the interface to show different fields might be necessary! Good support Why: things are great while they’re great, but what happens when things go wrong? © 1989-2014 brainwaregroup 13
- 14. Summary Tool requirements will vary based on each environment When selecting a licence/asset management tool, check both the out of the box capabilities as well as the customisation Use these requirements as a starting point, but build them out to suit your environment Find a vendor that can align to your tech roadmap as your requirements may evolve; but can your selected tool keep up? © 1989-2014 brainwaregroup 14
- 15. www.brainwaregroup.com Barry Johnson +44 7921 073277 Barry.johnson@brainwaregroup.com © 1989-2014 brainwaregroup 15
- 16. Your contacts Marius Dunker Spider LCM GmbH Vice President Business Development +49 (40) 78 88 999-0 marius.dunker@brainwaregroup.com Barry Johnson Brainware Technologies Limited Business Development Manager +44 7921 073277 Barry.johnson@brainwaregroup.com © 1989-2014 brainwaregroup 16
Editor's Notes
- 8
- Key points about the network SCCM is already collecting the data for the desktops in the US; it’s wise to use this data initially until the quality is called into question A connection to the CAS would enable the collection of data from one place rather than having to make a connector to each site server The data could be collected to any of the two datacentres as the 100Mb MPLS link makes the link speeds irrelevant London and Edinburgh could be collected by agent based methods as they will most likely need metering data from the desktops to make decisions about application removal/re-harvesting. Due to London’s low bandwidth, it may be wise to have a collection point locally and then schedule the upload of the data back to the MPLS network during non-business hours. All of the laptops should have agents deployed to them either from another SCCM server or whichever tool platform is being used SCCM would work on the laptops with regular agents as they are most likely connected using Direct Access (since port 62000 is used for the Network Location Server to enable Windows 7+ clients to determine how to handle traffic back to the corporate network) For the Johannesburg office, it’s also a good idea to have an aggregation point as the bandwidth is very low and uploading during business hours could seriously impact the network. The DHCP server in the Johannesburg office has a problem because all of the desktop devices have been allocated 169.254.x.x addresses which are allocated automatically by the OS when a valid DHCP response is not received and the network card is set to dynamically obtain an IP address. Whichever tool used either would need to work over the 80, 443 or 62000 ports to receive data from the Johannesburg office as no VPN or site to site link has been specified. It might be better to suggest to the customer about considering a site to site VPN than try to have a discussion about opening firewall ports.
- Microsoft SA is required on the Windows Server and SQL Server licences due to the cold backup rights needed to spin up machines on other hosts SA also required on the Windows Server and SQL Server licences as licence mobility is required The licensing volume (if discounting four servers for the Oracle estate) means that there will be around 16 servers/host meaning that the density is enough to go for Windows Server 2012 R2 Datacenter Edition licensing (unlimited virtualisation for the number of host) Each host would require one Windows Server licence (as they are only dual processor) Oracle Don’t run Oracle on VMware! If Oracle needs to be run on VMware, be aware that the physical hosts must be licenced Best practice would be to split the Oracle servers into a separate smaller cluster from the rest of the machines to still run them on VMware but without having to license the entire cluster Consider higher end hardware to get the most out of the investment Are there any OEM databases in use? Red Hat Limit the number of physical servers that the Red Hat servers are on and then take a subscription for the number of processors for that cluster Best to keep these with the Oracle boxes as it’s easier to manage given that the Oracle cluster should be split from the main Microsoft technology cluster anyway VMware Enterprise Plus licences would be required across the board – reason being is that if there is to be load balancing at the storage level, Storage DRS would be required and this is only included as a feature of Enterprise Plus It could be considered to manage some of the cluster with Enterprise licences if Storage DRS isn’t in use but the requirement for DRS across all hosts means that at least Enterprise licences would be required.