Scott Ivey's questions

I have a windows failover cluster running Server 2016 for a SQL 2017 Enterprise Availability Group. We have no shared disks on the server, just separate storage on each machine for the SQL AG. On both sides of the cluster, we've got storage spaces running stripes of 1TB disks for storage. (This is in azure, so it's stripes of P30 disks.)

I need to add capacity to the stripe, so I added 1 additional 1TB disk to the storage pool, and then tried to run the optimize-storagepool command to spread the data onto the new disk, but it failed. The error message I get looks like this:

        Optimize-StoragePool : The operation is not supported while the cluster is being upgraded.
    Activity ID: {b2a5cd56-0d4a-4904-92b7-1b6a4ccb7203}
    At line:1 char:1
    + Optimize-StoragePool -InputObject $pool
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (StorageWMI:ROOT/Microsoft/...SFT_StoragePool) [Optimize-StoragePool], CimEx
        + FullyQualifiedErrorId : StorageWMI 40009,Optimize-StoragePool

... but our cluster is not being "upgraded." How do I get past this, and make the cluster know that it's no longer being upgraded? Or can I force the opimize-storagepool to happen some other way?

I have an HP MicroServer that I use for dev/test. I've successfully installed Windows 2019 Server Standard on it (a dozen times now!) - and everything works great until I add the Hyper-V role. (This server was previously running Windows Server 2016 with Hyper-V with no issues.)

Once I add the Hyper-V role, and reboot, the thing just goes into a boot loop. When the boot loop happens, there is no BSOD, just a reboot every time. I've tried to boot into "safe mode" and remove the role, but even after doing that, it just continues in a reboot loop. After a few failed boots, it'll kick into the automatic repair screen, and that appears to be no help.

What is the best way to troubleshoot this and get Hyper-V installed? I've tried adding the role via the server manager, powershell, the new Windows Admin Center - and have the same results every time. Am I missing some sort of prerequisite for Hyper-V that the installer isn't adding automatically?

I have System Center Virtual Machine Manager 2008 R2 installed, and have a Hyper-V R2 host and a Virtual Server 2005 host. I'm trying to migrate my machines from the VS2005 host to the Hyper-V host, and keep getting the following error...

VMM is unable to complete the requested file transfer. The connection to the HTTP server myserver.mydomain.local could not be established. (Unknown error (0x80072efd))

Recommended Action Ensure that the HTTP service and/or the agent on the machine myserver.mydomain.local are installed and running and that a firewall is not blocking HTTPS traffic.

(Note - migrations between Hyper-V hosts managed by the VMM server work fine - my problem is just going from VS2005->Hyper-V hosts)

I have no firewalls turned on on either of the servers, and no firewalls in the middle. I've looked all over for answers to this problem, and am getting nowhere. All the articles I find when searching are talking about either V2V or P2V - and i'm just trying to do a straight migrate VM.

I've tried rebooting the boxes, changing the BITS SSL port number, restarting services, triple-checking firewalls, etc.

Does anyone have any good suggestions as to how I can resolve this problem?

In windows 7 we now have the ability to create and attach VHD files as drives. Does anyone know how we can compact the dynamic disks from within windows 7?

I have a problem with Win7 & VirtualPC - every time I start up a virtual machine, it appears to start fine, and then about 10 seconds into the boot process, my laptop either BSOD's or just hangs.

I have a Dell Inspiron 1721 notebook that i've been running the x86 version of Win7 on - and have had the issue with both build 7000 & 7100. I also have the issue with the Windows Virtual PC beta and with the Virtual PC 2007 product.

I've tried to use WinDBG to get what I can out of the minidump files - but i'm not sure if I have that set up correctly. Here's what I get from that...

CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 00000061, Clock interrupt time out interval in nominal clock ticks. Arg2: 00000000, 0. Arg3: 807c4120, The PRCB address of the hung processor. Arg4: 00000001, 0.

--Anyone know what I can look at to correct this? As a developer, i REALLY miss my virtual PC.