Welcome to the Community.
As for your questions.
1. IIS with Web Access/Secure Gateway can be setup in an NLB Cluster and I have this up and running now without issues. We leave the NLB Cluster configuration up to the client as they may have standards set for this type of infrastructure. With that said, we (Quest) may have something coming down the lines with a 'Web Access/Secure Gateway NLB Setup/Configruation' document. This will be a setup which we (Quest) have tested and have it proving to work properly.
2. Database Mirroring is supported. If you look at our Database, you will see that it has Private/Foreign keys all through it. This should allow you to Mirror/Cluster it without any issues. We leave this configuration/setup with the client as well. I am not sure if we have anything in the lines as to a document for this type of setup on our Database though.
I also have a requirement for setting up DB Mirroring in SQL 2008 R2... Although I know how to do this in SQL, by folllowing published articles from MS, is there anything I need to change/do in vWorkspace to get this configured and working?
Ok in that case I would look at clustering the database server rather than mirroring. I think mirroring is best suited for DR which is geographically dispersed. Interested to see what other people think on that..
Yes clustering would be a good option but the costs are much greater. i.e. Enterprise OS requirements, shared storage etc... If I went down the Mirrored DB with a witness server, how do I go about configuring the vWorkspace components to use such an envirnonment?
Now I've got my live environment tin shipped, racked and powered, I've started building the 'Live' environment. I've created a mirrored 'vWorkspace Database' but can't seem to see how the cleint connection, from connection brokers, TS, etc are configured?
You are only able to configure one database in vWorkspace at a time. For automatic fail over of the database you need clustering. In your case the mirrored database would be sitting there as a "live backup" which would require a manual database configuration change for vWorkspace in the event of a database issue. (which could be scripted to speed the process up)
I am out of office and have limited access to email and voicemail, so please account for a delay in my replies. I will not be back before November 22. This email will not be forwarded.