VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

 VMware Workstation and Hyper-V are not compatible. Remove the Hyper-V role from the system before running VMware Workstation.

This is because the Hyper-V role is installed and this conflicts with VMware Workstation. To disable



Hyper-V from starting the following command can be used:

bcdedit /set hypervisorlaunchtype off

A reboot of of the Windows OS is necessary.



To enable the Hyper-V role again use the following command:

bcdedit /set hypervisorlaunchtype auto

A reboot of of the Windows OS is necessary.

OpsMgr Management Configuration process fails with timeout exception

Log Name:      Operations Manager 
Source:        OpsMgr Management Configuration 
Event ID:      29181 
Level:         Error 
User:          N/A 
Computer:      server.domain.com 
Description: 
OpsMgr Management Configuration Service failed to execute ‘DeltaSynchronization’ engine work item due to the following exception 
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperationTimeoutException: Exception of type ‘Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperationTimeoutException’ was thrown. 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation operation, String operationName) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.WriteConfigurationDelta(IConfigurationDeltaDataSet dataSet) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.TransferData(String watermark) 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.DeltaSynchronizationWorkItem.ExecuteSharedWorkItem() 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.SharedWorkItem.ExecuteWorkItem() 
  at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.ConfigServiceEngineWorkItem.Execute()

Solution
========
We can increase the timeout using the following method on all management servers:

Make a backup of "x:\Program Files\System Center 2012\Operations Manager\Server\ConfigService.Config"
Increase the timeout values in ConfigService.config for the following:
<OperationTimeout DefaultTimeoutSeconds="30"> to 300 seconds
<Operation Name="GetEntityChangeDeltaList" TimeoutSeconds="180" /> to 300 seconds.
Restart the configuration service

SCDPM - An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041024) (0x80041024))

Analysis

=========

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)
An unexpected error occurred while the job was running. (ID 104 Details: Unknown error (0x80041024) (0x80041024))

Solution

========
To resolve this issue open the settings of the affected virtual machine in the Hyper-V Console. Under Management go to Integration Services uncheck “Backup (volume shadow copy)”. After that, return to Data Protection Manager and perform a consistency check.

SCVMM 2016,Error (2912) An internal error has occurred trying to contact an agent when creating new VM

To solve this problem you could change the BITS port SCVMM is using during transfers:

1. On your VMM Server open the Registry

2. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings

3. Locate BITSTcpPort which should have a value of decimal 443. Change this to some port unused in your environment. (e.g. 8800)

4. Restart Virtual Machine Manager Service so that the change takes effect.

SCOM 1807 - User can choose to enable/disable APM component while installing agent

This feature allows more flexibility to the users by providing an option to enable/disable APM component in the agent

Fail discovery JBoss after only Import one JBoss MP

JBoss的探索與舊版的JBoss MP有相依性，所以建議匯入所有JBoss MP

SCOM 2016 – Linux Agent Deployment “Signed certificate verification operation was not successful”

If you are facing this scenario and your UNIX/Linux server has a different hostname then what is in DNS you have two choices. Either you change the hostname on your server, which may or may not be an option, or you create a new certificate with the FQDN hostname and private key without touching the server name at all using the scxsslconfig tool. I decided to perform the latter. Just open the a shell and run…

/opt/microsoft/scx/bin/tools/scxsslconfig –h Linuxname –d domainname.com -f –v

After executing the command, make sure to restart the agent.

/opt/microsoft/scx/bin/tools/scxadmin –restart

After the service is restarted head back to your SCOM console, and attempt to manage the Linux server again.