General plan of implementation

1

1. Providing server and client resources in accordance with their system and hardware requirements
2. Installation and configuration of Remote Desktop Services role on session basis.
3. Installation of additional Microsoft components required for correct operation of Indeed Identity PAM server components.
4. Configuration of networking between server and client components according to the requirements.
5. Configuration of Indeed Identity PAM data storage:
   
   1. Installation of Microsoft SQL Server/PostgreSQL Pro or providing access to an existing Microsoft SQL Server/PostgreSQL Pro instance.
   2. Creation of databases and configuration of service account or provision of access to an existing account.
6. Definition of LDAP paths to containers and organization units in the Active Directory hierarchy to place Indeed Identity PAM end users to.
7. Creation and configuration of service account for use with Active Directory user directory or provision of access to an existing account.
8. Creation and configuration of service account to use for service operations in Active Directory or provision of access to an existing account.

1. Choosing a deployment type.

2. To deploy PAM components on Windows OS:

   • Management server
   • Access server (RDP/RemoteApp).

   To deploy PAM components on Linux OS:

   • Management server
   • Access server (SSH)

• Installation of Indeed Identity PAM Agent client component.
  
• Installation of the PamSu component.
• Installation of PAM Desktop Console utility.

1. Operability check for server and client components.
2. Check of system functions and customer scenarios:
   1. Configuration of service operations for Windows resources.
   2. Configuration of service operations for *nix resources.
   3. Configuration of user connections.
3. Troubleshooting.

1. Demonstration of operation.
2. Training to use the Indeed Identity PAM.
3. Testing.