Royal TS V 2.1 is right on track and we are making huge progress. You will find lots of new features in 2.1. The most popular and long awaited Terminal connection type (see: http://www.code4ward.net/main/Blog/tabid/70/EntryId/142/Early-Royal-TS-V2-1-Beta-Version-with-SSH-connection-type-released.aspx) and many, many more.

This blog post is dedicated to a smaller but still very useful feature:

Prompt for Credential

Ok, you may now think, that’s quite underwhelming… but read on, I’m not finished yet

As you might expect, checking the Prompt for Credentials will, well, prompt for credentials:

This is what you can do with the credential picker:

• Selection of an existing credential using the cursor keys. As you can see, the credential name, the configured user name and the path where you’ve placed the credential in your document structure is shown in the grid. After you’ve selected the credential you want to use,  hit Enter to continue. Hit Cancel (or ESC) to cancel the connection process.
• Find as you type: When the credential list is focused (default) you can just start typing the credential name to jump to the credential you are looking for.
• Use CTRL + F to show the Find/Filter panel which allows you to enter a name or fragment of the name. The grid will filter/highlight the search results.
• The checkbox below allows you to enter a username and password in case the credential you want to use doesn’t exist.

The dialog is easy to use, even navigation by keyboard is smooth.

But wait, there’s more:

Prompt for Credential for Ad Hoc Connections

In V2.0 you could enter a hostname/IP address in the Ad Hoc connection text box to quickly connect to a machine. Now, with a simple syntax you can invoke the credential picker as well:

Use “?@” (without the quote) to indicate that you are looking for a credential and want to use it for your connection. You can specify a filter string before the ?@ characters which allows you to filter the list of available credentials (as shown above).

Note that the filter string is also pre-populated in the Username field in case you want to use Username/Password.

If you just put ?@ in front of the hostname/IP – without a filter string, you will get the unfiltered credential picker dialog.

If you put a filter string in front of the ?@ which doesn’t match a a credential, you will get the credential picker prepared for username and password entry:

Here are some examples how you can use the Ad Hoc connection functionality in 2.1:

• HostOrIP
  just the hostname/IP works like in 2.0 and will connect to the host
• ?@HostOrIP
  the credential picker dialog appears
• SomeCredName?@HostOrIP
  the credential picker dialog appears with pre-filtered credential list and pre-populated username text box

There’s still one more little thing:

Specify Port in Ad Hoc Connections

In Royal TS V 2.1 you will also be able to specify the port in the URI string (where applicable: currently Terminal and Remote Desktop connections). The port will override any configuration in the port property of the connection if specified with the hostname/IP.

As I mentioned before, it’s the little things. It might not seem to be a “big” feature but I think with the above improvements, Royal TS got a new powerful feature helping you to be even more efficient in your daily business.

Download and Test the Current Beta

You find the current beta version and installation instructions here:

http://code4ward.net/main/Forums/tabid/61/forumid/9/postid/891/scope/posts/Default.aspx#891

As always, I’m happy to hear your feedback: http://code4ward.net/main/Forums/tabid/61/forumid/9/scope/threads/Default.aspx

cheers,
Stefan

 

We’ve just uploaded a new Royal TS release 2.0.4 (build #60505). This latest release includes a number of bug fixes as well as a couple of new, minor features. Read the Release Notes for more details. This is the second 2.0.4 release after just two days, this time a small glitch was fixed and the help file is included again. 

New Mouse Events Setting

The option “External Window: Select Dashboard” lets you control the behavior of Royal TS when you select active connections in the Navigation tree. By default (if unchecked) Royal TS will always switch the the connection tab as soon as you select an active connection. Since external connections show a tab containing some helpers allowing you to re-embed or disconnect the session, you may want to jump to the Dashboard tab instead. When the above setting is checked, Royal TS will show the Dashboard tab (only if available in the tab bar!) when the connection is hosted in an external window.

New External Window System Menu

When you work with external windows, you may find the new system menu “Embed Connection” helpful. This allows you to put back your external window connection into the tab quickly and easily.

Download

To download this release, visit our Download page.

I’ve now heard from multiple customers that they want to better control when their Service Manager connectors are running. For whatever reason, Microsoft didn’t really include a UI to control the schedule of most connectors, except for the SCCM and SCOM connectors. What if you want to control the schedule for the Active Directory connector, for example?

You have the following options:

Method 1: Initiate the synchronization using PowerShell

SCSM has a rich PowerShell API. The cmd-let Start-SCSMConnector allows you to initiate the synchronization.

On my test machine, I have a connector called “AD, all users”. When I start the Service Manager Shell and execute the command
Get-SCSMConnector
I get a list like this:

The command
Get-SCSMConnector | fl
will show some more information, including the schedule (sync time, type and interval):

As you can see from the screenshot above, the AD connector will synchronize automatically every day at 2:00 AM

Now to start connectors using PowerShell immediately, you just need to get one or more connectors into a variable and pipe it to the Start-SCSMConnector cmd-let. In my case I just want to start this single connector but you could modify the line to include more connectors in the WHERE-OBJECT:

You could write this in one line, of course but for better readability I used a variable.

After you’ve executed the command, you will see the connector will start synchronizing after a minute or so.

Conclusion:
This is an easy way to start the connectors on your own schedule (using the task scheduler) or initiate synchronization at the end of an Orchestrator runbook. For example: consider an Orchestrator runbook which creates a user in the domain, executes a sync on the domain controllers and immediately start the connector for Service Manager afterwards.

Method 2: Change the synchronization schedule using PowerShell

Update: After fixing the last line in the script, the code works as expected. To be clear, MS may not support this, so I recommend you test this in a lab environment before you go ahead and use it.

Loading SDK Assemblies

To change the schedule on the connector itself, a little SDK magic is necessary. To access the SDK from PowerShell we need to load the SDK assembly. Type the following commands (assuming your service manager install directory is the default directory):

[Reflection.Assembly]::LoadFile("C:\Program Files\Microsoft System Center 2012\Service Manager\SDK Binaries\Microsoft.EnterpriseManagement.Core.dll")

[Reflection.Assembly]::LoadFile("C:\Program Files\Microsoft System Center 2012\Service Manager\SDK Binaries\Microsoft.EnterpriseManagement.ServiceManager.dll")

Connecting to the Management Group

$MG = New-Object Microsoft.EnterpriseManagement.ServiceManagementGroup “localhost”

Since I’m executing the PowerShell on the machine hosting the SDK service, I can connect to “localhost”. The above command has no output.

Get the AD Connector using the SDK

As we did in the example above, let’s store the AD connector we want to change in the variable $ad:

$ad = $MG.ConnectorFramework.GetConnectors() | where {$_.DisplayName -eq 'AD, all users'}

Note that the connector object from the SDK looks quite different compared to the one we used in the above PowerShell example.

Get the Enum from the SDK

Now let’s get the Enum with the Name “SyncTypeEnum”:

$EnumSyncType = $MG.EntityTypes.GetEnumerations() | where {$_.Name -eq 'SyncTypeEnum'}

The next command will get all child elements for the SyncType enumeration we gathered above:

$SyncTypes = $MG.EntityTypes.GetChildEnumerations($EnumSyncType.Id, [Microsoft.EnterpriseManagement.Common.TraversalDepth]::OneLevel)

If you select all the names from the $SyncTypes array, you’ll see the possible values. By default, the AD connector syncs Daily, we want to change that to every 2 hours.

Change the Sync Type and Interval

To change the SyncType and SyncInterval values using the SDK, type:

$ad.ConnectorObject.Item($null, "SyncType").Value = $SyncTypes | where {$_.Name -eq 'SyncTypeEnum.Hours'}
$ad.ConnectorObject.Item($null, "SyncInterval").Value = 2
$ad.ConnectorObject.Commit()
$MG.LinkingFramework.UpdateDataSource($ad.ConnectorObject.Id)

 

The last two lines are used to commit and save the changes to the management group.

As you can see, we’ve changed the connector schedule to every two hours.

Conclusion:
Compared to method 1, this is much more complicated, geeky and is prone to error. In the spirit of KISS (keep it simple and stupid) I recommend method 1. Much easier to setup and change.

cheers,
Stefan
http://www.code4ward.net

Royal TS 2.0.3 brings a couple of new things and of course bug fixes.

 

Remote Desktop Dashboard Changes

I should mention one bigger change in 2.0.3 upfront: Royal TS deals with credentials in the dashboard now differently!
Read the following blog post for more information:
http://www.code4ward.net/main/Blog/tabid/70/EntryId/141/Important-Change-in-upcoming-Royal-TS-Version-2-0-3.aspx

 

Disable Reveal Password

In 2.0.3 you can now also set a registry value to disable the “reveal password” functionality in object dialogs (like credential or connection). We’re also including an ADMX/ADML file to help you deploy this using GPO:

You can set this policy on both, the user level or the machine level (which also overrules the user level setting). The ADMX/ADML files can be found in the Royal TS install directory under Policies.

Alternatively, you can also set the registry value manually (using regedit or using a login script, for example). Value 1 will enable the setting, value 0 or if the value doesn’t exist will turn off the setting:

Contents of the .reg file for the HKLM path:

--- .reg file starts here ---
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\code4ward\RoyalTS\Security]
"DoNotAllowRevealPasswords"=dword:00000001
--- .reg file ends here ---

Contents of the .reg file for the HKCU path:

--- .reg file starts here ---
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Policies\code4ward\RoyalTS\Security]
"DoNotAllowRevealPasswords"=dword:00000001
--- .reg file ends here ---

