This article describes how to start the CIC Agent service as a qualified user, which is a user that has privilege to the network resources being accessed.

Procedure Overview

1. Create a new Access Point (to get the PowerShell installation script) in CIC.
2. Install and configure your CIC Agent.
3. Add new File System Endpoints in the CIC for both source and destination directories.
4. Set up your Data Flows.

Note: The solution described below uses UNC paths, not mapped drives. Mapped drives are relative to a logged-on user and their logged-on experience, and are therefore not effective/reliable for CIC Agent communications.

Assumptions

1. File server shares of desired data directories are set up properly on the Active Directory domain controller/file server.

• At least one domain user or user group has been given read and write (or Full Control) permissions to the share data directories.

Values used in this document for sample purposes only

Domain = win2019.local also known as WIN20190.

Domain user = cleo100 with a password of Password@1.

Domain user group (with Full Control to network share) = cleoagents.

File server = win2019.

Network directory UNC path = \\win2019\public\.

Client machine (running the CIC Agent) = win2019-2.

Procedure

Before proceeding with the steps below, please note the following on client machine administrative access.

• On the client machine (win2019-2), add the desired domain user (cleo100) or the desired domain group (cleoagents) to the local Administrators group.

Create an Access Point in CIC

Create and save an Access Point from the Network > Access Points page. As part of this process, a Powershell installation script is provided which, when installed as an administrator, ensures the CIC Agent has sufficient access to content on this Access Point. The status for this Access Point will be Pending, until the Agent is activated and successfully connected to the CIC Cloud.

Install and configure the CIC Agent

1. Install the CIC Agent via the PowerShell script. These instructions are provided in the CIC as part of Agent creation.
2. Launch services.msc.
3. Stop the Cleo Agent service if running.
4. Right-click on the Cleo Agent and select Properties.
5. From the Log On tab, select the This Account radio button and click Browse.
6. Click the Locations button, expand the Entire Directory field, and select the domain (win2019.local);  click OK when done.
   
7. Enter the desired network username (cleo100) and password (Password@1), then confirm the password and click OK.
   A dialog box should appear confirming that the user has been granted access to run the service.
8. Start the Cleo Agent service.
9. Continue to refresh the Services window (should take no longer than 10 seconds), verifying that the Cleo Agent service remains running.

Add a new File System Endpoint in the CIC (for source directory)

These steps take place from the Network > Endpoints page in the CIC.

1. 1. Create a File System Endpoint and select the newly created Access Point (described above).
   2. Edit the Access Point path by clicking the button, and enter the UNC path.
      
      For example: \\win2019\public\source\
      
      
   3. Once entered, click Go, Select, and then Save.

Add a new File System Endpoint in the CIC (for destination directory)

These steps take place from the Network > Endpoints page in the CIC.

1. 1. Create a File System Endpoint and select the newly created Access Point (described above).
   2. Edit the Access Point path by clicking the button, and enter the UNC path.
      
      For example: \\win2019\public\dest\
      
      
   3. Once entered, click Go, Select, and then Save.

Setting up Dataflows

Proceed with setting up dataflows to utilize the newly created endpoints.

Regarding VPNs

CIC itself is unaware of VPN connections, but the CIC Agent can be used with a VPN if the network directories are only reachable by a VPN. The VPN connection must be turned on and operational in order for the CIC Agent to use it. It is recommended to use IP address in place of domain names, if possible, to help alleviate DNS issues related to VPN connectivity.