<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Service Manager - Category - GoToGuy Blog</title><link>https://gotoguy.blog/categories/service-manager/</link><description>Service Manager - Category - GoToGuy Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 17 Feb 2017 12:07:19 +0000</lastBuildDate><atom:link href="https://gotoguy.blog/categories/service-manager/" rel="self" type="application/rss+xml"/><item><title>Cireson Portal 7.3 &amp;ndash; Admin Menu Items for Norwegian Disappeared</title><link>https://gotoguy.blog/2017/02/17/cireson-portal-7-3-admin-menu-items-for-norwegian-disappeared/</link><pubDate>Fri, 17 Feb 2017 12:07:19 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2017/02/17/cireson-portal-7-3-admin-menu-items-for-norwegian-disappeared/</guid><description>After upgrading a couple of customers and our own environment til the latest Cireson Portal 7.3, I saw that the new re-arranged Admin menu was missing some expected menu elements. This is what I saw: image After investigating I found that the reason was if the logged on Admin user was configured with Norwegian display language. When I switched to English, I saw this Admin menu: image To solve this I navigated to the Localization Settings and checked the list for NOR that missed translations, and provided Norwegian translations for every related setting for the Admin menu (both the links and the labels at each admin section): image After that I could switch back to Norwegian display language again, now showing the correct Admin menu: image</description></item><item><title>Experts and Community unite at last ever #SCU_Europe 2016! #ExpertsLive next</title><link>https://gotoguy.blog/2016/08/31/experts-and-community-unite-at-last-ever-scu-europe-2016-expertslive-next/</link><pubDate>Wed, 31 Aug 2016 09:36:18 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/08/31/experts-and-community-unite-at-last-ever-scu-europe-2016-expertslive-next/</guid><description><![CDATA[This years SCU Europe 2016, for the first time outside Switzerland in the 4th year running, was held in Berlin at the BCC (Berlin Congress Center) close to the Alexander Platz in the eastern parts of “Berlin Mitte”.
[caption id=&quot;&quot; align=&ldquo;alignnone&rdquo; width=&ldquo;625&rdquo;] image View from Park-Inn by Alexander Platz [/caption]
The intro video introducing the Experts: https://vimeo.com/180473884 Let’s begin with the end: at the closing note SCUE general Marcel Zehner announced and with a little bit of emotion that this was the last ever SCU Europe to be held.]]></description></item><item><title>Publish the itnetX ITSM Portal with Azure AD App Proxy and with Conditional Access</title><link>https://gotoguy.blog/2016/08/30/publish-the-itnetx-itsm-portal-with-azure-ad-app-proxy-and-with-conditional-access/</link><pubDate>Tue, 30 Aug 2016 13:13:10 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/08/30/publish-the-itnetx-itsm-portal-with-azure-ad-app-proxy-and-with-conditional-access/</guid><description>Last week at SCU Europe 2016 in Berlin, I presented a session on Application Publishing with Azure AD. In one of my demos I showed how to use Azure AD Application Proxy to publish an internal web application like the itnetX ITSM Portal. The session was recorded and will be available later at itnetX’s Vimeo channel and on Channel 9. In this blog post I will detail the steps for publishing the portal in Azure AD, and also how to configure Conditional Access for Users and Devices.</description></item><item><title>Notifying End Users that Incident is Closed When They Reply by Exchange Connector</title><link>https://gotoguy.blog/2016/03/31/notifying-end-users-that-incident-is-closed-when-they-reply-by-exchange-connector/</link><pubDate>Thu, 31 Mar 2016 06:21:36 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/03/31/notifying-end-users-that-incident-is-closed-when-they-reply-by-exchange-connector/</guid><description>A common challenge by using Exchange Connector and Service Manager is that when the Incident is set to status Closed, users still can reply to the Incident Record by using E-mail. Even though the Incident is Read-Only when Closed, it is still possible to create related End User Comments via the Exchange Connector. While the Exchange Connector cannot be configured in a way that it will not create those End User Comments based on Status, it would be nice to at least inform the user that the Incident is now Closed, and that they must create a new Incident record either via E-mail or the HTML portal.</description></item><item><title>Displaying Service Manager Service Requests Stats in OMS via Performance Collection and Operations Manager</title><link>https://gotoguy.blog/2016/02/24/displaying-service-manager-service-requests-stats-in-oms-via-performance-collection-and-operations-manager/</link><pubDate>Wed, 24 Feb 2016 08:26:00 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/02/24/displaying-service-manager-service-requests-stats-in-oms-via-performance-collection-and-operations-manager/</guid><description>Following up on my previous blog article on how to collect Service Manager and Incident statistics via Operations Manager to OMS, https://systemcenterpoint.wordpress.com/2016/02/19/collecting-service-manager-incident-stats-in-oms-via-powershell-script-performance-collection-in-operations-manager/ , this blog article will show how to get statistics for Service Requests and display that as Performance Data in OMS.
Getting Ready Please see the link above for the first article on getting SCSM data to OMS, and instructions for configuring your Operations Manager environment and SMLets PowerShell module.</description></item><item><title>Collecting Service Manager Incident Stats in OMS via PowerShell Script Performance Collection in Operations Manager</title><link>https://gotoguy.blog/2016/02/19/collecting-service-manager-incident-stats-in-oms-via-powershell-script-performance-collection-in-operations-manager/</link><pubDate>Fri, 19 Feb 2016 01:18:36 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/02/19/collecting-service-manager-incident-stats-in-oms-via-powershell-script-performance-collection-in-operations-manager/</guid><description>I have been thinking about bringing in some key Service Manager statistics to Microsoft Operations Management Suite. The best way to do that now is to use the NRT Performance Data Collection in OMS and PowerShell Script rule in my Operations Manager Management Group that I have connected to OMS. The key solution to make this happen are the &amp;ldquo;Sample Management Pack - Wizard to Create PowerShell script Collection Rules&amp;rdquo; described in this blog article http://blogs.</description></item><item><title>Publish Operations and Service Manager Consoles as Azure RemoteApp Programs</title><link>https://gotoguy.blog/2016/02/02/publish-operations-and-service-manager-consoles-as-azure-remoteapp-programs/</link><pubDate>Tue, 02 Feb 2016 22:15:35 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/02/02/publish-operations-and-service-manager-consoles-as-azure-remoteapp-programs/</guid><description>This blog post will show how you can publish System Center 2012 R2 Management Consoles like the Operations Console and Service Console as Azure Remote Apps. I already have an environment in Azure that runs Service Manager and Operations Manager 2012 R2. Now I want remote clients and platforms to be able to run these consoles as remote apps. When planning, I decided to use a Hybrid Collection, and the overall steps was (as documented in https://azure.</description></item><item><title>Getting SCSM Object History using PowerShell and SDK</title><link>https://gotoguy.blog/2016/01/27/getting-scsm-object-history-using-powershell-and-sdk/</link><pubDate>Wed, 27 Jan 2016 19:56:54 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2016/01/27/getting-scsm-object-history-using-powershell-and-sdk/</guid><description>Some objects in the Service Manager CMDB, does not have the History tab. For example for Active Directory Users: image This makes it more difficult to keep track of changes made by either the AD Connector or Relationship Changes. Some years ago this blog post from Technet showed how you could access object history programmatically using the SDK and a Console Application: http://blogs.technet.com/b/servicemanager/archive/2011/09/16/accessing-object-history-programmatically-using-the-sdk.aspx I thought I could accomplish the same using PowerShell and the SDK instead, so I wrote the following script based on the mentioned blog article:</description></item><item><title>Creating SCSM Incidents from OMS Alerts using Azure Automation – Part 2</title><link>https://gotoguy.blog/2015/12/08/creating-scsm-incidents-from-oms-alerts-using-azure-automation-part-2/</link><pubDate>Tue, 08 Dec 2015 16:58:17 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2015/12/08/creating-scsm-incidents-from-oms-alerts-using-azure-automation-part-2/</guid><description>This is the second part of a 2-part blog article that will show how you can create a new Service Manager Incident from an Azure Automation Runbook using a Hybrid Worker Group, and with OMS Alerts search for a condition and generate an alert which triggers this Azure Automation Runbook for creating an Incident in Service Manager via a Webhook and some contextual data for the Alert.
Part 1: Create an Azure Automation Runbook that connects to and generates an Incident in Service Manager via a Hybrid Worker Part 2: Create an OMS Alert that searches for a specified log event and triggers the Azure Automation Runbook with some contextual data for the Incident In Part 1 of the blog I prepared my Service Manager environment, and created Azure Automation Runbook and Assets to run via Hybrid Worker for generating incidents in Service Manager.</description></item><item><title>Publish the Service Manager Self Service Portal with Azure AD Application Proxy</title><link>https://gotoguy.blog/2015/09/23/publish-the-service-manager-self-service-portal-with-azure-ad-application-proxy/</link><pubDate>Wed, 23 Sep 2015 21:02:12 +0000</pubDate><author>Jan Vidar Elven</author><guid>https://gotoguy.blog/2015/09/23/publish-the-service-manager-self-service-portal-with-azure-ad-application-proxy/</guid><description>The Scenario Updated blog post: 10th November 2015. With todays release of Update Rollup 8 for Service Manager 2012 R2 (https://www.microsoft.com/en-us/download/details.aspx?id=49556 ) and the new HTML5 based Self Service Portal, I have made some changes to this blog post where the scenario is updated. Please read on for how to publish this portal externally via Azure AD App Proxy: Recently in a SCSM LyncUp call news came of a coming Self Service Portal that the Service Manager Team are working on.</description></item></channel></rss>