Firstcom
asked on
VMWare Horizon - Static IP VDIs
We have an environment where some of our workstations need to have static IPs.
The best I've been able to figure out how to accomplish setting static IPs is by enabling DHCP and allowing Horizon/Composer to create the VMs. From there, I've set up a post-processing vbscript that uses the netsh command to set the static IP, gateway, and DNS servers for the PC.
However, when it does this, it loses connection to the Horizon server and says "unreachable" even though I can connect to the VDI VM and do everything I need to.
I've tried adding a line to stop and start the VMWare Horizon Agent service, but that didn't help.
Has anyone else had to to implement a static IP environment in a Horizon View infrastructure? Or have any idea how to accomplish what I need to do?
Thank you!
The best I've been able to figure out how to accomplish setting static IPs is by enabling DHCP and allowing Horizon/Composer to create the VMs. From there, I've set up a post-processing vbscript that uses the netsh command to set the static IP, gateway, and DNS servers for the PC.
However, when it does this, it loses connection to the Horizon server and says "unreachable" even though I can connect to the VDI VM and do everything I need to.
I've tried adding a line to stop and start the VMWare Horizon Agent service, but that didn't help.
Has anyone else had to to implement a static IP environment in a Horizon View infrastructure? Or have any idea how to accomplish what I need to do?
Thank you!
Dirk Kotte
would use DHCP with reservations.
we too
ASKER
DHCP with reservations requires a MAC address, which is re-generated any time you rebuild a VM.
So an update on this. I think it' s unrelated to any network changes or static . The same issue occurs when I clear DNS entries completely and remove the script that sets the static IP. So something else is going on that is causing the agent to not communicate (or appear to be not communicating).
Any ideas?
So an update on this. I think it' s unrelated to any network changes or static . The same issue occurs when I clear DNS entries completely and remove the script that sets the static IP. So something else is going on that is causing the agent to not communicate (or appear to be not communicating).
Any ideas?
So what parameter is permanent when you rebuild machine? It is new machine by all detectable means.
ASKER
This is unrelated to static IP. The process we're using to implement static IPs works fine - the issue is something else.
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for Firstcom's comment #a40822949
for the following reason:
Different issue.
Accepted answer: 0 points for Firstcom's comment #a40822949
for the following reason:
Different issue.
You described one issue. Whats wrong with solutions?
ASKER
I have no way to verify or implement the solutions described, or to determine their accuracy, since the problem wound up unrelated to the original question posted.
can you describe real problem in one sentence?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Which I expected to hear, thanks and have fun
ASKER
Resolved on our own.