Support Portal

Installing the server

When the server is delivered, you can go ahead and install it by following the below instructions.

Step 1: Prepare your existing domain

If you have an existing Active Directory domain which your new domain controller will be joining, you need to prepare the existing Active Directory before you install your server. This is explained in the article Preparing An Existing AD Domain (If There Is One) For The Installation

Step 2: Install the server in its intended location

Put the server in its intended location, which could be an office or a purpose-made equipment room; which must be clean and tidy and free of excessive dust and vibration. It should have an ambient temperature at all times of between 12C and 26C.

If you have a rack mounted server, use the supplied rail kit to install the server(s) in the rack. If you have a HA cluster, ensure the two servers are in the same rack and in adjacent slots in that rack. Do not yet plug in the power lead.


Step 3: Optional - Connect the cluster interconnect cables

For HA servers only, the supplied cluster interconnect cables should be plugged into the labelled ports on each server, one cable from port CL1 on the first server to port CL1 on the second; and one from port CL2 on the first server to port CL2 on the second. The supplied cables are deliberately short. If they are not long enough, this suggests that the two servers have been inappropriately positioned and one should be relocated so that the supplied cables can be used.


Step 4: Connect the WAN, LAN and iLO cables.

The person performing the installation is responsible for supplying Ethernet CAT5e cables of an appropriate length for the WAN, LAN and iLO connections.

WAN. The cable (or cables in the case of HA) sourced for the WAN connection should now be plugged into the port labelled WAN on each server, then into the router/firewall through which each server will connect to the Internet.

LAN. The cable (or cables in the case of HA) sourced for the LAN connection should now be plugged into the port LAN on each server, then into the switch through which each server will connect to the client devices on the LAN.

If you have chosen to have DHCP turned on from the outset on the server, you should leave the LAN cable(s) disconnected from the switch until Zynstra has finished its commissioning that follow the installation. Your existing DHCP server should remain active until such time that Zynstra has completed its commissioning in case any issues are uncovered. Once the commissioning has been successfully completed, you can then turn DHCP off on your existing DHCP server and connect the LAN cable(s) into the switch which will activate DHCP on the Cloud Managed Server.

iLO. The cable (or cables for HA) for the iLO connection should now be plugged into the port labelled iLO on each server then into the router or firewall through which each server will connect to the Internet

Step 5: Connect the power and turn on the server

The power leads supplied with each server will enable its connection into either a UPS, a power strip or a standard power socket for the country in which the Cloud Managed Server is being deployed. The use of a UPS for each server is strongly recommended as power loss can cause damage, service outages and/or data loss. 

Step 6: Let us know the server has been turned on

Once the power button has been pressed, you should call the Support Team to notify us that the server(s) has/have been powered up and that the boot sequence has commenced. Once the boot sequence has completed, we will then perform a remote connectivity test to ensure that the Cloud Management Platform can communicate correctly with the server(s), both through the WAN and iLO connections. Zynstra will now start the Commissioning process, which usually takes approx 4 hours.

Step 7: Optional - create a static route on your existing LAN

If you are installing your server into an existing network, and keeping the existing default gateway device (normally a router or firewall) in place, then you need to add a static route so all client devices can access the virtual machines running on your new server. If you have an existing domain; the static route is needed so the new and old domain controllers can talk to each other. Please view the article Static Routes explained for help on how to create a static route

Step 8: All finished

When the Zynstra support team have finished the commissioning we will get in contact to let you know, and send you a Welcome email. The Welcome email will contain all the details of the server and the names and IP addresses of the virtual machines and management tools/interfaces.



Was this article helpful? 0 out of 0 found this helpful
Have more questions? Submit a request
Powered by Zendesk