Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Identified issues with Hyper-V on Windows Server 2012, when using eSATA Intel MB Ports

Unanswered Identified issues with Hyper-V on Windows Server 2012, when using eSATA Intel MB Ports

  • Tuesday, September 25, 2012 12:48 PM
     
     
    Sign In to Vote
    0

    I can now confirm Issues with  hard drives being recognized by Windows Server 2012 and Hyper-V, while using the 5th SATA port ( RED SATA  eSATA 4) on Intel DH67BL & DH67GD  motherboards. Windows Server can recognize the drive and will operate properly, but Hyper-V has issues recognizing the hard drive and showing ""any"" folder structure on any hard drive connected to the SATA (eSATA) port on the motherboard.

    When in Hyper-V manager or even SCVMM 2012, HYper-V only sees the drive letter, and SCVMM 2012 does even see the drive letter.

    This issue is being experienced on two Windows 2012 Servers, using Intel motherboard, and also issues have been experienced with Win 8 Pro with Hyper-V and drives.

    So this means there are three Intel motherboards experiencing issues when using the internal 5th SATA (eSATA port - internal Red ëSATA Connector on Board).

    I suspect other users who are having VHD creation issues on drives are also working on newer motherboards.

     Note: This issue is was not experienced when using Windows Server 2008R2 and SCVMM 2008R2

    Hope this helps.......

    RF


    • Edited by RUOK2 Tuesday, September 25, 2012 12:50 PM
    •  
     

