You are browsing the archive for 2009 August.

System Center Virtual Machine Manager: Hosts having 0kb free memory

5:24 pm in Uncategorized by mikeresseler

Hey All,

One of the big issues with SCVMM 2008 for me was that the memory available on the hosts is not correct.  If you are running quite a large environment with a lot of virtual machines, it is difficult to know how many you have left.  You can of course start calculating it manually but… ;-)

So here’s a screenshot of the problem

image

As you can see, all my hosts are giving zero kb free of memory.  That’s not exactly correct

Here’s how to solve this one:

On each host that has this problem, open the registry and go to the following key:

HKLM\SYSTEM\CurrentControlSet\Services\PerfOS\Parameters

If you see the key “Disable Performance Counters” then change it to 0.

Now you need to restart the WMI service on the host.  Please pay attention because it will restart other services too and you don’t want to do this during production hours…

image

After that the services are restarted, you can refresh your configuration in SCVMM and then you get the correct figures

image

 

Cheers,

Mike

System Center Virtual Machine Manager: R2 has RTM-ed

6:55 pm in Uncategorized by mikeresseler

Hey All,

Just got an email from the beta-progam:

System Center Virtual Machine Manager 2008 R2 has released to manufacturing (RTM’d) and will be generally available (GA) via volume licensing is October 1.

A 180-day evaluation version is now available on the Microsoft Download site. You can access it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=292de23c-845c-4d08-8d65-b4b8cbc8397b&displaylang=en. We encourage everyone to continue to explore the new System Center Virtual Machine Manager 2008 R2 and its new features such as quick storage migration, live migration, and many others. We even offer support for vSphere 4.

Finally, to learn more on the new features and capabilities of VMM2008 R2, please try to attend our upcoming TechNet session ‘Technical Overview of System Center Virtual Machine Manager 2008 R2’. Presented by our Technical Product Manager Kenon Owens, it will be chocked full of new and cool VMM 2008 R2 items. Go here: http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032423216&EventCategory=4&culture=en-US&CountryCode=US to register for this Wednesday, September 09, 2009 (10:00 AM Pacific) event.

Thanks! The SCVMM Team.

Cheers,

Mike

System Center Data Protection Manager 2007: New course and Exam

9:26 am in Uncategorized by mikeresseler

Hey All,

Just to let you know, now there is a new course for DPM available from Microsoft Learning:

Course 50213A – Implementing Data Protection Manager 2007

http://www.microsoft.com/learning/en/us/course.aspx?ID=50213A

There is also now an exam on DPM

Exam 70-658: TS: System Center Data Protection Manager 2007, Configuring

http://www.microsoft.com/learning/en/us/exam.aspx?ID=70-658

More information can also be found on All Backed Up: http://blogs.technet.com/jbuff/archive/2009/08/17/new-dpm-courseware-and-exam-now-available.aspx

Cheers,

Mike

System Center Data Protection Manager 2007: Installation Part III: Patching, patching and patching

2:24 pm in Uncategorized by mikeresseler

Allright, here is part 3 of the installation of System Center Data Protection Manager.  This is the part where we are going to install a lot of hotfix rollups and hotfixes.

To have a good DPM installation, these hotfixes are needed or otherwise, you will have a lot of problems.  So here goes and here is the list of necessary hotfixes:

 

  • Description of the hotfix rollup package for System Center Data Protection Manager 2007: February
  • Description of the hotfix rollup package for System Center Data Protection Manager 2007: April
  • Description of the hotfix rollup package for System Center Data Protection Manager 2007: June
  • An Update is available for Windows Server 2008-based computers to address issues with backing up and restoring Hyper-V Virtual Machines
  • A replica may be listed as inconsistent after you install System Center Data Protection Manager 2007 Service Pack 1 on a computer that is running an x64-based version of Windows Server 2003
  • Availability of a Volume Shadow Copy Service (VSS) update rollup package for Windows Server 2003 to resolve some VSS snapshot issues

 

Now this looks like a lot of updates / hotfixes to install, but luckily, not all are necessary.  Because the Hotfix rollup package of June contains the previous ones (April and February) and also KB 9615012

So that leaves us with KB 970867, KB 959962 and KB 940349

KB 940349 is needed if your DPM server is running win2k03 (not in my case) but is also needed on EVERY windows 2003 server that will be protected by DPM.  Also note that this KB is best installed BEFORE you push an agent to that server.

KB 959962 is necessary when you want to protect virtual machines.  This update need to be installed on the Host Hyper-V systems and afterwards, you need to upgrade all the integration services on the virtual machines.

