configuration manager and operations manager · web viewconfiguration manager and operations...

Configuration Manager and Operations Manager Deployment

Prepared forMOFA

7/7/2012Version 1.1

Prepared by

Aydin DemirSenior Consultant

[email protected]

mailto:[email protected]

000MOFA0

Revision and Signoff Sheet

Change RecordDate Author Version Change reference

03.07.2012

Aydin Demir 1.0 Initial draft for review/discussion

06.07.2012

Aydin Demir 1.1 Final Draft after Architect Review

ReviewersName Version

approvedPosition Date

A N Hasan 1.1 Architect 07.07.2012

Configuration Manager and Operations Manager Deployment, MOFA, Version 1.1 Final Prepared by Aydin Demir last modified on , Rev

000MOFA0

Table of Contents1 Executive Summary...........................................................1

2 Table of Reference.............................................................1

3 Business Opportunity.........................................................23.1 Operations Manager 2012.........................................................................................2

3.2 Configuration Manager 2012....................................................................................2

4 Project Vision and Scope....................................................34.1 Vision Statement...........................................................................................................3

4.2 Benefits Analysis...........................................................................................................3

4.2.1 Operations Manager 2012...............................................................................................3

4.2.2 Configuration Manager 2012..........................................................................................3

4.3 Requirements.................................................................................................................4

4.3.1 Business Requirements....................................................................................................4

4.3.2 User Requirements............................................................................................................5

4.3.3 Operational Requirements..............................................................................................6

4.3.4 Security Requirements.....................................................................................................6

4.4 Scope of Project.............................................................................................................7

4.4.1 Centralized Database with SQL 2008 R2...................................................................7

4.4.2 Operations Manager 2012...............................................................................................8

4.4.3 Configuration Manager 2012........................................................................................11

4.4.4 Out of Scope......................................................................................................................14

4.5 Version Release Strategy.........................................................................................16

4.6 Acceptance Criteria....................................................................................................16

4.7 Operational Criteria....................................................................................................18

5 Solution Design Strategies...............................................195.1 Architectural Design Strategy................................................................................19

5.2 Technical Design Strategy.......................................................................................20

5.3 Project Management Strategy................................................................................20

5.4 Project Organization Structure...............................................................................21

5.5 Project Roles and Responsibilities........................................................................22

5.5.1 Customer Project Roles and Responsibilities..........................................................22

5.5.2 Microsoft Project Roles and Responsibilities...........................................................23


000MOFA0

6 Risk Management............................................................236.1 Risk Management Process.......................................................................................24

6.1.1 Identify.................................................................................................................................24

6.1.2 Analyze................................................................................................................................25

6.1.3 Plan.......................................................................................................................................25

6.2 Project Risks.................................................................................................................25


000MOFA0

1 Executive SummaryMinistry of Foreign Affairs (“MOFA”) requested Microsoft Consulting Services to design and deploy the System Center Configuration Manager 2012 and Operations Manager 2012 in their LAN and internet network. This document will provide scope details for the work to be delivered.

MOFA has a need to implement a monitoring solution that will allow them to proactively monitor the IT services running business critical processes – in particular Active Directory, Exchange and Database Servers. Currently, there is no monitoring solution. Microsoft® System Center Operations Manager (SCOM) 2012 has been chosen as the solution that will provide enhanced application performance and availability monitoring across multiple platforms in MOFA’s datacenters.

The overall goal of the monitoring solution phase will take into account the future monitoring of all Windows servers in MOFA, some Unix/Linux servers, and network devices. MOFA has requested that initial implementation be performed in LAN and internet network. These networks are totally isolated and have different business functions. This will be reflected in the detailed design document, which will provide a design that can scale for the full production deployment of SCOM 2012.

In addition, Microsoft is partnering with MOFA to design and deploy System Center Configuration Manager 2012. With the adoption of the latest Microsoft management technologies, MOFA can implement an automated software distribution and management solution for the entire enterprise environment. Microsoft Services Configuration Management Offering defines and provides the framework for the proposed project. This Offering provides end-to-end guidance for the efficient planning, testing, deployment, and on-going operations of Microsoft System Center Configuration Manager 2012. Using this framework a consistent and predictable output is expected based on many executions of the overall process.

The overall goal of desktop management phase is to plan, develop, and implement critical desktop software deployment functions for MOFA using Configuration Manager 2012. This solution will consider the OS deployment, software asset, and software deployment features of Configuration Manager with an emphasis on the software distribution and OS deployment within all of the MOFA business units.

The purpose of this document is to provide a high level view of the solution architecture, explaining in exact and specific terms what the team is building and deploying. The Detailed Design Document is the final technical document which Microsoft and MOFA will use to collectively build the solution.

