Configure a SCVMM VM Template with the desired regional settings

This is an extract from the following KB. However, since I assume this is quite useful information, I will put it here for my own reference:

2709539 - Regional settings default to English when deploying a virtual machine using a template on System Center 2012 Virtual Machine Manager

Consider the following scenario:

• A virtual machine is configured to use regional settings other than en-US (example: ja-JP or fr-FR)
• A VM template is created from this virtual machine using System Center Virtual Machine Manager 2012.
• Virtual machines that are created using this template are configured to use the en-US regional settings.

Cause

Deploying virtual machines using a template in System Center Virtual Machine Manager 2012 will override the guest OS language setting with en-US by default.

Resolution

To work around this issue, perform the following steps:
1. Launch the VMM Console.
2. Click on Settings option.
3. Click on PowerShell and execute the below commands on respective Template.
4. $template = Get-SCVMtemplate | where {$_.Name -eq "Template_Name"}
5. $settings = $template.UnattendSettings;
6. $settings.add("oobeSystem/Microsoft-Windows-International-Core/UserLocale","cy-GB");
7. $settings.add("oobeSystem/Microsoft-Windows-International-Core/SystemLocale","cy-GB");
8. $settings.add("oobeSystem/Microsoft-Windows-International-Core/UILanguage","cy-GB");
9. $settings.add("oobeSystem/Microsoft-Windows-International-Core/InputLocale","0452:00000452");
10. Set-SCVMTemplate -VMTemplate $template -UnattendSettings $settings

NOTE For Steps 6-9, the regional settings will vary based on the language. Please refer to the following sites for the regional settings that should be used for each language:

Language Pack Default Values
http://technet.microsoft.com/en-us/library/cc766191(v=ws.10).aspx

Default Input Locales
http://technet.microsoft.com/en-us/library/cc766503(v=ws.10).aspx

In my case, the Swiss German settings are:

6. $settings.add("oobeSystem/Microsoft-Windows-International-Core/UserLocale","de-DE");
7. $settings.add("oobeSystem/Microsoft-Windows-International-Core/SystemLocale","de-DE");
8. $settings.add("oobeSystem/Microsoft-Windows-International-Core/UILanguage","de-DE");
9. $settings.add("oobeSystem/Microsoft-Windows-International-Core/InputLocale","0807:00000807");

More Information

Scripts used during MMS 2012 PowerShell session:
http://blogs.technet.com/b/hectorl/archive/2012/04/16/fi-b322-scripts-used-during-mms-2012-powershell-session.aspx

Hyper-V over SMB 3.0 in Windows Server 2012

With the release of Windows Server 2012, a new version of SMB is released. This version brings tremendous enhancements for multiple workloads. One of the workload that specially benefits from SMB 3.0 is Hyper-V. Let’s quickly discuss these new functionalities from a Hyper-V perspective:

SMB 3.0 Transparent Failover 

SMB transparent failover increases server availability. SMB 3.0 supports the placement of Hyper-V virtual machines on SMB file shares. To make these file share highly available, they can be placed on a failover cluster. Now, with SMB 3.0 these failover of the file share from one cluster node to another is transparent to server applications which means there is only a small IO delay during failover. The application that stores it’s data on the file share won’t notice the switch from one node to another.

Requirements:

• Windows Failover Cluster
• Both servers running application and file server cluster must be Windows Server 2012
• Share must be enabled from “continuous availability”

SMB 3.0 Scale Out

SMB Scale Out takes the file server cluster one step further. Instead of having a clustered file share available only on one cluster node, a Scale Out share is available on multiple cluster nodes (maximum of 4 cluster nodes). This capability provides a fault tolerance with zero downtime because the clustered file share are now in a Active/Active mode where each node can take over without the need to move resources.

These Scale Out file shares are targeted from application workloads and should not be used for normal file storage (which have more metadata operations).

SMB 3.0 Multichannel

SMB Multichannel detects and uses multiple network connections per SMB session. The configuration is automatic. There is no need to specially configure this. SMB Multichannel provides failover detections and bandwidth aggregation with multiple NICs. This works with teamed NICs as well as with non teamed NICs.

SMB 3.0 Direct (SMB over RDMA)

With SMB 3.0 Direct you have a capability to transfer the data from one NIC to the other without the intervention of the CPU on each side. Specially with 10 Gbit NIC, a lot of CPU resources is used to break all the data down to transfer it over the wire. Therefore, RDMA allows the NIC to handle most of that work. The NIC basically needs to support this capabilities.

VSS Support for Remote File Share

With SMB 3.0 VSS backups can also be done on a remote file share. VSS backups so far allowed application consistent snapshots in block storage. But with SMB 3.0 it’s also allowed with remote file storage.

For more information on SMB 3.0 see following links:

• Windows Server Blog - SMB 2.2 is now SMB 3.0.
• Windows Server Blog - Taking Server Application Storage to Windows File Shares.
• Storage and Continuous Availability Enhancements in Windows Server 8
• High-Performance, Continuously Available File Share Storage for Server Applications

