Cisco Unified MeetingPlace, Release 7.0 -- How to Manually Synchronize the Web Server in a Domain

From DocWiki

Jump to: navigation, search

Main page: Cisco Unified MeetingPlace, Release 7.0

Up one level: Configuration




Complete the following tasks in the order presented to synchronize the time between your Cisco Unified MeetingPlace Application Server and Cisco Unified MeetingPlace Web Server if your Web Server machine is part of a domain.



Contents

Pointing the Domain Controller to the External NTP Source

Before You Begin
  • This procedure is completed on the Domain Controller that includes the Cisco Unified MeetingPlace Web Server as part of its domain.
  • Use export to save all of the registry settings to a flat file.


Procedure
  1. Open a command prompt.
  2. Enter the following command: net stop W32Time
  3. Point the domain controller to the external NTP source:
    • Run the following command: w32tm /config /manualpeerlist:<NTP provider> /syncfromflags:manual /reliable:yes /update where <NTP provider> is an NTP provider such as clock.cisco.com.
  4. If the previous command completed successfully, enter the following command: net start W32Time
  5. Verify that the external NTP source is active:
    • Run the following command: w32tm /stripchart /<NTP provider> /samples:2/dataonly
    • The output should show the local time and the external NTP provider time. Compare the two times to confirm that there are not any differences between them.


NOTE: If you upgrade or reboot the Web Server, all manual changes made to the registry by the W32Time command are lost.


What to Do Next

Proceed to Changing the Registry Setting on the Web Server.



Changing the Registry Setting on the Web Server

Before You Begin
  • This procedure is completed on the Cisco Unified MeetingPlace Web Server that is part of the domain.
  • Use export to save all of the registry settings to a flat file.


Procedure
  1. Open a command prompt.
  2. Enter the following command: net stop W32Time
  3. Run the following command: w32tm /unregister
  4. Run the following command: w32tm / register
  5. Change the value of the registry setting "HKLM\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type" to NT5DS.
    Initially, this will be set to NTP.
  6. Enter the following command: net start W32Time
  7. Run w32tm /dumpreg to verify that all of the registry settings are correct.
    Note: Do not expect the Web Server to match the external NTP source immediately after starting the w32time service. Synchronizing the time between the two systems will occur gradually.


NOTE: If you upgrade or reboot the Web Server, all manual changes made to the registry by the W32Time command are lost.


What to Do Next

Proceed to Configuring the Application Server to Point to a Different NTP Server.



Configuring the Application Server to Point to a Different NTP Server

The Application Server currently points to the NTP server on the Application Server itself. Complete this procedure to point the Application Server to the NTP server referred to by the domain controller.


Before You Begin
  • This procedure is completed on the Cisco Unified MeetingPlace Application Server that the Web Server points to.


Procedure
  1. Sign in to the Cisco Unified MeetingPlace Application Server by using SSH with valid credentials.
  2. Run the net command and choose option 1 to list the current configuration.
    The current configuration should point to the NTP server that is on the Application Server.
  3. Select option 6 to configure the NTP service.
  4. When finished, select option 1 again to verify that the NTP provider is set correctly.

Rating: 0.0/5 (0 votes cast)

Personal tools