I've created an automated persistant desktop pool, automated non-persistant desktop pool, and an automated persistant desktop pool using linked clones. This was in a lab environment and is not currently being used by anyone. Yet, all the automatically deployed VMs are now constantly reconfiguring themselves. That seems very strange to me? Any thoughts?
Mine just started doing it on an individual desktop. I had to reboot all my vdi servers to get it to stop.
Driving me nuts. I don't get support till tomorrow as the PO gets processed....
only the automated - not persistant should reconfigure each time the VMs are created
the others only the first time they boot, with the exception if you change your base disk and recreate the snapshot in the Composer section
Jose
I guess you are talking about a Linked Clone (Automated) pool?
In this case the VM's are everytime reconfigured if the pool is: Recomposed, Refreshed or there is a Storage rebalancing be done
So please check your configuration:
1.) How often / When do you refresh the pool ?
Normally the broker will not do anything without the Administrators configuration.
Does that happen all the time?
Please could you check how often? Time?
Thanks,
Christoph
One thing I've noticed is that when you have a pool set to keep the VMs turned on ... make sure the power profile on the VM is set to never sleep, most of my configure events were the connection broker turning on a machine, only to have it go to sleep again 20 minutes later.
Curse XP for not having power management via GPO built in
Mine was doing it every 20 seconds for hours on end...
It would seem like it cannot be related to power settings since it also happens to an individual XP desktop that I've left powered off entirely for months now (ie. One not even part of an Automated Desktop Pool). Still reconfigures that one every 20 seconds just like the dozens and dozens of others.
Its extremely annoying either way but especially to have no explanation for it.
Do you have any replicas in this setup?
BR
Linjo
Yes one, could that be contributing to the issue?
It could be a potential reason.
Please try removing the replica and see if the reconfigure stops and then add the replica again.
BR
Linjo
The most common cause is that there are two different View environments attempting to use the VM, each reconfiguring the VM to point to itself when the settings appear incorrect. These reconfigure operations are updating a string value that can be passed through to the view agent - if you take several copies of the vmx file for the VM after reconfigure operations and compare the machine.id attribute, you should see which servers are making the changes. Feel free to paste the two values into the thread if you want more analysis.
I have only one view environment.
And I didn't have any replicas.
I haven't seen the problem arise again. So I bet it's a transient problem that will be tough to track down.
Especially since most VMSupport techs will tell you to reboot everything, thus never being able to troubleshoot the actual problem.
After we add an replica connectionserver and now this starts on every VM at 20 sek.. Is there an solution??
After uninstalling the replica server this is gone!!??? But we need this replica!! ![]()
