1 / 25

Common Solutions Group Workshop: Managing Large Environments Introduction and Background

Common Solutions Group Workshop: Managing Large Environments Introduction and Background. Susan Grajek, Yale Steven Sather, Princeton. Overview of Today’s Workshop. Introduction and background Managing desktop security Asset and inventory management Mobile device management

red
Download Presentation

Common Solutions Group Workshop: Managing Large Environments Introduction and Background

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. Common Solutions Group Workshop:Managing Large EnvironmentsIntroduction and Background Susan Grajek, Yale Steven Sather, Princeton

  2. Overview of Today’s Workshop • Introduction and background • Managing desktop security • Asset and inventory management • Mobile device management • Wrap up, next steps

  3. Workshop goals • What are managed environments? • Where do we stand today? • Challenges • Best practices • What are the benefits of managing environments?

  4. What are managed environments? • Ad hoc Managed Device group met in Chicago in July • Brown: Karen Asquith & Alan Usas • Chicago: Greg Anderson, Corey Liss & Kevin Vaccaro • Duke: John Cook • Princeton: Charlayne Beavers, Phil Immordino & Steven Sather • Stanford: There in spirit! • Virginia Tech: Bill Plymale • Yale: Lee Fontaine, Susan Grajek & Adriene Radcliffe

  5. Chicago workshop recap Goals • Define managed devices • Describe best practices • Identify opportunities for collaboration

  6. Defining device management • Security • Initial Configuration • Patching/Updates • Access Control • Malware (virus/spyware) • Privacy (encryption, hipaa) • Application deployment • Inventory and asset management • Image management • Data integrity • Remote assistance • Connectivity and registration • Software and licensing • (Accounts Management)

  7. Management environments Fully managed • Dumb terminals, thin clients. • No data or local applications other than those that facilitate access. Wide open • End users have administrative privileges at both the application and operating system levels. • Applications and data are stored locally. • No common base configuration. • Subscription and self-service tools unlikely to be available, so machine is managed manually. • No up-front prohibited protocols, devices, applications, or actions (but machine will be disconnected if it causes a problem to the rest of the network).

  8. Results of CSG Survey

  9. 24 respondents for 21 Schools and EDUCAUSE • Brown University • Carnegie Mellon University • Columbia University • CU-Boulder • Duke University • Harvard - Central Administration • Indiana University • MIT • Princeton University • Stanford University • University of Chicago • University of Delaware • University of Michigan • Campus Computing Sites • Health System • University of Minnesota • USC • University of Texas @ Austin (two submissions, data averaged) • University of Washington • University of Wisconsin-Madison • University of Virginia • Virginia Tech • Yale University • EDUCAUSE

  10. Desktop Management Environments

  11. Some highlights • University of Michigan reports 100% locked down for faculty, staff and students • Four schools reported more than 80% of faculty machines are fully unmanaged: • Chicago, Delaware, USC, CU-Boulder • Only three schools guessed that faculty machines could be fully managed: • Stanford (10%), UT-Austin (2%) and UVa (1%) • Two-thirds of schools believe that at least 50% of student machines could be at least partially managed.

  12. Different tools and processes will work in each environment.

  13. Process used Mapped each device management activity (e.g., application deployment) against each environment to: • describe what each of us is currently doing • consider other, additional options • draft best practices for each environment

  14. Example: Application deployment

  15. Summary of management tools and processes • Managed update tools (SMS, Zenworks, GPOs, WSUS, Shavlik) • Manual update (end user or technician) • Self-service configuration tools • Images • Remote data wipe • Tools to enable end-users select their management preference • Installers • Software virtualization • Thin client applications delivery

  16. Summary of management tools and processes • Network quarantine • Life cycle management (leasing, mediated purchasing and disposal) • Asset management tool • Vendor-supplied data • Bundle on CDs • Mac address/network registration • Published guidelines • Site licenses • Minimum requirements

  17. Results of CSG Survey

  18. Which practices and tools are we using? % of schools using

  19. How widely are we deploying tools & practices? <20% >80% 20-50% 50-80% % of devices used with

  20. How widely are we deploying tools & practices?

  21. Questions?

More Related