Microsoft has published a new Hotfix 3208888 for those who are running SCVMM 2016 Update Rollup 1. This includes a fix for the issue where when you use VMM to live migrate a VM from one host that’s running one version of Windows Server 2016 to another host that’s running a different version of Windows Server 2016, the placement page assigns a zero rating to the target host.(i.e Datacenter edition to Standard edition). This issue happens only when you try to live migrate between two version of Windows Server 2016 but not when you are trying a live migration between hosts that are running 2012 R2 and 2016.
This leads to block the live migration with below error message:
Unable to migrate or clone the virtual machine VM_name because the version of virtualization software on the host does not match the version of virtual machine’s virtualization software on source version_number. To be migrated or cloned, the virtual machine must be stopped and should not contain any saved state.
Note the this is applicable only to those who are running SCVMM 2016 Update Rollup 1.
- Download the KB package from here.
- Use an elevated Command Prompt to install the KB manually.
msiexec.exe /update kb3208888_vmmserver_amd64.msp
In Operations Manager sometimes you may need to revert back to an older version of a Management Pack for a particular workload. The Operations Manager UI allows to delete and re-import MPs from the “Installed Management Packs” screen. The problem happenes when there are multiple and multi-level dependencies on the MP that you are trying to delete.
However now there is an enhanced version of a script available at TechNet (developed by MSFT employee Christopher Crammond) that will help you to revert Management Packs with a single command.
Using the Script
- Open the Operations Manager Command Shell prompt as an Administrator.
- Download the script to remove a management pack with dependencies from here.
- Execute the script as below.
.\RecursiveRemove.ps1 <ID or System Name of the MP>
- For an example if you want to remove the SQL 2014 Disocvery MP run the script as below.
How to get the the ID or System Name of an MP?
- Selecting the MP that you want to delete in the Installed Management Packs view by clicking Properties in the Actions pane.
- Copy the content in the “ID :” text box in the General tab.
In my last post I’ve shared the console crashing issue you face after installing the security updates in MS16-118 and MS16-126. Now Microsoft has published a new KBs to fix the console crashing issue in SCOM after applying these updates.
Individual hot fixes are available for the following list of Operating systems which you can download from here.
- Windows Vista
- Windows 7
- Windows 8.1
- Windows Server 2008
- Windows Server 2008R2
- Windows Server 2012
- Windows Server 2012 R2
For Windows 10 and Server 2016, the fix was applied to the latest cumulative updates.
It seems like the October 2016 cumulative Windows updates (KB3194798, KB3192392, KB3185330 &KB3185331) cause the SCOM consoles 2012/2016 in all Windows versions from Windows Server 2008 R2 up to 2016 and Windows 7 up to 10 Windows 10 to regularly crash without any doubt.
According to Microsoft Germany’s SCOM PFE Dirk Brinkmann who has blogged about this issue here, the SCOM team is working on a fix for this as of now and no ETA for an resolution has been provided yet.
Once a fix is available you will be able to see it via SCOM team blog.
It’s not like everyday you might want to remove certain management packs from your SCOM management group. The most painful task is removing the dependent MPs as you need to manually track all of those and delete them first in order to successfully remove the parent management pack.
Microsoft Senior Software Engineer Chandra Bose has written a PowerShell script that can identify and remove all of the dependent management packs automatically in such situations. Lets explore that script a little in this post.
How to get started?
First of all you need to run the Operations Manager Command shell as an administrator, which should be a member of the Operations Manager Administrators group as well.
When you execute the script you can either provide the ID or the System Name of the parent management pack as below. You can find the MP ID by visiting Administration > Management Packs > Right click the desired MP and select properties > Look for the ID field in the General tab which shows the MP ID. The System Name is the unique name of the MP (i.e Microsoft.SQLServer.2012.Discovery)
.\RecursiveRemove.ps1 <ID or System Name of the MP>
You can download the RecursiveRemove.ps1 script from here.
Recently I was working in a SCVMM 2012 R2 deployment project and came across a DEFCON 1 situation. I was ready to uninstall everything and re-deploy VMM from scratch but I wanted to minimize the post installation configuration tasks after that. I came across a great post by the SCVMM team on how to achieve this with two SQL stored procedures and here is how I managed to save couple hours of the deployment time with that.
Although you seriously know what you are doing, it is wise to back up the VMM database first. Just in case if you manage to screw up the entire database you can always restore from a copy.
The entire process is clearly explained in this TechNet article so I’m going to skip the lecture. But there are few things that I followed based on my gut feeling to make it work in a single attempt.
- Stopped the VMM Server service before executing the first stored procedure and backing up the VMM database.
- I restored the backup VMM database using a dummy name and tested the stored procedures first to see there are any exceptions thrown during execution. Luckily it was successful. This is optional but it doesn’t hurt to try.
- After installing the secondary VMM server I made sure to install the relevant UR version that was installed previously in the old VMM instance. This is critical or otherwise the database will not be useful at all.
Now if you have a Highly Available VMM environment things might look a little scary (VMM service fails most of the times) but the article explains how you can safely use the existing database by stopping at starting the VMM service manually before and after proceeding with the setup.
When Microsoft released the Update Rollup 8 package for Service Manager 2012 R2 everyone was so excited to get hands on with the new HTML Self Service Portal replacing the SilverLight dependency. However there were number of issues with this release preventing customers from upgrading to new HTML portal. Recently Microsoft has released a hotfix (KB3124091) to overcome these issues in the UR8 package and to provide a much smoother user experience in the new HTML portal.
Bugfixes in KB3124091
- Affected user and Created by user is getting set to the service account
- Query type form element is not working for the Incident and User classes
- Request Offering forms are failing to load if a Query type form element is part of the form
- Username token is not passing values to the mapped field
- Cancelling request form does not work
- Text is overlapping for long strings inside the list in the middle pane
- Related activities inside My Requests always show state as active
- Filters inside My Requests and My Activities is not working for some languages
- Announcement is showing “Invalid Date” in Expired Date column for some languages
- Comments in the request are using incorrect class
- Required (mandatory) restriction is not working on query type form element
- Query form element allows multiple selection even when it is configured for single item selection
- Scroll bar does not work on some lower screen resolutions
- Double scroll bar appears while browsing Help Articles
- Some areas of portal are not rendering in Mozilla Firefox web browser
- My Activities shows 0 instead of removing the notification sticker when no activity is in progress
- With SSL enabled, the browser regularly prompts the message “Only secure content is displayed” with a button to “Show all content” while browsing the portal
- “Added by” inside the action logs show domain\username instead of the display name of the user
- Nested enumeration lists are now supported inside the Request offering forms
- Portal now allows you to share and access different objects inside the portal with direct URLs. You can refer individual items inside the portal with following URL formats –
- Request Offerings:
- Incident type requests:
- Service Request type requests:
- Manual Activities:
- Review Activities:
- Help Articles:
With dawn of the year 2016 almost upon us, Microsoft has released another build for it’s upcoming Windows Server & System Center 2016 suite of products. This Technical Preview 4 contains much new advancements and fixes based on customer feedback on the product clearly making it’s way as the cloud OS for next generation of computing.
Nano Server gets a new touch
Nano server, a headless installation option like server core which is going to be one of the installation option for Windows Server 2016 has improved a lot since last preview. In this release IIS & DNS server roles can be installed in Nano server in addition to existing Hyper-V & Scale-out File Server features.
Introducing Hyper-V Containers
Providing additional layer of isolation for Windows Containers, Hyper-V containers can be now deployed as virtual sandboxes to host application workloads. This technology utilizes the nested virtualization capability introduced in Windows Server TP4. Also you can use both docker & PowerShell to create, deploy and manage Windows Containers.
System Center 2016 Improvements
Another milestone is the System Center 2016 TP4 release with some awesome features for private cloud management. Now you can use the SCOM agent to monitor your Nano Servers in TP4. SCCM 2016 TP4 has introduced some new functionality to improve Windows 10 deployment experience via SCCM.
Mobile Device management (MDM): enhanced feature parity with Intune standalone – Many of the MDM feature that are supported via Intune standalone (cloud only) are also enabled for Configuration Manager integrated with Intune (hybrid) in this release.
Integration with Windows Update for Business – Now you can view the list of devices that are controlled by Windows Update for Business.
Certificate provisioning for Windows 10 devices managed via on-premises mobile device management
You can download Windows Server 2016 Technical Preview 4 & System Center 2016 Technical Preview 4 evaluation bits from here.
Savision has released their newest version of Live Maps Unity, which comes with great new features. In the new release, Savision has added more functionality on ways to proactively monitor business services with the advanced SLAs monitoring feature. Another great feature added to Live Maps Unity 7.5 is the new Web Portal.
Savision will be hosting two webinars to introduce the new features and show you how they work and how they can help you to make the most out of your SCOM environment.
Dennis Rietvink will be hosting the webinars. Dennis is Savision’s co-Founder and VP of Product Management. Savision will also be raffling a pair of HiFi Philips headphones amongst the attendees of the webinars.
Register for the webinars and find out more about the new features:
Advanced Service Level Agreement Monitoring
With this new feature, you can have more control over your SLAs as you will receive proactive notifications when they are in danger of being breached.
Brand New Web Portal
Get end-to-end service visibility and track interconnected infrastructure and applications from any mobile device, anywhere you are. Live Maps Unity is now Silverlight free.
Register now for any of the webinars:
EU Webinar – Wednesday, November 25th, 3:30 pm CET / 9:30 am EST
US Webinar – Tuesday, December 1st, 8:00 pm CET / 2:00 pm EST
Click here to register for the webinars.
It’s been a while since my last blog post. I’m working on a DPM 2012 R2 test lab these days which I’ve planned to update to the latest UR version. When I checked for the latest UR7 got to know that the bits have been re-released.
As for the DPM team there is an issue in DPM 2012 R2 UR7 released on 28.07.2015 which causes expired recovery points on the disk were not getting cleaned up, resulting an increase in DPM recovery point volume after installing UR7. This re-release has addressed this concern and you can download the upadted bits via DPM 2012 R2 UR7 KB or Microsoft Update Catalog as of today.
OK I have updated to UR7 before 21.08.2015. Now what?
For those who are facing this dilemma should know that the re-released UR7 is not pushed via Microsoft Update and advised to manually install the new package on the DPM Servers with older UR7 package installed. The installation process will automatically execute pruneshadowcopiesDpm2010.ps1 PowerShell script which contains the fix.
There is no change in the DPM version (4.2.1338.0) in this re-release and it will remain same after the update. Also you will have to update the Azure Backup Agent to latest version (2.0.8719.0) prior installing DPM UR7 to ensure the integrity of your cloud backups after this release.
For those who like me updating to UR7 the old fashion way (wait for a month or two, lookout for bugs and then update) you’ve got nothing to worry.