Operational MS Tibor Kolejak Regional IT Site Manger Microsoft Czech Republic Tibor Kolejak Regional IT Site Manger Microsoft Czech Republic Company Logo Here

Sydney Chofu & Otemachi Les Ulis TVP Dublin Benelux Madrid Dubai Singapore Johannesburg Sao Paulo 72,000 mailboxes Canyon Park, Redmond Los Colinas Charlotte Chicago Milan Stockholm Munich 400+ supported Microsoft sites worldwide 4.5M+ messages per day internally >400 apps 26M voice calls per month 50K employees 5K contractors 17K vendors 150,000+ PCs >7,000 servers 20 (?) Microsoft Exchange Messaging Servers Silicon Valley

Challenges Large, highly dynamic environment Security  2,500 attacks, probes, and scans daily  Over 125,000 virus-infected messages quarantined monthly Unique IT environments for product development, testing, support, and research require special security Technology-literate staff  95% with local administrator right to their desktop

Operational efficiency To get more with less… To increase service levels with less money… Adequate synergy of various factors required! People Processes Platforms Management tools etc. Network solutions Platform

Agenda Model Enterprise Windows Server 2003 Deployment Microsoft Operations Manager SMS 2003 Deployment

Model Enterprise Internet DC Local Office DSL/Local ISP/ Leased Line to local ISP AT&T/GX/Equant Leased Line AT&T/GX Leased Line ICO 1 - ICO 2 - Standard Building

Windows Server 2003 Deployment Major milestone for MS A lot of new innovative features Internal deployment coming from the need to improve security, availability and reliability Beta 2 Mar 2001 Int. Installations Beta 3 Nov 2001 RC1 Jul 2002 RC2 Dec 2002 RTM Feb 2003 Launch Apr 2003

Major Phases of Deployment Future Technology Integration Planning Test and Pilot Enterprise Deployment Sustain and Manage 0 Future Technology 1 Integration Planning 2 Test & Pilot 3 Enterprise Deployment 4 Sustain & Manage

Business Benefits Reliability Scalability Security Lower Support Costs

Microsoft Operation Manager Situation Monitoring the enterprise with many different tools makes the task expensive and inefficient Solution Consolidate and adopt Microsoft Operations Manager as key enterprise

MS IT using MOM Business Unit IT Messaging and Collaboration Services Enterprise Infrastructure Services Corporate Security

Business Benefits Lower TCO Proactive versus reactive/ Server availability increase Scaleable Flexible and interoperable

Patch Management Situation Security vulnerabilities can lead to loss of revenue and intellectual property Solution SMS 2003 is key tool in Microsoft IT patch management process

Patch Management Framework 1. Assess Environment to be Patched Periodic Tasks A. Create/maintain baseline of systems B. Access patch management architecture (is it fit for purpose) C. Review Infrastructure/ configuration Ongoing Tasks A. Discover Assets B. Inventory Clients 1. Assess 2. Identify 4. Deploy 3. Evaluate & Plan 2. Identify New Patches Tasks A. Identify new patches B. Determine patch relevance (includes threat assessment) C. Verify patch authenticity & integrity (no virus: installs on isolated system) 4. Deploy the Patch Tasks A. Distribute and install patch B. Report on progress C. Handle exceptions D. Review deployment 3. Evaluate & Plan Patch Deployment Tasks A. Complete patch acceptance testing B. Obtain approval to deploy patch C. Perform risk assessment D. Plan patch release process

Business Benefits Automated security update and application deployment  Enforcement within prescribed timeframes  Minimized unplanned downtime Central reporting and administration  Clear communication path More accurate and efficient patch management  More updates, fewer administrators, less time Reduction in manual effort to deploy updates  Automated tools, fewer scripts

1 Central Site Server Windows Server 2003 SQL Server 2000 SP3a 10 Primary Site Servers Windows Server ,000 Windows Server 2003–Based Servers Running SMS 2003 Advanced Client with Advanced Security Server Patch Management Architecture

Server Patch Management Process: Team Roles MSRC  Releases security bulletins Corporate Security  Assigns deployment priority Data Center Operations  Manages data centers  Hosts SMS infrastructures  Patches servers

Server Patch Management: Phases Two schedules, one deployment/enforcement process Phase 1: Monitoring for security bulletins and updates from Microsoft  Process of deploying update to servers begins after update is released

Server Patch Management Process: Phases Phase 2: Determining the risk level  MSRC - Critical, Important, or Moderate  CSCT - Deployment scheduled - based on adjusted MSRC rating  DCOPS - Security Update Inventory Tool helps determine which servers are vulnerable  MBSA scans for missing/installed updates

Server Patch Management Process: Phases Phase 3: Testing  Deploying synthetic patch to test deployment success  Monitor success, investigate and fix failures

Server Patch Management Process: Phases Phases 4–7: Deploying the patch Thursday Friday Saturday Sunday Hour 1 Hour 2 Hour 3 Hour 4 12 A.M.– 4 A.M. 4 A.M.– 8 A.M. 8 A.M.– 1 P.M. 1 P.M.– 4 P.M. 4 P.M.– 8 P.M. 8 P.M.– 12 A.M. 4 P.M.– 8 P.M. 8 P.M.– 12 A.M. Standard Deployment Emergency Deployment

Server Patch Management Process: Phases Phase 8: Reporting  Determine success of deployment and degree of voluntary patching  Advertisement Status Viewer

Demos

Asante sana kusikiliza!