Test Layout

I recently upgraded storage on my Hyper-V server that hosts all of my virtual machines to SSD drives. As part of this, I got lazy for some of the VMs and copied the files manually from drive to drive by using File Explorer rather than moving the VM storage by using Hyper-V Manager. After the disk reconfiguration was done, I got this error for the VMs where I had simply copied the data. Synthetic SCSI Controller (Instance ID GUID) : Failed to Power on with Error 'General access denied error'. Account does not have permission to open attachment ' PathToVirtualDisk '. Error: 'General access denied error'. This is a permissions error indicating that the VM doesn't have access to it's own virtual hard disk. As part of my file copying, the VM level permissions were lost. You can see in the screenshot below that only System, Administrators, and Users have permissions. Normally, you should also see permissions for a GUID that represents the VM with Full control.

I have an annoying issue where I'm storing scripts in a path so long that it makes it awkward to work at the PowerShell prompt. Almost everything I do is wrapping onto the next line. So, to set the prompt to static text that doesn't include the path, use the following command: function prompt {"PS> "} If I'm working with PowerShell prompts connected to different Office 365 tenants, I'll put in text that identifies the tenant. If you do need to view the current directory, you can use Get-Location or $pwd .

I bought some new SSD drives for my test server that I run VMs on. The number of disks the system could handle was maxed out. So, I needed to shuffle around some data as part of the installation process. During my shuffling, I temporarily added two of the SSD drives and used them as normal drives (not in a storage pool). Later, I deleted the data from those drives and wanted to create a new storage pool with those two drives. However, I found that when I ran the wizard to create the new storage pool, the drives were missing (not listed). They were also not listed in the primordial pool. Using Server Manager, I tried: removing volumes resetting the drives reinitializing the drives taking the drives offline and online changing between GPT and MBR I saw some web site references to drives attached to RAID cards having duplicate identifiers, but mine were attached directly to the SATA interface and had unique identifiers. However, when I ran Get-PhysicalDisk , I noticed that the drives had