Deleting Secondary domain and Post office in GW5.2

[benbeneke]

Hi all,

While doing some experimenting/testing a while back, I created a secondary Domain and a secondary Post office on another server (which has since gone) and after consideration deleted both BUT the operations had not gone through when I wiped the other server so our current mail server still believes that there is a secondary Domain and a secondary Post office out there somewhere that it cant talk to at the moment - also there are 3 test users in the address book which point to the same deleted secondary Domain and secondary Post office.

How can I remove all references to that domain and PO and delete those test users without wrecking the current mail setup which runs fine?

I need to complete this before I upgrade to GW6.5 as I dont want to bring my bad mistake with me.

Any help appreciatted.

Ben

 

[1stITMAN]

Ok run Groupwise Mailboc maintenance on the Post Office (Primary)
Check link configuration and delete any links to that post office the try synchronise

then mailbox/maintenance again.

 

[FarOut]

There are certain rules that have to be observed when deleting a Domain (Primary or Secondary). Below is a link that gives an overview of what has to be done.

http://www.novell.com/documentation...umentation/lg/gw6/gw6_admin/data/a3n5zxd.html

FarOut
V-Peace-V

 

[benbeneke]

THanks for the replys guys,

1stITMAN, I'll try your recommendation on the weekend when its quiet, looks promising.

Farout, Unfortunately that wont work as there are no NDS objects left to view. The secondary domain and po can be seen in GroupWise view but nothing has worked in there when I try to delete as it is still trying to authenticate to a tree that doesn't exist anymore.

Will keep you posted, if anyone has anymore ideas please let me know

Thanks
Ben

 

[FarOut]

Was not aware that you had multiple tree's, my apologies.

FarOut
V-Peace-V

 

[benbeneke]

Farout,

No need for apologies!

You never know where the catalyst for a new train of thought is going to come from.

I fixed a serious NW4.11 issue a week ago after reading a TID for NW5 and following some of it that applied then heading off on my own track.

Ben