2 Table of ReferenceThe contents of this document are based on the following documents/references, emails communications available.

SI. No. Name of Document/Document ID Version, Date of Issue1 MOFA - SCCMSCOM - SOW V2 20120612.docx V2.0, 12/06/2012

Table 1 - Table of reference

Page 1Configuration Manager and Operations Manager Deployment, MOFA, Version 1.1 Final Prepared by Aydin DemirConfiguration Manager and Operations Manager Deployment last modified on 6 Jul. 12, Rev 12

000MOFA0

3 Business OpportunityMicrosoft Services Consulting will work with MOFA to deploy SCCM 2012 and SCOM 2012 infrastructure in production which will allow the organization to deliver enhanced levels of service across IT services based on Microsoft products within the data center. Implementation will include services explained below.

3.1Operations Manager 2012By successfully implementing Operations Manager 2012, MOFA expects to:

Better proactively monitor the Windows® platform in the environment, supported UNIX and Linux servers and Network devices.

Provide operators with better information so that they can identify the root causes of issues and resolve them faster

Provide management with reports about how the environment is performing and meeting established Service Level Agreements (SLAs)

Report system failure trends across the organization to identify root causes and improve productivity

Provide a knowledge base of how previous issues were resolved Provide architects and engineers with tools that allow them to better understand the

current environment so that they can design better future solutions Provide capacity planners with real –time system information so that they can better plan

and model the environment Take advantage of Microsoft management packs to provide expertise on what should be

monitored in the environment and how to do so

3.2Configuration Manager 2012The following are key business opportunities that will be addressed by deploying Configuration Manager 2012:

Improve Technology Strategy – Better centralize & standardize PC systems management. Deploy Operating System and Applications - Delivery of the business and core applications

effectively to our next generation platform for the enterprise environment within the designated timeframe.

Improve Software Asset Management – Better inventory & management of licensed software is needed to gain control of software license expenses and deployment.

Provide PC Refresh Improvements – Out-of-date PC Refresh methods are costly; delivery over-the-wire and other automation capabilities will reduce costs.

Enhance Controls – New system management tools provide enhanced management and compliance controls to ensure enterprise level risks are controlled.

Mitigate Risks –Reduce risks of licensing overruns. Other Enhancements – Opportunities to offer other support, process improvements, refresh

and management costs reduction through automation.


000MOFA0

4 Project Vision and Scope4.1Vision Statement

MOFA System Center project vision

“To enable MOFA deploying Microsoft System Center products that helps the IT team to have more visibility on services and applications, reducing operations and facilities costs of Windows 7 deployment.”

4.2Benefits Analysis4.2.1 Operations Manager 2012By deploying a solution that is based on Operations Manager 2012 to manage IT services that are running on Microsoft products, MOFA will gain the following benefits:

Improve service levels and visibility with end-to-end service management of Microsoft services

Enable Operations and IT Management teams to more easily identify and resolve issues affecting the health of distributed IT services

Accelerate problem resolution through expert server and application knowledge of the Windows platform

Reduce IT management complexity by automating routine administration

4.2.2 Configuration Manager 2012MOFA is forecasting a significant improvement in software distribution capacity and efficiency, infrastructure service availability and a reduction in manual remediation effort by leveraging the new technology features provided in Configuration Manager. Coupled with the new OS deployment and application delivery capabilities is forecasting increased reliability and compliance reporting accuracy for security-related deployments throughout the environment.

Configuration Manager 2012 technology deployment sets the foundation for possible future services and process improvements such as:

Improved user experience using features such as maintenance windows to control systems management activities

Compliance reporting and remediation using Desired Configuration Management Integrated Windows 7 Operating System Deployment Enhanced reporting capabilities using SQL Reporting Services-based reporting Enhanced software license reporting (Asset Intelligence feature) Native Power Management configuration and monitoring Improved process for deployment of software updates


000MOFA0

4.3RequirementsThe requirements set forth in the following sections define the business, user, operational, and system requirements that must be met for this engagement to be successful.

4.3.1 Business Requirements

4.3.1.1 Operations Manager 2012

The solution must provide MOFA with a stable, secure infrastructure to ensure that IT service owners are able to accurately monitor and report on their availability and performance metrics through enhanced service-level monitoring. It also must allow IT operations staff improved access to the key functionality they need to maintain, enhance, and assure the services being delivered to end users.

The solution must provide MOFA with the ability to proactively monitor IT services that are running on Microsoft technologies in the enterprise. In addition, management packs will be tuned to ensure operational efficiency in how the services are monitored and so that only actionable alerts are generated.

The solution must include the following core requirements;

