1 / 18

the evolution of a technical services portal

Portal. Software. Information. Cloud. Support. the evolution of a technical services portal. PRESENTED BY BRIAN M. OSBOURN & CORY FALLDINE. What is techsite ?. A central portal for delivery of technical services Uses SharePoint and basic webpages

sheri
Download Presentation

the evolution of a technical services portal

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. Portal Software Information Cloud Support the evolution of a technical services portal PRESENTED BY BRIAN M. OSBOURN & CORY FALLDINE

  2. What is techsite? • A central portal for delivery of technical services • Uses SharePoint and basic webpages • Combination of Public & Authenticated Sites • Employees & Students • IT Staff • Starting point for every core service • Does not replace our campus portal

  3. Where does it fit in? TechSite

  4. Where does it fit in? TechSite

  5. In the beginning • PC Installation difficulty • Basic Web Page with links to installers (IE 3.0) • Only used internal to IT Department • Core concept still used today

  6. Version 2-4: We’re on to something • Useful for public, too • Additional features • New browser capabilities • Flash • No Code • Hosted on NetWare 2 3 4

  7. Version 7 & 9: introducing the portal • All features of previous versions • Authentication to eDirectory • Written in PHP • Custom content based on role (Employee or Student) • Customized software install options • Printer installer (iPrint) • File Access (NetStorage) • First to target students (StudentAccess) • Asset Tracking

  8. Problems ahead • Continuous Improvement • Broke My Own Rule • Lost entire staff of developers • The start of Novell’s Open Source Folly • Where Do We Go From Here?

  9. Version 10: sharepoint • Foundation • Active Directory authentication • Back to “No Code” Mentality • Complete rebuild • Current Features – Asset tracking, software installation, printer installation, Student web page and file access • New Features - IT Departmental teams, Project Teams, Project Information Sites, license management and a Training Registration module

  10. Version 11: role-based sites • Sites customized to status and location (Employee vs. Student, On-Campus vs. At Home) • No technical restriction (installers not available off campus) • URL’s customized for single sign-on on campus • Split architecture to have static introductory html public web pages • Content split between 2 SharePoint servers, and 1 web server • Completely virtual • Team-based, projects wrapped up, IT Department moved to SharePoint Enterprise on its own server

  11. Version 12: the feedback edition • Teams started working much closer together on changes, new features • Feedback from technical staff and customers • 11.5 was to include a few fixes from v.11, huge number of requests • Architecture stayed the same • Contentand delivery, user experience

  12. The Features of v.12 • InstallPoint • TechDocs • Forms Server • Project & Team Sites • PrintCenter • Information Security Policies • Windows 7 Support • MacSite • Helpdesk (informational) • LaunchPoint • Anti-Virus at Home • Downloads for Home • MyFiles2.0 • Communicator

  13. More FEATURES of v.12 • PCInfo • PrinterInfo • ServerSite and ServerInfo • LicenseCommander

  14. the architecture of v. 12 • Web Server – Windows Server 2008 R2 x64 • 2 x SharePoint Services 2007– Windows Server 2008 R2 x64 • Authenticates to AD • Backed up with Data Protection Manager • All virtual using Hyper-V R2

  15. Lessons learned • Control technologies used • Feedback & Collaboration are key • Adapt • Don’t go overboard • Continuous Improvement

  16. Techsite.next • SharePoint 2010 • Fewer servers • Content Management • MySite • Team and Collaboration focus • Social Networking • Office Web Apps • More focus on Internet functionality

  17. Questions?

  18. Contact Info & download • Full PowerPoint is available to download from TechSite (http://techsite.emporia.edu), • Brian Osbourn, bosbourn@emporia.edu • Cory Falldine, cfalldin@emporia.edu

More Related