Quick Tip ! Automate it !

April 28, 2016


I am a big fan of automation , you improve efficiency by generating a consistent result fast.

But it needs to be worth it, you need a certain quantity of requests before the investment pays off.

Luckily we have these kind of environments in our partner portfolio.

Here we use the service manager portal not for the end-users but we present the portal to the first line helpdesk so they don’t have to escalate certain tasks to second line. All requests are automated by orchestrator runbooks.


And we are on 4874 completed request.


Simple math : about 10 minutes if the action is performed manually , this makes 48740 minutes -> 812 hours -> 101 working days saved, this time can be spent on tasks that create a real added value for the partner.


Gino D


ServiceManager 2012 Server Error in Knowledge Articles

July 6, 2012

Today I wanted to verify the opening of a knowledge article in the service manager portal site and recieved an error.

Strange since the other portal items were working fine.
The solution lies in the verification of the web.config file in .\inetpub\wwwroot\System Center Service Manager Portal\ContentHost\Web.config.

Verify the Appsettings section in order to verify the url that you are using for opening the service manager.

If a match then the KB link should work.

Just make sure the certificates used for the portal matches the fqdn of the service manager server and the modifications have been performed as described in a previous post of “Portal Issue”


Gino D

Service Manager 2012 Portal issue

March 5, 2012

So .. The portal is installed but not working ! How come …
When we open the portal page as Service manager admin we see this …

After verifying the certiciate information I saw that a different Server name was used.

So test with the correct name in order to resolve the certificate error message.

Export the certificate …

And import it in the computer account …

… As trusted root certification Authorities.

Still … No resolution for the blank screen in the middle of the portal. So open the IIS portal and go to Application settings.

Modify the Portal Webcontent URL from the old value …

… To the correct name on the certificate.

Test -> OK it works.

So now for a permanent solution. Create a new certificate using the IIS manager. -> <ServerName> -> Server Certificates -> Create new self-signed certificate using the fqdn of the service manager server.

Link the newly created certificate to the portal site by right clicking the service manager portal and the SCSMWebContentServer in IIS and selecting “edit bindings” -> select the newly created self-signed certificate.

Now finally make sure the Portal Webcontent URL ( as described above ) uses the FQDN of the service manager server.

However if we retest using a norma user account ( no service manager admin ) then we recieve the same issue. How come …

In order to resolve open sharepoint administration site …

… Select “Manage web applications”

…Select the portal site and click user policy and add domain users Full read Permissions.

Now test ( as normal end-user ) -> Success !!

Enjoy …

SCSM2012 RC Portal install

February 18, 2012

So we have set up a great infrastructure for incident, problem and change management but it’s no good without the self-service portal. So let’s install this component now.
Remember ! Do not install the portal server on the management server. You cannot uninstall the portal component without reinstalling the whole management server. So take a seperate server for the installation of the portal. Or you’ll end up reinstalling your management server several times … Trust me 🙂
Start with the following link for more information : http://technet.microsoft.com/en-us/library/hh495575.aspx

-> First install the prerequisites. Add IIS server, ASP.NET , basic and windows authentication.

-> Now download the Microsoft Sharepoint Foundation 2010

-> Start the sharepoint setup.

-> The setup will install the necesarry prereqs

-> Unfortunately not all necesarry updates were installed automatically. So you can find the necesarry updates listed here :

The missing updates can be downloaded manually and installed.

-> Restart the sharepoint setup so it will no longer stop because of missing prerequisites.

-> Select a standalone installation.

-> Let the installer perform its magic.

-> Run the configuration wizard.

-> Verify the result.

-> Now modify the sharepoint permissions as described on technet.

See link : http://technet.microsoft.com/en-us/library/hh495661.aspx

Ok ! We can now start with the service manager portal installation.
-> Install the web portal.

-> Select both components ( here for lab purpose )

-> Choose correct location

-> Verify that all the necesarry prerequisites are installed.

-> Use the default config and enable the SSL encryption.

-> Select the correct SQL server and instance name. ( ignore the collation warning, the collations are checked on all instances during the install wizard )

-> Select a domain user account for the portal ( normal domain user )

-> Select the correct sharepoint config.

-> Select a user account for the app pool.

-> Verify the summary and continue.

-> Verify the result of the installation.

-> That’s it. We will verify the portal itself in the next post.

Modify url end user portal

November 19, 2011


By default the url for the end user portal in service manager is https://PortalServer.domain.suffix/Enduser, not really convient.

So we are going to modify the url to https://PortalServer.domain.suffix

How ?

Add the URL redirection component to your portal server. ( Add role service )

Select http redirection.

Click Install.

Open your IIS manager and select the SCSMPortal Site.

Now the select the HTTP redirect button on the right side.

Enable the redirection and select the option “Only redirect requests to …”

Apply and test !