And the Hotfix rollup (KB 970867) will need to be installed on the DPM server.

Here’s how:

First, run the x64_DataProtectionManager2007-KB970867 (or the x86 variant)

image

Again, you get the same notifications as you received with the SP1 update.  Please also note that you will need to restart your DPM server if you didn’t installed the rollups before (As it is in my case) or when the DPM Console or Management Shell is open.

image

The license agreement

image

The installation

image

Again the question for the Microsoft Update (I really start to wonder here ;-))

image

And in the end he asks me to open the DPM console, and apparently I didn’t need to reboot after all.

Second part of the installation is the  SQLPrep package, unless you are running the dedicated instance on the DPM server as I do, so I don’t need to run this one.

Finally, you will need to run the Management Shell update on all computers where you have the Management Shell installed.

When that is all done, you need to start the DPM Management console and update the agents

image

Press the Update Available link for each agent.

image

Press Yes to continue.  The system tells you that you will need to run a consistency check afterwards.

image

Press the Update Agents button.

image

Now you need to fill in your credentials.  Make sure that you select the Manually restart the selected servers later because it is NOT necessary to restart the servers afterwards.

image

The system is upgrading the agent.

image

Finished.

That’s it.  In the next posts we will be giving a further demonstration on how to configure DPM.

Till then,

Cheers,

Mike

 

 

 

System Center Data Protection Manager 2007: Installation Part II: The program and SP1

10:03 am in Uncategorized by mikeresseler

Hey All, here is part two of the installation manual for SCDPM.  In the previous part, we have prepared our environment and installed the prerequisites.  Now it is time to install the software itself and this part exists out of two steps:

Step 1: Installation of SCDPM RTM

After you start the installation, this is the first screen you get:

image

Choose Install Data Protection Manager.  Please note that this will automatically install the DPM Management Shell

image

As always, accept the License Terms

image

The Welcome screen, press next to continue

image

The installation wizard will now run a prerequisite check to verify if everything is ok.

image

Now the product registration

image

In this window, you need to select the SQL instance you want to use or create a new SQL installation which will be a dedicated one.  Note that DPM is only supported on a SQL 2005 environment.  In fact, you will not get past this screen if you try to install it on a SQL 2008 environment because the installer checks it.  In my case, I will go for the dedicated SQL installation which is the best solution in my opinion.  (After all, if your SQL server dies, you want to be able to restore it.  How are you going to start with it if you don’t have the DPM SQL anymore :-)

image

If you have chosen for the local dedicated installation, you need to choose a strong password for 2 local restricted accounts.  Make sure it is a strong one as these accounts their passwords don’t expire.  The accounts are:

  • MICROSOFT$DPM$Acct: This account runs the SQL Server service and the SQL Server Agent service
  • DPMR$<nameserver>: This account securely generates reports

Then press Next to continue

image

Here you can choose whether you want to use Microsoft Update or not.  Depending on the policies of your company you can choose to put this on or off.

image

Choose whether you want to make use of the Customer Experience Improvement Program

image

Finally you get the summary and we are ready for the installation.

image

This is a screen during the installation.  Notice that in my case the SQL Server installation is busy.

image

And finally, it is finished.  You get a link to get the latest updates for the product, but since we are going to install immediately Service Pack 1, I didn’t bother to visit the link :-)

Last but not least, you get this notification

image

I’ve tried to start the installation of SP1 without restarting but that doesn’t work :-)

Step 2: Installation of Service Pack 1

image

The first thing the installer did before starting with the installation was the installation of the Visual C++ 2008 Redistributable Setup

image

Of course you need to accept the license agreement.

image

This installation took a matter of seconds.

image

And now the upgrade of SP1 starts.  The first thing it does is inform you of possible issues that can arise during the upgrade:

  • Any jobs that are in progress or that are scheduled during the install will fail
  • The installation will backup the DPM database
  • The process can take a large amount of time if you protect a large or multiple large sharepoint farms.

These warnings are no problem for my installation as I don’t have any sharepoint farms or jobs for the moment since I am upgrading from a clean installation.

image

Again you need to accept the License Terms, and in the top bar you can see that this service pack is also known as KB 959605

image

No further configuration here, since it is an upgrade and the installation is busy

image

Again the question about the Microsoft Update (If you choose yes, you would get an additional screen for the update settings… but as I said, I prefer that this is arranged on organization level)

image

And the finish, notifying that you need to restart.

image

I’ve tried to start DPM without restarting but then you get this error:

image

After restarting, I was able to get into the DPM console

image

