1 / 46

CapaInstaller

CapaInstaller. CMS 4 CUG 20101125. Agenda. 10.00 Velkomst 10.10 CMS – v/Jan Koch og Ronnie Jakobsen 12.00 Frokost 13.00 Niras 14.00 Generalforsamling. CapaInstaller Management Solution. Asset. Q4. Q1. Software Provisioning. CM. Q4. Q1. Q3. Patch. Q3. CMS 5. OSD. Q4. Q1.

vina
Télécharger la présentation

CapaInstaller

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CapaInstaller CMS 4 CUG 20101125

  2. Agenda 10.00 Velkomst 10.10 CMS – v/Jan Koch og Ronnie Jakobsen 12.00 Frokost 13.00 Niras 14.00 Generalforsamling

  3. CapaInstaller Management Solution Asset Q4 Q1 Software Provisioning CM Q4 Q1 Q3 Patch Q3 CMS 5 OSD Q4 Q1 Q3 SP CMSaas Q1 System Q4 Q2 2011(2H) 2011(1H) 2010(2H) 2013

  4. CMS 4 Jan Koch

  5. CMS 4 • Device Lifecycle Management • Software Metering • CapaInstaller Scripting Library updates • Using a NAS device as deployment server • Service Update 1 – 2011 • CapaInstaller Service desk

  6. CUG Device Lifecycle Management

  7. Device Lifecycle Management • Why • Keep track on asset from ”new born” until it reaches end of life.

  8. Device Lifecycle Management • Universally unique identifier • A UUID is a 16-byte (128-bit) number(e.g. 550e8400-e29b-41d4-a716-446655440000 • The number of theoretically possible UUIDs is therefore about 3 × 1038 • It’s unique

  9. Device Lifecycle Management • Enable • Point of no return

  10. Device Lifecycle Management • Enable • Agent will request ”.jps” file regenerate • UUID will be used from a – z to identify communication between unit and container.

  11. Device Lifecycle Management • Benefits • Rename computer without having a new unit created • Reinstall computer without having a new unit created • Support units with same netbios name

  12. Device Lifecycle Management • Show units with fqdn/upn

  13. Device Lifecycle Management • Reinstall • Client will be reinstalled with the same packages which was previously installed

  14. Device Lifecycle Management • Potential pitfalls • Custom script where ”netbios” name is used as identifer • Use: HKEY_LOCAL_MACHINE\SOFTWARE\CapaSystems\CapaInstaller\Client\UnitName • F12 reinstall will always install previously installed packages (option: unlink all packages and groups not available)

  15. Device Lifecycle Management • Demo • FQDN/UPN • ”Agent” folder • Container • Unit name

  16. CUG Software Metering

  17. Software Metering • Purpose • License optimization • License optimization • License optimization • License harvesting • Prevent application startup • Identify behavior and minimize costs • Etc.

  18. Software Metering • Prerequisites • License contracts/overview • Create application groups which coresspond license contracts • “Define licenses” and queries for application groups • Enable metering for “expensive” application (Create Metering groups)

  19. Software Metering • Getting started – Basic application • Create group and associate ”group query” • Define metering executable • Rerun agent • Check log file <CapaInstaller logs>\CapaInstaller Metering Agent.log • Start/stop application • Reun agent and check console (Last usage/# usage)

  20. Software Metering • Reporting • Select node (Group) • Deploy to reporting service • Send link to ”Application owner”

  21. Software Metering • Getting started – ”complex application” • Filescan • Define application • Follow procedure • Reporting

  22. Demo • Metering agent • Simple application • Complex application

  23. Software Metering • License Consolidation - Concept • The license consolidation concept is based on the business needs for optimizing license usage. If an application installed on a computer/server in the organization is inactive (not used) it could automatically be uninstalled and the license used elsewhere.

  24. Software Metering • LC – Getting started • Define metering rules for a package • Define inactive period for an application • Schedule the package License Consolidation (Always, Daily, Weekly) • Add Package License Consolidation to computers

  25. CUG CapaInstaller Scripting Library updates

  26. CapaInstaller Scripting Library updates • New and improved since 1/9 2010 • Variable • gsSystemDirx86 • gsProgramFilesx86 • gsCommonFilesDirx86 • Functions • Reg_Getx64String(sHandle,sKey,sVariable,bMustExist) • Reg_Setx64String(sHandle,sKey,sVariable, sValue) • CMS_RerunAgent() • CMS_RunSystemAgent

  27. CapaInstaller Scripting Library updates • New and improved since 1/9 2010 • Functions • PS_IsScriptAllowedToRun(sScript,bSigned,bRunUnrestricted) • PS_ExecuteCommand(sCommand) • PS_ExecuteScript(sScript,sScriptArg,bSigned,bRunUnrestricted) • Available: Service Update 1 - 2011

  28. Demo • CMS_RerunAgent() • CMS_RunSystemAgent • Powershell • Execution policy • PS_ExecuteScript • PS_ExecuteCommand • Succes/Failiure

  29. CUG Using a NAS device as deployment server

  30. Using a NAS device as deployment server • Pros & Cons • Infrastructure • Best practice • The funstuff

  31. Pros & Cons • Pros • Cost effective device • Easily replaceable • Most devices supports failover file systems • Energy efficient • some support power scheduling and wake on LAN/WAN • Cons • Completely dumb storage device • Still requires communication with CMS Management Server from the client • No Support for BITS • Most devices are slow compared to PCs

  32. Infrastructure • Setup in CMS • NAS devices must be a child of a Windows server • NAS devices cannot have child servers • Make sure you assign distribution points • Replication of data • All replication is pushed to the device • No BITS

  33. Best Practice • Devices • We recommend • Synology, Qnap , NetGear and Buffalo • Features to look for • Domain support • RAID 1 or even 5 or 10 • Setup • Setup security • Use domain support if available • Create share on the NAS device • Remember to assign rights to account • Create NAS server in CMS • Use differentiated replication • If using user security and the CMS is a domain controller no account will be created automatically • You have to do this yourself … but only on domain controllers • Therefore use device with domain support ;-) • Beware of the impact of sync schedules

  34. The Fun Stuff The Fun Stuff • How to support NAS based PXE boot • Requirements • Customizable DHCP options • Doesn’t have to be in the NAS device • TFTP server service on the NAS device • How to … (the Synologymethod) • Enable the backdoor • telnet or ssh • Installpackager • Ipkg, apt etc. • Install and configure services • dnsmasq • atftp, tftp-hpa • Transfer the files • Fixing the last bits

  35. The Fun Stuff • Pitfalls • Not supported in CMS • Case sensitive file system • Firmware upgrades may overwrite stuff • Tampering may be unsupported by NAS provider • CMS Support in the future? • No promises … 

  36. CUG Service Update 1 – 2011

  37. Service Update 1 – 2011 • Requirements • New terms in CMS • What is changed? • What does this mean to me?

  38. Requirements • .NET Framework 3.5 SP1 • Services are currently using .NET 2.0 only • Upgrade will happen automatically • In the near future clients with also require .NET Framework 3.5 SP1 • And we just might move up to 4.0 soon

  39. New terms in CMS • CMSaaS • Hosting setups are now much more integrated • This will progress further in the future • WCF • Database Access Proxy & Service • Security • Distribution Servers • Only storing packages, models and images • Much like a NAS device but with better Sync

  40. What is changed? • OSD is getting differential replication • For images and models • Servers can be created offline • And installed later using a portable kit • Sync is more firewall friendly • No more SQL and SMB ports to be opened across firewalls • Host System Health View • Services monitoring • Web console • Version 1 will be for hosting customers • We will increase support for this for all customers in the future

  41. What does this mean to me? • You don’t have to change anything • Servers running any CMS service must run .NET Framework 3.5 SP1 • To use the firewall friendly mode for services you have to create a Database Access Service

  42. CUG CapaInstaller Service desk

  43. Inventory collection User Service Desk Connectors CI and Inventory is collected from management systems using connectors

  44. Incident creation User Service Desk Service Desk collects State snapshots User creates an incident Connectors

  45. Incident process Supporter handles incident User Service Desk Solution is provided Incident is closed Knowledge data is stored for future reference Connectors

  46. Service desk • Key features • Easy logging • Dashboard overview directly from CMS - Web based front end • Possibility to prioritize daily operation tasks • Use CMS and PG as data providers • Focus on customers who are technical driven and ready to take the next step regarding support of customers • Build a solution based on best practice and our experiences. • Simple reporting

More Related