This message was deleted.

What is your hypervisor? We just did this w/ Nutanix and i worked w/ someone that created an awesome automated script and paired that w/ a controlup script to initialize/format/mount which let us do it in bulk

VMware. I assume MCS can't have a D drive in it's template? I'm so used to PVS. It a new change. I need a D drive to store wem cache, logs, and pagefile.

i dont think Citrix allows it by default but could be wrong. and yup thats exactly why we did it, to redirect windows logs to try and track a blue screen issue back in the fall. the controlup script should be linked in that article. i'll ping our nutanix SE to see if he can ask the author about vmware options

I have went through this process. Assuming MCS can't ha e a persistent drive in it's template. I could add it to my master image. Do what I needed to. Seal shutdown. Deploy machines. The run the script to add the extras drive so my logs all all that starts on D. However I am not sure if I can just use the MCSIO drive as well? Can I?

hmm that i am not sure about. w/ pooled we ran into the issue even adding to the image that it NEEDED to be setup on each pooled machine, initialized and mounted for it to work for us

So when the MCSIO drive is created is it shown up as a drive like PVS write cache?

we actually dont use the MCSIO since i guess its not needed in a Nutanix setup we're told (similar benefits just w/ their tech) so cant say for sure. for us we only see the c:\ so needed to go the script route

Yea I'm pushing for Nutanix as well man. Definitely want that beast in my environment

mcsio will give you a persistent disk but you’ll need to build a new machine catalog to use it

Yup mcsio is good now (not the old crap release in 7.15) and the persistent disk can be leveraged the same as pvs (BIS-F support makes it too) - else it’s a manual task

Nice. That's good to know. But I guess where I am confused at is. I take a window 10 image. Spin it up do whatever it is I need to do. Typically I would have a non presissent disk as a drive drive. Then I would covert it to a template. Then spin it up. Each machine would have it's logs and other stuff on D. I guess I am not positive how it works in MCS pooled now. If I don't have another drive and I seal it with BISF. Not sure how it would work if there isn't a D drive for example. Where does all the logs go, wem cache, ect. I'm also assuming that once the MCSIO drive is spun up I could redirect event logs to it without impact. I just have to run through this

Are you sure you need a persistent WEM cache drive?

No old habbit. I can change my ways. I just burned it in my head years ago when it was a thing. James told me about 2 years ago it's not needed.

You don’t need dedicated drive for WEM cache. You can add drive via hypervisor after VM deployment. It does remain even with updates. There’s the MCSIO route in 19xx versions but I haven’t really used MCSIO.

Thank you all for the information. I appreciate it very much. I'm getting away from PVS slowly. So its a change for me.

whats making you move away from pvs to mcs out of curiosity? i've always favored mcs myself but curious what others have gone through in case i have to help justify it w/ other examples

On your master image add a D drive. Configure BISF policy accordingly. When you seal, bisf will do redirects etc. when you create catalog, mcs ignores the second drive on the master and adds it’s own if you choose mcsio, bisf on start ensures that things line up. You may need a reboot after provisioning and in azure there are different rules

ahh yup thats what i remember. when we were moving to our new setup we also were switching to nutanix and were told about the hyperconverged benefits . (and that we wouldnt need mcsio w/ that setup)

pvs also makes image management a lot easier. Much quicker to swap between images if testing too.

MCS can do quick swap if you change your process. Rolling catalogs for the win.

Oh hi @Andrew Gresbach 👋🏻

I had WEM’s cache on a persistent drive until 1808ish. Went back to the default based on an old thread here... old habits, n’at.

Thank guys. I'm preparing for the azure move in 1 year for us. That why I'm forcing myself to move

Hey @Kees Baggerman! didnt know you were in here too