Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

DHCP IP address lease not released for Instant Clones (76275)

Last Updated: 2/2/2023Categories: TroubleshootingTotal Views: 19500Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Instant clone virtual machines do not release DHCP acquired IP address lease during refresh/recompose.
Clone customization fails because no new IP addresses are available.

Note: This KB is applicable for VMware Horizon 7 version 7.8 and above

Cause

DHCP lease for IP address is released by a clone during shutdown operation. If the clone shutdown was not gracefully completed, the IP address may not be released. The connection server waits 60 seconds by default for shutdown to complete during refresh/recompose cycle. If shutdown is not complete by then, it will force power-off the clone VM causing the lease to not be released.

Resolution

To resolve this issue:

If you have windows update enabled on clones, it can cause increased shutdown times while windows is applying updates. In this case, run windows update on your primary image, disable windows update service on primary and push a new image. If the issue persists, follow option 2 or 3 described below.

Configure a power-off script to release the IP address during shutdown. Note that this will release the IP address early in the shutdown process. If there are other services/drivers requiring network connection, follow option 3 explained below.

Create a batch script on primary VM containing the command “ipconfig /release”. For IPv6 environment, use "ipconfig /release6".

Edit the pool on connection server and set the value for “Power-off script name” to absolute path of the script on primary VM.

Push the new primary image to update instant clone pool.

A slow shutdown, taking longer than 60 seconds, will cause the connection server to power off the VM. In that case, increase the timeout for guest shutdown from default of 60 seconds to a longer timeout. Follow the below steps to change the timeout to 120 seconds. No reboot or push image is needed after this change.

Connect to view ADAM Database. Refer: KB 2012377

In the ADSI Edit navigation pane, select OU=Properties, OU=VirtualCenter.

Find the correct virtual center object by validating pae-VCURL attribute. To view attributes of an object, right click and select Properties.

Scroll to pae-NameValuePair attribute. Edit and add value guestOsShutdownToolsTimeoutSec=120.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
データベースのフェイルオーバー イベント後に一部のサービスを復旧できない問題を解決するための vRA 8.0.0 HA 環境用のパッチ (76222)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

VMware Horizon 8

VMware Horizon 7 version 7.8.x

Take Our Survey

Support Assistant