Cisco Unified MeetingPlace, Release 6.x -- Cisco Unified MeetingPlace Directory Services Implementation Steps and Checklist

From DocWiki

Jump to: navigation, search

Cisco Unified MeetingPlace, Release 6.x > Cisco Unified MeetingPlace Directory Services



The information in the following sections is for Cisco partners or technical personnel who are responsible for installing Cisco Unified MeetingPlace for Directory Services:


Contents

About Implementing Cisco Unified MeetingPlace Directory Services

Before you implement Directory Services, you should understand the following information:

  • Without a good data source-a well populated directory and disclosure of the directory schema-obtaining proper business rules is difficult.
  • To speed installation, you must have access to stake holders at each step and obtain as much information as possible.


Implementing Cisco Unified MeetingPlace Directory Services

This section contains the following procedures:


Implementing Cisco Unified MeetingPlace Directory Services

To Implement Directory Services
  1. Analyze network architecture and corporation directory data source, and target information flow and explain the impact of implementing Directory Services. Action required: meeting/diagram.
  2. Evaluate customer directory schema and data, ensuring that you know how well populated each attribute is. If you cannot depend on having data, then business rules are harder to create. Meet with the programmer/system manager of the customer directory. Action required: sample directory data and schema.
  3. Evaluate the existing profiles to determine the patterns for creating user names, profile numbers, and so on. Ideally, this data is found in the customer directory, and you can continue to use the existing business rules after implementation occurs. Meet with the current system administrator and others who have a stake in the profile creation rules. Action required: meeting/discussion and decision.
  4. Establish business rules for creating new profiles. Discuss these rules with the current system administrator and others who have a stake in the profile creation rules.
  5. Obtain the checklist in Completing the Cisco Unified MeetingPlace Directory Services Implementation Checklists to use while implementing Directory Services.
  6. Set up a Windows NT or Windows 2000 server for a dedicated Directory Services system and a Cisco Unified MeetingPlace lab server for initial test synchronization. The lab server is for an existing customer who needs to implement Directory Services into existing Cisco Unified MeetingPlace systems. We suggest using a lab Cisco Unified MeetingPlace system to do test synchronization before you implement Directory Services into production Cisco Unified MeetingPlace system. You can use the new Cisco Unified MeetingPlace system as lab system for a new customer. Time required: 1-2 days for Cisco Unified MeetingPlace lab server and NT server setup.
  7. For new Directory Services customers, proceed to Step 11.
    or
    For existing Cisco Unified MeetingPlace Directory Services customers, the Cisco Unified MeetingPlace lab server will need to be populated with current profiles. Time required: Approximately 4-8 hours for directory export and import for 20,000 entries.
    Note: Step 7 through Step 9 take the most time because each profile creation takes roughly 1 second to synchronize, and the steps must be repeated as the Directory Services is migrated into production.
  8. Install Directory Services software and establish MetaLink agreements between the customer directory, Directory Services, and the Cisco Unified MeetingPlace lab server. Time Required: Implementation time depends on actual size of customer directory.
  9. Test business rules to ensure that conflicts do not occur and that the proper number of profiles are being created. Time required: This step may take anywhere from 1-2 days to 1-2 weeks, depending on the variety of customer directory data.
  10. Back up the production Cisco Unified MeetingPlace system for existing Cisco Unified MeetingPlace customers. Time required: 2-4 hours.
  11. Migrate Directory Services into the Cisco Unified MeetingPlace production system. Time required: Implementation time depends on the actual size of customer directory.
  12. Automate the Directory Services process and train the Cisco Unified MeetingPlace Directory Services system administrator. Time required: 4 hours.


Completing the Cisco Unified MeetingPlace Directory Services Implementation Checklists

Complete the following checklists:


Table: To Verify Before You Go on Site
Description Complete
Preinstallation Directory Services Server Requirements

1. Your system meets the hardware and software requirements listed in the System Requirements.


2. Installing Directory Services on an existing Cisco Unified MeetingPlace gateway system requires a reboot. Schedule a reboot (gateway down time) if necessary.


3. NTFS partition for Directory Services software installation


