Up until now we've been using the registry based method for the 3 delivery controllers during VDA install on our MCS images en have Auto-update enabled.
We want to replace the current delivery controllers with new controllers on a newer operating system, since that means new hostnames we want to handle the delivery controllers via a GPO instead in the future.
Now we also see a personality.ini in the root of C: of our VDI's that seems to have old information cause it's missing a delivery controller in the list. Apparently this does not get updated by Auto-update. I understand this file get's injected by MCS during the image creation but we want to get rid of it to avoid VDA's registering on obsolete delivery controllers.
Question
Peter van Leeuwen
Up until now we've been using the registry based method for the 3 delivery controllers during VDA install on our MCS images en have Auto-update enabled.
We want to replace the current delivery controllers with new controllers on a newer operating system, since that means new hostnames we want to handle the delivery controllers via a GPO instead in the future.
Now we also see a personality.ini in the root of C: of our VDI's that seems to have old information cause it's missing a delivery controller in the list. Apparently this does not get updated by Auto-update. I understand this file get's injected by MCS during the image creation but we want to get rid of it to avoid VDA's registering on obsolete delivery controllers.
How/where would one do that?
Link to comment
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now