Configuring Multiple OWA/ECP Virtual Directories on the Exchange 2013 Client Access Server Role

I suppose I'm shooting the messenger here, but I have to point out that this is ridiculously complicated for something that should be simple. Delete and recreate the vdirs every time we do an update to Exchange, really?

Why not just have a separate vdir for EAC so that we don't have to worry about this anymore? (Do it in the next CU ... Keep the original vdir as-is for anyone who doesn't mind opening up their EAC to the Internet, but then give us the option of turning off

EAC on it, and using /eac instead.)

Or, why not make the CU installer figure this stuff out for us? We're using Exchange Powershell commands to do all of it, why wouldn't it be able to keep track of what it needs to do during an update?

Also this is two years too late ... everyone's already come up with their own set of steps in the meantime. Seems a little odd to call all of these installs unsupported, since they didn't follow instructions that didn't exist yet?

By the way, it seems to work fine if I point the second IIS web site to the same wwwroot as the first, and point the second ECP or OWA vdir to the same directory as the default vdir. Not sure if I did any cumulative updates yet, but it seems like that problem

should solve itself, since they're pointed to the same directory? Maybe this should be the officially supported method instead?