4. Internet Explorer version 5.5 through 7 is installed (For Cisco Unified MeetingPlace Release 6.0 MR5 only, we also support IE 8.)


5. Static TCP/IP address and resides on the same segment as the Cisco Unified MeetingPlace server


6. TCP/IP connection to corporate directory server


7. Round-trip latency to the Cisco Unified MeetingPlace Server is less than 100ms


8. Access to the Internet


9. 100 mps network speed recommended


10. Sun Java Runtime Environment (JRE) version 1.4.2_05 is installed


11. User name on the Windows 2000 server/workstation with local administrator rights


12. User password


13. Logon as service rights granted for this user


14. Operation System allows short directory/file name conversion (for example, "c:\MeetingPlaceDirectory" can be displayed as "c:\Meetin~1")


Testing Cisco Unified MeetingPlace Server Requirements

15. Test that the Cisco Unified MeetingPlace system is online


16. All profiles have been imported from current production Cisco Unified MeetingPlace system


17. Cisco Unified MeetingPlace server name or IP address


18. Server version


19. Number or profiles


20. License key installed for Directory Integration option


21. Superuser password of the day


22. Cisco Unified MeetingPlace username


23. Cisco Unified MeetingPlace user password


24. System manager rights granted to this user


Customer Directory Requirements

25. Attribute mapping and directory information (obtained from customer)


Netscape/SunOne/iPlanet LDAP Server Requirements

26. User name (Full Qualified Directory Name) in LDAP directory that is used as connection account for Directory Services


27. User password


28. Read and search rights granted on Changelog property to this user


29. Read and search right granted on extracting subtree in LDAP directory to this user


Microsoft Active Directory Requirements

30. User name (Full Qualified Directory Name) in Active Directory


31. User password


32. Replication Directory Changes rights for Active Directory domain (extracting domain) granted to this user


33. Replication Synchronization rights for Active Directory domain (extracting domain) granted to this user


34. Replication directory changes all rights for Active Directory domain (extracting domain) granted to this user (for Active Directory 2003)


35. Read rights for Active Directory domain (extracting domain) granted to this user


36. Extracting subtree




Table: To Verify Before You Begin Onsite Work
Description Complete
Directory Services Installation

1. Directory Services software is downloaded from Cisco.com


2. Directory Services utility is downloaded from FTP site


3. Cisco MeetingTime is downloaded from Cisco.com and installed


4. Corporate directory MetaLink configuration files are copied to the proper directory


5. Install on the console or though PC anywhere/VNC, though not by using Windows Terminal Services


6. Login as local Admin with Logon as Service right


7. Cisco Unified MeetingPlace MetaLink suspense folder is created before you install Directory Services


8. Directory Services console username


9. Directory Services console user password


10. Enable Deletion List


11. Number of entries from corporate directory


12. Cisco GWSIM on Directory Services connects to Cisco Unified MeetingPlace system


13. Deletion time (sec)


14. Deletion update time (sec)


15. Scheduled restarting task


Production Cisco Unified MeetingPlace System

16. Cisco Unified MeetingPlace server name and IP address


17. Cisco Unified MeetingPlace Directory Integration registry key verification


18. Guest user password change to


19. Guest user password change time


20. Guest user profile password change to


21. Guest user profile password change time


22. Guest user group


23. Max Password days (user and profile)


24. Maximum advance day to schedule in Cisco Unified MeetingPlace system


25. Number of profiles




Table: To Verify After You Complete Work On Site
Description Complete
Cisco Unified MeetingPlace Directory Services Server

1. Number of entries in Directory Services


2. Free hard drive space/Used hard drive space


3. MetaLink configuration file and .mmu file backup


4. Update interval with customer directory


5. Disable anonymous access


6. Viewing directory


7. Backup directory


8. Troubleshooting Guide


9. Training


Production Cisco Unified MeetingPlace System

10. Verify that new user can log in to Cisco Unified MeetingPlace (Web Conferencing and MeetingTime)


11. Verify that new changes can be propagated from customer directory to Cisco Unified MeetingPlace


12. Profiles in system after implementation


13. Backup schedule


Rating: 0.0/5 (0 votes cast)

Personal tools