Monitoringo Windows Serverso Supported Linux and UNIX serverso Cisco Switcheso F5 load balancerso Juniper Firewalls

Management Packso Windows Server OS (2003/2008/2008 R2)o Exchange 2010o SharePoint 2007 / 2010o DHCPo Hyper-V o DNS (Windows 2008/2008 R2)o IIS o Active Directory (Windows 2003 / 2008 / 2008 R2)o Group Policyo Cluster Serviceo SQL 2003 / 2008 / 2008 R2o SCCM 2012o TMG 2010

Additional ServicesPage 4

Configuration Manager and Operations Manager Deployment, MOFA, Version 1.1 Final Prepared by Aydin DemirConfiguration Manager and Operations Manager Deployment last modified on 6 Jul. 12, Rev 12

000MOFA0

o Performance Monitoringo Audit Collection from Windows Security Logso Operations Manager 2012 server roles must be deployed on existing virtualization

platform.

4.3.1.1 Configuration Manager 2012

MOFA has the following requirements

Computer Discovery and adding new computers to Configuration Manager hierarchy should be less than one day

Inventory should be collected once per week Desktops will be more secure due to a more dependable software update process,

including OS and application patching. Desktop stability through a more robust management solution will allow more opportunity for business productivity.

Existing Trend Micro 10.5 should be uninstalled and System Center Endpoint protection should be installed without user interference

Costs (Direct and Indirect) associated with the current MOFA OS deployment process will be reduced. As an indirect one will the cost of the engineer going to a remote location to deploy an Image from a USB.

Unlicensed software exposure will be minimized by the ability to identify the software in use in the MOFA environment.

Automating the OS deployment process and automatically applying updates and patches will reduce administration cost.

Configuration Manager 2012 server roles to be deployed on existing virtualization platform.

Power Management should provide efficient reduction of power consumption on clients only.

4.3.2 User RequirementsMOFA users have the following requirements;

Licensed applications should be available to deploy at any time. Mandatory patch deployments should not affect daily operation Applications deployment should be done out of working hours Users should be able to reschedule deployments in 3 days. Existing Trend Micro 10.5 should be uninstalled and System Center Endpoint

protection should be installed without user input Users should be able to install applications using portal provided without any

approval.


000MOFA0

4.3.3 Operational RequirementsThe following section provides a summary of the goals and requirements considered significant by the technical stakeholder, which usually consists of IT Administrators, IT Operators and Help Desk Personnel who operates or administer the solution.

4.3.1.1 Operations Manager 2012

The Operations Manager solution has to be highly available or provide automated failover between system components. Reporting and data warehouse database should be configured in highly available configuration. In addition, operations guidance and information about activities required to maintain a stable Operations Manager implementation should be provided. Operational activities include but are not limited to:

Managing Operations Manager server roles Backing up Operations Manager components Managing notifications and subscriptions Managing security configuration Maintaining database performance Managing management packs

4.3.1.1 Configuration Manager 2012

The following operational benefits would be expected based on implementing Configuration Manager 2012 in the MOFA environment;

Minimize time taken to re-deploying image by preserving the user data Minimize the time to deploy a new Standard Operating Environment Minimize the time to build or rebuild a workstation Ensure that common tools are used so that operations and support skills are easy to

source Provide increased agility by having a more flexible platform to deploy new

applications Ability to apply non-Microsoft applications updates such as Acrobat Reader Minimize the time taken to update or patch applications Minimize the time taken to deploy applications

4.3.4 Security RequirementsMOFA requires that the following security practices to be implemented;

Agent and server communication should be done with encryption between client and servers

All application components require service accounts will use domain based accounts with complex passwords

Solution should be implemented in isolated network where all access is restricted.


000MOFA0

All administration should be restricted to trained administrators. All servers and services should be hardened.

4.4Scope of ProjectMicrosoft will provide the following services:

4.4.1 Centralized Database with SQL 2008 R2

We will deliver a design and deployment for SQL 2008 R2 cluster to host all the databases in the internet environment. We will provide the following services:

4.4.1.1 Planning Phase

During a Planning phase, the team develops the logical and Physical designs and compiles that information in a functional specification document. The team also develops a detailed project schedule that includes development, testing, communication, and other related tasks required for a successful implementation. The goal of this phase is to enable the team to create a detailed design of the centralized SQL 2008 R2 infrastructure for internet environment to meet your functional requirements.

Design of one central high available Microsoft SQL 2008 R2 environments along with Reporting services

Design the SQL server platform monitoring and reporting by SCOM 2012 as available within this platform

Conduct a technical design workshop to discuss and evaluate the detailed design solution architecture

Planning High availability to make sure all the components are available if one server goes down

