The Facts:
Windows 7 64 BIT 6GB Reserved Memory
No Paging File on the Guest OS
Non-Persistent Clones
Office 2016 as an app stack not part of the reference image
Issue described below is not reproducible on demand
The symptom:
Excel users report infrequent crash/freeze with particular spreadsheets
My gut/experience:
My question:
Paging file? I've been told by instructor to avoid using a paging file. The Googles are all over the place on paging files.
Does anyone have an opinion/real world experience with 'on or off' virtual memory/page file?
Thank you!
Update:
Appears this may be related to a Windows update:
KB4018319 needed the following non-security update
KB4011128
I unfortunately don't have a answer to this but would like to know if you get one. We've seen some issues where VMs are doing a lot of paging when there is sufficient memory and have considered disabling the page file.
During a Horizon training, the instructor advised disabling the Windows 7 virtual memory AND making the memory assigned to the VM reserved.
I don't believe the issue we are experiencing is related to the Win 7 page file (we've gone without it for 8 mos.), I've been watching the end users VM with VROPS
Update:
Appears this may be related to a Windows update:
KB4018319 needed the following non-security update
KB4011128
As this was post originally was in regards to paging file:
We do not use a paging file, we reserve the memory and do not experience performance issues (that we admins know of), this issue (Excel crashing) was resolved by the updates marked as 'Correct Answer'.