Good evening to the community.
Are these all on the same subnet or different ones? Do you have the netmask? (For example 255.255.255.0)
Typically these would be on different subnets since you will have problems with broadcast-storms with that many machines.
I would recommend to divide them into 4 pools with 250 desktops each on separate VLAN:s.
// Linjo
Hi Linjo,
All in diferent subnets. The netmask is 255.255.255.0
Unfortunately, today, VMware View doesn't have the ability to explicitly set the IP that a given VM uses when it is created. This is controlled entirely by the port group that a VM gets attached to and the DHCP server available to the VMs on that port group.
As Linjo states, if you are stuck with having separate subnets then you will have to split your pools into sizes of about 250 VMs.
To get around the naming conflict you are mentioning you will need to set a naming pattern with a fixed length using the following section of the Admin Guide:
Essentially you will need to configure each pools naming pattern similar to the following to keep them separate:
Pool 1: VPC1{n:fixed=3}
Pool 2: VPC2{n:fixed=3}
Pool 3: VPC3{n:fixed=3}
Pool 4: VPC4{n:fixed=3}
Each pool will also need to have a master VM that resides on separate port group and that port group will need to be configured to talk to the DHCP range that you want for that set of VMs.
You will then need to create 4 AD groups and add the desired users to those groups. Then entitle those groups to the desired pool.
-Mike
Thanks for the help.
Best Regards.
Absolutely. If your environment allows the use of superscopes then that could allow you to group all VMs into one large pool.
-Mike
This would have a downside?
You can generate broadcast storm?
Best Regards.
If the subnets are all separate and configured as /24 then it shouldn't matter if you separate the pools or use a superscope. You would have a problem if you were using on large subnet for all ~1000 VMs.