Page History

Follow these steps to start the data migration process:

1. Log on to the SAM server by using SAM service account.
2. Run the utility in test mode as an administrator on the Windows command line: IndeedCM.Migrate.SAM.exe /test utility. The test run of the utility is required to generate a report on what devices and certificates will be migrated during migration, as well as to display information on errors that occurred. In this mode, no data from the repositories is migrated and no events are logged.
3. If no critical errors were detected in the test mode, continue the migration. To do this, run the IndeedCM.Migrate.SAM.exe utility at the Windows command prompt, running as an administrator.
4. During operation, the utility will display the actions performed on the devices and display error information.
   Image RemovedImage Added

If the IndeedCM.Migrate.SAM.exe.config file has the report option enabled, a report file named IndeedCM.Migrate.SAM.Report_dd-MM-yyyyy_HH-mm-ss.csv will be created automatically in the directory with the migration utility.
An example of the contents of a report file opened using Microsoft Excel:

Image RemovedImage AddedData migration success or failure events can be logged on the Indeed Certificate Manager server.

To log migration events to the Indeed CM server, you must use the IndeedCM.EventLog.Proxy component, which allows you to log events to the server log from remote workstations (other Indeed CM servers or the SAM server where the migration utility is running).

To configure the migration utility to record events in the event log of the Indeed CM server, follow these steps:

1. Open the ...SAMMigration\IndeedCM.Migrate.SAM.exe.config file as an administrator in a text editor (for example, Notepad) and add the proxyServer element to the eventLogAuditSettings section with the following attributes:
   • url - the path to the eventlogproxy service deployed on the Indeed CM server
   • userName - user name which to connect to the service (must match the name in the authorization section of the web.config file of the eventlogproxy application)

   • password - password of the service account used to connect

     Code Block
     language xml title Example of a completed section:
     <proxyServer url="https://server2012r2.demo.local/eventlogproxy" userName="DEMO\Administrator" password="P@ssw0rd" />

     
     

2. Save the changes.
3. Install the IndeedCM.EventLog.Proxy component (located in the server distribution directory) on the Indeed CM server.

4. Open the C:\inetpub\wwwroot\eventlogproxy\Web.config file as an administrator in a text editor (for example, Notepad) and specify the credentials for accessing the eventlogproxy service in the authorization section.

   Code Block
   language xml title Example of a completed section:
   <authorization> <deny users="?" /> <allow users="DEMO\Administrator"/> <deny users="*" /> </authorization>

   
   

5. Save the changes.