Storage sizing

Architecture and design detailing that details the proposed high availability solution

Document the design specifications of the Virtual platform in a design specifications document or Microsoft Office Visio® 2007 diagram.

Hold a design-complete milestone review.

Finalize specifications for all hardware and software for pilot and production.

4.4.1.2 Deployment and Stabilizing

In this project phase, the Microsoft team will work alongside your team with the initial pilot production deployment of the solution over the projected duration of the pilot and then final complete rollout.

Deploy the 2 node Windows 2008 R2 SP1 Failover cluster


000MOFA0

Deploy SQL 2008 R2 on the failover cluster

Deploy SQL Reporting Service

Completed production deployment of Centralized SQL 2008 R2 Cluster

4.4.2 Operations Manager 2012

The project team will review the document protection strategy in addition to the network, client, and directory environments to design a solution and a deployment plan that meet the MOFA requirements and expectations.

4.4.2.1 Envisioning and Planning

Create logical and Physical architecture including:

o Defining management group structure

o Define management packs

o Define server roles and targeting

o Define client roles for targeting

o Availability and recovery strategy

o Traffic and load estimation

Create a detailed design including:

o Hardware and software specification

o Hardware capacity and high availability design

o Server placement

o Management sever design and configuration

o Operations database design and configuration

o Reporting and data warehouse design and configuration

o Agent installation and configuration design

o Active Directory integration design

o Notifications design and configuration

o Alert settings and configuration

Audi Collection Services

Create a security design including:Page 8


000MOFA0

o IIS server security

o SQL server security

o Management point security

o Role based security / Views

o Service accounts

o Run as accounts

o Network port and firewall configuration

Planning Network monitoring for the below network devices however they should be listed in the supported devise list as mentioned in the below note

o Cisco Switches

o F5 load balancers

o Juniper Firewalls

Planning heterogeneous monitoring (Linux and Unix) only the version approved by SCOM 2012 as listed in this link: http://technet.microsoft.com/en-us/library/hh212713


In this project phase, the Microsoft team will work alongside your team with the initial pilot production deployment of the solution over the projected duration of the pilot.

LAN Environment

o Operations Manager Infrastructure deployment with 2 Management Servers

o Reporting Infrastructure

o Pilot 25 Agent Deployment covering all the server roles including networking devices supported by SCOM 2012

o Enable Audit collection service

o Deployment of following MPs

Windows Server OS (2003/2008/2008 R2)

Exchange 2010

SharePoint 2007 / 2010

DHCP


http://technet.microsoft.com/en-us/library/hh212713

000MOFA0

Hyper-V

DNS (Windows 2008/2008 R2)

IIS

Active Directory (Windows 2003 / 2008 / 2008 R2)

Group Policy

Cluster Service

SQL 2003 / 2008 / 2008 R2

SCCM 2012

TMG 2010

o Basic Management Pack Tuning

Internet Environment

o Operations Manager Infrastructure deployment with 2 Management Servers

o Reporting Infrastructure

o Pilot 25 Agent Deployment covering all server roles including networking devices supported by SCOM 2012

o Enable Audit collection service

o Deployment of following MPs

Windows Server OS (2003/2008/2008 R2)

DNS (Windows 2008/2008 R2)

DHCP

IIS

Active Directory (Windows 2003 / 2008 / 2008 R2)

Group Policy

Cluster Service

SQL 2008 / 2008 R2

SCCM 2012

Hyper-V


000MOFA0

TMG 2010

o Basic Management Pack Tuning

4.4.3 Configuration Manager 2012

Microsoft will deliver a design and deployment for SCCM 2012 along with end point protection, as described below for both LAN and Internet environment

4.4.3.1 Planning

The Planning phase ends when the functional specification is approved. This milestone represents the approval to move forward and to begin construction of the solution elements in the Development phase.

Conduct technology planning sessions and workshops, to define the end-state system, documenting the results in the Functional Specification document.

Design the SCCM 2012 architecture consisting of the following topics:

o Site design

o Boundary design

o Client settings and schedules

o Basic software updates management

o Remote Control tools

o Distribution Point design for software distribution

o Client Discovery and installation methods and strategy

o Software distribution strategy like Windows 7 OS and Office 2010

o Remote control

o Endpoint Protection

o Planning for Desired Configuration Management for standard client baseline

Software Updates for Windows Products and WSUS integrated Partners

Planning one x32 bit Windows 7 OS with Microsoft Office 2010 SP1 image and one x64 bit Windows 7 OS with Microsoft Office 2010 SP1 image.

Planning for Asset Intelligence

Planning for Power Management Features


000MOFA0

Determine hardware and software requirements, and produce a detailed bill of materials.

