Deployment

 LDAP Sync ModeCombine with Online ModeCombine with Offline Mode/Off-Grid Mode/SCIF Mode
AD/DS | LDAP Sync OnC/S/PC/S
AD/DS | LDAP Sync OffC/S/PC/S
C: Client, S: Server, P: Portal

Client Deployment

The client installation package is all you need for a batch deployment. It includes the following major components:

  • Client Connection File (client.connection)
    The IT admin can edit the IPv4 and port from this file to point to the CICB server. Then deploy this file along with the CICB client.
  • Banner (banner.exe)
    It will display on the screen based on settings from the server -> settings -> group -> screen.
  • Client (client.exe)
    It will ping the server via a socket default TCP port: 56789, the IT admin needs to exempt the port prior to deployment.
  • Client Config Manager (CCM or ccm.exe)
    The IT admin can deploy this file along with the CICB client if the goal is to update the user profile’s security group via a CLI command. (See CCM for more use case examples)

Group Policy Objects (GPO)

With a customized script file, the IT administrator can deploy the CICB client (non-installation version) to all target workstations/OS/VMs. The IT administrator can set up the CICB server with a port before deploying all clients.

Agent Deployment

Agent License File (<agent-id>.license)

Refer to the user manual’s license section. The IT administrator can change the CICB server port to your desired port.

Software Portal Deployment

There is no plan to provide this part to any 3rd party for their LAN deployment yet.