Skip to main content
Waters

What steps are required to migrate to a new audit trail (LogLynx) server for a MassLynx Security environment? - WKB96609

Article number: 96609

OBJECTIVE or GOAL

Migrate to a new audit trail (LogLynx) server for Masslynx Security environment.

ENVIRONMENT

  • MassLynx 4.1
  • MassLynx 4.2
  • MassLynx Security
  • Windows 7 Professional
  • Windows 10 Enterprise

PROCEDURE

  1. Export events from current audit trail file:
    1. From any PC with MassLynx Security enabled and LogLynx installed, enter LogLynx as either as a MassLynx Administrator or user with rights to Import and Export from LogLynx.
    2. In LogLynx, go to File > Export.
    3. Enter the date and time range to export the events that will be transferred to the new audit trail file.
      • Note: To export all events, enter a From date that is 1 day earlier than the first date in the audit trail and enter a To date that is 1 day later than the last entry.
    4. Select the Mode, Export or Export and Remove.
      • Note: Which option is selected here will be based on local operating procedures regarding exporting of events from the log.
    5. Click the Export button
    6. Read the Export Event message. Click YES if agreeing to the message.
    7. Click OK to the message, noting the number of events and the size of the export file.
    8. Enter an appropriate file name for the export file and save in an appropriate location. Note the location. Hit Save.
    9. Verify that the file was created in the specified location. File extension is *.ear.
  2. Prepare new server:
    1. Log into new server as an administrator with rights to create users and install software.
      • To install MassLynx with full security, you must have the password for the default Windows Administrator account for the local machine.
      • There must also be a user account with the username Micromass on the local computer. The password for this account can be set by the IT group but configured not to change or expire and not to change upon first login.
    2. If no Micromass user account exists on this PC, create one before moving on to step 3.
    3. Make the appropriate changes to the Firewall and DCOM setting on the server per the attached document.
    4. After making the changes outlined in the document, reboot the server.
    5. Install MassLynx with Full Security, selecting the following options:
      • Note: The purpose of installing MassLynx on the server is to install the two required services and to create the new audit trail file.
      • No Instrument (Desktop Only)
      • Appropriate Security option Full Security or Basic Security
      • Do not install the Audit Trail Viewer (LogLynx) on the server
      • Specify a location for the Audit Trail file if not using the default location (C:\Windows\MMAuditLog)
      • Do not install any Standard or Optional Application managers on the server
      • Use the local Micromass user account and local Administrator user account to sign off on the installation (if installing Full Security)
      • Launch MassLynx to start the services
  3. Connect MassLynx Acquisition and Processing PCs to the new server:
    • Note: The following steps must be performed on each Acquisition and Processing PC with MassLynx Security installed.
    1. Log in to the MasslLnx Security Manager.
    2. From the menus, go to Policies > Audit...
    3. In the Audit Policy > Remote Logging section, specify the name of the new server in the Store On field. Server names are case-sensitive.
    4. Click OK to accept the changes.
      • Note: If the changes are not initially accepted, reboot the MassLynx PC and try again.
    5. Save the new security settings.
    6. Close the MassLynx Security Manager.
  4. Importing the Audit Trail Events:
    1. From any PC with MassLynx Security enabled and LogLynx installed AND where the Audit Policy > Remote Logging has been updated to the new server, enter LogLynx as either as a MassLynx Administrator or user with rights to Import and Export from LogLynx.
    2. Go to File > Import.
    3. Browse to the *.ear file created in Part 1 of this procedure.
    4. Click Open.
    5. Review the Import Details in the dialog that appears and click OK.
    6. Verify that the events imported into the new audit trail file are correct.
    7. Close LogLynx.

ADDITIONAL INFORMATION

 

id96609, MLYNX, MLYNXV41, SUPMM

Not able to find a solution? Click here to request help.