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!

Which domain to connect to when making changes

Status
Not open for further replies.

dethingt

MIS
Mar 14, 2001
3
US
We are running Groupwise 6, sp1, and are having problems with adm changes not synchronizing through the system. Novell has told us to connect to the primary domain when making any changes in the Groupwise system. The changes then do not seem to promulate through the system, even with NDS sync active. I have taken Groupwise 5.5 training years ago, and I thought you should connect to the domain you are making the changes in. When you connect to the domain you are making the changes, it seems to work, but it goes against what Novell has told the other network administrator. I can't seem to find anything in the documentation , so any help would be appreciated.
 
Depending on what kind of changes you are speaking of, it could go either way...

If you are talking abount Link COnfiguration changes, then you should be connected to the Secondary Domain that requires the changes.

If you are talking about changes to the User information, then either way would work.

Since I really don't know what your GroupWise environment looks like, here's a question...

When you connect to a Secondary Domain and make changes, are the changes then propagated across the entire GroupWise system?

When you make a change at the Secondary Domain, that change should then be propagated to the Primary Domain. The Primary Domain should then propagate these changes to the rest of the Secondary Domains.

If the above is not occurring, you may want to look at you Link COnfiguration to see if you are missing something.

Good Luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top