A question was asked about the MasterFQDN key for non-persistent images and its function. It sets a registry value on the master image, which allows each subsequent machine to register to the backend. It is recommended to clear this value after updating the image to avoid all non-persistent machines having the same value.
Read the entire ‘Understanding the MasterFQDN Key for Non-Persistent Images in ControlUp’ thread below:
Question regarding the MasterFQDN key for non-persistent images. What does this do? Should it be cleared prior to sealing the golden image post updates? What happens, aside from all targets (citrix pvs) having the same value for MasterFQDN, if you don’t clear it?
It sets a specific registry value on the master image. Each time a non-persistent machine is created based on this image, that machine will successfully register to our backend
Thanks. So if we update that image after the cuagent is installed, do we need to clear that value? Assuming that if we do not, then each non persistent machine would have the same value there.
Continue reading and comment on the thread ‘Understanding the MasterFQDN Key for Non-Persistent Images in ControlUp’. Not a member? Join Here!
Categories: All Archives