Prepare and present functional specification document (architecture and design document).

Have functional specification document reviewed and signed off by the project sponsors.

Develop Test Testing plan along with MOFA IT team


In this project phase, the Microsoft team will work alongside your team with the initial pilot production deployment of the solution over the projected duration of the pilot.

LAN Environment

o Deploy Configuration Manager 2012 Infrastructure, including a central administration site, primary sites and secondary sites where appropriate but maximum 5 sites.

o Enable and provide guidance on the SQL Reporting Services (SRRS) from the Configuration Manager console

o System Center Configuration Manager 2012 Endpoint Protection (EP) Infrastructure

o Configure 5 Distribution Points where appropriate

o SCCM 2012 Servers deployment with the following features:

Software update management

Client Discovery

Inventory

Software distribution

Remote Control tools

o Configuring Operating System Deployment feature for Windows 7 Deployment

o Creating two base images with hardware drivers

X32 bit Windows 7 image along with Office 2010 SP1



000MOFA0

o Testing Driver Updates

o Deployment of SCCM 2012 agents to 100 pilot desktops (Windows XP SP3 and above)/servers (windows 2003 SP2 and above). MOFA should provide the list which has the machine names or OU or IP address

o Removing the current Trend Micro Antivirus and Deployment of Endpoint protection to 100 pilot desktop or servers. MOFA should provide the list which has the machine names or OU or IP address

o Deployment of Windows 7 and Office 2010 image on 5 compatible Desktops or laptops

o Configuring Desired Configuration Management for standard client baseline

o Perform post-deployment configuration actions and validate functionality.

Internet Environment

o Deployment one Primary site

o SCCM 2012 Servers deployment with the following features:

Software update management

Client Discovery

Inventory

Software distribution

Remote Control tools

o System Center Configuration Manager 2012 Endpoint Protection (EP) Infrastructure

o Configuring Operating System Deployment feature for Windows 7 Deployment

o Configuring the environment

o Creating two base images with hardware drivers



o Testing Driver Updates

o Configuring Desired Configuration Management for standard client baseline


000MOFA0

o Deployment of SCCM 2012 agents to 100 pilot desktops (Windows XP SP3 and above)/servers (windows 2003 SP2 and above). MOFA should provide the list which has the computer name and IP address or OU name

o Removing the current Trend Micro Antivirus and Deployment of Endpoint protection to 100 pilot desktop or servers. MOFA should provide the list which has the machine names or OU or IP address

o Deployment of Windows 7 and Office 2010 image on 5 compatible Desktops or laptops

o Perform post-deployment configuration actions and validate functionality.

Project Completion and Signoff

4.4.4 Out of Scope

Any area that is not explicitly listed in section “within scope” is out of scope for this engagement. The areas that are out of scope for this engagement include, but are not limited to, the following:

Products Training

Repair of major problems of the existing Infrastructure.

Documentation of MOFA network.

Investigation of any non-Microsoft products compatibility with the proposed environment.

Microsoft is not accountable for providing information relevant to any third party software. However Microsoft can provide recommendations for the optimum selection of third party products during the envisioning phase.

Investigation and analysis of Network Utilization

Planning and Designing of an Enterprise CA / PKI Infrastructure

The installation or configuration of third party applications in this engagement will be the responsibility of the customer team.

Post-deployment technical support (this should be covered by Premier contracts)

Any client OS Deployment other mentioned in the in scope section

Internet Based Client Management

Device Management

Fixing unhealthy clients if the issues persist with the operating system


000MOFA0

Third-party software packaging (Wise, InstallShield, repackaging, or others).

Additional software delivery responsibilities, such as the System Center Updates Publisher.

Hardware mounting, configuration, or base image installation.

Deploying SCCM clients on third party operating systems

Custom development of System Center Configuration Manager reports. The default out-of-the box System Center Configuration Manager reports will be implemented

Integration between System Center Configuration Manager and any third-party software.

NAP Integration and DCM for Servers

Application Compatibility Activities

Any third party applications or devices configuration

Monitoring of solution using Microsoft Systems Centre Operations Manager or 3rd party monitoring tools

Hardware/Operating System deployment

Monitoring other IT services not stated Areas within Scope; service-level dashboard; or scorecards.

Development of custom management packs.

Deployment and configuration of management packs not stated in areas within scope section

Agent deployment on any platform not specifically supported by System Center Operations Manager 2012.

Installation and configuration of SQL Server in the LAN environment. It is assumed that SQL Server / cluster will be ready and no upgrade is required.

Resolving Network Connectivity Issues

Resolving Hardware Issues of the existing environment

Configuration of the SAN environment

