Blog Image

Blog - Dries Willems - Freelance IT Consultant

About the blog

The main reason I use this blog, is to help myself tackling similar issues. You can see this as a very small online documentation library.
Also it is useful for others who experience the same issues.

Enabling CLR Integration

SQL Posted on Tue, March 17, 2015 17:29:22

Query test
sp_configure ‘clr enabled’

Query change
sp_configure ‘show advanced options’, 1;
GO
RECONFIGURE;
GO
sp_configure ‘clr enabled’, 1;
GO
RECONFIGURE;
GO

https://msdn.microsoft.com/en-us/library/ms131048.aspx



Orchestrator Designer generates a prompt for a license key after you migrate the Orchestrator database

SCO Posted on Tue, March 17, 2015 17:04:39

When you migrate the Orchestrator database from one instance of Microsoft SQL Server to another and then try to open Orchestrator Designer in Microsoft System Center 2012 Orchestrator or in System Center 2012 R2 Orchestrator, Orchestrator Designer starts to open and then generates a prompt that indicates that the license key has expired. When you enter a valid key and then click OK, the same prompt appears.

For all the details as well as a resolution, please see the following:

KB2920037 – Orchestrator Designer generates a prompt for a license key after you migrate the Orchestrator database (http://support.microsoft.com/kb/2920037)

To resolve this issue, follow these steps:

Stop the Orchestrator Management service.

Open the Orchestrator database on the new instance of SQL Server.

Open a new query, and make sure that the Orchestrator database is selected.

Execute the following two lines on the database, one at a time:

Delete the old key:

[Microsoft.SystemCenter.Orchestrator.Cryptography].[DropOrchestratorKeys]

Create the new key:

[Microsoft.SystemCenter.Orchestrator.Cryptography].[CreateOrchestratorKeys]

Start the Orchestrator Management service.

When you now open Orchestrator Designer, you are again prompted for the key. When you enter the key, the key works as designed.

http://blogs.technet.com/b/orchestrator/archive/2014/01/09/kb-orchestrator-designer-generates-a-prompt-for-a-license-key-after-you-migrate-the-orchestrator-database.aspx



Reporting Services Site Role Setup: Instance Blank/Empty

SCCM Posted on Tue, March 17, 2015 10:55:29

When attempting to set up and configure the ConfigMgr 2012 site system role for reporting services, a frequently experienced “problem” is that the instance name can be blank/empty in the wizard and thereby unable to proceed with the wizard. This usually occurs when SRS has not been pre-configured properly.
While it is common “knowledge” that the reporting services database needs to be created first, an oft-overlooked step is to use the Reporting Services Configuration Manager to create the virtual directories for IIS. And it is these steps which need to be completed to get you on your way.
Open Reporting Services Configuration ManagerConnect to the server/instanceClick on Web Service URL – make a fake change, such as changing the name of the virtual directory and then putting it back to ReportServer – and clicking Apply. This will then create the new virtual directories.
Click on Report Manager URL – again, make a change to the name and put back to just Reports – and click Apply to generate the new virtual directories.Close configuration managerReturn to the CM12 site role setup program, click “Verify” for the database connection, and voila the instance is now populated correctly!

http://myitforum.com/myitforumwp/2012/10/10/reporting-services-site-role-setup-instance-blankempty/#



Unable to remove the Component Server Site System Role

SCCM Posted on Tue, March 17, 2015 10:27:38

Problem:

I am trying to remove a DP from a server. I’ve gone to Administration | Overview | Site Configuration | Servers and Site System Roles

I right-click on the server that is hosting the DP I want to remove and select Delete from the context menu.

However, I then get a Delete Server dialog box stating:

The server “\\<server_fqdn>” cannot be deleted because it contains the following site system roles:

Component server

The component server role supports other site system roles and is created automatically by Configuration Manager. Although there might be a delay, this role is automatically removed after you remove other site system roles on this server.

I’ve tried right-clicking on the Component server role under Site System Roles but the Remove Role option is greyed out so I’m unable to remove the Component Server Site System Role.

As this server is only hosting a DP I don’t understand why it has the Component server installed on it.

Resolution:

The server in question must have had another Site System role installed on it at some point in the past as the Component server role gets installed on a server whenever a Site System role is installed with the exception of a DP (so if the server has only ever run as a DP you will not see the Component server).

Chances are a role other than the DP was installed at some point in the past and removed but the Component server role hasn’t been removed for some reason.

The quickest way to kickstart this is on the affected server:

Right-click Site system under Site system Roles and select Properties from the context menu.

Make a change to a setting on the Site system properties screen such as checking the Require the site server to initiate connections to this site system then click OK.

Wait 10 – 15 minutes.

Refresh the console and the Component server role should now have disappeared.

You should now be able to delete the server hosting the DP.

– See more at: http://www.faqshop.com/wp/configmgr/cm12/cm12trobshoot/cm12sitesys/unable-remove-component-server-site-system-role#sthash.VzDrv9CV.dpuf

http://www.faqshop.com/wp/configmgr-2012-unable-remove-component-server-site-system-role