Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Moving GroupWise 6.5.1 to another tree

Status
Not open for further replies.

Kratzyman

IS-IT--Management
Apr 4, 2004
10
US
I tried to use NWCONFIG /NDSREMOVE so as to disassociate the 2 GW servers that we use from the tree that it was in so as to run NWCONFIG to install NDS into another tree. It failed. I reinstalled NW6 and service packed them both to SP4. Copied the domain and post office directories from backup back onto the server that is used to store the mail. Now I plan to graft, in C1, GW into the new NDS tree, and then reinstall the agents. A GroupWise 6.5 system did at one time exist in the destination tree, but has been removed. My question is - Is the scheme still extended even though the GroupWise system has been removed or should I do an install of GroupWise and at the components screen choose - Administrative files only? Any suggestions as to procedures before I graft?
 
I don't exactly follow what you're saying, but a couple things.. NWCONFIG /DSREMOVE is the command to force NDS off the server. I've never heard of using "/NDSREMOVE". /DSREMOVE will force it off despite any errors that happen during the removal process. So even if it says it failed, it actually does remove it.

Also, the Schema on your server should stay in place regardless of whether you take NDS off or not. But since you reinstalled the whole server, all bets are off. But even if it's gone, you should be able to extend the schema during the first part of the Groupwise install.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Thank you. I misspelled the switch. Your right, its /dsremove. To be sure that I had a backup of NDS, I used harware upgrade option in NWCONFIG '/noswitch' to make a backup of it. This locked DS, so I unloaded and reloaded DS.NLM with -ndb switch. Then went to NWCONFIG without a switch to Install NDS and choose the other tree. DS remained locked. So, I did a restore of NDS 'after hardware upgrade' so as to unlock it. Then I ran NWCONFIG /DSREMOVE to do the actual removal, but DS remained locked. Since it remained locked, and I knew that I had a copy of both the Domain and PO directory, I reinstalled NW6 on both servers, and Service Packed them. Then I copied the backed up directories, Domain and PO, and recreated the Software Distribution Directory. Now I am wondering if the schema of the destination tree that the newly installed servers now reside in are still extended. A GW6.5 system once existed in this tree. Can I just graft this system into the new tree and just install the agents, or do I need to do an install of GW onto the Primary Domain server to install needed files that the agents don't install and extend the schema at the same time? I don't mean a complete install, just an install that will put the administrative files on.
 
personaly if in doubt extend the schema from the sp
i will probably not need it any way then graft them in a her presto

 
Thank you Terri.
All appeared to go well, until I tried to delete a PO that was still in the primary wpdomain.db. This PO was a backup, and was not in use at all. I kicked myself for not doing so before blowing away the servers.
I found out that even after repeated installs of GW Administration snapins into C1, that the version of the snapin would not update from v6.0.4. I had to browse into the snapins folder to uncheck Read-Only property on the GroupWise folder. Then a reinstallation of Administration snapins succeeded.
After that I had to clean up a mess that that created, but its working great now.
Thanks for your help
 
yep it can be a bit funny if it's not in the right order
glad its ok
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top