More Enhancements

In addition of the above, we’ve implemented two smaller enhancements in 2.0.3:

1. Hold the SHIFT key while you perform a Connect action to open the tab(s) in the background

2. External connection windows now also show the description field (if available) in the window title (pretty much like the main window does)

 

Bug Fixes

Read the release notes for a list of fixed issues and bugs:
http://www.code4ward.net/main/RoyalTS/ReleaseNotes.aspx

 

Download

To download Royal TS 2.0.3 go to: http://www.code4ward.net/main/RoyalTS/Download.aspx

We’ve just published a brand new beta release of Royal TS which will now also support SSH terminal connections:

While you are connected, you can switch between two different selection modes: Standard or Block selection.

You can also enable/disable the right-click mouse paste feature.

The SSH connection type supports many features and is highly customizable:

Optional private key (incl. putty private keys) and passphrase support.

Credentials, connect and disconnect tasks as well the other standard features (key sequence and window mode) are working the same way as with other connection types.

Advanced Settings:

Specify which Encoding to use, choose from 3 terminal types (Ansi, Wyse 60 and Pick), configure wrap settings, etc.

In the Proxy Settings you can choose between direct connect, Socks4, Socks4a, Socks5 and HTTP connect.

Font:

Configure your favorite font and size.

Input

Customize the input behavior of your terminal session and provide default settings for the mouse paste and selection mode.

