Mystery solved! Thank you Andrew Wood for help. See below:  Hi,  This is Andrew from Quest.  I raised this case for you because I would like the original copy of your Config.xml file to test with.  This does work via IIS for most people.   I even copied/pasted your config above into my config.xml file and it worked fine for me.  However, I think in editing the farm name, you may have inadvertantly fixed it!    1. Take a backup of your old Config.XML  2. Copy/Paste the text from your post above  3. DON'T delete any of the quotation marks " "  4. Try it!  I can reproduce the error that you get if I delete the "   I imagine what you've done is accidentally deleted a quotation mark and then simply replaced it when typing in your farm name. However, there is a fair chance that the ASCII for your Regional Setting quotation mark at the time wasn't the same as US English so it looks the same to you and I but not to a computer.  Thank you, Andrew  My Response:  Hi Andrew,  You were right! I removed the quotation marks and recreated them and that fixed it. Very weird!  Thanks for the prompt assistance!  Regards
Hi all,  I have a quick question which I hope you can help with. I have 3 sites joined via WAN links. Even though they are linked, they are managed independantly and have there own infrastructure and only sharing the Active Directory domain, DNS etc. The problem I have is that all 3 sites have there own HyperV cluster and alos there own vWorkspace Connectio broker etc. The vWorkspace Connection brokers do not know about each other at all.  So here is my problem: Since they share DNS, if I create the provision DNS record in the 1 suite and point it to the IIS server hosting the config.xml file for the one site all the other sites get that same config. So in other words, they all then get configuration from site A. Is there anyway to use for instance a site name instead of provision as an A record for the vWorksapce clients to lookup to get there config?  Thanks in advance!
Config.XML and the Provision DNS record