nwadmn32.exe couldn't recognize groupwise domain,

[itguy66]

I found "how to move groupwise domain to a new server" in faq section. very useful.

I meet a prolem now. when I run nwadmn32.exe, it prompts to select domain, but no matter the old or new domain directories I selected, the nwadmn32.exe couldn't run until I cancel groupwise function.

I want to move groupwise domain to new server, the tree and domain name are all different. First I setup a new domain and postoffice in new server and copy database from old server and I just follow the steps below I found in faq but stoped in step 2. I really need help, thanks so much.

sunny

got from faq (thanks to author)

It is pretty simple. Follow the instructions below:

Assuming both servers are in the same tree, do the following:

1. Copy all GroupWise directories to the new server. (Domain, Post Office, Software Distribution) Rename the old directories for recovery (backup) purposes and so that the next step will work.

2. Launch NWADMIN and connect to the domain database in its new location. You will probably be prompted to do this when you launch the utility, as it won't be able to find the domain database in its old location (only if you rename, move or delete old directories).

3. Once you're connected to the domain database, in GroupWise View go into the domain (and secondary domains if any), and all post offices' details and change the UNC paths to reflect their new locations. You can do this by just browsing to the new location of the databases. (Also modify any TCP/IP addresses that have changed).

4. Next you need to install the GroupWise agents to that server (assuming you want them running there). Run an agent install from the AGENTS directory under your SoftWare Distribution Directory. Follow the prompts.

5. Next install any gateways you want running on this server.

At this time you should be done. GroupWise should be fully functional. The workstations will never know the difference.

Good Luck,

Mark

 

[yvfwc]

sunny,

I will assume you had no problem running GroupWise View before the move. Is the server change hardware only? The NetWare version & Service Pack version are the same? Are you running NWAdmin from the new server or the old server? (\public\win32)

With a little more info I'm sure we can get you past this.

Cheers,

Mark ;-)

 

[itguy66]

Hello Mark, nice to meet you,

Actually, I had 2 nw server, one file server and one mail server. It works well but very slow, so I changed to new compaq server (just hardware as you said). The new file server is fine, but mail server(groupwise 5.5) does not work properly.
The tree and containers are all same, so I just copy the gw database to new server, and install a domain/postoffice as default gw installation (the old server is same). Then set the UNC path to old database (domain/postoffice). It works but I hv a very big problem, I couldn't config the any groupwise's objects (it's grey!!!!), and couldn't add new users in NDS and groupwise at the same time (using neat32.exe). before I can do that.

Because the old and new server's tree/containers' name are all same, I couldnt' do graft as you said. how can I do in this situation?

BTW, if there is a prompt" the groupwise domain database was not found" when I start up netware administrator, and it doesn't recognize any domain, how can I do, delete some *.dll files or ...

Looking forward your good news....
Thank you so much
sunny