Configuration Manager and Operations Manager Deployment



-1143000000Configuration Manager and Operations Manager Deployment Prepared forMOFA7/7/2012Version 1.1Prepared byAydin DemirSenior ConsultantAydin.Demir@Revision and Signoff SheetChange RecordDateAuthorVersionChange reference03.07.2012Aydin Demir1.0Initial draft for review/discussion06.07.2012Aydin Demir1.1Final Draft after Architect ReviewReviewersNameVersion approvedPositionDateA N Hasan1.1Architect07.07.2012Table of Contents TOC \o "1-3" \h \z \t "Heading 9,9" 1Executive Summary PAGEREF _Toc329366307 \h 12Table of Reference PAGEREF _Toc329366308 \h 13Business Opportunity PAGEREF _Toc329366309 \h 23.1Operations Manager 2012 PAGEREF _Toc329366310 \h 23.2Configuration Manager 2012 PAGEREF _Toc329366311 \h 24Project Vision and Scope PAGEREF _Toc329366312 \h 34.1Vision Statement PAGEREF _Toc329366313 \h 34.2Benefits Analysis PAGEREF _Toc329366314 \h 34.2.1Operations Manager 2012 PAGEREF _Toc329366315 \h 34.2.2Configuration Manager 2012 PAGEREF _Toc329366316 \h 34.3Requirements PAGEREF _Toc329366317 \h 44.3.1Business Requirements PAGEREF _Toc329366318 \h 44.3.2User Requirements PAGEREF _Toc329366319 \h 54.3.3Operational Requirements PAGEREF _Toc329366320 \h 64.3.4Security Requirements PAGEREF _Toc329366321 \h 64.4Scope of Project PAGEREF _Toc329366322 \h 74.4.1Centralized Database with SQL 2008 R2 PAGEREF _Toc329366323 \h 74.4.2Operations Manager 2012 PAGEREF _Toc329366324 \h 84.4.3Configuration Manager 2012 PAGEREF _Toc329366325 \h 114.4.4Out of Scope PAGEREF _Toc329366326 \h 144.5Version Release Strategy PAGEREF _Toc329366327 \h 164.6Acceptance Criteria PAGEREF _Toc329366328 \h 164.7Operational Criteria PAGEREF _Toc329366329 \h 185Solution Design Strategies PAGEREF _Toc329366330 \h 195.1Architectural Design Strategy PAGEREF _Toc329366331 \h 195.2Technical Design Strategy PAGEREF _Toc329366332 \h 205.3Project Management Strategy PAGEREF _Toc329366333 \h 205.4Project Organization Structure PAGEREF _Toc329366334 \h 215.5Project Roles and Responsibilities PAGEREF _Toc329366335 \h 225.5.1Customer Project Roles and Responsibilities PAGEREF _Toc329366336 \h 225.5.2Microsoft Project Roles and Responsibilities PAGEREF _Toc329366337 \h 236Risk Management PAGEREF _Toc329366338 \h 236.1Risk Management Process PAGEREF _Toc329366339 \h 246.1.1Identify PAGEREF _Toc329366340 \h 246.1.2Analyze PAGEREF _Toc329366341 \h 256.1.3Plan PAGEREF _Toc329366342 \h 256.2Project Risks PAGEREF _Toc329366343 \h 25Executive 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. DOCPROPERTY Customer \* MERGEFORMAT 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 DOCPROPERTY Customer \* MERGEFORMAT 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 DOCPROPERTY Customer \* MERGEFORMAT MOFA will use to collectively build the solution.Table of ReferenceThe contents of this document are based on the following documents/references, emails communications available.SI. No.Name of Document/Document IDVersion, Date of Issue1MOFA - SCCMSCOM - SOW V2 20120612.docxV2.0, 12/06/2012Table SEQ Table \* ARABIC 1 - Table of referenceBusiness OpportunityMicrosoft Services Consulting will work with DOCPROPERTY Customer \* MERGEFORMAT 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.Operations Manager 2012By successfully implementing Operations Manager 2012, DOCPROPERTY Customer \* MERGEFORMAT 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 fasterProvide 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 productivityProvide a knowledge base of how previous issues were resolvedProvide architects and engineers with tools that allow them to better understand the current environment so that they can design better future solutionsProvide capacity planners with real –time system information so that they can better plan and model the environmentTake advantage of Microsoft management packs to provide expertise on what should be monitored in the environment and how to do soConfiguration 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. Project Vision and ScopeVision StatementMOFA 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.” Benefits AnalysisOperations Manager 2012By deploying a solution that is based on Operations Manager 2012 to manage IT services that are running on Microsoft products, DOCPROPERTY Customer \* MERGEFORMAT MOFA will gain the following benefits:Improve service levels and visibility with end-to-end service management of Microsoft servicesEnable Operations and IT Management teams to more easily identify and resolve issues affecting the health of distributed IT servicesAccelerate problem resolution through expert server and application knowledge of the Windows platformReduce IT management complexity by automating routine administrationConfiguration 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 RequirementsThe 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.Business Requirements4.3.1.1 Operations Manager 2012The solution must provide DOCPROPERTY Customer \* MERGEFORMAT 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 DOCPROPERTY Customer \* MERGEFORMAT 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;MonitoringWindows ServersSupported Linux and UNIX serversCisco SwitchesF5 load balancersJuniper FirewallsManagement PacksWindows Server OS (2003/2008/2008 R2)Exchange 2010SharePoint 2007 / 2010DHCPHyper-V DNS (Windows 2008/2008 R2)IIS Active Directory (Windows 2003 / 2008 / 2008 R2)Group PolicyCluster ServiceSQL 2003 / 2008 / 2008 R2SCCM 2012TMG 2010Additional ServicesPerformance MonitoringAudit Collection from Windows Security LogsOperations Manager 2012 server roles must be deployed on existing virtualization platform. 4.3.1.1 Configuration Manager 2012MOFA has the following requirementsComputer Discovery and adding new computers to Configuration Manager hierarchy should be less than one dayInventory should be collected once per weekDesktops 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 interferenceCosts (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. User RequirementsMOFA users have the following requirements;Licensed applications should be available to deploy at any time.Mandatory patch deployments should not affect daily operationApplications deployment should be done out of working hoursUsers 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 inputUsers should be able to install applications using portal provided without any approval.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 2012The 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 rolesBacking up Operations Manager componentsManaging notifications and subscriptionsManaging security configurationMaintaining database performance Managing management packs4.3.1.1 Configuration Manager 2012The 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 EnvironmentMinimize the time to build or rebuild a workstationEnsure that common tools are used so that operations and support skills are easy to sourceProvide increased agility by having a more flexible platform to deploy new applicationsAbility to apply non-Microsoft applications updates such as Acrobat ReaderMinimize the time taken to update or patch applicationsMinimize the time taken to deploy applicationsSecurity RequirementsMOFA requires that the following security practices to be implemented;Agent and server communication should be done with encryption between client and serversAll application components require service accounts will use domain based accounts with complex passwordsSolution should be implemented in isolated network where all access is restricted. All administration should be restricted to trained administrators.All servers and services should be hardened. Scope of ProjectMicrosoft will provide the following services:Centralized Database with SQL 2008 R2We 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 PhaseDuring 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 servicesDesign the SQL server platform monitoring and reporting by SCOM 2012 as available within this platformConduct a technical design workshop to discuss and evaluate the detailed design solution architecturePlanning High availability to make sure all the components are available if one server goes downStorage sizingArchitecture 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 StabilizingIn 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 clusterDeploy SQL 2008 R2 on the failover clusterDeploy SQL Reporting ServiceCompleted production deployment of Centralized SQL 2008 R2 ClusterOperations Manager 2012The 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 PlanningCreate logical and Physical architecture including:Defining management group structureDefine management packsDefine server roles and targetingDefine client roles for targetingAvailability and recovery strategyTraffic and load estimationCreate a detailed design including:Hardware and software specificationHardware capacity and high availability designServer placementManagement sever design and configurationOperations database design and configurationReporting and data warehouse design and configurationAgent installation and configuration designActive Directory integration designNotifications design and configurationAlert settings and configurationAudi Collection Services Create a security design including:IIS server securitySQL server securityManagement point securityRole based security / ViewsService accountsRun as accountsNetwork port and firewall configurationPlanning Network monitoring for the below network devices however they should be listed in the supported devise list as mentioned in the below noteCisco SwitchesF5 load balancersJuniper FirewallsPlanning heterogeneous monitoring (Linux and Unix) only the version approved by SCOM 2012 as listed in this link: Deployment and StabilizingIn 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 EnvironmentOperations Manager Infrastructure deployment with 2 Management ServersReporting InfrastructurePilot 25 Agent Deployment covering all the server roles including networking devices supported by SCOM 2012Enable Audit collection serviceDeployment of following MPsWindows Server OS (2003/2008/2008 R2)Exchange 2010SharePoint 2007 / 2010DHCPHyper-V DNS (Windows 2008/2008 R2)IIS Active Directory (Windows 2003 / 2008 / 2008 R2)Group PolicyCluster ServiceSQL 2003 / 2008 / 2008 R2SCCM 2012TMG 2010Basic Management Pack TuningInternet EnvironmentOperations Manager Infrastructure deployment with 2 Management ServersReporting InfrastructurePilot 25 Agent Deployment covering all server roles including networking devices supported by SCOM 2012Enable Audit collection serviceDeployment of following MPsWindows Server OS (2003/2008/2008 R2)DNS (Windows 2008/2008 R2)DHCPIIS Active Directory (Windows 2003 / 2008 / 2008 R2)Group PolicyCluster ServiceSQL 2008 / 2008 R2SCCM 2012Hyper-VTMG 2010Basic Management Pack TuningConfiguration Manager 2012Microsoft 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 PlanningThe 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: Site designBoundary designClient settings and schedulesBasic software updates managementRemote Control toolsDistribution Point design for software distributionClient Discovery and installation methods and strategySoftware distribution strategy like Windows 7 OS and Office 2010Remote controlEndpoint ProtectionPlanning for Desired Configuration Management for standard client baselineSoftware 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 IntelligencePlanning for Power Management FeaturesDetermine 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 team4.4.3.2 Deployment and StabilizingIn 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 EnvironmentDeploy Configuration Manager 2012 Infrastructure, including a central administration site, primary sites and secondary sites where appropriate but maximum 5 sites.Enable and provide guidance on the SQL Reporting Services (SRRS) from the Configuration Manager consoleSystem Center Configuration Manager 2012 Endpoint Protection (EP) InfrastructureConfigure 5 Distribution Points where appropriateSCCM 2012 Servers deployment with the following features:Software update managementClient DiscoveryInventorySoftware distributionRemote Control toolsConfiguring Operating System Deployment feature for Windows 7 Deployment Creating two base images with hardware driversX32 bit Windows 7 image along with Office 2010 SP1X64 bit Windows 7 image along with Office 2010 SP1Testing Driver UpdatesDeployment 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 addressRemoving 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 addressDeployment of Windows 7 and Office 2010 image on 5 compatible Desktops or laptopsConfiguring Desired Configuration Management for standard client baselinePerform post-deployment configuration actions and validate functionality.Internet EnvironmentDeployment one Primary siteSCCM 2012 Servers deployment with the following features:Software update managementClient DiscoveryInventorySoftware distributionRemote Control toolsSystem Center Configuration Manager 2012 Endpoint Protection (EP) InfrastructureConfiguring Operating System Deployment feature for Windows 7 Deployment Configuring the environmentCreating two base images with hardware driversX32 bit Windows 7 image along with Office 2010 SP1X64 bit Windows 7 image along with Office 2010 SP1Testing Driver UpdatesConfiguring Desired Configuration Management for standard client baselineDeployment 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 nameRemoving 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 addressDeployment of Windows 7 and Office 2010 image on 5 compatible Desktops or laptopsPerform post-deployment configuration actions and validate functionality.Project Completion and SignoffOut of ScopeAny 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 UtilizationPlanning and Designing of an Enterprise CA / PKI InfrastructureThe 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 sectionInternet Based Client ManagementDevice ManagementFixing unhealthy clients if the issues persist with the operating systemThird-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 systemsCustom development of System Center Configuration Manager reports. The default out-of-the box System Center Configuration Manager reports will be implementedIntegration between System Center Configuration Manager and any third-party software.NAP Integration and DCM for ServersApplication Compatibility ActivitiesAny third party applications or devices configuration Monitoring of solution using Microsoft Systems Centre Operations Manager or 3rd party monitoring tools Hardware/Operating System deploymentMonitoring 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 sectionAgent 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 IssuesResolving Hardware Issues of the existing environment Configuration of the SAN environmentProducts Training other than on job knowledge transfer during entire proj ect lifecycleMicrosoft 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.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:TrendMicro Office Scan version 10.5Version Release StrategyThe 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. Acceptance CriteriaMOFA requires the following deliverables, services and deployment to be completed.Documentation should be delivered using MSF methodologyAll design and deployment should be revised and approved by Technical LeadThe following applications and services providedProject PhaseService Deliverable NameService Deliverable DescriptionsAcceptance CriteriaEnvisioningScope and VisionA 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 pagesEnvisioningProject PlanProject plan will provide final delivery schedule for in scope deliverables.Microsoft Project file providing detailed schedule and milestones of the projectPlanFunctional SpecificationDescription of the technical functionalities in a document according to the agreed format defined in the MSF templateDocument accurately reflects in-scope requirements gathered. The document will vary between 50 to 100 pagesStabilization and DeploymentDeployment GuideDescription of the technical steps during the phases according to MSF deliverablesDocument should be prepared according to Microsoft Solution Framework Standards which should include the followingDeployment Requirements and AssumptionsTechnical DependenciesTechnical Requirements related to environmentThe document will be between 60 to 100 pagesStabilization and DeploymentSCCM DeploymentSCCM Deployment as per DesignSuccessfully deployment of the SCCM infrastructure as listed below on both LAN / Internet environmentCM 2012 Central, Primary and Secondary sites and distribution points as per designOperation of all enabled features and reportsCreation of two base images (x32 bit and x64 bit) with office 2010Deployment of SCCM 2012 agents on 100 desktops or serversRemoving Trend Micro AV and deployment of Endpoint protection in 100 desktops or serversDeployment of Windows 7 and office 2010 image on 5 compatible Desktop / laptops through SCCMConfiguring desired configuration for standard client baselineStabilization and DeploymentSCOM DeploymentSCOM Deployment as per DesignSuccessfully deployment of the SCOM infrastructure as listed below on both LAN / Internet environmentDeployment of 2 Management ServerConfiguring Audit collection servicesDeployment of management packs as per designDeployment of SCOM 2012 agent on 25 clients covering all server rolesStabilization and DeploymentSQL Server DeploymentSQL Server Deployment as per DesignSuccessfully deployment of the SQL 2008 R2 Database cluster on the Internet environmentDeployment of 2 node windows 2008 R2 fail over clusterDeployment of SQL 2008 R2 clusterDeployment of SQL Reporting services Table SEQ Table \* ARABIC 2 - Acceptance criteriaOperational CriteriaMicrosoft 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 recommendationsAll Management packs mentioned below to be imported to SCOMWindows Server OS (2003/2008/2008 R2)DNS (Windows 2008/2008 R2)DHCPIIS Active Directory (Windows 2003 / 2008 / 2008 R2)Group PolicyCluster ServiceSQL 2008 / 2008 R2SCCM 2012Hyper-VTMG 2010Windows 7 image should address all driver and applications requirements in the project scope with “error free” operation. Solution Design StrategiesArchitectural Design StrategyThe 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 SEQ Figure \* ARABIC 1 - Architecture Design StrategyTechnical Design StrategyMicrosoft Consulting Services to design and deploy the following;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 AntivirusDesign 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 AntivirusDesign and Deploy Centralized SQL 2008 R2 Cluster to host multiple DatabasesConsolidated Approach: Microsoft provide design and deployment considering business requirements with consolidated approachSizing: Design and deployment will address current and 3 years business, technical and operations goals. Security: Microsoft will provide design and deployment with high security hardening requirements to minimize attack surface. Project 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. 12052301991995Figure SEQ Figure \* ARABIC 2 - Project management trade off matrixFigure SEQ Figure \* ARABIC 2 - Project management trade off matrix12052302159000A 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.Project 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 SEQ Figure \* ARABIC 3 - Project Organization ChartProject Roles and ResponsibilitiesThis section provides a brief description of key project roles and responsibilities.Customer Project Roles and ResponsibilitiesRoleResponsibilitiesProject CommitmentCustomer Project SponsorMakes key project decisions, assists in escalating unresolved issues to the Executive Steering Committee, and clears project roadblocks Part TimeCustomer Project ManagerPrimary point of contact for Microsoft teamResponsible 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 projectCoordinates the activities of the team to deliver deliverables according to the project schedulePart TimeTechnical Team Lead Primary technical point of contact for the team that is responsible for technical architecture and code deliverablesPart TimeTable SEQ Table \* ARABIC 3 - Customer roles and responsibilitiesMicrosoft Project Roles and ResponsibilitiesRoleResponsibilitiesProject CommitmentMicrosoft Engagement ManagerResponsible for deliverable quality and Customer’s overall satisfaction with Microsoft’s servicesSingle point of contact for billing issues, personnel matters, contract extensions, and MCS project statusFacilitate project governance activities and leading the Project Steering CommitteeFacilitate project governance activities and leading the Project Steering Committee, providing advice and guidance on:Project direction and scopeStakeholder communication issue resolution and escalationPart timeMicrosoft Project Manager Responsible for managing and coordinating the overall Microsoft projectResponsible for Microsoft resource allocation, risk management, project priorities, and communication to executive managementManages day-to-day activities of projectCoordinates the activities of the team to deliver deliverables according to the project schedulePart timeMicrosoft Lead ArchitectProvide technical oversightVerifies whether Microsoft recommended practices are followedResponsible for overall solution deploymentPart timeSubject Matter Expert (SME)Provide Technical Planning, Build, Stabilizing and DeploymentDeliver the solution according to Microsoft recommended practices.Provide Knowledge TransferFull timeTable SEQ Table \* ARABIC 4 - Microsoft roles and responsibilitiesRisk 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.Risk Management ProcessThe Risk Management process is split it into five distinct areas that are perpetually executed during the life of the project:IdentificationAnalyzePlanTrackControl Figure SEQ Figure \* ARABIC 4 - Risk Management ProcessIdentifyThe 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/SOWAll un-vetted assumptions in the Charter/SOW or any other foundational documentRisk Analyses workshop (s) conducted by the project teamRisks identified by individual contributors and logged on the Project Risk RegisterRisks identified during team meetingsRisks identified by any other stakeholdersAnalyzeThe 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.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 (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:Mitigate – Two part process:a Mitigation plan should be implemented to minimize the probability of occurrencea Contingency plan should be devised to minimize the impact if the risk eventuatesTransfer – assign the work package containing the risk item to a third party (eg –outsource work to a specialized vendor)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.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).Project RisksRisk IdentificationConsequenceActionOwnerMOFA does not have detailed documentation regarding their infrastructureSome of features may face performance issues for some sitesConsultant in planning and design phases will need more work to collect information.Project TeamMOFA does not have detailed analysis of bandwidth between sitesSome of features may face performance issues for some sitesConsultant in planning and design phases will need more work to collect informationProject TeamLAN Network does not have internet access, there would be obstacles connecting the Software update services to download updates directly from InternetSoftware Update feature requires internet access. This would create an issue while downloading updatesResolvedProject TeamThe project should be delivered within the existing budget and timelines. No extra budget to move aroundProject cannot exceed timeline. This would create CPE issue.Project Plan deadlines should be followed as priority 1.Project TeamMOFA has limited staff for supportOperations 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.MOFAMOFA Users have large local data in distributed locations. This would require more sophisticated analysis while configuring USMT settings of Windows 7 imagingWindows 7 deployment may create dissatisfaction due to missing user data.Collect and organize user data locations Project TeamMicrosoft consultant needs to handover the project to another resource due to training and vacation planned earlierMicrosoft 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. MicrosoftTable SEQ Table \* ARABIC 5 - Project Risks ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download