Unsolved
This post is more than 5 years old
14 Posts
0
4057
September 27th, 2011 05:00
Getting vWS to assign IP to provisioned virtual desktops
Hi Guys,
I'm not sure if this is possible or if anyone has an idea about how we can do this, but let me lay it on you.
We have a CB connected to a VMWare ESX host, and basically we want to use it for external customers. so for example we might hire 20 developers that we want to connect in to our network via virtual desktops managed by vWS. Ideally we would set up a desktop group with 20 desktops, vWS would then tell ESX to create them. But as this bunch of 20 developers will probably need special access through various firewalls, we want to control which IPs their virtual desktops are given so we can give a simple range or VLAN to the network guys to create firewall rules. I can't see any obvious way of doing this, any ideas?
Thanks!
Nick.
Michel Roth
173 Posts
0
September 27th, 2011 05:00
One way I can think of is to pre-create the VMs, note the MAC address and create a DHCP reservation for those.
DELL-David Y
228 Posts
0
September 27th, 2011 07:00
Hi Nick,
Michel's suggestion is probably the easiest to implement. The only other way I can think of would be to create a sysprep (unattend.xml for Win7) that includes adapter specific information so that you specify the IP settings rather than rely on a DHCP scope. You could either modify the IP address on creation of a VM or create a unique file for each one.
This approach would require more effort upfront but allow your VM creation process would be managed by vWorkspace.
Regards
David
omniw0lf
14 Posts
0
September 27th, 2011 23:00
thanks for the posts.. i did think of this method but it was pretty much the last resort. i think it might be easier to let vWS create the VMs for me, then i would log in to each one individually and change the network settings.
i was also toying with the idea of somehow having the VMs tagged for their own DHCP scope.. but i can't think how we would do that either.
hmm
DELL-David Y
228 Posts
0
September 29th, 2011 07:00
Hi Nick,
I had a look at this for you but could not find any evidence that it is possible to specify a VLAN tag in the unnatend.xml or sysprep.inf files. I think the build and then configure approach will be the best method.
Regards
David
omniw0lf
14 Posts
0
October 18th, 2011 02:00
hi guys, thought i would just pop back in here and let you know what we ended up doing in case anyone else is curious.
1) got our network guys to create us a VLAN, eg 10.30.40.1 - 10.30.40.20
2) in the ESX host, we created a VLAN label that pointed to this VLAN
3) created a VM, and set the VM to this VLAN label
4) converted this VM to a template
then, every VM that is created from that template will get put in the VLAN and will have predictable IPs
it's a little bit of upfront hassle, but it means we don't have to log in to each VM and change the IP settings, and we can pre-setup a couple of VLANs and VLAN labels and just re-use them as appropriate.