Solving DNS Issues for Horizon View/VMware Horizon and Controlup Agents

This discussion focuses on a DNS issue experienced with Controlup agents communicating with the console and monitor. Possible solutions include using a logoff script to release the IP address, solving the DHCP scavenging issue, flushing the DNS, and setting permissions to only allow the DHCP server to update DNS records. VMware Horizon (previously Horizon View) was also mentioned.

Read the entire ‘Solving DNS Issues for Horizon View/VMware Horizon and Controlup Agents’ thread below:

Hoping I can pick the brain of some horizon view heads. having what I think are DHCP issues that are affecting the Controlup agents and communication with the console and monitor. My experience that DHCP needs to be working right or you run into an issue, With the horizon view install, from my understanding its is best practice to delete the VDI when the user logs of, Were i think this issue is the the DCHP lease is 1 hour and the constant deleting and recreating of the VDI’s is causing issues. When i do a reverse lookup on the IP i get a different host name

Can you run a script that releases the IP address just before the machine is deleted?

would have to see if that is possible with a logoff script i think any other method woukd fail

stand to be corrected

I’ve had this issue with another customer. However they approached Microsoft and Microsoft resolved it for them. So I don’t know how they did it 😞

It’s most probably a dhcp scavenging issue from my experience

problem is the DHCP team refuse to entertain there is any issue

very fragmented and political teams

What you might try to work around it to see if a flush dns works,

sometimes dose but not always#

Another thought is that the new machine with the same IP address can’t update the reverse DNS name because of security permissions on the object.

thats a possibility as they have extream lock down and security

Hi.

The Check/Fix DNS Permissions script may be able to help here. But from the way you describe the situation, you may be lacking in permissions to try that. Try Check first of course.

yep we can’t run scripts from the console and they don’t have automation

but i’ll have a look at the scripts thanks

thanks for all thoughts here

If Console is not possible, maybe download from the library and run by hand? It needs to run on a machine with AD PowerShell module installed though.

will have a look tomorrow

Luke I’ve seen problems in the past where the client and DHCP server are both trying to update DNS records and ownership of the record can change depending on who created the record. The fix was to only allow the DHCP server to update DNS records and prevent the clients from doing that via GPO. You may have to delete all DNS records for your VDI machines in order to allow DHCP to register the records properly with the correct permissions.

:thinking_face: that sounds promising

What I’ve seen very often is that vdi machines create their own dns registration in DNS. This is fine, but especially stateless desktops get recreated with the same name (and thus dns record), but a different Mac address. This vdi machine then tries to update the existing record, but is not allowed to anymore (the dns server security prevents this) resulting in wrong dns records. What Anthony suggests solves this problem. The other option, lowering DNS security is not a good option, but does also solve this problem. Lastly, Horizon View has not existed for quite a while now, the current product name is VMware Horizon. 😁

🙂 lol shows my experience with the product and thanks guys this was all a big help will go back to the customer tomorrow

We aim to please ❤️

Continue reading and comment on the thread ‘Solving DNS Issues for Horizon View/VMware Horizon and Controlup Agents’.  Not a member? Join Here!