Download link and instruction can be found here:
http://code4ward.net/main/Forums/tabid/61/forumid/9/postid/891/scope/posts/Default.aspx#891

For feedback and bug reports, please use the Beta forums:
http://www.code4ward.net/main/Forums/tabid/61/forumid/9/scope/threads/Default.aspx

cheers,
Stefan

Due to some security considerations, we will change the default behavior of Royal TS’ Hyper-V and Sessions dashboard.

In Version 2.0.2 and earlier Royal TS has a bug which may cause account lockups. This may happen when you are using credentials without setting a password or if you’ve changed your password due to applied security policies.

The default behavior of the Hyper-V and the Sessions dashboard is to first try to gather the information with the currently logged on user (the user who is running Royal TS). If this fails, Royal TS would automatically try to gather the information using the configured credentials. In most cases this isn’t a problem but if the password has changed or if no password is set, an account can be locked out very easily by just clicking on a couple of inactive connections.

What will change in 2.0.3?

First of all, Royal TS will not try to use the configured credential if no password is set. This was clearly a bug and is fixed in 2.0.3.

Secondly we will introduce a new setting in the Dashboard configuration which allows you to control whether or not to use the configured credentials to retrieve the dashboard information.

Note: Because of the above implications, the default setting for this configuration item is OFF! You may want to re-enable the setting if needed.

If your connection(s) are configured to “Use the application default setting” (which is set by default), you just need to open the Royal TS Options on the View tab and check the “Use Credentials” check box:

If you’ve configured your connection(s) to use individual settings, you can also set this option for those connections:

Is there a workaround?

If you are experiencing account lockouts, please disable the automatic Hyper-V and Session information retrieval in the Dashboard settings.

Best regards,
Stefan
code4ward.net

 

Thanks to Arsimael, who  blogged about that in German here, I’m happy to translate and re-blog his content on our blog in English. If you want to make Royal TS V2 portable and start it from a USB memory stick, external drive or even from a Dropbox folder, continue to read…

What does portable mean?

Portable means, that you do not have to install Royal TS to use it. You just put in your memory stick and start Royal TS from the memory stick – without installing it.

To make a portable version of Royal TS V2 you need to download and install it once. After you’ve installed it on your computer it’s a very simple procedure to make it portable:

1. Copy Royal TS V2 to the new location (memory stick, external drive, etc.)

Copy the contents from the Royal TS V2 installation directory to the new location.

