System Center Updates Publisher adds support for new OSes
Hello everyone, we are happy to let you know that an updated version of System Center Updates Publisher (SCUP) is now available and can be downloaded here. SCUP enables independent software vendors or line-of-business application developers to manage custom updates. Using SCUP, you can: Import updates from external catalogs (non-Microsoft update catalogs). Modify update definitions including applicability, and deployment metadata. Export updates to external catalogs. Publish updates to an update server. Read about it in the Enterprise Mobility + Security blog.
SCSM 2019 - Skip Activity Task for non-admins
Hello Community! So this is my first post and hoping it brings value for some of you! I currently work at Cireson and in my role I am heavily involved in the SCSM space. Recently I had a request from a customer to ask if there was a 2019 version of the below Custom Task that Rob Ford built: https://gallery.technet.microsoft.com/SCSM-2012-Skip-Activity-5a3a763d#content I noticed that there wasn't (Well I couldn't find one!), so decided to refactor Rob's code and get this working for 2016/2019. The aim of this task is to allow non admins to skip activites in the console as the out of the box task is admin only. So simply this is just a task override. Attached you will find an .mpb file which contains the .xml, the icon and the .dll which is running the code for the task. Just import the .mpb into your SCSM environment and give it a test! Let me know what you think and if this will help. Thanks, ShaneFirst System Center Semi-Annual Channel release now available
We are excited to announce that System Center, version 1801 is now available. Based on customer feedback, we are delivering new features and enhancements in this release including improved Linux monitoring support, more efficient VMware backup, additional support for Windows Server, and improved user experience and performance. System Center, version 1801 is the first of our Semi-Annual Channel releases delivering new capabilities at a faster cadence. Semi-Annual Channel releases have an 18-month support policy. In addition, we will continue to release in the Long-Term Servicing Channel (LTSC) at a lower frequency. The LTSC will continue to provide 5 years of mainstream support followed by 5 more years of extended support. Read about it in the Azure blog.Add localization to Service Manager 2016 Self-Service Portal (with Estonian localization sample)
Introduction As setting up Service Manager 2016 Self-Service Portal we wanted to add Estonian localization to the new HTML Self-Service Portal as we had done with the old one. Without too much hassle we figured out how language files are added and where the files are so the next steps were to translate the new localization file and make a minor adjustment to "Company" title to make it change with localization. Steps to add a new localization Step 1: Create the missing localization file to the following folder on you SSP IIS server In our case we created the following file: SelfServicePortalResources.et.resx C:\inetpub\wwwroot\SelfServicePortal\App_GlobalResources\ Step 2: Add the missing localization by adding a line to _Layout.cshtml file in the following folder C:\inetpub\wwwroot\SelfServicePortal\Views\Shared\ You can choose your own position but I set Estonian as first on the list and either delete the ones that you don't need or comment them out with <!-- comment --> tags. <ul class="lang_menu hidden" data-select-lang=@currentCulture> <li value="et-EE">Eesti</li> <li value="en-US">English</li> <!-- <li value="fr-FR">français</li> <li value="de-DE">Deutsch</li> <li value ""> ..etc.. </li> --> </ul> That's pretty much it if you don't want to change the "Company" title when changing the localization. Step 3(optional): When you also want to make localization changes to change the "Company" title you need to make a tiny change to _Layout.cshtml file in the following folder C:\inetpub\wwwroot\SelfServicePortal\Views\Shared\ You need to change the following line from <div class="col span_15 logo">@System.Web.Configuration.WebConfigurationManager.AppSettings["CompanyName"]</div> to <div class="col span_15 logo">@Resources.SelfServicePortalResources.PageTitle</div> This change will make your "Company" title information come from the active localization file instead of console defined "Company" name. <data name="PageTitle" xml:space="preserve"> <value>Localized "Company" title</value> </data> Restrictions I know that Service Manager 2012 that was built on SharePoint 2010 supported only a specific set of languages but I would think that the new portal supports more. Resources (in attachments) Attached a .zip archive with translation files for Service Manager 2016 and if anyone is still looking for this a Service Manager 2012 localization. If you don't want to download a ready file you can alternatively copy-paste the SM16 code from Spoilers! below. SelfServicePortalResources.et.resx - SCSM 2016 SSP localization SilverlightModule_StringResources.ET.resx - SCSM 2012 SSP localization Sources http://www.lingoes.net/en/translator/langcode.htm - find your language code in this list Translated with the help of my dear colleaguesFrequent, continuous releases coming for System Center
In today’s digital world, customers expect companies to interact with them through applications, and managing and monitoring these applications and the infrastructure they run on is crucial. While more applications and workloads are moving to the cloud, managing on-premises resources remains an important job for most organizations. To help you deliver agile IT operations at the pace of the cloud across all your workloads, we are excited to announce that System Center will soon offer more frequent feature release cycles. This will give you the opportunity to try new features and provide timely feedback to inform the roadmap items for the upcoming releases. We will be delivering features and enhancements on a faster cadence in the next year, focusing on the highest priority needs of our customers across System Center components. You will see releases twice a year, aligned with the Windows Server semi-annual channel timelines. A technical preview is planned for release in the fall with the first production version available early next calendar year, and subsequent releases approximately every six months. These releases will be available to System Center customers with active Software Assurance. System Center Configuration Manager will continue to offer three releases a year to give you the latest updates for managing servers, PCs, and mobile devices. Read about it on the Hybrid Cloud blog.
VMM Module in PowerShell 7
With the latest news in the tech industry, when can we expect to see the System Center PowerShell modules to be supported in PowerShell 7.0? I believe MECM/MEM works in pwsh7 already but VMM doesn't at this point. Requiring a Windows machine to use the VMM module doesn't make a ton of sense.Dropdown menus not showing in SCSM 2022 - With Update Rollup 2
Dear Community, we have the following problem with our newly installed environment: Any kind of dropdown menu only shows values when hovering over it (e.g. Resolving an Incident or Classifications) - although you can navigate with the arrow keys. Have any of you experienced a similar problem?
System Center Orchestrator 2022 Web Console Issues
This is more for information for others that have experienced the issues I have with System Center Orchestrator 2022 and the Web Console. Issues Discussed: Runbooks not visible in the Web Console Cannot remove stale runbook server entries Runbooks checked out in Web Console Issue 1: Runbooks not visible in the Web Console. In this issue the left hand pane where the runbook structure should be populated is blank. Solution 1: Ran this query on the Orchestrator DB GRANT CONTROL ON ASYMMETRIC KEY::[ORCHESTRATOR_ASYM_KEY] TO [Microsoft.SystemCenter.Orchestrator.Admins] GRANT CONTROL ON SYMMETRIC KEY::[ORCHESTRATOR_SYM_KEY] TO [Microsoft.SystemCenter.Orchestrator.Admins] GRANT EXECUTE ON object::[Microsoft.SystemCenter.Orchestrator].[GetSecurityToken] TO [Microsoft.SystemCenter.Orchestrator.Operators] GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[Settings] TO [Microsoft.SystemCenter.Orchestrator.Operators] GRANT SELECT ON object::[Microsoft.SystemCenter.Orchestrator.Internal].[AuthorizationCache] TO [Microsoft.SystemCenter.Orchestrator.Admins] Issue 2: Unable to delete stale or orphaned runbook server instances I decommissioned some older runbook servers but was unable to delete them from any of the orchestrator consoles. Solution: Run these sql queries against the orchestartor database DELETE FROM [Orchestrator].[dbo].[CLIENTCONNECTIONS] WHERE [ClientMachine] = 'SCORCHRB' -- Here SCORCHRB is my Runbook Server Name. DELETE FROM [Orchestrator].[dbo].[ACTIONSERVERS] WHERE [Computer] = 'SCORCHRBServer' -- Here SCORCHRBServer is my Runbook Server Name. DELETE FROM dbo.OBJECTS where Name = ‘SCORCHRBServer’ -- Here SCORCHRBServer is my Runbook Server Name. Issue 3: Runbooks remain in the checked out state in the web console I have run into an issue where no matter how many times i check in a runbook, the runbook in the web console remains checked out. Solution 3: Run this sql query against the orchestrator database use Orchestrator GO Truncate table [Microsoft.SystemCenter.Orchestrator.Internal].AuthorizationCache DECLARE @secToken INT DECLARE tokenCursor CURSOR FOR SELECT Id FROM [Microsoft.SystemCenter.Orchestrator.Internal].SecurityTokens where ExpirationTime >= GETUTCDATE() OPEN tokenCursor FETCH NEXT FROM tokenCursor INTO @secToken WHILE @@FETCH_STATUS = 0 BEGIN PRINT 'Computing Authorization Cache for Security Token: ' + Convert(Nvarchar, @secToken) exec [Microsoft.SystemCenter.Orchestrator].ComputeAuthorizationCache @TokenId = @secToken FETCH NEXT FROM tokenCursor INTO @secToken END CLOSE tokenCursor DEALLOCATE tokenCursor
Application isn't being terminated in Application Group Deployment
So I have been working with my SCCM Desktop Engineer and we are configuring an Application Group deployment. However, what we have found out is that when you do an Application Group deployment you don't get the same option to "Automatically close any running executables..." check box as you do with a normal application deployment. So because we don't get this check box as an option, we notice that the application that is setup in the Install Behavior to terminate it isn't being respected and performed and thus the deployment fails. Can someone tell me what I might be missing in regards to making it so that when you create an Application Group deployment that it will respect the Install Behavior setup like it will at the application level, but at the Application Group deployment itself? Please let me know if there is any additional data or details I can supply to help find an answer. Thanks.System Center 2019 – What’s new
Microsoft just launched Windows Server 2019 and Windows Admin Center, which also raised the interest in System Center 2019. At Microsoft Ignite, Microsoft was talking about what is new in System Center 2019, the future of System Center, and how it fits in with Windows Admin Center and other management tools. Check out what is new in System Center 2019 here: https://www.thomasmaurer.ch/2018/12/system-center-2019/
