Paging File -- Windows 2012 R2, HyperV host & guest OS ?

Both of the below links act like you should "leave the
Windows 2012 default of system managed pagefile on the
C drive if you do NOT have issues"

Does anyone disagree ?

If so, what is your recommendation ?
===========================================================
https://support.microsoft.com/en-us/kb/2860880 says
For Windows Server 2012 R2 Hyper-V, the page file
of the management OS (commonly called the host OS)
should be left at the default of setting of
"System Managed." This is per the Hyper-V
product group.

http://windowsitpro.com/hyper-v/hyper-v-pagefile-configuration says
Windows Server 2012 changed this; the system managed
pagefile is intelligent and by default will ensure
that the pagefile is at least big enough to capture
a kernel memory dump but isn't the size of the
complete memory. If the system experiences a bug
check (blue screen), then for the next four weeks
the pagefile will be increased in size to match
the amount of memory. This ensures that if a bug
check occurs again, the entire contents of memory
can be captured; after the four weeks has passed
(the date of the last bug check is stored in the
registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
\Control\CrashControl\LastCrashTime), the pagefile will
shrink back to the smaller size. Jeff Hughes documents
this in the blog post "Windows 8 and Windows Server
2012: Automatic Memory Dump."
finance_teacherAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Cliff GaliherCommented:
Letting windows manage the size is fine. Moving it off C can provide performance benefits though. Nothing in either link says or implies otherwise that I saw. You seem to have added that last part on your own. :)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I agree with the statements made in the opening post.

System Managed. and the default location is generally fine, as it's not defragmented, but read the EE post below.

This was discussed here, in another question I answered.

http://www.experts-exchange.com/Software/Virtualization/Q_28680848.html
it_saigeDeveloperCommented:
Surprised you didn't mention this one as well Andrew.  ;)

http:/Windows_Server_2012/Q_28589642.html

-saige-
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
I have an EE Article that should be helpful: Some Hyper-V Hardware and Software Best Practices.

We set the host's page file to 4192MB. We configure the host for MiniDump (256KB). With today's servers having 128GB, 256GB, 512GB, and we're looking to deploy 1TB based boxes having that much space for a page/dump file does not make economic sense.

We leave the guest's page file set to System Managed.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Hyper-V

From novice to tech pro — start learning today.