ElderUsr's Blog

This is a small journey in my recent headaches of Windows Server 2016 and updating. I had the opportunity to work with a fresh Windows 2016 Version 1709 copy of Windows. I was super stoked was ready to use it to install some wonderful microsoft services and then BAM. 0% Downloaded, Updates Available. Hmm. Ill let it sit for a few hours (cause that whole waiting for a kettle to boil thing) and come back. Still nothing. Finally, go digging: - Restarted the box. - Restarted both BITS and Windows Update Service - Wiped out the SoftwareDistribution folder under %windows% What's next? I have no clue. I am hoping that I will be able to come back to this post with the answer. Until then thats that. Found the issue. Dont disable Windows Firewall Service in Server 2016 1607. Once it was re-enabled and still Firewall disabled, Windows update started to work. Who'd knew?!

This post is for my own sanity, and will explain how I went ahead and got Linux Server (Ubuntu 16.04.1) reporting in my BigFix Server. Installation of the Client : 1. Create a directory - mkdir /etc/opt/BESClient 2. Download the associated file for your Linux Client from here . 3. Install the deb file using dpkg -i 4. Copy the Masthead from your BigFix Server over to the Linux Server and rename it: wget http:// :port/masthead/masthead.afxm cp masthead.afxm /etc/opt/BESClient/actionsite.afxm 5. Start the service - /etc/init.d/besclient start  Using built-in QnA functionality: One of the biggest things that I did notice/like is that it does have the ability to use either graphical QnA if you have a graphic version instead, or CLI QnA, I'm still learning some of the Linux Relevancy and how it works, but its pretty much the same as what you use within Windows: 1. Create a file called runqna and open it with your favorite text editor, entering the below code: #!/bin/...

This post will outline the steps associated with installing a RJ45 (Cat 5e) Wall Jack using Beldin Wall jack. Parts List: Cat 5e or Better Cabling Belden PS5E BIX DVO Outlet Nordix Punch-down Tool Steps: 1. Start with a basic Cat 5E Ethernet Cable 2. Cut cable back approximately .5 inches, which gives you enough room to pull on the thread back. 3. Make a small incision on the shielding which allows you to pull back the thread further. Do not use the associated .5 inches on the end portion of the Belden as you do not know if you accidentally cut the wire. 4. Pull back on the thread, revealing more of the cable up to 2 inches worth. 5. Clip off the shielding and the thread used to cut back the shielding. 6. Open up the container holding the Belden PS5E and separate the faceplate from the Belden Outlet. 7. Pass the cable through the cable management portion on the Belden Outlet, and then begin wiring. 8. The pattern for wiring the Outlet is: w/bl, bl, ...

This document will outline how to configure from Factory Reset a Unifi 48-Port PoE Switch into a AWS Cloud Controller. 1. Reset your Unifi 48-Port PoE Switch by pressing and holding in the Reset button on the right-side of the switch for 5 seconds. 2. Verify that it is connected to the LAN that either your controller is located, or in this case a network that can provide DHCP Services and reach the internet for AWS Controller Registration. 3. Your Device will boot up with an acquired DHCP IP address. You can either find out the IP of the switch using the details provided from your local DHCP Server, or use a tool such as Zenmap or Nmap. 4. Once found, SSH into the device using ubnt/ubnt as the default login and password and perform set-inform http:// :8080/inform this will then allow your device to show up within the Unifi Controller for adoption. Note : You can also cat the /var/log/ on the server to get additional details if it is functioning or failing. 5. Make sure t...

This document assumes that you have already created an AWS Cloud Controller for Unifi + opened associated ports that are required for communication between the server and the endpoint. 1. Plug it all in, using the LAN port plug your PC in, and WAN port for your ISP. 2 Go to https://192.168.1.1 on your PC. 3. In the Inform URL section, type in your AWS Cloud Instance's URL and :8080/inform at the end of it such as: https:// :8080/inform 4. If that does not work, SSH into the device using ubnt/ubnt as the default credentials and perform the following commands: set inform https:// :8080/inform set inform http:// :8080/inform 5. Recheck your AWS Controller, it should now have an option for adoption such as below. 6. Log back into the USG via SSH, and issue the adopt/inform command again, it'll show another message about adoption within the Controller. You may need to do this twice. 7. It eventually will show Provisioning and then after a reboot with the new conf...

This document outlines how to setup a host-check for a Fortigate SSL VPN (Web only): config vpn ssl web portal edit "portalname" set web-mode enable set host-check custom set host-check-policy "Microsoft-Windows-Firewall" set os-check-enable set ip-pools "PoolName" set split-tunneling disable set page-layout double-column set theme orange config os-check-list "windows-7" set action check-up-to-date set latest-patch-level 1 end  config vpn ssl web host-check-software edit "Microsoft-Windows-Firewall" config check-item-list edit 1 set target "HKLM\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\StandardProfile:EnableFirewall==1" set type registry next edit 2 set target "HKLM\\SYSTEM\\CurrentControlSet\\Services\\SharedAccess\\Parameters\\FirewallPolicy\\PublicProfile:EnableFirewall==1" set type registry next edit 3 set target "HKLM\\SYSTEM\\CurrentControlSet\\S...

The below image outlines a combination of a few diagrams that was on Cisco's support website and I have taken them and placed them here for my own reference when working on trying to help understand the 802.1X Timers and which fields does what

Building Site-to-Site B2B from Unifi USG to Fortigate (500D or other models) Fortigate Configuration 1. Build a New VPN Tunnel using Custom VPN Tunnel (No Template) 2. Under Network, point to the Public Side IP of the USG (Public IP, not WAN interface) 3. Leave everything else default (NAT-T Enabled, DPD Disabled..ect) 4. Authentication, use PSK and IKEv1 with Main 5. Phase 1 Purposal, set algorithms to AES128 and SHA1, with DH 14. 6. Phase 2 Purposal, set Local Address and Remote address to 0.0.0.0/0.0.0.0 and 0.0.0.0/0.0.0.0 respectively. 7. Set Encryption to AES128/Sha1, Replay Detection and PFS enabled, along with DH14. Enable Autokey Keep Alive, and Auto-Negotiate, and save changes. 8. Build a Static Route pointing to the Far-End Destination/Segment you want to reach. 9. Build a Policy Stating which Segments can hit the Far-End Destination/B2B USG Configuration 1. This is assuming that USG is already registered to the Unifi Controller. 2. Go t...

Implementing 802.1X Using Windows Server 2012R2 & Cisco 4500 Series Switches Overview: This document is to outline how the configuration between Windows Server 2012 R2’s NPS Services and Cisco 4500 Series switches has been implemented. High Level Diagram:   Requirements: Windows Server 2012 R2 with NPS Server installed Windows Server 2012 R2 with CA Services Windows AD Environment Cisco 4500 Series Switches Windows 7-10 Clients to connect NPS Configuration: 1. This assumes the above requirement that the NPS Service has already been installed on Windows Server 2012 R2 2. Disable all existing Policies under Connection Request Policies and Network Policies as you will be making your own, except one that states “Catch All” with the below parameters: 3. You will then need to add in a new Radius Client to have Policies built around. Friendly Name will be used going forward for the Policies for referencing the document. 4. Once completed...