Description:

This document is meant to validate basic configuration of the Cloud Service Appliance. It takes into account most all potential configuration issues. Please read step-by-step as that is how this document was created.

Here is a video of the process that includes core and agent side information: LANDESK - CSA - Installation and Configuration - YouTube

Note: With the Virtual CSA you may see eth0 and eth1, or eth2 and eth3, etc… this is normal. The lowest numbered NIC is typically the external NIC.

Steps:

1. Click System > Configure date and time
2. Click Save
3. Click on System > Network Settings
4. Remove any references to the 192.168.0.1 and 192.168.0.2
5. Set IP, subnet, and gateway for your network on eth0
6. Click add
   1. If you are setting up dual NIC repeat steps 5 and 6 for eth1, else move on to 7
7. Enter DNS server if applicable
8. Click add
9. Set the hostname and DNS suffix for your device
10. Click save
11. Click on the hostnames tab
12. Remove any references to the 192.168.0.1 and 192.168.0.2
13. We will want to add the core server(s) here
    1. Take note of the format as it is different for different items
14. Core IP, Core FQDN, Core Hostname (no caps) click add
15. Ping license.landesk.com, patch.landesk.com and patchec.landesk.com to validate the IP addresses as they are always subject to change
16. Enter  204.246.148.180, license.landesk.com, license.landesk.com click add
17. Enter 64.40.112.186, patch.landesk.com, patch.landesk.com click add
18. Enter 67.59.141.4, patchec.landesk.com, patchec.landesk.com click add
19. Enter 84.51.239.169, patchemea.landesk.com, patchemea.landesk.com click add
20. Click save
    
21. Click on the security section
22. Remove any subnets you use from the blocked list
    1. Take note of the subnets and if they overlap your ranges
23. Add the core IP to trusted list, even if you plan to disable the firewall it will ensure if for some reason it is turned back on your core will still connect
24. Add the 204.246.148.180, 64.40.112.186, 84.51.239.169, and 67.59.141.4 IP's in the trusted. These are the LANDESK patch and license servers
    
25. Click save at the bottom
26. Click on the users section. Make sure you know the service account password; we will need this to configure the core. It will only be used on the core server(s) in one location(Configure > Manage Gateway/Manage Cloud Service Appliances), so if you don't know it go ahead and reset it so you can have the correct password
27. Click on the Gateway Service Section. In the additional Hostnames section you will want anything the gateway can resolve to or from, FQDN, internal and external IP. DO NOT ADD SHORTNAMES
    
28. Click Save
29. Install Patches (See link for order of operation in regards to 4.2 CSA)
    1. Best Known Method for Configuring LANDESK Cloud Service Appliance (former Management Gateway) version 4.2 and newer
30. The next steps apply only to 4.3 CSA and only after the first time its patched
31. Click Manage LDMG Certificates
32. For self-signed certificates only, click Remove
33. Click OK to verify you want to remove the certificate
34. Repeat process to remove the second certificate
35. Click System
36. Click Appliance
37. Click Reboot
38. Click OK to verify the reboot
39. If this is a VM take a snapshot at this point as it will be your base configuration
40. Access CSA via web browser http://CSAIP
41. Click Cloud Service Appliance Console link
    1. if you see this certificate prompt, click cancel until you get a username and password prompt
       
42. Login with the admin user
43. Click System > Backup and restore
44. Click Backup Now
45. Export backup
46. Your CSA is now ready to have the core server connection configured