In the next part, I will discuss the various rollups and hotfixes that are necessary to install.

Cheers,

Mike

System Center Data Protection Manager 2007: Installation Part I: Prerequisites

9:02 am in Uncategorized by mikeresseler

Hey All,

In the next 3 posts, an installation guide for System Center Data Protection Manager 2007.  Let’s start with explaining the environment I’ve used and the prerequisites.

First, let’s look at the prerequisites as they are provided by Microsoft. (http://technet.microsoft.com/en-us/library/bb808832.aspx)

First, the security requirements

1) Security Requirements

To install DPM you must be a local admin and logon to the computer where you want to install DPM.  OK, this can be arranged :-)

After the installation of DPM, you need to have a domain user with administrator access to use the DPM Administrator Console.  Basically, this means that when you need to be able to use the administrator console, you need to be a local administrator on the DPM server.

2) Network Requirements

According to Microsoft, you need to have a windows server 2003 or windows server 2008 active directory domain.  My testenvironment is a native windows server 2008 domain so no problems there.  You also need to have persistent connectivity with the servers and desktop computers it protects and if you are protecting data across a WAN, then you need to have a minimum network bandwidth of 512kbps.  So far so good

3) Hardware Requirements

Disks:  You should have a disk that contains the storage pool and one that is dedicated to system files, DPM installation files, prerequisite software and database files.  Basically, this means that you need an OS and program files just as any other server (you can divide it into multiple volumes) but the storage dedicated for the backups can’t be the same as above.  When DPM takes the storage, it allocates it and it is not usable for something else.

CPU: Minimum 1Ghz, Recommended 2.33 Ghz

Memory: Minimum 2 GB RAM, Recommended 4 GB Ram

Pagefile: 0.2 percent the size of all recovery point volumes combined, in addition to the recommended size (1.5 times the Memory)

Disk Space:

- Minimum: Program Files: 410 MB, Database: 900 MB, System Drive: 2650 MB

- Recommended: 2 till 3 GB of free space on the program files volume

Disk Space for storage pool: 1,5 Times the size of the protected data, recommended = 2 – 3 times the size of the protected data

LUNS: Maximum of 17 TB for GPT dynamic disks, 2 TB for MBR disks

32-bit servers: 150 data sources

64-bit servers: 300 data sources

Since this will be a test environment, there is no way I’m going to follow the complete requirements for DPM. :-)

4) Operating System Prerequisites

32-bit or 64-bit servers.  No ia64 bit is supported

The DPM server cannot be a management server for SCOM

The DPM server cannot be an application server or an DC server.

There is a VSS limitation on 32-bit servers.  It can’t outgrow 10 TB of protected data.  Preferred is 4 TB on a 32-bit server.

OS: Windows Server 2008 Standard and Enterprise Edition or Windows Server 2003 (R2) SP2 or later or Windows server 2003 Advanced server or Windows Server 2003 Storage server.

The management shell can also be run on windows XP SP2, Vista and Windows Server 2003 SP2 or later.

 

My Environment

I will run the server on a Hyper-V platform (Not yet R2) and I’ve created a virtual machine with the following specifications

CPU: 2 * 3.60 GHz Xeon

Memory: 2048 MB

Storage: C:\ 40 GB  (OS and application) D:\ 60 GB (Play storage for backup)

OS: Windows Server 2008 x64 SP2, Fully patched

Software Prerequisites

Before I started with the installation, I’ve installed following things first:

- IIS 7 with the following options on:

  • Common HTTP Features
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
    • HTTP Redirection
  • Application Development
    • ASP.NET
    • .NET Extensibility
    • ISAPI Extensions
    • ISAPI Filters
    • Server Side Includes
  • Health and Diagnostics
    • HTTP Logging
    • Request Monitor
  • Security
    • Windows Authentication
    • Request Filtering
  • Performance
    • Static Content Compression
  • Management Tools
    • IIS Management Console (not really a prerequisite but handy ;-))
    • IIS 6 Management Compatibility
      • IIS 6 Metabase Compatibility
      • IIS 6 WMI Compatibility
      • IIS 6 Scripting Tools
      • IIS 6 Management Console

 

- SIS (Single Instance Store)

To enable this, open a command prompt with administrator privileges and run the following command:

start /wait ocsetup.exe SIS-Limited /Quiet /norestart

image

After this is finished, restart the server.  To check if the SIS is enabled, open regedit and check the existence of the following key:

HKEY_LOCAL_Machine\SYSTEM\CurrentControlSet\Services\SIS

image

That’s it

