Cireson’s Self-Service Portal is a complete replacement for the out of box Microsoft Self-Service Portal. Not only does it replace the ageing, lagging, Silverlight based portal, it fuses all functions of the current Cireson Web Analyst console into one stop shop. I had the privilege to participate in the closed beta and I must say the leadership and enthusiasm for this application is unmatched. It was like the developers had a passion from the pain of the current portal and direct Microsoft inspiration 🙂
Choosing the Windows Azure Pack “WAP” style interface has created a beautiful layout and interface. I can’t stress enough how the portal will enhance the end-user to full administrator experience. Below is an install and basic customizations. I did hit a snag but it was due to a bad download. Other than that the deployment of the Cireson Self Service Portal is a cakewalk.
Cireson’s Install KB (please follow their documentation, below is just a sample install)
I will be using the Cache Windows Service and pre req powershell deployment on a independent web server.
I kick off the pre-req powershell deployment.
I copied over the .dll since this is a independent web server that is not a SCSM Management server
Now lets import the management pack.
Kill the System Center Data Access service.
Extract/Copy CiresonPortal-2014-X-X folder to the “Inetpub” location and rename folder CiresonPortal
Update the “connection string” and “application title” in the web.config.
Update the “connectionString” and “AnalystADGroup” in the Cireson.CacheBuilder.Service.exe.config
Now everything is configured kick off
C:\ISO\System Center 2012\Cireson_SCSM_APPZ\CiresonPortal-2014-04-21\CacheBuilder\WindowsService\Scripts\Install-CacheBuilder.ps1
Now lets add the website.
Update the application pool identity
Choose an AD account that is a full admin in Service Manager.
If you wish to use SSO enable “Windows Authentication” and disable “Forms Authentication”.
Aight lets do an IIS reset and fireup this bad boy and…….
Server Error in ‘/’ Application
The view ‘login’ or its master was not found or the view engine supports the searched locations. The following locations were searched: ~/views/login/login.cshtml
Well after extensive troubleshooting, I had bad media. Probably my fault since I have been battling my ISP Comcast since they think 75% uptime is acceptable (another topic for another time).
Cireson was happy to provide a different link just incase the original one was corrupt and after deploying the new code I receivied the following upon first log.
After I inputted our license key you will see a logon if you did not select SSO. Here is where you will see the customization you made in the web.config under “ApplicationTitle”.
Now once we logon we see a BEAUTIFUL “WAP” inspired interface.
Here is what “My Requests” now look like. I have not once see the bug where this does not render!
Service Catalog with big icons.
Service Catalog with 32×32 icons. These are all the same icons from when you uploaded them to your Request / Service offering in the SCSM Thick console. There is nothing different when creating an offering as before when you were publishing to Microsoft’s Self-Service Portal, only other then the fact the Cireson SSP is a work of art.
Here is one more customization that I implemented. In my organization we wanted to rename the “Configuration Items” section to “CMDB”. To do this we have to create a override display string.
Now we have CMDB!