Doing Initial System Setup and Adding to Domain

Post date: Jul 08, 2016 1:42:49 PM

Configuring a new PC for use on the ADXBA Network

Adding the System as an Asset, and Labelling

As part of our company process, we need to ensure that our equipment is logged and labelled correctly with the PC Name and asset code.

In order to do this, you need to send some information to our accounts department:

As so, with the details specified, if you don’t know the cost then say so!

Accounts will then give you the asset sticker to stick onto the system:

Asset No Sticker Location

A sticker with the system asset details needs to be stuck on a workstation chassis or on the bottom of a laptop on a NON REMOVABLE cover.

System Sticker Location

A sticker with the system name (IE. ADXBA-NB30) needs to be stuck on the bottom right of the display (on a laptop) or on the workstation chassis)

On the New Computer

<----Our Computer Naming Convention

In order to standardise our equipment we have a set naming convention when adding systems.

We ALWAYS put ADXBA at the start, followed by a hyphen (-)

Then for Workstations (Ie. normal PC’s) we use WS

And for Notebooks / laptops we use NB

So a Workstation could be ADXBA-WS10 or a notebook ADXBA-NB30

---->

Please ensure you set the PC name using this convention

Local User on Computer

As we’re using a fresh copy of windows, we need to go through the wizard to do the basic setup.

We’re generally happy with express setup, BUT we do not want to register the system to a microsoft account etc.

So You must ensure that you set the local user, and make sure you use the following user setup:

adxba

Usual

This allows us to always have the local user the same through all of our assets.

The system will then take a short while to sort itself out, reboot and will present you with a login screen, login with the user you created.

Install OpenVPN

We use openVPN to allow all of systems to be connected together, and as such the first stage of any setup is to get this installed and setup.

All of the needed files are on our OpenVPN directory on the Technical Shared Drive

Download the Open-VPN installer, and run through the wizard (standard settings should be fine for now) <------ Tom to double check this

And Click Install.

During the installation process OpenVPN will want to install a new network adapter, make sure you allow this otherwise it won’t work!

Configuring OpenVPN

OK, now we have openVPN installed on the system, we need to do some basic configuration to get it to work .

We now need to enable the service to allow the system to automatically connect.

So we need to:

Open run command (Windows Key + R) and type services.msc

We just need to validate that our DNS is working as well, so lets try pinging int.adxba.co.uk

So you can see that the same server responded so it means that it is correctly forwarding the traffic.

For any diagnostics there is a log file in c:\program files\openvpn\log\client.log.

Adding the system to the domain

OK, now the VPN connection is established to our Active Directory server, we need to add this computer to the domain.

Do do this we need to open the system properties, quickest way to do this is right click the start button and click System

In System we want to go into the Computer name, domain and workgroup settings and click Change Settings

Make sure Domain name is INT.ADXBA.CO.UK

In the next window, we need to use the PC name that we determined earlier during the OpenVPN config