![]() With that said, below and even above, is what I witnessed while at a customer recently. It seems to have to do with a given organization's/company's security configurations within AD, DHCP and DNS. I want to start this off by saying this problem doesn't seem to be 100% uniform across all VMware View Composer implementations. The DHCP record will eventually drop off after the lease expires, but the DNS entry will persist even after the DHCP lease expires. These old records are considered "stale". You have an automated VMware View Composer floating linked-clone pool in an environment using Windows Active Directory DHCP and DNS, and whenever you remove or recompose linked-clone desktops it leaves the old (outdated) DNS records in place, and looking in DHCP you see more than one lease for the same computer name. ![]() ![]() In effect, this issue should no longer occur if you are running View 5.1 or newer. With the release of View 5.1, floating (stateless) linked-clones now retain their MAC addresses unlike previous versions of View.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |