Microsoft Dynamics NAV 2013 management pack is now updated to support feature pack 1 of the application. The MP is version 1.1 but the downloads point to to other version one for SCOM 2007 (7.0.0.1) and one for SCOM 2012 (7.0.1.1). In the new version only the following change is made – Monitoring Microsoft Dynamics NAV Web Server instances added in Microsoft Dynamics NAV 2013 Feature Pack 1.
You can download the MPs and the guide for importing here.
As we are in the Q3 of the year the third update rollup for System Center is now available. Here are the changes:
When you try to add a Microsoft System Center 2012 Virtual Machine Manager (VMM) connection by using either the UI or a Windows PowerShell command, the connection is unsuccessful. Additionally, you receive the following error message:
Connection address must be a fully qualified domain name.
This problem may occur when the fully qualified domain name (FQDN) contains a hyphen (-) in the last part of the name.
When a Windows Azure subscription contains a high-memory (A6 or A7) Windows Azure virtual machine, Azure functionality is not available in Microsoft System Center 2012 App Controller. Additionally, you receive the following error message:
Retrieved data is incomplete.
When you click More details, you receive a "Service Unavailable" message. You may also receive a "Requested value ‘A6’ was not found" message.
When you try to use App Controller together with a proxy server, you receive the following error message:
(407) authentication required.
Note App Controller does not use configured proxy settings.
When you view the network properties of a deployed virtual machine and then click OK, the network connection is set to None. For example, the network connection field is empty and does not show the current network adapter.
When you move quickly between virtual machines in a list and then click the Properties task, the properties page for the previously selected virtual machine is displayed.
When you deploy an Azure virtual machine when the User must change password at next logon option is selected, you receive the following error message:
Bad Request
App Controller cannot be installed if the Microsoft SQL Server database server name starts with a number.
See Installation of App Controller to a Remote SQL Server fails with Exception Error Code: 0x80131500 for more information.
Setup incorrectly reports that the SQL Server database has insufficient disk space.
Setup on a non-English operating system is unsuccessful when it tries to enable Internet Information Services (IIS).
When you use a tape library that has many slots, the Microsoft System Center 2012 Data Protection Manager database becomes bloated over time.
When you try to set up library sharing when you use Data Protection Manager SP1 Update Rollup 2 (UR2), you receive the following error message:
Failed to execute RBACRolePermissionOnStoredProcScript.sql on DPMServer\Database
When you run a Windows PowerShell script that retrieves the protection groups, the console crashes.
The VMM Helper Service stops responding, and no virtual machines are backed up. A restart enables the backups to continue.
The Audit Collection Services (ACS) dtPrincipal tables sometimes are missing a user’s domain name.
If you decide to see more than two days’ worth of data in a Service Level Dashboard view, the data is displayed from the Daily Aggregated data and does not contain the last two days’ worth of data.
The Health Service stops collecting performance data on Windows Server 2008 R2.
The web console crashes when the Active Alerts view and the Windows Computer State view are accessed at the same time when Internet Explorer 9 is used.
A memory leak may occur in the console when the performance widgets dashboard is left open.
When the Operator role is used, many 26319 events are generated. This causes performance problems.
Health Service availability reports are incorrect because of duplicate entries in the HealthServiceOutage table.
When the Orchestrator Integration pack is under a high-load scenario, a software development kit (SDK) process deadlock may occur.
This update includes fixes to the following Advisor Connector issues:
The Solaris agent cannot be installed on Solaris 11.1 because it does not find the prerequisite OpenSSL package.
Knowledge editing pages are not displayed when monitors that were created by the Shell Command templates are edited.
Log files that are encoded in schemes other than ASCII cannot be monitored.
You receive an invalid prefix length error and cannot set migration subnets if the prefix length is not between 4 and 30 characters for IPv4 or between 64 and 126 characters for IPv6.
Migration subnets for cluster and cluster nodes must be read-only.
Virtual Machine Manager (VMM) cannot take any action on Recovery Virtual Machine (VM) post-failover without reverse replication.
In some cases, a virtual machine on an SMB file share that is registered by using a NetBIOS name on a cluster will be in an unsupported cluster configuration state in VMM. This problem may occur even though the virtual machine is healthy and running. Additionally, the virtual machine status cannot be updated after that.
The virtual machine refresher does not correctly update the state of the virtual machine even after an unsupported cluster configuration issue is corrected.
In a bare-metal setup, the VMM service crashes when an out-of-range IP address is specified.
Every time DRA Initialize occurs in the VMM service, a database corruption exception is received.
You receive an "Unable to connect to the VMM DB" exception when you try to publish host and virtual machine network data to the SQL Server Reporting Service.
When you try import a Linux template from VMware in Virtual Machine Manager 2012 Service Pack 1, you receive error 22723.
The Get-SCVirtualMachine cmdlet does not return virtual machines by their IDs when the virtual machines contain clustered pass-through disks.
A user cannot set the domain name in Service Setting.
The VMM service crashes intermittently.
The VMM ID registry subkey value is set to a null value after Update Rollup 1 is applied.
This update fixes some UI text issues in the Virtual Machine Manager 2012 Service Pack 1 console for Disaster Recovery and for the HRM Azure Service.
This update fixes some reports that are not working with SQL Server 2012.
If a virtual machine has a static IP address, Test Failover does not set the IP address on the test virtual machine.
Virtual machine snapshot operations might fail if multiple snapshots are restored at the same time and have the same name.
The VMM server might crash when you create a virtual machine template from a virtual machine that has a previous failed task checkpoint data.
Logical unit numbers (LUNs) for EMC storage cannot be assigned to a cluster in VMM.
The VMM service crashes if a VMWare cluster or host is added by using a local root or administrator account.
Some log information is recorded multiple times in the guest log file.
This update fixes some performance issues in a bare-metal installation.
The placement of the Network Load Balancing (NLB) clusters in a network environment does not work for NLB load balancer and nested host groups.
The VMM service may stop while VMWare vSphere 4.1 is updated.
If Test Failover is initiated while VMM is restarting, the recovery side of VMM crashes.
Installation instructions and download links you can find here.
Previously I’ve covered HP Storage Management Pack but now there is another HP Storage tool that integrates with System Center component named HP Storage UI add-in for System Center Virtual Machine Manager. These two tools combined together represent HP Storage Management Integration with Microsoft System Center.
So what is exactly this new tool:
HP Storage UI add-in for System Center Virtual Machine Manager (SCVMM) enables enhanced integration of SCVMM and HP Storage providing our customers a single pane-of-glass monitoring view of physical, virtual and cloud environments. It automates HP Storage management and provides an integrated view of VMs and associated storage resources.
HP Storage supports all SMI-S-enabled functionality introduced in SCVMM 2012 – Storage Discovery, Storage Classification, Storage Provisioning and Storage Allocation.
HP Storage also provides a new HP Storage UI Add-in for enhanced monitoring, provisioning and control of HP Storage in SCVMM environment.
Personally I haven’t the chance to try it but from what I’ve seen from demos and screenshots it is definitely worth a try if you have one of the following storages:
You can download it for free from here.
I was installing SCOM 2012 R2 Preview today and after the installation I’ve tried to access the Web Console to see if it is healthy but I’ve received error “The user credentials are invalid or user does not have permissions to access the application”:
For sure my account had access as I was working in the Operations Manager console at the same time.
How I solved it?
I’ve started IIS Manager and check what authentication methods are enabled. Windows Authentication was disabled so I’ve enabled it:
After that I’ve logged to the Web console without problem. This is not specific SCOM 2012 R2 preview issue I am sure it could be met in older versions as well.
If you’ve already installed SCOM 2012 R2 you’ve probably noticed that System Center Management Service is gone. Now we have Microsoft Monitoring Agent:
But that is not all folder location is also changed:
You will notice the change also in the Control Panel:
We already know that changes are not only in the name now but the service can actually can be leveraged by other products. Could we see in the future this agent be leverage by other products as well? May be something like Windows Azure Monitoring (WAM) or Windows Azure Operations Manager (WAOM)? We can only speculate for now and wait to see what will happen.
Note 1: This is not the first time the name of the service is changes in 2005 it was MOM, in 2007 RTM/SP1 it was OpsMgr Health Service and in 2007 R2, 2012 and 2012 SP1 it was System Center Management Service.
Note 2: The built-in agent in Service Manager 2012 R2 is also renamed to Microsoft Monitoring Agent in services.msc and Control Panel so if you need to restart Service Manager 2012 R2 health service you have to restart Microsoft Monitoring Agent. The installation folder of the agent is where Service Manager is installed.
Cloud Administrator in Azure World 