Products Training other than on job knowledge transfer during entire proj ect lifecycle

Microsoft is not accountable for providing information relevant to any third party software. However Microsoft can provide recommendations for the optimum selection of third party products during the envisioning phase.

Hardware will not be provided under this Work Order. Customer is responsible for acquiring all necessary hardware required as a result of Work Order.


000MOFA0

Windows XP or Windows Vista or Windows 7 Application compatibility testing will not form part of the responsibility of the assigned Microsoft team members.

Custom development of Configuration Manager Reports will not be done as part of this project. The default out-of-the box Configuration Manager 2012 reports will be implemented.

Removal of any existing endpoint security products on desktops, laptops, and servers with the exception of:

o TrendMicro Office Scan version 10.5

4.5Version Release Strategy

The current version of the project is to do planning and designing for infrastructure for the MOFA production environment. Once the planning and designing version of the project has been completed and all documentation has been sign-off, Microsoft will carry on with the deployment of the solution into the production environment.

The deployment strategy will be included on the deployment guide that is part of the deliverable.

4.6Acceptance CriteriaMOFA requires the following deliverables, services and deployment to be completed.

Documentation should be delivered using MSF methodology

All design and deployment should be revised and approved by Technical Lead

The following applications and services provided

Project Phase

Service Deliverable

Name

Service Deliverable Descriptions

Acceptance Criteria

Envisioning

Scope and Vision A Vision and Scope document, which states the project goals and scope.

Document accurately reflects in-scope requirements gathered. The document will be between 15 to 25 pages

Envisioning

Project Plan Project plan will provide final delivery schedule for in scope deliverables.

Microsoft Project file providing detailed schedule and milestones of the project

Plan Functional Specification

Description of the technical functionalities in a document according to the agreed format defined in the MSF template

Document accurately reflects in-scope requirements gathered. The document will vary between 50 to 100 pages

Stabilization and Deployment

Deployment Guide

Description of the technical steps during the phases according to MSF deliverables

Document should be prepared according to Microsoft Solution Framework Standards which should


000MOFA0

Project Phase

Service Deliverable

Name


Acceptance Criteria

include the following1. Deployment Requirements

and Assumptions2. Technical Dependencies3. Technical Requirements

related to environment4. The document will be between

60 to 100 pagesStabilization and Deployment

SCCM Deployment

SCCM Deployment as per Design

Successfully deployment of the SCCM infrastructure as listed below on both LAN / Internet environment

1. CM 2012 Central, Primary and Secondary sites and distribution points as per design

2. Operation of all enabled features and reports

3. Creation of two base images (x32 bit and x64 bit) with office 2010

4. Deployment of SCCM 2012 agents on 100 desktops or servers

5. Removing Trend Micro AV and deployment of Endpoint protection in 100 desktops or servers

6. Deployment of Windows 7 and office 2010 image on 5 compatible Desktop / laptops through SCCM

7. Configuring desired configuration for standard client baseline


SCOM Deployment

SCOM Deployment as per Design

Successfully deployment of the SCOM infrastructure as listed below on both LAN / Internet environment

1. Deployment of 2 Management Server

2. Configuring Audit collection services

3. Deployment of management packs as per design

4. Deployment of SCOM 2012 agent on 25 clients covering all server roles


SQL Server Deployment

SQL Server Deployment as per Design

Successfully deployment of the SQL 2008 R2 Database cluster on the Internet environment

1. Deployment of 2 node windows 2008 R2 fail over cluster


000MOFA0

Project Phase

Service Deliverable

Name


Acceptance Criteria

2. Deployment of SQL 2008 R2 cluster

3. Deployment of SQL Reporting services

Table 2 - Acceptance criteria

4.7Operational Criteria Microsoft must provide System Center Configuration Manager 2012 and Operations

Manager 2012 infrastructure solution that all applications on virtualized environment.

All Applications must provide backup and restore recommendations

All Management packs mentioned below to be imported to SCOM

o Windows Server OS (2003/2008/2008 R2)

o DNS (Windows 2008/2008 R2)

o DHCP

o IIS

o Active Directory (Windows 2003 / 2008 / 2008 R2)

o Group Policy

o Cluster Service

o SQL 2008 / 2008 R2

o SCCM 2012

o Hyper-V

o TMG 2010

Windows 7 image should address all driver and applications requirements in the project scope with “error free” operation.


000MOFA0

5 Solution Design Strategies5.1Architectural Design Strategy

The figure above shows the architecture design strategy that will be used to define the Functional Specification. Information will be received from an environment assessment and also from the business in the form of business requirements. This input information will be used to define a Functional Specification which will be used as a basis for the technical design documentation.

Figure 1 - Architecture Design Strategy


