Ok, so I've gotten into a real mess here.
I have the GW servers virtualized on a KVM type server (QNAP fw 4.3.5).
So I was running GW 14.2.2.
I did a snapshot before attempting to update to GW 18.
The update went fine, but darned, the license I have doesn't currently cover GW 18, so I thought no problem, I'll just revert to before the snapshot.
BUT, the snapshot feature malfunctioned when rolling back, my guess is that it rolled back disc 0, but not disc 1 (GW datastore).
So now I have a mixed system, part of it is 14.2.2, the other is 18, the webaccess didn't work, the GMS didn't work.
The webaccess didn't want to log in 'not compatible with po'.
When looking in the monitors for the agents they all said Groupwise 18, but I could see that the db's where still at 1420
So after fiddling a bit, and activating external support for the KVM like system to make them roll back properly, I noticed that they had started the agents, which now fed mails into groupwise folders, OH NO.
Now I can't roll back, then I'll loose 2 days of mail.
Looking at the domain and po folders, the .dc files are not updated, and the databases are still 1420
I decided to install 14.2.2 again, on top of 18.
All the agents are now back to 14.2.2, the webaccess is working again, the GMS can log in as well, so far so good.
Now the only thing that is odd, is that if I start the groupwise administration console, it still says 18???
What on earth is that now?
How do I get that fixed, so that will also install as a 14.2.2? Will I get in trouble if I modify anything with a GW18 administration console on a GW14.2.2 system (apart from licensing issues which I can't figure out in that case).