By default Royal TS V2 is installed in “%ProgramFiles(x86)%\code4ward.net\Royal TS V2\”.

Note: Do not move the files to the new location. After you’ve copied the files to the new location, you may uninstall Royal TS again, since you will the start it from the new location.

2. Create a configuration folder

Royal TS needs a couple of configuration files. By default they are stored in the users profile directory. Since we also want to have our settings wherever we go, we need to create a new configuration folder in the new location where we copied the Royal TS files.

In the folder where RTS2App.exe was relocated, create a subfolder called with the name config

3. Change configuration path

In the new location, open the file RTS2App.exe.config in notepad and search for the following text:

%APPDATA%\code4ward

change the line above to:

.\config

4. Copy the configuration file to the new configuration folder

Go to: %APPDATA%\code4ward and copy the file code4ward.RoyalTS.UserPreferences.config to the folder you created in step 2.

Royal TS is now portable!

Things you should know

While the above works well in general, there might be the one or the other issue:

• Royal TS V2 needs the .NET Framework 4 (Full Profile) and the setup installer makes sure that it’s installed before it proceeds. The portal version doesn’t have a check like this, so you have to take care and make sure that .NET Framework 4 is installed otherwise Royal TS will not work. Take a look at our System Requirements page for more information.
• File associations are created by the installer. Since you do not install Royal TS when you use the portal version, double-clicking a .rtsx file may ask you to specify the application you want to open for the file. The Windows Explorer allows you to remember the setting and the next time you double-click a file it will open the application from your portable location.
• Uninstall Royal TS using the Control Panel after you made your portable version. This avoids that the “original”/”non-portal” version is opened when you double-click a .rtsx file.
• When you want to upgrade to a newer version of Royal TS, install it on a computer, execute step 1 from above without overwriting/deleting the config folder in the portable location.
• When you start Royal TS the first time from the portable location you may have to re-enter your license information.

Have fun and thanks again to Arsimael for the blog post!

cheers,
Stefan

My last two blog posts:

http://www.code4ward.net/main/Blog/tabid/70/EntryId/137/System-Center-2012-Service-Manager-RC-Installation-Experience.aspx

and

http://www.code4ward.net/main/Blog/tabid/70/EntryId/138/System-Center-2012-Service-Manager-RC-Self-Service-Portal-Installation.aspx

showed how I installed SCSM 2012 RC in my lab with a minimum set of hardware/software.

The last bit of the self-service-portal didn’t really work. The setup finished successfully but the portal didn’t work. The links were there but the content is missing. As it turns out the setup wasn’t correct and I’m experiencing SSL certificate issues (btw. the setup didn’t really complain).

After reading that Technet piece, I began to understand the issue. And here’s how I ‘ve resolved it:

1. Create a correct certificate

The first issue is, that the self-signed certificate I used in my lab installation wasn’t matching the computer name. I used the default certificate which came with the OS installation during the setup but it turns out that is a show stopper.

The certificate needs to be issued to the exact same name (FQDN) of the web server(s), which are running SharePoint and and the Web Content Server. Since I’m running both on the same server, I just need one correct certificate.

Unfortunately I have no CA at hand and I don’t want to install one. So let’s create a “correct” self-signed certificate using IIS manager.

Open the “Server Certificates” feature in the IIS manager:

Once opened, click on “Create Self-Signed Certificate” and enter the FQDN of the server:

2. Change Portal Application Setting

Go to the “Service Manager Portal” web site and double-click on “Application Settings”:

Edit the SMPortal_WebContentServer_URL setting and ensure you also have the FQDN of the content host (which must match the SSL issued to value):

3. Assign the new certificate to the web sites

Go to the “Service Manager Portal” web site, click on “Bindings…”, edit the https binding and select the newly created certificate:

Go to the “SCSMWebContentServer”web site, click on “Bindings…", edit the https binding and select the newly created certificate:

4. Verify/Change the Content Server web.config file

Ensure that the “ContentHostAbsoluteUri” setting in web.config file also uses the FQDN:

After those changes and an iisreset, the portal worked for me:

cheers,
Stefan
http://www.code4ward.net

This blog post is basically the continuation of my previous blog post which describes my installation experience of System Center Service Manager (aka SCSM) 2012 (Release Candidate). In SCSM 2012 the self-service-portal, which can be used by users to log an incident or submit a service request, is now SharePoint based.

Again, since this is a LAB environment, I install SharePoint and the Self-Service-Portal on my Service Manager management server. In a production environment you should carefully plan your deployment and place the SharePoint server somewhere near your users.

