Things to Consider When Planning your Service Manager 2010 Deployment
Microsoft will likely be announcing the public availability of their long awaited System Center Service Manager 2010 “helpdesk” product at the Microsoft Management Conference (MMS) in Las Vegas this week. I have several chapters in my book “System Center Enterprise Suite Unleashed” on SCSM covering design, planning, implementation, customization, and support that provides a real world understanding of SCSM in the enterprise.
The next handful of blog posting will be a sneak peek into this new product out of Redmond!
The following are best practices in designing and planning your Service Manage 2010 rollout:
► Always create a design and planning document when deploying Service Manager, even if it is a simple one.
► Take future expansion and relevance of hardware into account when sizing servers for SvcMgr deployment.
► Keep the installation of SvcMgr components on a separate server or set of separate dedicated member servers that do not run any other separate applications.
► Use SQL Enterprise Edition when combining components on the same server.
► Use SQL Enterprise Edition when scaling up Service Manager.
► Allocate adequate space for the databases depending on the length of time needed to store work items and the number of computers in the organization.
► Size the disk subsystems to provide sufficient IOps to support the anticipated data flows.
► Use SANs where possible for the improved throughput.
► Connect Service Manager to Active Directory, Operations Manager, and Configuration Manager for maximum benefit.
This posting is 1 of a monthlong series of postings on the Microsoft System Center family of products. This is an excerpt from my book “System Center Enterprise Unleashed” with more postings on the System Center family of products up at http://www.networkworld.com/community/morimoto
