1 / 40

Maximizing Your BindView Investment: Optimizing bv-Control for Windows

The presentation will begin momentarily. Scheduled start time is: 11:35 ET 10:35 CT 8:35 PT For AUDIO: US Dial-in details: 800-559-9370 International Dial-in details: 847-619-6819 Confirmation Number: 11375273

anahid
Télécharger la présentation

Maximizing Your BindView Investment: Optimizing bv-Control for Windows

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. The presentation will begin momentarily. Scheduled start time is: 11:35 ET10:35 CT8:35 PT For AUDIO: US Dial-in details: 800-559-9370 International Dial-in details: 847-619-6819 Confirmation Number: 11375273 In order to enhance your participation in this event, please note the following:-Your screen resolution should be set to 1024 X 768 Maximizing Your BindView Investment: Optimizing bv-Control for Windows

  2. Maximizing Your BindView Investment: Optimizing bv-Control for Windows Jeanne Garnero, Sr. Systems Engineer

  3. Agenda • Architecture and Communication • Mapping Out Your Environment • Deployment and Optimization • Diagnostics and Healing • Optimizing Query Structure

  4. Distribution Rules RMS Console Architecture How it Works - The Big Picture Resource Domain/Data Warehouse MQE SQE NT 4.0 Domain Boston MQE Windows2000/ AD MQE SQE Houston New York

  5. Site 1 Synchronized MQE SQL Site 3 BVIS Site 2 DCA’s DCA’s DCA’s RMS Console Architecture Communication - Let’s Break it Down ECS

  6. QE Scope Variables • %MQES • %SQES • %QES • %ALLMQES • %ALLSQES • %ALLQES List of QE’s in the reporting Domain that report on that Domain List of QE’s that report on the reporting Domain. QE can be in any Domain. Mapping Your bv-Control Environment It’s 8 a.m., do you know where your QEs are?

  7. Deployment and Optimization Where Do I Start? • How many Information Servers Should I Deploy? • Do I have “separate environment” needs? • How many QEs are enough? • How many domains do I have? How many sites do I have? • Do I have large storage environments I need to query? • Where to place the QEs • Hardware considerations, other apps on the box • Why workstations aren’t a good idea • Revisit the questions above • When to use a Multi-Master QE setup • Security Considerations • How to Configure the QEs • DCAs • MQE vs Support Service on the DCs – Optimize caching • Port Settings • Bandwidth • Distribution Rules/Redundancy and failover Ref: bv-Control for Windows Planning and Deployment Guide

  8. Deployment and Optimization How many Information Servers Should I Deploy? • Geography • Workload • Autonomy • Security

  9. Deployment and Optimization How many QEs are enough? • How many domains do you have? • Do you have large sites? • What type of queries are you running? • MQE takes care of all Directory Object queries • Machine based queries…. what type of data? • Patch Assessment – 1 DCA - 16 targets. DCA default of 6 = 96 target machines. 5 minutes. 5000 machines? You can either: • a) wait about 4 hours for the one query engine to gather all information • b) make sure you have lots of RAM and bump up your DCAs to the default max of 30 so you hit 480 machines with the one query engine every 5 minutes and finish in about 52 minutes • c) install another 51 SQEs with the default 6 DCAs and get your information in 5 minutes, or • d) meet somewhere in the middle • Entitlement Reporting – Each file server should have its own SQE. * • Event Logs and Calculated disk space queries – 150 Targets per SQE.

  10. Deployment and Optimization Where should I place the QEs? • On a dedicated box!! Hardware is cheap! • Geographically close to the data you are querying* • One per domain minimum • Refer back to “how many do I need?”

  11. Deployment and Optimization Why would I use Multi-masters? Four scenarios: • Multiple Domains • Performance gain for multiple users sharing the QE infrastructure to target different regional machines – central repository for information. • Put MQEs close to each data consumer • Each MQE could also be an SQE for another MQE • Use distribution rules • Idiot Plan – some companies have a group of people who insist on running huge, inefficient queries – thus creating an MQE bottleneck for everyone else. Give them their own MQE! • Security – can use multiple MQEs, each with a different credential to limit users to only what the credential allows. Best practice would be to use the Credential DB to do this…however…

  12. Deployment and Optimization Configuring the QEs – How Do I Do That?

  13. Data Collection Agent Settings Set the directory where the Query Engine stores collected data Query Engine Settings Agent Settings - If you have the horsepower, rev the engine… *1-54: Default 6: Add 25Mb RAM for each DCA

  14. Query Engine Settings Caching Information • Computer Cache • Computer Name • Domain • Comment • Type (DC, Server) • O/S Major/Minor Version • Status • User Cache • User Name • Domain

  15. Query Engine Settings Advanced User Cache Settings • 3 Modes: • Support Service • MQE • None

  16. Query Engine Settings Port Settings

  17. Query Engine Settings Bandwidth MQE 100 56k 128k 128k 128k 50 SQE SQE SQE SQE

  18. Assigning Subordinates to Masters I’m the Master, to whom can I assign work? Svr1 Svr26 Win2k7 HouFS02 HouFS03

  19. Distribution Rules I’ve just been given a job, which machines can I report on?

  20. Distribution Rules Assign specific SQEs to gather data from specific targets • Absolute assigns a single reporting computer to a single SQE. • Wildcard uses pattern matching to assign a group of computers whose host names match a pattern to a group of SQEs. • Computer Group assigns all computers defined in a Computer Group to a single or multiple SQEs. • Associated with each set of distribution rules is a default group. It contains SQEs that will query computers if none of the absolute or wildcard rules match the computer or if assigned QEs in other rules fail.

  21. Distribution Rules Other types of rules…

  22. The Distribution Rules Results dialog displays the machines that are assigned to each SQE Distribution Rules Testing the Rules

  23. Site 3 Site 1 Site 2 Set the Default Group Membership Distribution Rules Testing the Rules

  24. Diagnostics and Healing • Query the Query Engine – Health and Status Check • What settings could be causing a bottleneck? • Live Diagnostics • Event Logging

  25. Diagnostics and Healing Query the Query Engine • RAM • CPU • DCA, AAA, SRA count • Services (other Apps ) • IP information

  26. Diagnostics and Healing Health and Status Checks

  27. Diagnostics and Healing Health and Status Checks – What to look for • Are all QEs running the same version, service pack, and hotfix? • Do all QEs have the same DCA count? • Do Connection Databases and Distribution Rules make sense? • If using the Support Service to gather last logon – does every DC have one installed? • Default Group Membership

  28. Diagnostics and Healing Remember the QE Settings?

  29. Diagnostics and Healing Diagnose bottlenecks while a query is running

  30. Diagnostics and Healing Diagnose bottlenecks while a query is running

  31. Optimize Query Structure Type and structure of queries A few rules…. • MQE – always queries for Directory Object information • Scope first, filter last – Narrow the area to search, then pick out exactly what you are looking for. • Use Entitlement Reporting wisely • Don’t gather more information than you need. Why read through a huge amount of information looking for the particulars you need – let bv-Control do that for you. • AUTOMATE, AUTOMATE, AUTOMATE!

  32. Query Building Best Practices Entitlement Reporting

  33. Query Building Best Practices Event Log Reporting NO!!

  34. Query Building Best Practices Event Log Reporting

  35. Query Building Best Practices Summary Remember… • Field – What do you want to see on your report? • Filter – If it meets what conditions… • Sort – In what order? • Scope – From where do you want to gather the information? • Scope first, filter last – Narrow the area to search, then pick out exactly what you are looking for. • Don’t gather more information than you need. • AUTOMATE, AUTOMATE, AUTOMATE! - Schedule

  36. Questions and Answers

  37. BindView Upcoming Events Online Training • May 24 - Maximizing Your BindView Investment: Using BindView for NetWare and bv-Control for NDS eDirectory • June 21 - Maximizing Your BindView Investment: Using bv-Control for Windows for Entitlement Reporting

  38. Hands-On Training Houston Training • May 23-25 – Core Class: bv-Control for Windows & Exchange Administrators • June 2-3 - bv-Control for NetWare and NDS • June 6-10 - BindView Certified Systems Administrator Training

  39. Free Gift! WebEx Survey (Live Event only – not applicable for archived events) • Free BindView level and screwdriver with each completed survey • COMPLETED surveys are also into a drawing for a 15x18 magnetic dartboard

  40. Contact Information BindView www.bindview.com Technical Support 1-800-813-5867 www.bindview.com/Support/ Sales 1-800-813-5869 sales@bindview.com Professional Services for your Training and Consulting needs: psquestions@bindview.com www.bindview.com/services

More Related