000MOFA0

5.2Technical Design StrategyMicrosoft Consulting Services to design and deploy the following;

1. Isolated Environments: Microsoft will provide design and deployment services considering LAN and Internet Network with completely isolated infrastructure and requirements.

LAN Environment (1500 users with 6 sites)

Design and Deploy SCCM 2012 along with end point protection to replace the existing Trend Micro Antivirus

Design and Deploy SCOM 2012 with Audit Collection Services (ACS)

Internet Environment (900 users with one site)

Design and Deploy SCOM 2012 with Audit Collection Services (ACS)

Design and Deploy SCCM 2012 along with end point protection to replace the existing Trend Micro Antivirus

Design and Deploy Centralized SQL 2008 R2 Cluster to host multiple Databases

2. Consolidated Approach: Microsoft provide design and deployment considering business requirements with consolidated approach

3. Sizing: Design and deployment will address current and 3 years business, technical and operations goals.

4. Security: Microsoft will provide design and deployment with high security hardening requirements to minimize attack surface.

5.3Project Management StrategyIn the best possible world, all products could be delivered good, fast and cheap. The reality is that, if any two of those attributes are successfully achieved, the third cannot be satisfied. Project management requires that a balance be struck among resources/cost, delivery dates and features of any product. Any of those three attributes can be managed in order to

optimize, constrain or accept its outcome. MCS recommends the project management strategy diagrammed in the following figure.


Figure 2 - Project management trade off matrix

000MOFA0

A desired upper limit on the project’s budget constrains the resources that can be applied. This limited group of people is asked to deliver the desirable features by a deadline set in the future. Their goal is to work creatively to deliver as much value as possible, but to meet the time deadline. In order to do this, the project team and customers must accept that some features will not be in the final product. The goal of this strategy is to understand the customer’s desires and needs, and rank them from most important to least. With this strategy, even important features may be left out of a specific version of a product if the benefit delivered by releasing the product outweighs the opportunity cost lost to a feature’s absence. This strategy is known as “shipping is a feature.”

Using the matrix on above figure, other project management strategies can be devised, but they must adhere to the following rules:

One column must be checked in each row indicating how that attribute will be managed.

No column can be checked more than once, in order to avoid conflicting strategies.

5.4Project Organization StructureThis section describes the overall project organization structure, reporting relationships, and key project roles.

The project will be organized as depicted in the following diagram.

Figure 3 - Project Organization Chart


000MOFA0

5.5Project Roles and ResponsibilitiesThis section provides a brief description of key project roles and responsibilities.

5.5.1 Customer Project Roles and ResponsibilitiesRole Responsibilities Project Commitment

Customer Project Sponsor

▪ Makes key project decisions, assists in escalating unresolved issues to the Executive Steering Committee, and clears project roadblocks

Part Time

Customer Project Manager

▪ Primary point of contact for Microsoft team

▪ Responsible for managing and coordinating the overall project

▪ Responsible for resource allocation, risk management, project priorities, and communication to executive management

▪ Manages day-to-day activities of the project

▪ Coordinates the activities of the team to deliver deliverables according to the project schedule

Part Time

Technical Team Lead

▪ Primary technical point of contact for the team that is responsible for technical architecture and code deliverables

Part Time

Table 3 - Customer roles and responsibilities

5.5.2 Microsoft Project Roles and ResponsibilitiesRole Responsibilities Project Commitment

Microsoft Engagement Manager

▪ Responsible for deliverable quality and Customer’s overall satisfaction with Microsoft’s services

▪ Single point of contact for billing issues, personnel matters, contract extensions, and MCS project status

▪ Facilitate project governance activities and leading the Project Steering Committee

▪ Facilitate project governance activities and leading the Project Steering Committee, providing advice and guidance on:− Project direction and scope− Stakeholder communication issue

resolution and escalation

Part time

Microsoft Project ▪ Responsible for managing and Part timePage 22


000MOFA0

Role Responsibilities Project Commitment

Manager coordinating the overall Microsoft project

▪ Responsible for Microsoft resource allocation, risk management, project priorities, and communication to executive management

▪ Manages day-to-day activities of project

▪ Coordinates the activities of the team to deliver deliverables according to the project schedule

Microsoft Lead Architect

▪ Provide technical oversight▪ Verifies whether Microsoft

recommended practices are followed▪ Responsible for overall solution

deployment

Part time

Subject Matter Expert (SME)

▪ Provide Technical Planning, Build, Stabilizing and Deployment

▪ Deliver the solution according to Microsoft recommended practices.

▪ Provide Knowledge Transfer

Full time

Table 4 - Microsoft roles and responsibilities