In the next part, the installation of SCDPM 2007

Till then,

Cheers,

Mike

System Center Service Manager: Questions Answered

7:43 am in Uncategorized by mikeresseler

Hey All,

As said in my previous posts, I had a few questions concerning the product (probably more to come but…) so I asked them at the Microsoft Forum.  I also promised to let you know the results so here they are:

 

Q1: No R2 Components Allowed

As stated in the documentation, you can’t install no Operations Manager R2 components on the server(s) running the Service Manager Components.  This is the answer I’ve got

 

Quote from Anders Bengtsson

With the current version it is not supported to install any operations manager 2007 SP1 or R2 components on a service manager server, doing that might result in collisions as both the products are built on the same platform. This will be fixed before RTM.

Unquote

Fair answer, let’s hope they fix this indeed before RTM

 

Q2: I’ve noticed that you had to fill in a name for the management group, and that I had to do it twice (once during the DataWarehouse installation and once during the Service Manager installation).  I’ve installed it with entering two times the same name and this seemed to be the correct decision.  I’ve asked the support team what the meaning is of these management groups and if my decision was the right one.  Here is the answer, again from Anders Bengtsson

Hi,
With the current installation wizard you have to input the name twice, that might change before RTM. If you look under the hood it is two seperate installations of the R2 platform, that is why you have to input two management group names. There are more info about what a management group is at http://technet.microsoft.com/en-us/library/cc540367.aspx . In operations manger a management group name is the name of the logical installation, most often based on responsibility or geography, for example EMEA or "Exchange Team".

 

Cheers,

Mike

System Center Service Manager: Installation Part III: The Service Manager Management server, CMDB and a console

6:50 pm in Uncategorized by mikeresseler

Hey All, this is part 3 of the installation of System Center Service Manager Beta 1.  This time I’m going to install the Service Manager Management server, the CMDB and a console.  Please note that you can’t install this on the same computer as the Data Warehouse because according to Microsoft, this will work but the results will be unpredictable.

image

After running setup.exe, I got the start screen again.  This time I have chosen for Install Service Manager management server. 

image

Again I have the Product registration page.  I’ve changed username, company and accepted the license agreement.  Again, no key is needed for the time being.

 image

Choose the location where you want to install the program.

image

The prerequisite wizard has run, and again I got a warning.

image

In the SCSMSetupWizard log (in my case found under the directory where the installation media was extracted) I notice (again) that I don’t have enough memory.  Still I continue (It is a virtual after all, I can add more memory if necessary)

image

On this page, I needed to tell the program where the SQL server was located.  Since this was the same as where my Data Warehouse was located, I choose that one and again he listed me the only possible instance.

I wanted to create a  new database and choose that one.  The setup program filled in the rest for me.

image

Here I need to point to the server which contains the Data Warehouse.  This is optional if you have installed a data warehouse.  Otherwise, this is not necessary to fill in.

image

Again I need to tell the name of the management group which I can’t change afterwards, so I decided to take the same name for the management group as I did for the Datawarehouse.  I’m not sure if that is the good decision so I’m gonna post a question on the Microsoft forums and let you know what their answer is.

image

The account for Service Manager, which is in my case the SM_Acct account.

image

Finally the installation summary.

image

image

And job done.  Again, this took less then 10 minutes to install.

image

To check if everything works, I started the console on the server.

image

I get this window, where I filled in the servername of the Service manager management server.

image

And yes, it worked.  The first view on Service Manager 2010 beta 1.

To check for more, find the logs that I talked about in the previous post.

Next posts will be the first configuration.

Cheers,

Mike

System Center Service Manager: Installation Part II: The Datawarehouse

6:18 pm in Uncategorized by mikeresseler

Hey All, this is part two of the installation post of System Center Service Manager Beta 1.  In this part, we will install the Service Manager Data Warehouse.

I started the installation with the Setup.exe (of course ;-))

 image

I choose Install Service Manager Data Warehouse

image

Now he is asking for some data. The traditional name, organization and key.  Since this is a beta, I don’t need a key yet.  I’ve checked the License acceptance box and continued.

 image

Here I choose the installation location.

image

Now the prerequisite checker has run and he has given me warnings.

 

image

In the SCSMSetupWizard.log (in my case found under the directory where the installation media was extracted) I can read that he warns me that I don’t have enough memory (Still I’m going to try with the 2 GB ;-))

 

image

In this screen, I need to give the instance for the Databases.  Since he only shows the possible instances, this is an easy one :-)

 image

On the next page, I need to choose the Data Warehouse Management group name.  I left it as default, but be aware that you can’t change this name afterwards.

