my personal blog about systemcenter

Virtual Machine Manager 2016 TP2 Require SQL Enterprise Edition

Categories: Uncategorized
Comments Off on Virtual Machine Manager 2016 TP2 Require SQL Enterprise Edition

So at least for now during the preview manually installed VMM require SQL Enterprise Edition and not Standard

Will be interresting to see if this is still a requirement at GA , and if the SQL entitlement will follow


The Virtual Machine Manager database was not created.
The Virtual Machine Manager database was not created. Delete NO_PARAM.mdf and NO_PARAM_log.ldf if they exist at NO_PARAM or use a unique name for the database. Also, verify that disk quota management is not enabled for the drive where the database is being created. Then run Setup again.
09:15:47:Failed sql script: Threw Exception.Type: Microsoft.VirtualManager.DB.CarmineSqlException, Exception.Message: Unable to connect to the VMM database because of a general database failure.
Ensure that the SQL Server is running and configured correctly, then try the operation again.
09:15:47:StackTrace: at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlContext.ExecuteNonQueryCommand(String command, Action`1 parameterAdder)
at Microsoft.VirtualManager.Setup.DBConfigurator.ExecuteScript(String fileName, IVmmDbTransaction tx)
09:15:47:InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Online index operations can only be performed in Enterprise edition of SQL Server.
09:15:47:InnerException.StackTrace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.VirtualManager.DB.SqlRetryCommand.ExecuteNonQuery()
09:15:47:Out of Impersonation

Updated 2012 R2 ISO includes November Update.

Categories: Uncategorized
Comments Off on Updated 2012 R2 ISO includes November Update.









Includes November 2014 update roll up, please review KB3000850 for more information.

Before installing this product please review KB2966870.

Automatic Virtual Machine Activation
Release Notes: Important Issues in Windows Server 2012 R2



Not sure how i missed this but there is a “new” ISO on MVLS and MSDN for download that includes the large November update so easier / faster to baseline a new host after install

Thank you Microsoft


Error 25250 Unable to find Adapter

Categories: Hyper-V, Virtual Machine Manager, Windows Server 2012 R2
Comments Off on Error 25250 Unable to find Adapter



Error (25240)

Adding a member to the adapter team Applications failed with error Unable to find Adapter HP FlexFabric 20Gb 2-port 650FLB Adapter #2 in Team after addition

Recommended Action

Ensure the team is functioning correctly and retry the operation.

I ran into the following problem applying a Logical Switch to a some shiny new hyper-v hosts , i could select the adapters and create the Logical Switch , but appyling it ended up in a rollback after it tried to add the 2nd adapter to the team


After looking around for a bit i saw that the 2nd network card was disabled in Windows


And after enbling the network card everything was green again

So always check the cable Smiley err i mean the network card

Adding HP Blade Centers to Operations Manager

Categories: HP, Operations Manager, SCOM
Comments Off on Adding HP Blade Centers to Operations Manager


Install the HP Blade Management pack on a host with a Operations Manager Agent Installed


Add Onboard Administrator , to start with later we can add virtual connect domain


Add DNS/Ip and username / password to the HP Blade Onboard Administrator


And we have a few to start with


And now the waiting game start


Discovery is every 4 hours or if you kick the agent , just after a litle while


And after a bit we have the first enclosures in the monitoring and ready to add more.

‘VMNAME’ could not initialize. (Virtual machine ID GUID)

Categories: Hyper-V, NetApp
Comments Off on ‘VMNAME’ could not initialize. (Virtual machine ID GUID)

Recently ran into a issue where i couldnt start a VM located on a NetApp Running SMB 3.

Rights on the filesystem looked without issue , opening the vhd over the network worked but anything manipulated from HYper-V failed with a resource attached to the system failed.

After digging around a bit i found that the time was shifted on the NetApp box so any kerebous authentication failed


And the culprint on the NetApp was

secd.kerberos.clockskew: Kerberos client or node clock skew error (-1765328351). 

Description :

This message occurs when there is a “time error”(clock skew, time skew, time out of bounds). This error indicates that there is a time discrepancy between client and node or client and Key Distribution Center (KDC). The kerberos authentication request from the client was forwarded to the KDC and it failed because the timestamp encrypted in the client’s kerberos ticket was different by more than the maximum time difference that is configured on the KDC.

Action :

Ensure that the clock time of the node is identical to that of the client and to that of the KDC. Ensure that the correct time zone setting is selected on the node. To keep the node and KDC time clocks in synchronization automatically, configure Network Time Protocol (NTP) services on the node. You might also want to increase the clock skew interval. To do so, modify the kerberos-realm configuration clock-skew (“Maximum tolerance for computer clock synchronization” in Windows(R) Active Directory) parameter from the default 300 seconds to 600 seconds or more. Note: Increasing the clock-skew interval makes the client protocols less secure against network replay attacks.

and then setting a NTP server that actually worked then everything was working again after a few minutes.

And then setting a NTP server on the NetApp box that are in sync with ActiveDirectory = Sucess.