GraniteStateColin

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Management Tools » Group Policy  ·  Flag idea as inappropriate…  ·  Admin →
    GraniteStateColin shared this idea  · 
  2. 608 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    started  ·  55 comments  ·  Management Tools » Windows Admin Center  ·  Flag idea as inappropriate…  ·  Admin →
    GraniteStateColin supported this idea  · 
  3. 148 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    29 comments  ·  General Feedback » Applications & Add-ons  ·  Flag idea as inappropriate…  ·  Admin →
    GraniteStateColin supported this idea  · 
  4. 52 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    7 comments  ·  General Feedback » Bug  ·  Flag idea as inappropriate…  ·  Admin →
    GraniteStateColin commented  · 

    I can also confirm this problem -- couldn't shut down or execute a restart with the pagefile on a separate volume. Found out about this bug in Hyper-V, changed nothing except moving the pagefile to the boot volume and it worked fine. I believe this problem is new to Server 2016. I believe it did support a separate volume in Server 2012.

    Also, as to reasoning to want to put the pagefile on a separate volume, there are at least 2 big ones:

    1. So the pagefile isn't part of a backup
    2. If performance of the base drives is not critical, then allowing those to be HDD (or an HDD RAID array) is fine, but for performance reasons it would be better to put the pagefile on an SSD.

    GraniteStateColin supported this idea  · 

Feedback and Knowledge Base