6 Risk ManagementRisk is inherent to any type of consulting engagements and Microsoft Services is exposed to risks of different types and severities. For engagements classified as complex projects, risk management starts at deal management with a self-assessment done by the opportunity owner.

In the case of complex engagements project management team, reviews and manages impacts from risks along with the risk reserve. The risks connected to running a project are typically documented, reviewed, and managed by the Project Manager or Engagement Manager.

6.1Risk Management ProcessThe Risk Management process is split it into five distinct areas that are perpetually executed during the life of the project:

a. Identificationb. Analyzec. Pland. Tracke. Control


000MOFA0

RetiredRiskList

Plan3

Analyze2

Control5

Identify1

RiskAssessmentDocument

Track4

Topn

Risks

Figure 4 - Risk Management Process

6.1.1 IdentifyThe first step in the risk management process is to identify each risk. During this stage, the various components of the risk are recognized with respect to the conditions, consequences, source, and cost associated with each risk.

Risks are actively exposed through the following mechanism:

Risks identified during initial development of the Project Charter/SOW All un-vetted assumptions in the Charter/SOW or any other foundational document Risk Analyses workshop (s) conducted by the project team Risks identified by individual contributors and logged on the Project Risk Register Risks identified during team meetings Risks identified by any other stakeholders

6.1.2 AnalyzeThe second stage in the process is to analyze the risk in terms of its probability, impact, and exposure. Determining the probability of a risk involves figuring how likely the condition of that risk are likely to occur (for example, a 10% or 50% chance of probability). The impact of the risk requires measuring the severity of the loss that can be caused by the risk. For example, this might mean using a scale of 1 to 5 where 1 means the risk has little impact to an organization and 5 means the risk will cause very severe damage. Calculating the exposure of a risk means multiplying the probability of the impact. For example, sometimes a highly probable risk can have low impact and be safely ignored while at other times risks can have a high chance of happening and have a severe impact meaning it should be dealt with immediately.

6.1.3 PlanRisk action planning involves turning the information gathered from the previous steps into decisions and actions. This involves defining the mitigations (steps that can be taken before the risk occurs), triggers (indicators that identify when a condition will happen), and contingencies


000MOFA0

(the steps to take if an action occurs) for each risk. During this stage, it will be important to prioritize the mitigation and contingency plans for each risk.

Each identified risk is addressed in one of four methods:

a. Mitigate – Two part process:i. a Mitigation plan should be implemented to minimize the probability of

occurrenceii. a Contingency plan should be devised to minimize the impact if the risk

eventuatesb. Transfer – assign the work package containing the risk item to a third party (eg –

outsource work to a specialized vendor)c. Escalate – raise the issue to Executive Steering Committee for evaluation and

assignment to other teams within NFCU. NOTE: Escalation of a risk should be accompanied by a request or recommendation for action by the ESC. It should never be simply “handed over” to the ESC without a proposed solution from the project team.

d. Accept – the risk is deemed acceptable or, no viable transfer/mitigation plans can be effected (eg – fast tracked schedule items pose a certain degree of risk that cannot be fully mitigated and thus must be accepted).

6.2Project Risks

Risk Identification Consequence Action Owner

MOFA does not have detailed documentation regarding their infrastructure

Some of features may face performance issues for some sites

Consultant in planning and design phases will need more work to collect information.

Project Team

MOFA does not have detailed analysis of bandwidth between sites

Some of features may face performance issues for some sites

Consultant in planning and design phases will need more work to collect information

Project Team

LAN Network does not have internet access, there would be obstacles connecting the Software update services to download updates directly from

Software Update feature requires internet access. This would create an issue while downloading updates

Resolved Project Team


000MOFA0

Risk Identification Consequence Action Owner

Internet

The project should be delivered within the existing budget and timelines. No extra budget to move around

Project cannot exceed timeline. This would create CPE issue.

Project Plan deadlines should be followed as priority 1.

Project Team

MOFA has limited staff for support

Operations Manager and Configuration Manager features may not be used as expected.

MOFA does not have ITIL based operational assignments. This has to be resolved ASAP.

MOFA

MOFA Users have large local data in distributed locations. This would require more sophisticated analysis while configuring USMT settings of Windows 7 imaging

Windows 7 deployment may create dissatisfaction due to missing user data.

Collect and organize user data locations

Project Team

Microsoft consultant needs to handover the project to another resource due to training and vacation planned earlier

Microsoft consultant needs to leave on 10th of July. This would create a CPE issue. MOFA needs highly skilled consultant.

Microsoft DPRM needs to take action ASAP.

Microsoft

Table 5 - Project Risks


configuration manager and operations manager · web viewconfiguration manager and operations...

Documents