Import contacts to Office 365

If you use Microsoft’s subscription email client, Outlook 365, then importing contacts will need to be done via Outlook 2016, 2013, 2010 or 2007 (desktop or laptop client).

In Outlook desktop client, add your Outlook 365 account.

Just go to the file and then click on Add Account option and add your email account here. It could be your gmail account or any other email account. Just the add the account and click finish.

The two Outlooks should then sync and you will find your online emails and contacts accessible on the desktop client.

You will then need to import your new contacts to the synced account.

On the desktop client go to file at the top right side.

 

 

Go to Open & Export and choose Import/Export.

 

 

The Import/Export wizard will open asking how you wish to import. If you’re importing a CSV file, go to ‘Import from another program or file’.

 

 

Select ‘Comma Separated Values’ and then click next.

 

 

You will be asked to locate the CSV file on your computer, so make sure it is in an easy to locate place (such as desktop or downloads folder).

 

 

You will also be asked about importing duplicates, so check the option you prefer (the default is ‘allow duplicates to be created’).

Click Next and you will be asked where you want your contacts to be saved. Here you will need to make sure that you are selecting your Outlook 365 account.

 

 

Once you’ve selected the destination, click Next and then Finish.

 

 

Log in to your Outlook 365 account and your new contacts should be fully imported!

How to Static an IP Address

In this tutorial you will learn step by step how to assign static IP addresses and DNS server addresses on Windows 10.

To set up a static address you need to locate the Connection you are using.

windows-settings

 

1. Click on the Windows Icon Lower left.

2. Click the Settings icon

3. The windows setting screen appears click on the network and Internet link.

windows-settings-Inter

4. In the Network status pane locate the change adapter options link and click it

network-status-window

5. You should now see your network adapters. I have two installed and the Wi-Fi adapter is disabled. If your PC is equipped with two; as most are, then only use one and disable the other.

network-connections-window
6. Right click on the icon and select properties from the drop down list.

network-connection-properties

7. Use the scroll bar to locate TCP/IPv4 and click it to highlight it,and then click the properties button.

Local-connection-properties

If you are using DHCP then you should see a screen like the one below.standard-ip-address-settings
You can uncheck the automatic assignment of IP address and or DNS server address. Then enter your own details as show below:

static-ip-address-assignment

Notes:

1. My home network use the network address 192.168.1 (first three numbers) also common is 192.168.0 and 10.x.x.x

2. The default gateway is the address of your router. This is assigned to the router as a static IP address.

3. The subnet mask is important as is usually 255.255.255.0

4. You need the address of 1 DNS server to access websites on the Internet. The Google DNS server is available to use for free but you can use your ISP DNS servers.

5. You can choose to manually assign the DNS addresses and automatically assign the IP address or vice versa.

Why it’s important to secure your remote desktop connections

Created by XKLN, this website gives a useful non-technical explanation of why RDP is so dangerous and why it’s important that it never be opened directly on your router, and explains in a way, why CNS utilizes VPN’s for Remote Desktop connections to our customers Servers.

 

 

View the full site at https://rdp.exposed/

Install MikroTik RouterOS on a Vultr VPS

MikroTik RouterOS is a Linux kernel based operating system that turns a computer into a network router. It possesses the following features:
  • Firewall.
  • Virtual private network (VPN) server and client.
  • Bandwidth shaping.
  • Quality of Service (QoS).
  • Ability to act as a wireless access point.
  • Bridging.
  • Portal-based hotspot.

Prerequisites

Step 1: Upload, deploy and run the SystemRescueCD live ISO

  1. Navigate to the Vultr’s Upload ISO page.
  2. Copy and paste a link to the SystemRescueCD ISO inside the “Remote URL” text field.
  3. Click the Upload button and the ISO will be installed in your personal library.
  4. When you are ready to deploy your server, proceed as you would normally, except choose the Upload ISO option when deploying, and click on “systemrescuecd-x86-x.x.x.iso” under My ISOs.
  5. Start your server instance.

Step 2: Download and install the MikroTik RouterOS raw disk image

  1. Open your browser to the MikroTik RouterOS download page.
  2. Scroll down to the “Cloud Hoster Router” section.
  3. Right click on the floppy disk image in the “Raw disk image” row and the “x.xx.x (Current)” column.
  4. Select “Copy Link Location” on the menu. The raw disk image URL will be saved to your operating system’s clipboard.
  5. Open a text editor and paste the URL for safe keeping.
  6. On the Vultr server instance page, click on View Console for your running SystemRescueCD instance.
  7. Use the wget command to retrieve the URL link you pasted in your text editor by typing it inside of the *View Console” window.
    wget https://download2.mikrotik.com/routeros/x.xx.x/chr-x.xx.x.img.zip
    
  8. Use the unzip command to extract the raw disk image.
    unzip chr-x.xx.x.img.zip
    
  9. Use the dd command to write the raw disk image to the Vultr virtual disk.
    dd if=chr-x.xx.x.img.img of=/dev/vda
    
  10. Under the SettingsCustom ISO section of your server instance, click the Remove ISO option. Your server will be rebooted.
  11. Refresh the View Console windows and type admin at your new MikroTik login. The password is blank. Just hit the “return” key.

