#Cireson added value on System Center

October 16, 2013


As you’ve probably heard Cireson has a number of addons on the system center service manager. Today we talk about some of them.

Additional information can be found on the cireson website here : http://www.cireson.com/app-store/

First up : The notify analyst solution.

In short : the addon allows notification of user / group upon assignment of workitems. Detailed information can be found here : http://www.cireson.com/scsm/cireson-notify-analyst-app/

Our ( free trial ) version had the incident and the service request notifications available.

Now let’s start with the creation of an incident template for the notification.

Add the required information for the email.

Select the newly created template in the incident settings page.

And test, assign an incident to a specific Analyst and verify the result.

You can verify the status of the workflow using the console.

… and the result

So there you have it, nice easy-to-use and does just what it says.

Second up : The Cireson web console.

Well heard comment , people like web consoles ( if they are fast and responsive and offer the same functionalities as a native console 🙂 ).

Cireson has an addon for the service manager console to be available as a web console. ( based on html 5 )

Install is pretty straightforward and well documented, and afterwards you get an additional settings button.

In the general settings we can define the AD Group that contains all the analysts who have access to the webconsole.

In the AD prefix we define a prefix that will be used for enumeration of Incident and service request tier groups.

Example we have “Tier 1” as a incident tier defined.

We also have an AD Group SCSM-Tier 1 containing several members.

Now if we start the web console we can assign an icident to a specific user after selecting the tier.

Unfortunately , this did’t work at first.Because … my language settings in IE were modified. I was using the dutch language.

Now if we start the “Assign to Analyst by group” button

We see that no users are available …

But if we rename the group to “SCSM-Laag 1” , logoff and try again …

Then we see it works as expected. A solution could be to use nested groups. ( Create an EN group and make member of the NL group etc. )

The rest of the console looks very promising. A lot of functionalities are available using the web console.

Also a very nice Search Work items tab can be used :

The only thing I am missing is the “send email functionality” on the portal … maybe a feature request 🙂

Overall a real added value for the service manager.


Gino D


Microsoft ASP.NET 2.0 AJAX Extensions 1.0 Setup failed

July 5, 2012

One of the requirements for the installation of the SCOM web console is the installation of Microsoft ASP.NET 2.0 AJAX Extensions 1.0. Recently, I the installation failed with the error:

Microsoft ASP.NET 2.0 AJAX Extensions 1.0 Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run the Setup Wizard again.

To know what went wrong, I executed the following command to try to install it again, but from a command prompt with administrative privileges:

    ASPAJAXExtSetup.msi INSTALLDIR=c:\AJAX ALLUSERS=2 /l c:\ajax\log.txt

After trying to install again, I searched through the installation log and found the following information:

ExecNetFx: The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. (Exception from HRESULT: 0x80070422)
ExecNetFx: Error 0x8007006d: failed to allocate output string
ExecNetFx: Error 0xffffffff: Command line returned an error.
ExecNetFx: Error 0xffffffff: failed to execute Ngen command: C:\Windows\Microsoft.NET\Framework\v2.0.50727\ngen.exe update /queue
CustomAction NetFxExecuteNativeImageCommitInstall returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

So what is the issue? The Microsoft .NET Framework NGEN v2.0.50727 services are needed by the installer but are disabled by default. They need to be started by .NET installers. To solve this, change the startup type of both services Microsoft .NET Framework NGEN v2.0.50727_X86 and Microsoft .NET Framework NGEN v2.0.50727_X64 to manual and re-install the application, which now runs fine!