Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.

Re-configuring network services - after permanently removing serverfrom Tree

We have a company that has left our network, and we're
preparing to remove its server and related objects
from our Tree.

Including this server, we have five NetWare 6.5 servers.
All are on their own boxes, except for our GWIA/WebAccess
server, which is on a Virtual machine. Three servers, including
the one being removed are File Servers, the remaining two are
Application Servers related to GroupWise.

Our two GroupWise servers share the same Context, but all our
other servers (including the one being removed) are in their
own Context. All Contexts are directly below our one Tree.

The server being removed has a Read/Write Replica, serves as a
Primary Time Source and an SLPDA.

Of our remaining four servers:

- One is a Reference Time Source with a Read/Write Replica
- One is a Primary Time Source and SLPDA with a Master Replica

- One has our GroupWise POA and a Secondary GWIA running
- One has our Primary GWIA and WebAccess running

....for our two GroupWise-related servers, Directory Services
were removed to improve performance.

The number of network users should be down to about 250-350 users.

What would be the best practice recommended for handling Directory
Services, Time Source, and SLPDA's in the above scenario?

- Should we add back, Directory Services to one of our GroupWise servers
(providing a third server containing a Replica)?

- Should we add a second Primary Time Source to one of our GroupWise

- Are there any problems running a second SLPDA to a GroupWise server?


Labels (1)
2 Replies
Absent Member.
Absent Member.


It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (

Be sure to read the forum FAQ about what to expect in the way of responses:

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team

Absent Member.
Absent Member.

Change the REFERENCE time server to be a SINGLE - such a small tree doesn't need the ref/pri timesync model. Then change the remaining PRIMARY to be a SECONDARY. Point all SECONDARIES to the SINGLE's IP address, or just use service advertising.

The remaining SLPDA will be fine by itself, if it's been configured to point to the DA that's being removed, just undo that.

As long as time and eDir are in perfect sync, you can then just remove eDir from the server with nwconfig - directory services, and that will take care of everything as far as replicas goes.

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.