I know it has been a while since my last post, and I am sorry.
My career has taken a slight turn (not a major turn but a very pleasant divert). As such I don’t have the opportunity to write much here any more.
I hope at some point in the future I’ll be able to once more write about technology and other exciting subjects.
Yours,
Gyp
This how to will show you how to block internet access for a user, users or computer within an Active Directory Group Policy Object. I’ve tested this on Windows 7 and Windows 10 and it works great!
There are plenty of tutorials out there detailing a way to block access is via enforcing a non-existent proxy. This method will work for some things, but the problem is not all software necessarily uses these settings to connect to the internet and doesn’t necessarily stop a determined user or bad guy.
McAfee Web Gateway (MWG) is a pretty phenominal product, if you’re looking for a commercial web filtering solution then MWG should certainly be something you should investigate. If however you already have a MWG and are looking at a rule base to make sure that your users can only logon to your approved Microsoft Office 365 domains then read on.
Microsoft Office 365 (O365) is a pretty phenominal product, if you’re looking for a collaboration system then O365 should be something you should investigate. If however you want to make sure that only your organisation can log on to O365 via your network then read on.
I was asked a question if there was an easy way to scan an entire subnet and display not the certificate of each device or service but the certificate authority which provided it. I thought there has to be a relatively easy way of doing so, and here it is! This is a relatively simple solution and doesn’t take account of things like SNI. If you need SNI support you will have to tweak the code below and probably include the -servername switch in the initial s_client line. Drop a comment below if you want a help with this.
In a corporate environment shared key encryption is rarely used due to the problems associated with distributing the appropriate keys. In the corporate wireless world many organisations prefer to use 802.1x or Radius authentication so that their users can log on to the wireless networks with their domain credentials.
I was recently asked to set up just s system with Unifi access points and controllers on Windows Server 2012 with Microsofts own Radius solution NPS (or Network Policy Server) and 802.1x. There is plenty of information out there but I found that some of it was out of date and others were missing some fairly key components. So I present this tutorial to hopefully helps others get this up and running as quickly as possible.
FCH: Hi Gyp
Fantastic notes above.
I have an MBA and want to take the BA...
Willem: Thank you for this article. I am looking for a simple way to ONLY ALLO...
Piracha: Just booked the exam for foundation certificate as first step towards ...
CW: Apologies for the long post, but I hope that these hints and tips are ...
LA: Hi Gyp,
Notes look great, I'm prepping for the oral exam, anyone go...
