× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Migrating Notes from the IPCS
  • From: "Carole Houghton" <mchcah@xxxxxxxxxxxxx>
  • Date: Fri, 17 Jul 1998 07:07:58 -0700

At the Implementing Domino Lunch and Learn on July 14th, a 
sheet was included on migrating from the IPCS.  The object was to 
use the same names.nsf and server.id.  What I run into is 2 
certifiers in the name and address book with the same name.
With this situation, the cert.id created last is not the same as the 
server is certified with, therefore the new administrator cannot do 
anything with the server.  THere is a new redbook being written 
about this but it is not out yet.  Does anyone know how to do this 
correctly?  Should the server.id, cert.id and names.nsf from the old 
server be put into the data directory rather than the server.id and 
names.nsf like the instructions say?  Where can I find information 
on this subject?  Any and all help would be greatly appreciated. 
Carole A. Houghton
Wenger Corp
mchcah@deskmedia.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.