MikroTik RouterOS is now installed to your Vultr instance. Follow the guide here to secure your router, which will allow you to access it remotely. Thanks for reading.

How to adopt Unifi Devices

UniFi – Device Adoption Methods for Remote UniFi Controllers

Overview

This article describes several different layer-3 methods for adopting and deploying UniFi devices remotely. Our recommended methods are found below under the Chrome Web Browser and Mobile App sections.

Table of Contents

  1. Introduction
  2. Initial Setup
  3. Recommended L3 Adoption Methods
    1. Chrome Web Browser
    2. Mobile App
  4. Advanced L3 Adoption Methods 
    1. Discovery Utility
    2. DNS
    3. DHCP Option 43
    4. SSH
  5. User Notes & Tips
  6. Related Articles

Introduction

In many deployments where it’s not possible to have the UniFi Network Controller running on-premise, you can run the controller in the Cloud or your NOC. For example, for a large-scale project with many devices there are a few possible methods for adoption of devices:

  • Take a laptop to the device’s site to perform adoption via Chrome Browser (easiest method).
  • When you’re at the site, open a browser and navigate to Cloud: either the UniFi Cloud Access Portal or the UniFi Network Controller (when launched using Cloud).
  • Create a virtual controller instance on Amazon EC2. Read this article on the subject.
  • Either configure the DHCP server, DNS server or simply use the UniFi Discovery Utility to make all local access points (APs) inform back to the controller.

Initial Setup

Please make sure you’re familiar with how a regular L2 adoption on UniFi works (where the devices and Controller are on the same network) before attempting L3 (remote) adoption. Also, remember that in order to adopt, the following conditions must be true in order to have internet access and also have access to the router from within the network (locally):

1. WAN port connected to the Internet.
2. LAN port connected locally to access management features on the router (USG or third party).

UniFi APs have a default inform URL http://unifi:8080/inform. Thus, the purpose of using DHCP option 43 or DNS is to allow the AP to know the IP of the Controller.

Chrome Web Browser

After installing the Discovery tool plugin (freely available in Chrome Web Store) on a computer running Chrome browser, any locally-available, unmanaged UniFi Devices (i.e., same L2 network as your computer) will appear as “Pending Adoption” in the UniFi Cloud Access Portal as well as your UniFi Network Controller itself (in the Devices section in both cases). To access the Controller remotely Remote Access will have to be enabled.

Via the UniFi Cloud Access Portal

1. Go to https://unifi.ui.com/ and log in with your Ubiquiti SSO credentials.

2. Go to the Devices section and locate the model with the Pending Adoption status. Click ADOPT.

3. In the Adopt window that will appear, select the controller and the site that will be adopting the device and click Adopt.

Via the UniFi Network Controller

1. Launch the UniFi Network Controller, go to the Devices section, find the device that is to be adopted with the status “Pending Adoption” and click Adopt under Actions.

Mobile App

1. After installing the UniFi Mobile App (freely available in iOS App Store & Android Play Store), launch the app, and tap Direct Access (in iOS, in Android you will see the Direct Access section on the screen once you launch the app, see images below).

NOTE:Your mobile device must be connected to the same network as your devices, and must be able to access the controller directly (using HTTP). A public IP and/or port forwarding may be necessary. The inform port of the controller must be 8080.

2. Select your Controller from the list, or tap the “Add Controller” to log in and add your controller.

iOS

Android

3. For iOS: Once logged in to the Controller, tap More. There will be a Layer 3 Adoption option under Utilities.

For Android: Once logged in to the Controller, tap More, then click on Remote Adoption from the menu.

iOS

Android

4. Devices will be displayed on this screen. Tap on the device that is to be adopted and select Adopt.

iOS

Android

5. After a few seconds (15-30 seconds, times will vary) the device will appear under the Devices section, which will be accessible by clicking on the Devices icon on the bottom menu bar.

Discovery Utility

This utility listens to the multicast/broadcast packets from UniFi APs and allows you to configure the AP to inform any URL you’d like. It is important to note that only APs in a default state or not in contact with any other controller will be displayed.

UniFi Discovery utility is installed along with the UniFi Network Controller.

  • On Windows, it’s in Start Menu > Ubiquiti UniFi >UniFi-Discover
  • On Mac, /Applications/UniFi-Discover.app (or use Spotlight to find it)
  • Run “java -jar <unifi_base>/lib/ace.jar discover”

The option of the Ubiquiti Discovery Tool Chrome extension is also available, downloadable directly from Google Chrome here, or from our Ubiquiti download page.

