Good Morning,
I recently tried to perform an upgrade from v9 to v10.1.5 and ran into a problem.
Following the instructions provided, I uninstalled the console, rebooted, and upgraded the primary server, which contained a group with a primary and a secondary server. After the reboot I reinstalled the console, rebooted again, and tried to unlock the group. The console said it couldn't communicate with the group so I cleared the cache. When it rediscovered, it found the original group, but also created a version 2 of the original group that contained the secondary server!
I proceeded with the upgrade on the secondary server - opting to upgrade from CD rather than roll-out, uninstalling and reinstalling its console as well, doing the key copy, etc, but the phantom group is still there.
The main problem is that the secondary server still recognizes that it is a secondary server, which leaves no primary server for the phantom group. Plus, it recognizes that the original primary server is still its primary. Therefore, I can't set it to be the primary of the phantom group.
So, with no primary in the phantom group, it wont let me do anything to that group, either move the secondary out to it's real group, or move the primary in to its group. Plus, I think the primary conflict that exists is creating problems with accessing the real group as I frequently have to clear the cache before I can unlock that group.
Does anyone have any idea of how I can resolve this issue? I am a little loathe to do a straight uninstall/reinstall as the secondary is the parent of many clients and in the past, disrupting that has created a lot of problems trying to get the clients pointed back to a parent.
Thanks for your help...
I recently tried to perform an upgrade from v9 to v10.1.5 and ran into a problem.
Following the instructions provided, I uninstalled the console, rebooted, and upgraded the primary server, which contained a group with a primary and a secondary server. After the reboot I reinstalled the console, rebooted again, and tried to unlock the group. The console said it couldn't communicate with the group so I cleared the cache. When it rediscovered, it found the original group, but also created a version 2 of the original group that contained the secondary server!
I proceeded with the upgrade on the secondary server - opting to upgrade from CD rather than roll-out, uninstalling and reinstalling its console as well, doing the key copy, etc, but the phantom group is still there.
The main problem is that the secondary server still recognizes that it is a secondary server, which leaves no primary server for the phantom group. Plus, it recognizes that the original primary server is still its primary. Therefore, I can't set it to be the primary of the phantom group.
So, with no primary in the phantom group, it wont let me do anything to that group, either move the secondary out to it's real group, or move the primary in to its group. Plus, I think the primary conflict that exists is creating problems with accessing the real group as I frequently have to clear the cache before I can unlock that group.
Does anyone have any idea of how I can resolve this issue? I am a little loathe to do a straight uninstall/reinstall as the secondary is the parent of many clients and in the past, disrupting that has created a lot of problems trying to get the clients pointed back to a parent.
Thanks for your help...