Update Rollup 1 for System Center 2012 Released

    Microsoft released the first Update Rollup for System Center 2012. This Update Rollup contains fixes for:

• System Center 2012 Virtual Machine Manager
• System Center 2012 App Controller
• System Center 2012 Operations Manager

For detailed information what issues are fixed look here: http://support.microsoft.com/kb/2686249#Instructions

Installation

The update packages for Virtual Machine Manager and App Controller are available from Microsoft Update.

To download the management pack update for VMM, go to the following Microsoft Download Center website:

http://www.microsoft.com/en-us/download/details.aspx?id=29679 

To download the update packages for Operations Manager, go to the following Microsoft Download Center website:

http://www.microsoft.com/downloads/details.aspx?FamilyID=c593536c-94f3-4c71-b963-5ab3b7fc05e1

Windows Server 2012–Cluster in a box

With the new Windows Server 2012 storage functionality of shared SAS and Storage Spaces, Microsoft is now able to provide an architecture that allows the creation of a “Cluster in a box”. A cluster in a box is basically a two (or four) note cluster with networking and storage that come in one chassis that can be fitted into a standard server rack. All the components of this cluster are preconfigured and, according to the following, should be ready in only 15 minutes after running through a simple wizard.

For more information watch the following Channel 9 Edge show:

More information:

• Jose Barettos blog post: Updated Links on Windows Server 2012 File Server and SMB 3.0

Installing Windows Server 2012 Beta from USB device into a VHD file

Here’s an quick and easy step by step guide on installing and booting Windows Server 8 Beta from a VHD using a USB device. You only need:

• A Windows Server 8 Beta ISO file: Windows Server 8 Beta from Technet
• The Windows 7 USB DVD Download tool: Windows 7 USB DVD Download tool from Microsoft Store

1. Connect a USB stick of 4 at least GB. Important:  the USB device will be formatted.

2. Install the Windows 7 USB DVD Download tool

3. Run the tool and browser to your Windows Server 8 ISO file. Click Next.

4. Choose the USB Device.

5. Click on Begin copying. Important the USB device will be formatted.

Once the formatting and copying is finished close the tool.

6. Ensure that your computer can boot from USB device. If required change the BIOS settings accordingly.

7. Boot from the USB device.

8. On the regional settings windows, just press SHIFT-F10. This will open a command prompt.

9. Start diskpart.exe. Diskpart allows you to create the VHD file that you are going to install Windows 8 to.

     Type the following command to create and attach the VHD file to the running setup:

           CREATE VDISK FILE=C:\vhd\WindowsServer8.vhd TYPE=fixed MAXIMUM=30000

      SELECT VDISK FILE=C:\vhd\WindowsServer8.vhd

      ATTACH VDISK

10. Exit diskpart and exit the Command Prompt.

11. Continue with the Windows Server 8 Beta installation and select the created VHD when ask to specific a location.

Have fun.

SCOM 2007 R2 – Rough Guide on SCOM 2007 R2 & Data Warehouse Installation

    Everyone that has install SCOM 2007 R2 with the SCOM data warehouse on multiple servers will know that it is quick tricky to get it right the first time. Therefore I put some installation notes together right before the release of SCOM 2012.  In this installation I have one SQL 2008 R2 server and one Windows 2008 R2 server. The Windows server will hold the SCOM 2007 R2 management server, reporting server and the web console.

1. User Accounts & Groups

In Active Directory Users and Computers, create six accounts:

• Management Server Action account, e.g. SRV_OM7_MSAA
• SDK and Configuration Service account, e.g. SRV_OM7_SDK
• Data Reader account, e.g. SRV_OM7_READER
• Data Warehouse Write Action account, e.g. SRV_OM7_WRITER
• Operations Manager Administrator account. e.g. OMAdmin
• SQL Server Reporting Services account. e.g. SRV_SSRS

Add all these accounts to the local administrators group on the futur SCOM server. Create a Operations Manager Admins group, e.g. OMAdmins. Add a the OMAdmin user account to the group.

2. SQL Server Installation

I installed SQL server on one Windows Server 2008 R2 server and SQL 2008 R2 Reporting service on the future management server.

• SQL collation setting must be configured for SQL_Latin1_General_CP1_CI_AS

3. SCOM database and data warehouse database installation

Next install the SCOM databases. I use the DBcreateWizard to do this.

• Log on to the SQL server with a account that has SQL sysadmin rights and local admin rights.
• Use the DBCreateWizard.exe from the SCOM 2007 R2 installation media (/support tools/AMD64) to have the SCOM database created. Choose a management group name and select the OMAdmins group to have permission on the management group. In the same way create the data warehouse database. 

4. Install SCOM management on the server

Log in to the SCOM with the same user that created the databases. This user must be a local admin on the SCOM management server and it needs to be in the OMAdmin group.

After the installation, log in with the OMAdmin account, start the console and verify that the installation completed.

5. Install SQL Reporting server

This installation could have happened earlier as well. It just needs to be done before the SCOM reporting service is installed.