image

And finally, on that same screen, I need to choose the admin(s) for that management group.  I choose for the created admin group, SM_Admins.

image

For the Data Warehouse account, I chose the user we created in the 1st post named sm_acct.  The great thing here is that you have a button to test the credentials to see if your account is ok.

image

Finally the summary and of we go.

image

The installation is running

image

After less then 10 minutes the installation was finished.

For more information about the installation, or to troubleshoot a failed installation, check the log @ \users\<user name>\AppData\Local\SCSM\Setup or at the location where the installation files are located.

And finally, to validate if everything is ok, check if the following databases are created: DWSMDB, SCDM and SCDW

Up to the next part of the installation

Cheers,

Mike

System Center Service Manager: Installation Part 1: The prerequisites

6:10 pm in Uncategorized by mikeresseler

Hey All,

In the next 3 posts I will give a walkthrough how to install System Center Service Manager Beta 1.  Before I start with the installation, I would like to tell what kind of environment I’ve used to test the Beta and the prerequisites.

To be able to test the product, you need two servers. One for the datawarehouse and one for the management server.  I’ve created two virtual servers in my testdomain names VD-FCSD-SCSM01 and VD-FCSD-SCSM02.

VD-FCSD-SCSM01 is a hyper-v virtual machine (not yet R2), will  and has the following specifications (this one will be used as the management server):

CPU: 2 times 3.60 Ghz Xeon

RAM: 2048 MB

Harddrive: 40 GB (C:\ drive)

Nic: 1

OS: Windows Server 2008 Enterprise Edition x64 SP2 fully patched

VD-FCSD-SCSM02 is also a hyper-v virtual machine, will be used as the datawarehouse and has the following specifications

CPU: 2 times 3.60 Ghz Xeon

RAM: 2048 MB

Harddrive: 40 GB (C:\ drive) 60 GB (E:\ drive)

Nic: 1

OS: Windows Server 2008 Enterprise Edition x64 SP2 fully patched

 

I’ve downloaded the Beta 1 from the connect website (connect.microsoft.com) and started reading the SM_Initial_Config_SxS.doc that is included with the download.

According to Microsoft, the hardware requirements are as following:

For the CMDB: Quad-core 2.66 Ghz, 8 GB Ram, 10 GB of available disk space en RAID 1 or 10

For the Management Server: Dual-core 2.66 Ghz, 4 GB Ram, 10 GB of available disk space

For the Management Console: 2.0 Ghz, 2 GB Ram, 1 GB available disk space

For the Data warehouse: Quad-core 2.66 Ghz, 8 GB Ram, 100 GB of available disk space

As you can see, this is much more than I have foreseen, but considering that Microsoft tested the environment for these specifications for 10000 computers, 10000 users, 50 configuration items per computer, 5500 incidents and 1500 change requests, I figured I can do with a little less since I have no access to an environment the size of that :-)

 

For the software requirements:

For the Management Server: Windows Server 2008 x64 Standard or Enterprise (check) and Microsoft .NET framework 3.5 with SP1 (check). The .NET is also included with the installation media of SCSM

For the CMDB and the Data Warehouse: Windows Server 2008 x64 Standard or Enterprise (check), SQL Server 2008 x64 (Check) and the SSRS component of SQL Server 2008 (Check)

For the Service Manager Console: Vista 64-bit (Damned), Windows Server 2008 x64 Standard or Enterprise (Check) and .NET framework 3.5 SP1 (Check)

 

For SQL Server 2008

The configuration has to be:

  • Default SQL_Latin1_General_CP1_CI_AS collation with a default instance
  • Service Account configured as Local System
  • SSRS service configured and running

 

SMTP Server

  • A valid SMTP Server is necessary if you want to use the notification features.

 

Preparation for the installation

After the software prerequisites are ready, I’ve started with the preparations for the deployment.

  • One of the important things is that there could be no R2 components of SCOM 2007 on the system.
  • Created a group called SM_Admins that will be used as the security group for the Service Manager Administrators.
  • Created an account FCSD_MResse which is my testuser and which has the following rights:
    • SQL Server sysadmin on the SQL Server
    • Member of the SM_Admins group
  • Created a service account called SM_Acct
    • Member of the SM_Admins group
    • Member of the local administrators group of both servers
    • Sysadmin role of the SQL Servers
    • Content Manager role of the SQL Server Reporting Services
  • SQL instances have to use port number 1433 (Hope this will change…)

 

So, as you can read, a lot of preparation work.

Cheers,

Mike