Welcome to part 2 of the DIY Analyst Portal for Service Manager. This post is dedicated to the most basic page on the site, the default.aspx home page. It is purely HTML and anyone could create it in seconds but I’ve included it anyway. The code has been generalized and only the pertinent code required to run the site has been included.
<p><a href="details.aspx?tech=tech1">Tech 1</a></p>
<p><a href="details.aspx?tech=tech2">Tech 2</a></p>
<p><a href="details.aspx?tech=tech3">Tech 3</a></p>
<p><a href="serial.aspx">Check Serial Number</a></p>
Our organization has an interesting bug with some of our servers – if they don’t “cleanly” shut down and are down for 15+ minutes, the DNS record is deleted when they come back up causing all sorts of issues. The servers that were encountering this issue were all Windows 2008 R2.
While attending a recent local user group of IT professionals, Microsoft KB 2520155 (link here) happened to be mentioned during a presentation on a members journey of updating a SBS2003/Exchange 2003 server to Windows Server 2012 R2 and Exchange 2013. As the article hasn’t been modified since 2012 who knows if the 2012 or 2012 R2 versions of Windows Server are prone to the issue or not.
What is interesting is we have had tickets open with Microsoft before regarding our issue and have had them check our systems with no mention of this particular article or the hotfix.
So if you have a randomly disappearing DNS record, whether client or server, check this out!
One of the shortcomings of the Service Manager product is the lack of an analyst portal for remote technicians to easily view and resolve tickets without having to remote into a machine and use the SCSM console.
This short series of blog posts will show my way of getting around this limitation and after this prelude I will start to add more posts in the near future. Using the SDK for SCSM I was able to build my own analyst portal which performs beautifully on both a desktop browser and mobile device.
This is a straightforward HTML website driven by C# in the background – no fancy HTML5 or anything here (so far)! I will generalize the code as I post it as some menu items are hard-coded, such as technician names to link to their tickets. Also the current implementation only looks at IR (Incident Request) tickets that have been submitted. In my organisation we do not use Service Requests or Change Requests but if you do you can try modifying the code.
This code is offered freely for you to investigate and carries with it no warranty or anything like that.
Hello and welcome to my new blog. Over the coming weeks, months, and years I hope offer what advice, tips, or tricks I have discovered in my time as an IT professional. I’ll also share some of my custom-built work in the hopes that it helps others.