From what you have been describing having two separate brokers is
definitely your best option based on what your trying to do.

You should be able to point both brokers at the same VC/ESX
environment without any trouble.

Just don't add one virtual machine to both brokers or it will cause
problems!!!

Regards,

Mike

On Nov 4, 2009, at 8:39 AM, "Moterbiker" <communities-

The implementation of a seperate connections broker is the quickest and most cost effective method of doing this, a more elegant solution would be to use an Environment manager to configure desktops based on connection IP/Client name, AppSense EM is one such posibility

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth VCP / vExpert
VMware Communities User Moderator
Blog: www.planetvm.net
Contributing author on "VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment”. Currently available on roughcuts

Hi,
Actually you wouldn't need to create another database or View Composer instance since both Connection Servers would be pointing to the same VC/View Composer environment as Mike suggested.
(View Composer must be installed on the same system as VC)

If I'm understanding this correctly, you'll want to have the following:

1. 2 Connection Servers - CS1 and CS2 both pointing to the same VC/View Composer system
2. a) CS1 deploys a pool using a master image that contains Office 2007 for students in Classroom A
b) Point all clients in Classroom A to CS1
3. a) CS2 deploys a pool using a master image that DOES NOT contain Office 2007 for students in Classroom B
b) Point all clients in Classroom B to CS2
4. Both pools would use the same entitlements. Depending on which Connection Server they access, they would get different desktops.

Hope this helps.

Michael

... Just realized this is basically a rehash of stonegossard's suggestions ...

Message was edited by: vm-michaeln

What errors were you getting?

Mike

Moterbiker

We are a school in Rotherham who have run View for the past year and a half on Wyse thin clients. Because of a limitation in the original Wyse OS the only way we could be sure to assign desktops to clients in a particular room was to create a connection server for each room with one pool (newer OS version has addressed this issue). This ensures that only desktops from that broker are assigned to that room. It has worked well. As to the provisioning errors:- 1. have you deleted a pool and then created another with the same name (can cause issues if it is not deleted cleanly ie disable provisioning, delete machines from disk (in broker) then delete pool) on a particular broker? 2. Are you using linked clones? if so have you deletes the temps correctly? Are the errors when you add to the domain (I had this and had to sysprep the original image, delete machine form AD, re add to domain etc)?