5 Best Practices for Network Discovery & Management in 2013
•
2 j'aime•1,775 vues
Like 62% of your peers*, do you lack an easy way to discover and manage devices both on and off your network? One thing that won't change in 2013 for IT Pros is the daily onslaught of challenges. The core of those challenges continues to be the management of an ever-evolving network complexity. With sensitive data and company security on the line, it's vital that you can quickly and easily discover and manage the multitudes of devices connecting to your network! Join this webinar to learn important in's and out's of increasing security and efficiency through discovery & proactive management. You'll hear valuable tips from IT Expert, Ray Barber of Kaseya, and real-life scenarios from Johnathan Nelson, Chief Technology Officer at American Association of Community Colleges, including: Discover the current state and health of your IT infrastructure Manage your constantly changing environment through a single platform Quickly and securely gain access to machines, domains, users, network devices and networks Automate monitoring and remediation of issues - before they impact operations Deploy software, security and settings to all machines across multiple sites at once without interrupting users or business systems
Recommandé
Recommandé
Contenu connexe
En vedette
Plus de Kaseya
Plus de Kaseya (20)
Dernier
Dernier (20)
5 Best Practices for Network Discovery & Management in 2013
- 1. IT Briefing Series 5 Best Practices for Network Discovery & Management in 2013
- 2. AGENDA • Introductions • 5 Best Practices Discussion • Recap • Q&A www.kaseya.com
- 3. SPEAKERS Ray Barber Johnathan Nelson Product Marketing Manager Chief Technology Officer Kaseya American Association of Community Colleges www.kaseya.com
- 4. The Correct Terminology www.kaseya.com
- 5. Good Practice #1 - DISCOVER Discover the Current State and Health of Your IT Infrastructure www.kaseya.com
- 6. Good Practice #2 – MANAGE Manage and Control a Constantly Changing IT Environment • Avoid the ‘Picasso’ effect • Driving consistent approach • Managing risk www.kaseya.com
- 7. Good Practice #3 – ACCESS Quickly & Securely Gain Access to Machines, Domains, Users, Devices www.kaseya.com
- 8. Good Practice #4 – AUTOMATE MONITORING & REMEDIATION Automate monitoring and remediation of issues - before they impact operations www.kaseya.com
- 9. Good Practice #5 – AUTOMATE DEPLOYMENT & SECURITY www.kaseya.com
- 10. OUR VISION “Providing Enterprise-Class IT Systems Management for Everybody” www.kaseya.com
- 11. CORE PRINCIPLES Discover Validate Manage Automate www.kaseya.com
- 12. CONSOLIDATED DISCOVERY N M A P Multiple Scan Methods www.kaseya.com
- 13. GOOD PRACTICE 100’s of Pre-Defined Views, Maintenance Routines and Policies • Device Views by Type – By OS Type/Ver – Exchange, SQL, IIS, etc • Maintenance Routines – PC and Server Maintenance • Monitor Sets – Application Events/Logs – Hardware Thresholds – Up/Down Faults – Servers, Database, Exchange and Domains – 3rd Party Backup, Security and Network Infrastructure www.kaseya.com
- 14. UNIFIED MANAGEMENT Automate the State of Discover the State of IT Manage the State of IT IT • Systems • Scheduling • Reporting • Assets • Procedures • Dashboards • Mobile Devices • API/Messaging • Interactive Data Views • Network Devices IT Configuration Management Business Continuity • Remote Management • Image Deployment • Image Backup • File & Folder Backup • Software Deployment • Desktop Migration • Image Virtualization • Power Management • Mobile Device Management Asset Management Service Delivery • Network Discover & AD • Asset Management • Service Desk/Ticketing • Policy Compliance • Hardware/Software • Virtual Machine Management • Policy Management • Time Tracking • Service Billing Security Systems Monitoring • AntiVirus • Patch Management • Systems Checks & Alerts • Agent-less Monitoring • AntiMalware • Software Updates • Agent Monitoring • Log Monitoring • Enterprise Monitoring www.kaseya.com
- 15. Join Us: Sign Up for a Demo Today! Contact us: 1 (877) 926-0001 sales@kaseya.com Learn more: www.kaseya.com
Notes de l'éditeur
- It’s important when we have a discussion about ‘Best practice’ that we first take a moment to consider the meaning and implications of the idea of best practice. “A best practice is a technique or methodology that, through experience and research, has been proven to reliably lead to a desired result.”So what is ‘best’ for one business may not be best for another, so in many circles of thinking on Service Management, such as ITIL, the term Good Practice is used, to define a process which is well formed and actually implemented to good use in one organization, and can at least be considered by other organizations. So today we are really going to be talking about GOOD practices, key ideas about how certain processes are undertaken within an organization and what has worked well, so that hopefully you can gain something from the shared experience.Of course this presentation is sponsored by Kaseya, and because our customer speaker today uses the Kaseya product, some of the information may be slightly specific to the platform, however even if you are not using or are not intending to use the same platform for Service and Systems Management, you can still gain insight from what processes have best gained from the adoption of a system to streamline them, which can help to either update your own use of a system or identify where perhaps some part of your process really does need a product to help get the best efficiency gains.
- “Johnathan “Mark” Nelson is a twenty five year veteran in the IT field. He has served as the Chief Technology Officer for the American Association of Community Colleges (AACC) for the last 20 years where he manages the Information Resource Management team as well as the Data Operations team for the Association. In addition to his responsibilities as CTO, Johnathan has had the opportunity to speak, write articles and serve on various boards for a number of for-profit startups. He holds certifications in Windows, Novell and VMware, ushering AACC into the virtualized world in 2002.
- It’s important when we have a discussion about ‘Best practice’ that we first take a moment to consider the meaning and implications of the idea of best practice. “A best practice is a technique or methodology that, through experience and research, has been proven to reliably lead to a desired result.”So what is ‘best’ for one business may not be best for another, so in many circles of thinking on Service Management, such as ITIL, the term Good Practice is used, to define a process which is well formed and actually implemented to good use in one organization, and can at least be considered by other organizations. So today we are really going to be talking about GOOD practices, key ideas about how certain processes are undertaken within an organization and what has worked well, so that hopefully you can gain something from the shared experience.Of course this presentation is sponsored by Kaseya, and because our customer speaker today uses the Kaseya product, some of the information may be slightly specific to the platform, however even if you are not using or are not intending to use the same platform for Service and Systems Management, you can still gain insight from what processes have best gained from the adoption of a system to streamline them, which can help to either update your own use of a system or identify where perhaps some part of your process really does need a product to help get the best efficiency gains.
- Discovery and Health of your IT InfrastructureGaining visibility into existing and newly acquired assets, in real-time.Even the basics of asset management cannot be accomplished if you cannot accurately track and uniquely identify every IT asset in your business, something as simple as a reconciliation against financial data becomes impossible without reliable accurate continuous discovery feeding all of your IT process.Keeping a current state of health on your infrastructureEvery other IT practice depends on the reliability of your discovery process to ensure that you know what is on your network at all times. Discovery is not just an audit, an audit is a snapshot in time as is out of date as soon as it is finished. You cannot manage what you cannot seePart of creating a reliable and stable environment is continuous management of all systems to a defined standard within the business. You can’t begin to even tackle this issue if you aren’t fully aware of every part of your environment. Even one device left off an audit or update process may leave a network out of compliance or with a security hole.Jonathan:Pro-active Network Audit, found Auditors. Good example of things happening without IT’s knowledge that wouldn’t be found without regular approach to discovery
- 2. Manage through a single platforma) Picassos are the ‘artists’ which have their own unique approach to everything but are impossible to replicate and expensive to replace – learn to paint by numbers b) Now we’ve made those decisions how to make sure that everything happens? single pane of glass helps drive consistency through all disciplines and across all parts of the organization. One thing that we have seen proven time and again with our Service Provider customers is that it’s possible to ‘manage to perfection’ – example of worst and best customerc) Deciding policy and knowing what it is – examples of how those decisions are made, and managing risk – e.g. patchingJonathan:Example 1: Group policy example - only one person who really knows that – single platform makes it more accessible
- 3. Quickly and easily gain accessOften times every different system has its own methodology for access, whether the actual UI is a web interface or local app, often separate accounts with their own security controls, VPN’s to get to remote sites, often giving more access than is required to gt the job done. It also all leaves a lot of administration overhead and makes managing security complex. Good practice for access means having a consistent approach through a single UI with one security context for immediate setup or disablement, and complete auditability on all actions, every action and process carefully recorded. Jonathan- National Centre of higher education, offices on 3 floors – example of how Kaseya improved efficiency by enforcing single approach to remote access to everything
- 4. Automate monitoring and remediationMonitoring is much more than just a ping – connectivity is important, but not the whole story – “The Mainframe is down”, need to have smart monitoring that is looking deeper to get the real story.And monitoring on it’s own in not pro-active, users notice before you can. Looking for the signs of problems and then taking an automated response – may be as simple as print spooler errorAutomated monitoring means that it is applied by policy, and enforced constantly to ensure correct operation – who watches the watchmanComplete integration is important – with everything in one system & Ensuring items that are discovered get the right response at the right time Johnathan examples: Automating virus responseCreate tickets to flag for follow up - automation means systems raising issues not peopleRay: Examples where diagnosis is already in the tickets
- Automating recurring IT tasksPatch UpdatesStandardization of ProcessesEveryone is always being tasked to do more with less. As complexity increases with systems, rules and regulations it becomes difficult to automate much of the daily tasks to ensure the overall health, wellness and security. Kaseya is all about automation, which can mean many things… one of which is applying one thing to many machines, Like Patch. Patch management example of automating deployment based on policy across all machines, handling file downloads centrally and dealing with reboots in a way that doesn’t impact users.By using a policy based approach to important tasks such as deployment and security we can ensure consistency of approach to minimize network and user impact. Auomated systems run the process directly on the machines so they can be done out of hours or even while users are working without disturbing them.Jonathan:How has a systems management solution like Kaseya allowed you to automate the management of deployment such as patches and everything that comes along with that like rebooting machines, or making sure the right machines get the right patches?
- Automating recurring IT tasksPatch UpdatesStandardization of ProcessesEveryone is always being tasked to do more with less. As complexity increases with systems, rules and regulations it becomes difficult to automate much of the daily tasks to ensure the overall health, wellness and security. Kaseya is all about automation, which can mean many things… one of which is applying one thing to many machines, Like Patch. Patch management example of automating deployment based on policy across all machines, handling file downloads centrally and dealing with reboots in a way that doesn’t impact users.By using a policy based approach to important tasks such as deployment and security we can ensure consistency of approach to minimize network and user impact. Auomated systems run the process directly on the machines so they can be done out of hours or even while users are working without disturbing them.Jonathan:How has a systems management solution like Kaseya allowed you to automate the management of deployment such as patches and everything that comes along with that like rebooting machines, or making sure the right machines get the right patches?
- Automating recurring IT tasksPatch UpdatesStandardization of ProcessesEveryone is always being tasked to do more with less. As complexity increases with systems, rules and regulations it becomes difficult to automate much of the daily tasks to ensure the overall health, wellness and security. Kaseya is all about automation, which can mean many things… one of which is applying one thing to many machines, Like Patch. Patch management example of automating deployment based on policy across all machines, handling file downloads centrally and dealing with reboots in a way that doesn’t impact users.By using a policy based approach to important tasks such as deployment and security we can ensure consistency of approach to minimize network and user impact. Auomated systems run the process directly on the machines so they can be done out of hours or even while users are working without disturbing them.Jonathan:How has a systems management solution like Kaseya allowed you to automate the management of deployment such as patches and everything that comes along with that like rebooting machines, or making sure the right machines get the right patches?
- Automating recurring IT tasksPatch UpdatesStandardization of ProcessesEveryone is always being tasked to do more with less. As complexity increases with systems, rules and regulations it becomes difficult to automate much of the daily tasks to ensure the overall health, wellness and security. Kaseya is all about automation, which can mean many things… one of which is applying one thing to many machines, Like Patch. Patch management example of automating deployment based on policy across all machines, handling file downloads centrally and dealing with reboots in a way that doesn’t impact users.By using a policy based approach to important tasks such as deployment and security we can ensure consistency of approach to minimize network and user impact. Auomated systems run the process directly on the machines so they can be done out of hours or even while users are working without disturbing them.Jonathan:How has a systems management solution like Kaseya allowed you to automate the management of deployment such as patches and everything that comes along with that like rebooting machines, or making sure the right machines get the right patches?
- Automating recurring IT tasksPatch UpdatesStandardization of ProcessesEveryone is always being tasked to do more with less. As complexity increases with systems, rules and regulations it becomes difficult to automate much of the daily tasks to ensure the overall health, wellness and security. Kaseya is all about automation, which can mean many things… one of which is applying one thing to many machines, Like Patch. Patch management example of automating deployment based on policy across all machines, handling file downloads centrally and dealing with reboots in a way that doesn’t impact users.By using a policy based approach to important tasks such as deployment and security we can ensure consistency of approach to minimize network and user impact. Auomated systems run the process directly on the machines so they can be done out of hours or even while users are working without disturbing them.Jonathan:How has a systems management solution like Kaseya allowed you to automate the management of deployment such as patches and everything that comes along with that like rebooting machines, or making sure the right machines get the right patches?
- Needs to be cleaned up.