During migration and upgrade process of our SCVMM server from 2012R2 to 2016 version we ended up with having our old and decommissioned VMM server.
We wanted to upgrade Servers to Windows server 2016 and to SQL 2016 version.
As part of this migration and upgrade, we ended up migrating and restoring our VMM DB to new server, and deploying new VMM.
As result we had fully functional SCVMM 2016 server. One thing was bugging me is that there was information in SCVMM that we have two SCVMM servers as part of infrastructure. One SCVMM server was running and responding state and second was unresponsive with no option to remove it using SCVMM console.
Continue reading “Removing orphan VMM Server from SCVMM.”
Issue and Logs
After checking through logs, I noticed that in 30 minutes interval we get bunch of Event ID 113 that source is MSiSCSI.
iSCSI discovery via SendTargets failed with error code 0xefff0024 to target portal *10.1.1.30 0003260 B06BDRV\L4SC&PCI_163A14E4&SUBSYS_045F1028&REV_20\5&6a108d3&0&30050200_0 .
Since, this host is part of Failover cluster, I was worried if we have some issues.
Based on Microsoft KB article it indicates the network issue.
Continue reading “iSCSI discovery via SendTargets failed – Event ID 113”
Event ID 1254 and 1069.
I came across with issue of unable to start VM. The affected resource was Virtual machine configuration file was “lost”
The event shows that Event ID 1254 and 1069.
Continue reading “Event ID 1025— Cluster failed to bring clustered role “VM1” online…”