This message was deleted.

We use zones as fault domains

Ok, fault domains? Vsan ?

Sure. I'm good with that

Thank you. Is this the WEM ninja Hal Lange? I assume it is.

Yup.

Sweet, I though so. Yea you input is highly respected.

We have a primary zone that has no resources. All the secondary zones own the resources. Do not use home zones

Bit confusing to be honest. I need to keep reading

Kind of like the empty root on AD that MS used to want

Ahh I see. Yea let me look for that.

Depends on your requirements but if you are using multiple data centers for higher availability I prefer separate sites so that you get database resiliency as well.

Thanks Rob, that is what I built because I didnt like the zones. Even PVS, but my images doubled. Which I Know isn't zone related.

We actually have multiple sites and multiple zones. We use a boot script to change image per site, per zone, so still only have one image

PVS as well?

It does go back to its own after next reboot. And yes, I have one PVS image for multiple XD sites across multiple secondary zones. At boot we change the WEM, SR, and DDC to match what site and zone it is booting in.

Wow , that's impressive. Different PVS farms as well?

One for each datacenter and a "stage" XD site, PVS farm, WEM and SR to test all changes before going prod. All use same image that we replicate to all PVS farms and import into it

That's really awesome. Are you just using the PVS poweshell commands to do that?

To import yes. For the image, we use a combo of reg keys and pvs personality to help determine what zone and env and then use a boot posh script to dynamically change it. We call it our bootstrap

Awesome, thank you for doing that. I wanted something like that so I could have couple farms and replicate export and image to other farms. I wonder if the PVS replication tool could do something similar?

Honestly, we just use robocopy to replicate to all the PVS servers

PVS personality is a powerful thing to use in these scenarios. Nice one @Hal Lange.

We're using zones to ensure a certain group gets dedicated access to a subset of machines. Not the most elegant solution but works for us.

I tend to go zone now just because managing a bunch of sites and keeping them in sync is a huge headache for most places because they don't have the staff. If they do and they need that level of resiliency then multi site is the way to go.

Thanks everyone for the input.

Here is a copy of a boot process that we use utilizing PVS Personalities. We schedule the script called bootstrap.ps1 as a machine startup script after networking starts. we utilize the following PVS Personalities FS = File Server WEM = WEM Server SR = Session Recording Server PRN = Print Server DDCs = DDCs in a space separated list CTXEnv = different environments or Delivery Groups (eg, Env1, Env2)

Thank you very much Hal, I appreciate the heck out of this. If there is anything I can ever help you on. Please let me know.