All Replies

  • Thursday, September 27, 2012 5:20 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Thank you for your question.
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

    Thank you for your understanding and support.

    Best Regards,
    Aiden

    TechNet Subscriber Support

    If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.

    Aiden Cao

    TechNet Community Support

     
  • Thursday, September 27, 2012 8:54 AM
     
     
    Sign In to Vote
    0

    Hi,

    Thank you for your response.....

    I have applied this "potential" remedy, that had been experienced with other Intel motherboards....

    ====================== Previous Post=======================================================

    I think this link below will provide the solution !!!!

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/b9c91808-67ee-4123-9d42-1f323d4d97e1

    Search for the Reg Key and view the subkeys, you will see it is relevant to Hyper-V also.....there are 40 + subkeys

    Looks like this

    0000

    0001

    >>

    >>>

    >>>>

    0040   ( this key for me Shows MS Hyper-V Virtualization Infrastructure Driver)

    0043  ( this key for me shows Microsoft Hyper-V Virtual Disk Server )

    We just have to follow the info in the link on how to deal / process / fix it

    --------------------------This issue I have with two 2012 Win Servers, also with Win 8 box......I had performed the steps ....but it has not cured the problem.....

    Hopefully this will be addressed either by MS, or by Intel updated chipset drivers....

    ============================================================

    Cross Thread to other users postings

    http://social.technet.microsoft.com/Forums/en-US/w8itprovirt/thread/20da7ff7-05a7-4085-8e67-258f11755f3d/

    You may want to pass this info to the appropriate people....

    Thank You

    Regards,

    RF

     
  • Thursday, September 27, 2012 11:54 AM
     
     
    Sign In to Vote
    0
    Hi , Thanks for your feedback. I would like to know if you have the latest chipest firmware updated and compatible with Windows 8 and windows server 2012. As I have no hardware to local reproduce, I will try to see if others have the same question. Thanks.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


     
  • Thursday, September 27, 2012 12:51 PM
     
     
    Sign In to Vote
    0

    Hi,

    Your welcome...........  Yes, I do have the lastest Intel Chipset Drivers installed......

    Notes:

    1.) Intel's chipset driver install works from the Win 7 x64 download, as was stated from an Intel Tech, it is only noted within the included text document for the Win 7 chipset drivers that they also support Win 8 ( I suspect they are not optimized for Win 8, more of a rush to market)

    2.) the drivers install without any errors or issues, but issue is not resolved.

    3.) The link I had provided from the other discussion relevant to the Intel Chipset driver issues and what they had stated for a potential resolution, I did check their recommendations and ( Microsoft's at that time) and the issue IS relevant to Win 8 & Win Srv 2012, and the permission issue had to be corrected in the registry permissions so that further reg keys would be displayed, their recommendation worked in regards to the Reg Keys, and the issue was the same on Win 8 and 2012, but it did not fix the issue.

    In regards to you having no hardware on site, I would suspect ANY newer PC ( Dell, IBM, Etc that has the Intel 6 Chipset on the board and supports 5 SATA connection to the board 4 Regular, one eSATA internal on board, would experience the same issue.

    Regards,

    RF

     
  • Thursday, September 27, 2012 2:55 PM
     
     
    Sign In to Vote
    0

    I have just again tried "after specifically" updating the chipset drivers for each component in Device Manager, since the Intel Chipset Drivers don't update everything......after successfully updating each component ......rebooting, and trying to create a VHD on Windows 8 Hyper-V .....all drives work, except one....the eSATA drive does not work.......So the issue pertains to BOTH Windows 8 and Windows Server 2012....and the integrated eSATA port ( 5th on board port) of three different newer Intel motherboard models......

    Note: Not all drives worked before...and there were issues with the other NON eSATA connected drives,,,kept receiving permission issues, for which now are no longer happening on the NON eSATA connected SATA drives......

    So progress has been made, BUT, not with eSATA drives on connected to the 5th SATA port on Intel motherboards, on both Win8 and Win Serv 2012.

    RF

     
  • Monday, October 01, 2012 9:43 AM
     
     
    Sign In to Vote
    0
    Hi , Thanks for your information. Could you please capture some screenshots of the symptom and share it on SKYDrive so that we can investigate it furhter? I appricate your help.

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Monday, October 01, 2012 10:36 AM
     
     
    Sign In to Vote
    0

    Hello,

    You are welcome....

    I must say I have spent much time working with, and finally identifying the issues with Win 8 & Win Serv 2012 . At this point I am done with further testing, info and such, as I have identified the issue, provided the information. I have cut off how much time I am wasting on this issue, I managed around it by moving all VHD's off of the internally installed eSATA drives onto other internal SATA drives.  As these are testing systems and I can do without, until it is addressed by MS/Intel.

    I am sure this issue will present itself further once the Win products are released, and with this there will be others who can spend their time providing further details / experience.

    Earlier today MS TechNet support responded to my posting an said I had to open a case and "pay", for which is not going to happen, as this is not an end-user issue its a MS / Intel issue ..... As stated before.......there were not such issues when using Windows 2008R2/ hyper-v/ scvmm 2008r2, the issue is ONLY with Win 8 & win 2012, same issue on both Hyper-V's and the 5th port eSATA that is integrated on the MB with 3 different Intel 6 Series Boards.

    MS Support can test the issue on Newer Intel 6 series chipset motherboards.

    Sorry to be so blunt, but I have wasted enough time trying to raise the red flag on this....

    Regards,

    RF

     
  • Tuesday, October 02, 2012 9:27 AM
     
     
    Sign In to Vote
    0

    Hi ,

    Well I am trying to report this issue for dicussion. Thanks for your effort in investigation. 

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Tuesday, October 02, 2012 9:53 AM
     
     
    Sign In to Vote
    0

    Hi,

    Thank you......

    Based upon contact/ communication with another user here he has managed to raise this issue with a MS support person who has said they are going to forward this issue to the appropriate channels.....

    Here is the thread....

    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/8801a909-6e4f-4775-a0fd-21f8ce0a3a8b/

    Thank you Aaron,

    RF

     
  • Saturday, November 03, 2012 9:47 AM
     
     
    Sign In to Vote
    0
    Hi ,

    Please check if the following update from DELL is suitable for you.

    http://www.dell.com/support/drivers/us/en/19/DriverDetails/Product/latitude-e6430-atg?driverId=2PWDK&fileId=2998372451

    The original thread:

    http://social.technet.microsoft.com/Forums/en-US/w8itprovirt/thread/20da7ff7-05a7-4085-8e67-258f11755f3d/

    Thanks. 

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

     
  • Sunday, November 18, 2012 12:17 AM
     
     
    Sign In to Vote
    0

    There is another issue that may give you an access denied on secondary drivers. This occurs if you have object access policies configured. Here is what we have as a workaround to get you moving :

    >> Check the audit policy on removable storage:
    C:\Windows\system32>auditpol /get /subcategory:"removable storage"
    System audit policy
    Category/Subcategory                      Setting
    Object Access
      Removable Storage                       Success and Failure
     
    >> Disable them for success and failure.
    C:\Windows\system32>auditpol /set /subcategory:"removable storage" /success:disable /failure:disable
    The command was successfully executed.
     
    >> Check again to make sure auditing is disabled
    C:\Windows\system32>auditpol /get /subcategory:"removable storage"
    System audit policy
    Category/Subcategory                      Setting
    Object Access
      Removable Storage                       No Auditing

    >> Check creation of the VM now.

    >> Remove the policy to enable Audit object access from the machines. Open rsop.msc – and scroll down to – Computer Configuration > Windows Settings >  Security Settings > Local Policies > Audit Policy. Check which Group policy object is defining this policy. Unlink this object or move the machine to an OU where this policy no longer applies. Then reboot the machine, confirm that the Object access policy shows “not defined”.
    Then try creating the VM.

    <input id="65131899-7a0d-47d1-a1f7-0d4c0051a9ed_attachments" type="hidden" />
     
  • Sunday, November 18, 2012 1:23 AM
     
     
    Sign In to Vote
    0

    This thread and the other one you had posted to are both the same topics, issues, regarding the chipset.

    Regards,

    Ron

    RF