Is that a typo or the VM is connected to the partition via iSCSI? Also please include your support case ID when posting about technical issues.A VM running Windows Server 2012 got a second partition for WSUS (ISCSI 0:1)
Actually there are "SCSI" nodes in Hyper-V settings, not iSCSI, that's why I got confused. Not a big deal, nevermind.ISCSI 0:1 means the disk-order set in the hyper-v machine-settings - in fact it's a VHDX-Disk.
Have you checked repository load control settings?On more thing: The logfiles are telling that the repository isn't ready (just for that single machine).
You should open a new case if you want our support team to address the disk-exclusion issue.The case you mean is related to a company I worked before - different country and different infrastructure
Users browsing this forum: Google [Bot] and 13 guests