Cisco Cisco Unified MeetingPlace Directory Services

Página de 10
Release Note, MeetingPlace Directory Services Release 
4.2.7.22
 
Page 4 of 10
 
0050-0048-01, Rev. A0 
Revision Date: 04/25/2002
 
userid=salesengineer, profile# =0001 can be changed 
userid=technician, profile# =0002 can be changed 
userid=email, profile# =0003 can be changed 
Using MeetingPlace Directory Services Administrator interface with large directories 
After importing a large directory, you may like to see the directory in the MeetingPlace Directory 
Services user interface windows. It is hard for the interface to show all of the detailed entries. You can try 
using “list” mode by clicking “view” in the toolbar, then clicking “mode” and then “list”.  This means that 
the user interface window will only display the DNs of the entries (without the attributes) resulting in a 
search that returns much quicker.  You can also increase the search timeout.  This is done by using the 
ADUA (click on “tools”, then “options”) or by editing the NT Registry. Contact your support 
representative or installation specialist for more information on editing the registry. 
Suspense file limit size recommendation 
It is recommend that the suspense file size limit be set as large as 50MB for large corporate databases. 
Because in the initialization period, if connection between servers is lost, all changes will be recorded in 
the suspense file for later replay.  
Correlation attributes in a MetaLink must be unique 
Correlation attributes in the correlation rule section of the MetaLink agreement must be a unique attribute 
in the synchronization (corporate) directory. The attributes in your directory that will be mapped to the 
profile id (vuname, must be numeric) and the Username (mpname) in the MeetingPlace server should be 
unique. It is strongly recommended that you check the value of these attributes in your directory to make 
sure they are unique. 
MeetingPlace Directory Services – MeetingPlace Server MetaLink must be stabilized 
before creating other MetaLinks 
The MetaLink between MeetingPlace Directory Services and the MeetingPlace server must be created 
and be stabilized before the MetaLink agreement between MeetingPlace Directory Services and your 
synchronizing (corporate) directory can be created.  
MeetingPlace Directory Services installation on a Windows 2000 server/workstation 
MeetingPlace Directory Services must be installed on a Windows 2000 server/workstation console, not 
on a terminal services console. 
Replaying suspense file 
The suspense file must be replayed on a Windows 2000 server/workstation console, not on a terminal 
services console. 
License key requirement 
The Directory Integration Option license key in MeetingPlace must be installed prior to installing 
MeetingPlace Directory Services 
Assigning the guest password to a new user 
If you would like to use the guest password for a new user, make sure you know the guest password and  
change it as needed before creating the LDAP or AD link. If you would like to ask a new user to change 
their password when he/she logs in for the first time, change the guest password expired time to the 
expired status.