Part 1: Installing SharePoint Foundation 2010 (which is Free!)

You can download SharePoint 2010 Foundation from here: http://www.microsoft.com/download/en/details.aspx?id=5970

SP1 for SharePoint 2010 can be found here: http://www.microsoft.com/download/en/details.aspx?id=26640

On my Service Manager management server, I start the SharePoint installation and select “Install software prerequisites”:

The nice thing about the installer is that it takes care of all requirements (like IIS, SQL components, etc.):

Accept the license agreement:

And let the installer do its magic:

After that you might need to restart the machine before you can go ahead and install SharePoint Foundation:

Again, a license agreement:

Next screen asks us for the installation type we want:

We select “Standalone” which immediately starts the installation process:

After the installation is complete, keep the checkbox ticked to start the configuration wizard:

The wizard will start in a new window and after clicking Next, you may be asked to restart the services in order to continue:

Didn’t do much but after a while you get:

After you click on Finish, the SharePoint site should open up in your browser.

Before we go ahead and install the Service Manager components, let us apply SP1 for SharePoint Foundation. Start sp1 .exe, accept the license agreement to apply the service pack:

Part 2: Installing the Service Manager Web Portal

Once again, start the Service Manager 2012 setup.exe and select Service Manager web portal:

The first thing we get asked by the wizard is which Portal Parts we want to install:

The web content server is the “middle-tier” between your service manager installation and the SharePoint front-end server. I guess calling it Web Portal Application server would have been a better name (at least for my understanding).

The SharePoint Web Parts are the “front-end” parts you need to install on top of SharePoint. Since we are installing a very compact lab environment, we choose to install both and click on Next:

And another license agreement. We leave the installation location with the default values:

The Prerequisites checker looks fine:

The next screen allows us to configure the portal web site:

Note: I enabled SSL and used the default self-signed certificate of my windows server.

Enter the database server name and select the Service Manager database in the next screen:

Once again we get warned that we use an unsupported collation:

Configure the self-service portal user account:

The next screen will create a SharePoint portal site for the Service Manager self-service portal:

On the next screen we need to setup the user account used for the application pool:

The next two screens are about the Customer Experience Program and the summary page. After that the installation starts and once finished you should see something like this:

Ok, so everything is installed but if you’ve installed it the same way I have, you will soon find out that the Service Manager portal is blank and not working. I will publish another blog post, showing you how to resolve the issue.

cheers,
Stefan

http://www.code4ward.net

I’m just rebuilding my lab with Royal TS V2 (which is awesome, btw. ) and thought, why not blogging about the Service Manager installation experience. I’ve blogged before about the Operations Manager and Orchestrator setup experience, so it’s kind of tradition to do that for the Service Manager (aka SCSM) as well.

Components

First let’s “unbox” SCSM and see what’s inside the package:

• SQL Server
  SQL server is not really part of SCSM but you need an existing installation of SQL server or you need to provide a dedicated SQL server for your SCSM installation. SCSM stores the “inventory/CMDB” data as well as the data warehouse data in SQL server. Be sure you have configured your SQL server to use the correct collation: http://technet.microsoft.com/de-at/library/hh495583(en-us).aspx
• Service Manager management server
  This component is main component to run service manager. It’s the middle-tier between your SCSM console and the database and it’s also responsible to execute workflows. This component is installed first. Setup will also create the databases.
• Service Manager data warehouse management server
  This component takes care of all workflows and data processing routines necessary to build and maintain the data warehouse. The setup will create all necessary databases for the DW data.
• Service Manager console
  This is the SCSM UI, which is optional and will be installed on the Service Manager management server or can be installed separately on workstations.
• Service Manager web portal
  Also optional. The web portal is now completely SharePoint based and is probably subject for a dedicated blog post.

“Special” Requirements, Oddities and Side Effects

Installation and operations of Service Manager is a bit “unconventional”. Pretty much every System Center product can be installed and operated on a single server (i.e. OS installation). Of course, this is not recommended for production but in LAB or test environments you aim for low cost and a low footprint.

From the list of components above, the SCSM management server and the SCSM data warehouse management server are both needed in order to run SCSM but they cannot be installed on the same OS. You need two instances (either virtual or physical) to install those components.

Note: For production environments it’s highly recommended to properly spread out those components to multiple servers to ensure your environment is prepared to scale appropriately: http://technet.microsoft.com/de-at/library/hh495582(en-us).aspx