I use SQL 2008 R2. Start the setup, and install the setup support files. Select SQL reporting feature. Use a domain account for the service account e.g. SRV_SSRS.

Important: Update the SQL Server Reporting service with the latest service pack before continuing with the configuration.

The reporting service needs to be configured once it’s installed. To do this start the Reporting Service Configuration Manager:

• Verify the service account settings
• Create the Reporting database
• Apply the reporting web service URL
• Apply the report manager URL
• Do a backup of the encryption key

6. Install the SCOM 2007 R2 Reporting

On the reporting server, on the local groups look for a group name starting: SQLServerReportServerUser… Remove the string “_50”.

Start the installation wizard and on the Custom Setup page deselect Data Warehouse. Enter the Write and Reader account and start the installation.

After the installation, add the “_50” string to the local group again.

To verify the installation, log into the Operations Manager server with the OMAdmin account and start the Operations Manager console. Verify that the Reporting tab is available.

Additional information

• SQL Server Broker Service
  Operations Manager Discovery, in addition to other workflows, is dependent on SQL Server 2005 and SQL Server 2008 Service Broker, which must remain enabled for Operations Manager 2007 to be fully functional.
• Installing OpsMgr 2007 SP1 Reporting on Windows Server 2008

http://blogs.technet.com/b/wchomak/archive/2008/09/30/installing-system-center-opsmgr-2007-sp1-reporting-on-windows-server-2008.aspx

• Using a Firewall with Operations Manager 2007

http://technet.microsoft.com/en-us/library/cc540431.aspx

• Error message when you try to install System Center Operations Manager 2007 Reporting: "The wizard was interrupted before Operations Manager 2007 could be installed"

http://support.microsoft.com/kb/936219

• Using DBcreateWizard.exe

http://support.microsoft.com/kb/2425714

• Installing Operations Manager 2007 Reporting successfully

http://blogs.technet.com/b/momteam/archive/2008/12/04/installing-operations-manager-2007-reporting-successfully.aspx

• OpsMgr 2007: How to make your Reporting install a success

http://blogs.technet.com/b/operationsmgr/archive/2008/12/05/opsmgr-2007-how-to-make-your-reporting-install-a-success.aspx

Microsoft Private Cloud – Service Delivery and Automation

One of the characteristics of Cloud computing is Self-Service. Self-service gives the end user the ability to request the services he needs in a guided and controlled way. Through the use of automation, these requests are then processed, approved and executed in a consistent and predictable way. System Center Service Manager 2012 is at your hand to do exactly this.

Right away, here’s an example of a Private Cloud virtual machine service offering (the slides are taken from Sean Christensen’s Private Cloud CEP presentation ). These are the steps to create and execute a service request in System Center Service Manager 2012, with the help of System Center Orchestrator 2012 and Virtual Machine Manager 2012:

Click to read more ...

SCSM 2012–How to install the Self-Service Portal

One of the new and great features of System Center Service Manager 2012 is the new Self-Service Portal. This portal allows the end users to find the Service Offerings and the related Request Offerings that are published by Service Manager. Service Offerings and Request Offerings are the important ingredients for service delivery and automation.

The System Center Service Manager Self-Service Portal (or short SCSMSSP) is a separate installation and can be installed on one or two separate server. In this step-by-step guide I am going to install the Self-Service Portal on one server. The perquisites are:

• The 64-bit edition of Windows Server 2008 R2 Standard or the 64-bit edition of Windows Server 2008 R2 Enterprise
• Microsoft Internet Information Services (IIS) 7 with IIS 6 metabase compatibility installed
• A Secure Sockets Layer (SSL) certificate can be used on the IIS server that hosts the Self-Service Portal.
• ASP.NET 2.0
• Microsoft .NET Framework 4
• Microsoft Analysis Management Objects (AMOs)

Click to read more ...

Microsoft Private Cloud – Fabric Overview

The Microsoft Private Cloud solutions consists of a variety of components like infrastructure, applications, monitoring, automation, orchestration and service management. In this block will quickly look at the Private Cloud Fabric infrastructure. System Center Virtual Machine Manager 2012 is the key tool from the System System Center 2012 suite that lets you build and manage your Private Cloud fabric.

Let’s start with a overview diagram from Kenon Owens’ presentation in the Private Cloud Communicate Evaluation Program (https://connect.microsoft.com/site799/program7383).

Click to read more ...

Microsoft Private Cloud–System Center 2012 Virtual Machine Manager

The Microsoft Private Cloud solution is not a single product solution. Instead it is a composition of Windows server and System Center products. More specifically, it’s currently Windows Server 2008 R2 with the Hyper-V role and, in the near future, the System Center 2012 suite of products.

System Center 2012 Virtual Machine Manager (VMM) plays one of the major roles enabling the Microsoft Private Cloud solution. Why is that?

• Clouds: The Clouds feature in VMM allows the pooling of resources into a entity called Cloud. This entity has capacities and capabilities assigned that allows a data center administrator to shape virtual resources and provide these resource to a IT consumer as the consumer requires it.

Click to read more ...