Ok I’ll admit this is a pretty weird thing to do a review on a PoE injector but its one of those things that I wish I had to reference when I was first looking at these.
First things first if you are looking for a basic PoE injector that can run power at about 15W max then this injector will do nicely for you.
I’ve used these injectors to power things like HP 4110 Lync phones, Axis and Sony CCTV cameras as well as Aerohive Wireless APs all of which have worked fine.
The good things about this injector are
- Just as you would expect its plug and play nothing to configure ect
- Nice and compact just 8cm long
- Comes with a short network cable which is ideal as a patch panel style cable
Things I don’t like or that could be improved upon are
- Uses a separate power brick with a proprietary cable, although its compact enough to fit them side by side on a power strip I do prefer kettle lead style cables as this gives you more flexibility when working with things like UPSs.
The photos below show things in a little more detail.
Its looking like we got our sizing for our custom RDS servers right and we may well have answered (at least for own internal use) ‘how many users can you get on a RDS server?’.
The video shows our RDS farm under normal load with 24 clients remotely logged in (excluding the admin session I was using) with the CPU usage being either low or idle on occasion.
For quite some time now I’ve been a tad baffled about why the correct homepage settings are not being applied to users through group policy on first time login on recently deployed PCs. Quite often instead of reaching our intranet they are just greeted with the about:blank page.
A gpupdate /force fixes the issue quickly however naturally this is not a viable solution.
The fix took me on a tour of the Internet eventually ending up on the Microsoft Technet Forum (link) with an unlikely but correct fix of applying the ‘Disable external branding of Internet Explorer’.
You might (just like I did) instantly ignore this possible fix as you are a IT pro – you downloaded a copy of Windows 7 Enterprise from the Volume Licence Service Centre and deployed it using MDT/WDS/SCCM so where on earth could the external branding come from?
PS – A little bit more thought later on lead me to believe that it was indeed because I was using the Microsoft Deployment Toolkit (MDT) to deploy Windows to these PCs and MDT was indeed set to use about:blank as the default homepage (see in below screenshot sequence).
All the same this fix works and the group policy you are after can be found at User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer.
The screen shots below show this in a little more detail.
A few days ago a interesting problem cropped up with a WordPress website that I maintain for a 3rd party, the error occurred every time I tried up upload a file to the site using the fantastic WP-DownloadManager plugin and was saying…
You don’t have permission to access /wp-admin/admin.php on this server.
After trying a few possible solutions .htaccess (all of which did nothing) I eventually emailed the fantastic guys at UKWSD (website hosting company I use) who found that the problem was being caused by something called Mod_Security.
They turned off this feature and lone behold all is working fine again
After looking at all the grief that this error has caused others on the web I would strongly suggest that you spend no more than a few minutes mucking around with your .htaccess file before calling your web host and getting them to fix it for you 😉
After recently setting up a Moodle install (hosted on IIS on Server 2008 R2) with SSO (LDAP server based (good old Microsoft AD) with NTLM looking after things) we found that any new users were getting this error message appearing.
Fatal error: $CFG->dataroot is not writable, admin has to fix directory permissions! Exiting.
The simple solution is to this problem is to change the NTFS permissions on the moodledata folder to allow write/modify to any user who is using moodle (I just set ours to domain users).
The things that got me about their article were
- Use of a seriously underpowered CPU – Gaming isn’t just using the GPU, you need a CPU to match – the Intel Pentium G840 is at the low end of the Intels CPUs, a much better option (if you want to stick with Intel would be a i3/i5)
- Not factoring in postage – The article states ‘£294.05 plus postage’ – well that postage pushes your PC over the £350 mark, what makes it worse is the title of the article is ‘How to build a budget gaming PC for under £350’.
- Saying that you can get a copy of Windows 7 for £50 – The link to Windows 7 they provide is for a UPGRADE copy, you would not be able to use this to install a fresh copy of Windows on your PC
- An inaccuracy about RAM – ‘but doubling up to 8GB will help out with general computing tasks when you’re not tackling the latest shooters.’ come on! General computing tasks requiring more RAM than a PC game? I think not!
So then here ends the rant 🙂 here also begins a proper gaming PC that you could build for less than £350 (£330.91 including postage at time of posting). Continue reading
Having recently setup DFS-R and DFS name spaces we found that our users were reporting that a security warning was popping up every time they opened any file from our DFS shares (example above).
The warning in Word 2010 was
The file originated from an Internet location and might be unsafe. Click for more details.
The silly thing about it is its not an Internet location its an Intranet one.
As it turns out because I was using a FQDN to connect to our DFS shares Windows was picking up the files as coming from the Internet.
The simple solution to this problem is to manually define your FQDN as a Intranet Zone in Internet Explorer (screen shots below show how to do this via GPO).
If you have ever tried to boot a VirtualBox VM into PXE (Microsoft WDS/MDT based) using the default Intel PRO/1000MT Desktop adapter you may have seen the error message
FATAL: Could not read from the boot medium! System halted.
This extension pack includes the required files for boot to continue normaly, a few screen shots are shown below detailing what you need to do.
Recently I have been doing a lot of movements of server roles, one of those was changing our DCs to newer servers that will be pure best practice based (nothing else on them other than AD/DNS/File Storage). One of the old server however had the Sophos Enterprise Console (v4.7 for anyone who is keeping count) on and after removing AD DS from the server I was getting the following error when trying to get to the Sophos Enterprise Console-
Cannot open Sophos Enterprise Console
The user “DOMAIN\Administrator” is not assigned to any sub-estates. You must be a member of at least one sub-estate to run this console.
Contact your Administrator to resolve this issue.
Upon inspection (in Server Manager > Configuration > Local Users and Groups) it appeared that the user group Sophos Full Administrators no longer existed.
The simple solution is to create a new group (called Sophos Full Administrators) and assign your Administrative account to it, the screen shots below show this in a little more detail.