So after the release of 3.0 at the beginning of week there were some comments of desired features and bugs reported. I’ve sent those to Damian and as he is working on fast release cadence a new version is now ready to address those comment. Additionally we are including another friend and fellow MVP Cameron Fuller to the authors. We are now on version 3.0.1 with the following changes:
- Added Date to the Output object as requested
- Changed the behavious for the Write-CMTrace function to actually use the supplied log path, and not just the default (Sorry that was a bug)
- Added a switch to flag that MSI files should be extracted, based on a script from Cameron Fuller. Just add -Extract and enjoy.
All credits go to Damian and Cameron.
You can find the latest version here.
This blog post is to inform you that several MPs have been updated with some important fixes/features. You can find all the information here.
My personal best improvement is:
- Add Task launch PowerShell session on the remote machine for All Computers
So my good friend Damian Flynn and fellow MVP has decided to bring this script to another level by making more like PowerShell module than only script. The result is cleaner code and some parts can be reused. You can find the new version here. Some of the changes include:
- Refactored the script to a powershell module, and split the code into functions to ease support and prepare for some automation ;)
- added Write-CMTraceLog – to enabled it execute Get-SCOMManagementPacks –CMTrace
- removed two download links that are incorrectly gathered at the beginning
I hope you will like these improvements. Leave any feedback on the TechNet Gallery page. This is why community rocks. Expect more from Damian on this topic.
I would like to bring you two survey that you should fill in:
I’ve just released a PowerShell script similar to the ones released by Advisor team. The search in Advisor is focused on Required Updates for servers. You will need System Update Assessment Intelligence Pack enabled in Advisor. You can find the script here.
I’ve just received a message from Daniele Muscetta – one of the PMs for System Center Advisor that there are still slots available for the preview. So if you want to try it yourself head here for instructions.
SCSMWhile I was on vacation UR3 for System Center 2012 R2 and Windows Azure Pack was released. In this release the following components were up for update:
As always there are some important fixes and feature in this updated so I recommend to apply it. Of course first in your Test/Dev environment.
Here are some tips that you might find useful during deployment:
- VMM update contains a SQL script that you will need to execute against the VMM DB. That script you can find in the KB for the update;
- VMM Management Packs are also updated so you will need to import the new versions in SCOM. If one of the MPs fail during import try importing them again.
- VMM contains a DHCP extension plugin that is installed on Hyper-V hosts. There is updated for that extensions that you will need to apply manually. More here.
- When you update VMM management packs you might receive Report deployment error for ‘Microsoft.Virtualization.Reports.ForecastMachineGroupNetworkIO’. I would guess that this is some kind of a bug that will be fixed. Not a fatal one.
- When you apply VMM server update you may need to stop SCOM health service and Virtual Machine Manager agent service.
- SCSM update contains some special instructions of executing PowerShell script after update. You will find the information in the KB.
- When you apply SCSMA update for Runbook worker you will need to stop the Runbook Service.
- Updating SCOM will require executing scripts against OperationsManagerDB and OperationsManagerDW. Those scripts will be available in your SCOM installation folder after applying the update. It is better to stop your SCOM services on your Management servers while applying them.
- To update SCOM agents to UR3 you will need to reject them trough Pending Management and do repair trough Agent Managed.
- After update of SCOM Gateway server you will need to copy the new version of SCOM agent manually.
- After updating DPM agents on Hyper-V hosts you will need to restart the Hyper-V hosts in order backup to work.
- When DPM agents are updated on Hyper-V hosts and hosts are restarted you will need to do consistency check on backups of VMs.
- Remember to update consoles for SCSM, SCOM and VMM on places you have them installed.
Hope this was helpful for you.