Also note that there are several “manual” steps you may need to execute after installation, depending on your reporting setup and your data warehouse needs. I always suggest to read carefully the deployment guide and make sure to prepare yourself sufficiently before you go ahead and install SCSM!

Another thing worth mentioning is, that you cannot install a SCOM agent on a SCSM management server. Monitoring of SCSM components are only supported in an agentless way. As of today, even a server where only the SCSM portal web server components are installed, the SCOM agent installation will be blocked. If you install first the SCOM agent and then the SCSM portal web server components, setup will finish without any issues. It’s not clear yet if this is a supported scenario. I hope we get a clear answer from Microsoft by the time RTM is published.

Setup Part 1: Service Manager management server

My first (virtual) machine is a Windows 2008R2 server, fully patched with .NET 3.5 SP1 installed. My database machine is a separate machine running only SQL 2008 R2.

After running setup.exe, click on “Service Manager management server”:

We’re installing the 180 days eval. The product key can be entered afterwards when you got the license key and when you’ve upgraded RC to RTM.

… select the installation location:

The Prerequisite checker complains that I haven’t installed a couple of SQL 2008 components. The good news is, there are links to quickly download and install the missing stuff, the bad news: The links are all for SQL 2008 and I have to start over again with the setup after installation of the missing prerequisites:

Note: Since I’m using SQL 2008 R2 I went to this page: http://www.microsoft.com/download/en/details.aspx?id=16978 and downloaded the prerequisites for SQL 2008R2 components from there.

Ok, after installing those things, the prerequisite checker looks much better:

Next screen: Service Manager database

I’m using the (US English) default collation and I get an “unsupported” message. I will go ahead with my installation because for my lab environment I will only use English in Service Manager. If you have multi-language requirements or want to use SCSM with a non-English language, please check the collation link and make sure your SQL server is configured properly.

The management group name needs to be unique. Don’t use the same name you’ve used for any of your SCOM environments and do not use any special characters in the management group name. In the past, you ran into issues when you used dashes (-) or other characters in the name. I’m not sure if all the issues are resolved now but I tend to keep the name ASCII chars only to avoid any issues in the first place.

I’m also using the Domain Admins group in the dialog. Again, this is a lab environment and a non-production installation. In production you shouldn’t do that and use appropriate accounts and groups.

After configuring the management group name and specifying a domain group for the admins we’re asked to provide account details for the service accounts:

… and:

That’s it. The next two screens are "Customer Experience Program” and the summary page before the installation begins. Installation may take a while and when it’s finished you should see something like that:

After closing the setup wizard, I strongly recommend the encryption key in a safe place in case of a disaster recovery.

Setup Part 2: Service Manager data warehouse management server

As mentioned before, you need to install a second component on a different server (physical or virtual) in order to complete the SCSM setup. Like my first (virtual) machine, this one is again a Windows 2008R2 server, fully patched with .NET 3.5 SP1 installed.

Let’s start the setup.exe on the second server and select Service Manager data warehouse management server:

As before, accept the license agreement:

and specify the install location:

Remember that one?

Installing the prerequisites, like we did on the first server:

The next page is all about configuring the DW database and as before we are again warned about the collation settings:

Configure all three database settings and click on next:

The next steps allows you to create additional “data marts” for Operations Manager and Configuration Manager. After setup is completed you can pull in data (register the System Center DW to Operations Manager and Configuration Manager):
http://technet.microsoft.com/en-us/library/hh519633.aspx

Now we’ve configured all our databases (quite a lot) to create, so let’s move on:

As you can read the warning on the page, a dedicated management group will be created for the DW. This means you need to provide a unique name for the management group.

Now we’re asked to configure the reporting (SSRS) instance:

The last checkbox reminds us that we need to do some manual stuff. Execute the steps as described here and you should be good.

Now the service accounts for the Service Manager service (see above) and the reporting account:

After you’ve specified the accounts, we need to setup an OLAP cube and the analysis service account:

That’s it. The next two screens are "Customer Experience Program” and the summary page before the installation begins. Installation may take a while and when it’s finished you should see something like that:

After you’ve finished both installations, you need to complete the data warehouse registration(s):

Registering with the Service Manager Data Warehouse
http://technet.microsoft.com/de-at/library/hh495615(en-us).aspx

I had to restart the Service Manager console in order to get the Data Warehouse section.

You may also register the SCSM DW to Operations Manager and Configuration Manager:
http://technet.microsoft.com/de-at/library/hh519633(en-us).aspx

That’s it from the installation perspective. I will probably post another blog post covering the web console part.

cheers,
Stefan

http://www.code4ward.net