Alright folks, the Service Manager has just been released! its time to give it a shot and see what the ins and outs of the products.
I’ve summarized the installation steps for you so you can use this guide to start right away with your lab (this isn’t intended for production environments, more thorough planning should take place). I suggest that you take a quick look at the release notes for SCSM 2012 here
As for the installation, remember the good old days when you had to patch Server 2008 to get the latest System Center (R2, R3 stuff), but Server 2008 R2 worked out of the box just fine because it’s a lovely modern OS? well, hate to break the news for ya, but those days are gone; you better get your Server 2008 R2 SP1 Server running and START PATCHING! (actually 2 Servers) here is what you need:
1. Go get Hotfix 2600907 for Server 2008 R2 here (needs a restart)
2. Get the Authorization Manager hotfix here (included in Server 2008 R2 SP1)
3. Get the Microsoft Analysis Management Objects (X64) which is required by the
management console so it can work with SQL Server Analysis Services (SSAS)
4. Install Microsoft Report Viewer Redistributable Security Update KB971119 (no links?
yes! its in the Prerequisites folder of the SCSM Media, horray!)
5. Get .NET Framework 4 (for the Self Service Portal if you need it)
There are three (3) possible deployment topologies for the Service Manager 2012, the Single Computer Topology, the 2-Computer Topology, and 4-Computer Topology. Mmmm no, actually there are only two, yes you heard me, only TWO installation topologies. why do I say that? Well, because the Single Computer topology says that you need to get Hyper-V so you have one server on the physical host and another that you will virtualize.. Whaaaat? that’s a two computer topology! except that the Data Warehouse Server will reside on the other! wait, I didn’t tell you about the Data Warehouse Server and Data Management Server? Read on buddy, I’ll make it very very simple.
Service Manager is composed of two things (and their databases so that’s 4), the first thing is the Data Management Server and the other is the Data Warehouse Server, now these guys don’t really get a long, so you have to separate them, there is no way they can be on the same server (see, that’s why I told you to start patching two servers).
Now these guys have their databases, you can think of them as their wives, there is the Data Management Database and the Data Warehouse Database. it’s really flexible where you place the databases, whether the same server or a different one. Sooo the Single Computer Topology says that you install the (Management Server, Management Server Database, and Data Warehouse Server Database) on one computer and then install the Data Warehouse Server on the second, but why is that? I got no freakin idea (performance you say?), why would you separate the Data Warehouse Server from his wife the Data Warehouse Server Database? that is cruel. So place each two together and Boooom! this is the 2-Computer Topology! but what if you place each Server and Database on a different computer? YEP! it’s the 4-Computer Topology!
Simple. I’m doing the 2-Computer Topology.
Server 1 – Management Server and its Database
We need first to get the prerequisites ready, some of them are on the media, others are on the web. Install Server 2008 R2, join it to the domain, do the essential magical stuff (rename, network, update, remote desktop) and then:
- .Net Framework 3.5 SP1 (included in Server 2008 R2, its in the media if you are on Server 2008)
- ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2 <—clickable, go get it (included in Server 2008 R2)
- PowerShell (PS) 2.0 (included in R2)
- ReportViewer 2008 Redistributable with its security update (in the media!)
Installing: SQL Server
- Get SQL 2008 SP1 or SP2, SQL 2008 R2 or R2 SP1 (I got the latest, to be covered).
- Make sure you have Full-Text Search (FTS) marked
- Follow best practices for Service Accounts of your own (use domain accounts for extra security, I’m going to use local system or network system since I’m only testing).
- For the SQL Server collation, make sure you use a Case-Insensitive (CI) Database
- If you chose to use the default collation, you won’t be able to support multiple languages and Service Manager installation will display a warning (fine by me!)
- Proceed with installation (oh, don’t use an Instance name with $ in it, Service Manager wont install :-/ so leave it default)
Alright, fire up your SQL Installation, and the select those roles:
See how I got FTS? you do too, click next till you get
see? this means no other languages, and you get a warning by Service Manager, chose whatever collation you want but make sure its CI (Case Insensitive), AND the collation you chose should be the same for the warehouse database, they cant be different.
Installing: Service Manager
Once you got the SQL Server 2008 R2 SP1 installed, its time to start with the Service Manager 2012 Beta setup.
Type in your name, organization, accept EULA bla bla, until you get the Prerequisites Checker (which actually takes about 30 seconds to complete.. too long)
Type in the Management Group Name, and pay attention to what I have to say now, if you have Operations Manager in your environment and this name should UNIQUE and DIFFERENT FROM THE OPERATIONS MANAGER MANAGEMENT GROUP NAME.
As for the Management Group Administrators, I suggest you create a Security Global group and use it here, also you should create an Admin User account and place it in this group and in the local administrators group of the server. (beware of SQL database security issues, add it there if you face any)
The Service Account and Workflow Account should ordinary Domain Users accounts
aaaaand you’re done!