This message was deleted.
# citrix-vad
s
This message was deleted.
m
you need o set it to dump to a persistent disk
j
thoughts on how I would achieve that somewhat easily?
my only persistent disks at the moment are VHDs mounted in the OS... guessing thats not an option for a dump as the OS has crashed at that point. Machines are non-persistent MCS machines in a random pool
l
Attach a second disk manually and redirect crash dumps to that.
👍 1
a
like @Leee Jeffries said, thats the only way i think you can do it. we had a similar issue (nutanix ahv is our hypervisor) and had to bulk add a persistent disk to all non persistent machines (or make a test smaller pool and have someone that can reproduce it use that for a while) and point the needed logs to that. If you're using Nutanix i worked with the on a script to spin out a 2nd drive and a controlup script to initialize it / format and add as a drive letter
j
@Andrew Gresbach, mind sharing that script? will have to modify for Citrix Hypervisor, but I think I can figure out the hypervisor part, having the windows part would save me time
a
no problem! it was actually @Kees Baggerman script that did the majority of the magic. I just pieced together various things I found to make the ControlUp part once the disk was attached. http://blog.myvirtualvision.com/2019/11/19/nutanix-ahv-and-citrix-mcs-adding-a-persistent-disk-via-powershell-v2/
👍 1
d
You have to configure dedicated dump file to store the memory dump on a persistent disk. https://support.citrix.com/article/CTX127871
j
Thanks, @Dennis, I thought I had all the dump configurations down for C thinking I could keep it from refreshing long enough to get the dump, but I may have missed a setting in that doc too. Ironically enough, just seeing the bluescreen might have found our culprit, but if not down this road I go!
a
hopefully you caught it!
🙏 1
j
Thanks guys! I did not solve the issue, but I have gotten persistent disks and all the configurations right to dump to that drive for today. Much appreciated