Cannot Display

​Stop “installing” autonomous AI agents on your daily driver. You are doing it wrong. Our hero, Jolty (Zoë Roth AKA Disaster Girl) being told to ‘gonnae no dae that!’ a beautiful Scottish expression (please don’t do that) as a fire blazes in the background. This phrase perfectly sums up my feelings on MoltBot and the…

More posts

  • Remote Web Workspace not working [Solved]

    Remote Web Workspace breaks. Alot.

    In all versions of SBS (now end of life) Microsoft graced us with the ability for remote users to remote into the server to then hop accross to their own PC’s via RDP.

    This was great in theory, and worked for a while, until updated servers broke this feature. The root cause was an update to .net framework, starting at version 4.5.1 which included memory checking to make sure you have at least 5% free memory.

    Ok, so why the issues. Well anyone who knows Exchange, knows that the information store will use as much free memory as possible – which in turn often caused the Remote desktop Gateway service to crash, due to not having 5% free memory.

    Here is the quick fix if you only have 5 mins;

    – Restart the MS Exchange information store,
    – Then restart/start the Remote Desktop Gateway Service

    Here is the proper fix:

    – Run adsiedit.msc
    – Connect to: Select a well known Naming Context : [Configuration]
    – Expand the following:
    Configuration\Services\Microsoft Exchange\ (First Organization) \Administrative Groups\ (Exchange Administrative Group) \Servers\ (Server Name)
    – Right click on CN=Information Store and click properties
    – Update the values of msExchESEParamCacheSizeMin and msExchESEParamCacheSizeMax to something below 94% of your servers max ram capacity – i is in KB’s divided by a 32byte page so…

    Basic maths is ==> Target Cache Size in GB = (# * 1024 * 1024) / 32

    There is an excellent table over at meridian.ws which is much easier than doing the maths:
    http://meridian.ws/wordpress/?p=239

  • [Solved] Kali apt-get update key signature error

    Are you getting the below failed to fetch error?

    Failed to fetch http://http.kali.org/kali/dists/kali-rolling/InRelease The following signatures were invalid: EXPKEYSIG ED444FF07D8D0BF6 Kali Linux Repository

    Then to install:
    dpkg -i kali-archive-keyring2018.1all.deb

  • Adobe reader on Server 2016

    Adobe have been rather silent recently when it comes to running reader on server 2016

    Adobe reader is used by many professions, and in many capacities. It used to be one of the most commonly installed applications on business PC’s by anyone in any sector. However, Server 2016 is not supported.

    https://helpx.adobe.com/reader/system-requirements.html

    This makes it a nightmare for modern portable apps, RDS servers(Terminal servers) or even just file servers.

    So there is a work around, however it is not recommended. The best fix for this is to scrap Adobe, and move to one off the other large PDF Vendors out there to cater to your PDF viewing needs.

    Three that i have personally verified as working and are supported on server 2016 are:

    • Nitro Pro
    • Abby PDF reader
    • TinyPDF

    There will however be a small percentage of us admins or superusers, that have to get this Adobe based software working.

    Workaround to get Adobe reader on Server 2016

    Start by using the latest installer for Windows 10,
    Once installed, you may find that it will work for a while, but eventually as it updates you will no longer be able to open PDF documents using it.
    To get around this you have to unfortunately turn off protected mode.

    Now, i shouldn’t really need to preface this, but i will. This is not supported, nor recommended – Reader has a protected mode for a reason, disabling it is opening you to all sorts of vulnerabilities.

    If you do wish to continue, open up Adobe Reader – go into Edit –> Preferences –> Security (enhanced) –>

    Turn Protected mode off, and untick ‘ Enable protected mode at startup’

    If you like I could not even get to the preferences panel in order to change these settings then all you need to do is open adobe reader by accessing via compatibility mode. Set this as XP (which itself does not support protected mode) – then change settings, and then change compatibility mode back off.

    Let me know in the comments if this has helped you.

  • Get rid of the “Updates are available” pop-up

    The Updates are available popup is the source of much irritation for anyone remotely administering windows 10, Server 2012 and server 2016

    To get around this popup – which lets face it, is just downright inconvenient; we need to stop the exe file that produces this window from running. Code below, with comments preceded by a #

    Run command prompt as administrator (elevated) and enter these commands:

    #change directory to system32
    cd /d "%Windir%\System32"

    #Take over permissions owner to current admin
    takeown /f musnotification.exe

    #Change permissions to deny anyone/system running from it
    icacls musnotification.exe /deny Everyone:(X)

    #Take over permissions owner to current admin
    takeown /f musnotificationux.exe

    #Change permissions to deny anyone/system running from it
    icacls musnotificationux.exe /deny Everyone:(X)

    You will see form the above, that there are two processes ‘musnotificationux.exe’ and ‘musnotification.exe’ that are responsible for querying updates and notifying the end user. The great part of this fix, is that it will not interfere with any update processes themselves, just the notifications. So have no fear – updates will still continue to function as normal, just now without this troublesome pop-up.

Latest Posts: _