To perform L3 adoption with the Discovery utility:

  1. Launch the Discovery Utility and wait until the device appears. If the device is not in a default state (new out of the box, or reset to its factory default settings), click “reset”, specify the SSH username/password and click “Apply”. If unsure about device authentication credentials, please take a look at this article: UniFi – Accounts and Passwords for Controller, Cloud Key and Other Devices.
  2. Click “manage”, modify the inform URL and leave the SSH username/password as ubnt/ubnt and click “Apply”.
  3. Open a browser to your UniFi Network Controller and you should see the device is “Pending Approval” in the Devices screen.
  4. Click on “Adopt”. You’ll see it going to “Adopting” state, ignore it as it’ll eventually become “Adoption Failed” or “Disconnected”.
  5. Perform step 2 again, setting the inform URL again. There is no need to wait for step 4 to finish.
  6. After a few moments, the devices will now be managed by the Controller and will appear as Connected. You may need to leave the Devices page and return to see this reflected on the screen.
NOTE:If your L3 Controller is available over the WAN then you need to make sure the necessary ports are open at the Controller side (minimum port 8080 for inform). If you do not have a static IP then you may want to consider using a dynamic DNS service, and use the domain name instead of the IP for the inform address. If you’re using a USG then you can use the DDNS client that is available on that device itself.

DNS

You’ll need to configure your DNS server to resolve ‘unifi’ to your Controller’s IP address. Make sure that the device can resolve Controller’s domain name. For example, if you are setting http://XYZ:8080/inform, then ping from the device to determine if XYZ is resolvable/reachable. Or you may also use FQDN for the Controller inform URL: http://FQDN:8080/inform

Troubleshooting: Device (with static IP) fails to connect to the L3 Controller

  • When configuring a device from DHCP to static in the Controller UI, make sure you have put the IP of DNS. If not, then the device cannot contact DNS to resolve Controller domain name.
  • If the device has been reset, make sure that you have “informed” the device twice (using the Discovery Utility) about the Controller’s location. See steps in the section above.

DHCP Option 43

If using Ubiquiti’s EdgeMAX routers, then DHCP option 43 can be done by just entering the IP address of the UniFi Network Controller in the “unifi” field on the DHCP-server.

NOTE: TheUniFi Security Gateway (USG) will not use DHCP option 43 to add the UniFi Network Controller location when obtaining a DHCP lease on the WAN interface.

To use DHCP option 43 you’ll need to configure your DHCP Server. We provide some third party examples below, but please refer to the manufacturer’s support documentation for up to date instructions. For example:

Linux’s ISC DHCP server: dhcpd.conf

# ...
option space ubnt;
option ubnt.unifi-address code 1 = ip-address;

class "ubnt" {
        match if substring (option vendor-class-identifier, 0, 4) = "ubnt";
        option vendor-class-identifier "ubnt";
        vendor-option-space ubnt;
}

subnet 10.10.10.0 netmask 255.255.255.0 {
        range 10.10.10.100 10.10.10.160;
        option ubnt.unifi-address 201.10.7.31;  ### UniFi Controller IP ###
        option routers 10.10.10.2;
        option broadcast-address 10.10.10.255;
        option domain-name-servers 168.95.1.1, 8.8.8.8;
        # ...
}

Cisco CLI

# assuming your UniFi is at 192.168.3.10
ip dhcp pool <pool name>
network <ip network> <netmask>
default-router <default-router IP address>
dns-server <dns server IP address>
option 43 hex 0104C0A8030A # 192.168.3.10 -> CO A8 03 0A

# Why 0104C0A8030A ?
#
# 01: suboption
# 04: length of the payload (must be 4)
# C0A8030A: 192.168.3.10

Mikrotik CLI

/ip dhcp-server option add code=43 name=unifi value=0x0104C0A8030A
/ip dhcp-server network set 0 dhcp-option=unifi

# Why 0104C0A8030A ?
#
# 01: suboption
# 04: length of the payload (must be 4)
# C0A8030A: 192.168.3.10
User Tip: Find more DHCP Option 43 instructions in the User Notes & Tips section.

SSH

If you can SSH into the device, it’s possible to do L3 adoption via CLI command:

These notes have been added thanks to user collaboration. Have anything to contribute? Click on the Give Feedback button below!

Windows Server DHCP Option 43

User Tip:For Windows Server please see this external blog post.

Using PFSense with DHCP Option 43

NOTE:As in all our examples, we are using a sample IP address, you would input your own.

1. Input your IP in https://www.browserling.com/tools/ip-to-hex

Screen_Shot_2018-02-21_at_2.05.39_PM.png

2. Click Convert to Hex!

Screen_Shot_2018-02-21_at_2.05.46_PM.png

3. Add 01:04 to the beginning of the converted IP, so it would look something like this:

01:04:ac:10:21:04

4. Insert this in the Value field.

Screen_Shot_2018-02-21_at_2.07.32_PM.pngUsing Palo Alto Networks with DHCP Option 43 (Pan OS 7.1)