4

I am in the midst of migrating to a Hyper-V 2012 R2 cluster and am currently configuring the first host to connect to the iSCSI CSV via MPIO.

I "think" I have everything working properly but when I try to create a log file to verify via the MPIO properties (GUI) or invoke the "mpclaim -v" powershell command (or command prompt) while elevated as Admin, I get the following errors;

GUI - Failed to probe MPIO storage configuration. Access is denied.

Elevated Powershell/CMD - File creation failed. C:\Windows\System32\MPIO_Configuration.log. Error 5 Failed to write MPIO configuration to file. Access is denied.

I have only been able to locate one article relating to the same problem but the solution was not applicable to me. Someone made a reference to " Local Security Policy/Public Key Policies/Encrypting File System/Properties/Certificates" and to allow something there but when I go there on the local machine, there are no keys or anything.. just a message that says "No Encrypting File System Policies Defined".

Here's the article;

https://social.technet.microsoft.com/Forums/windowsserver/en-US/6526b8c8-0fa9-4b47-9c31-3463896ffd51/access-denied-trying-to-capture-mpio-config?forum=winserverfiles

Anyone have any insight into this?

Thank you in advance!

Steven Gedzyk
  • 77
  • 1
  • 5

2 Answers2

1

solution is (if you dont want to troubleshoot EFS certificates), create a small temporary VHD, attach it, format to FAT32 and you can save MPIO report there. ThIS is valid also for mpclaim -v (access denied issue).

ewashx
  • 11
  • 1
  • 1
    I would recommend you to add commands next to the explanation so it's a better formed answer and can be easier to follow :) – sysfiend May 11 '16 at 11:48
1

I used a USB thumb drive formatted as ExFAT and that worked as well. MPIO settings copied right over.

TheDel
  • 11
  • 1