vROps 6.x Email Templates

This blog post explains how to use the vROps APIs with Postman (API development environment) to create custom email templates for vROps.


Change Maximum Days Limit to Pause Windows Updates



Typing @-character is delayed with Asus GPU TweakII and scandinavian keyboard layout (at least norwegian)

After I reinstalled my computer a while back, I noticed that one characters (the @-sign) had a long delay before showing up after I had hit the key on the keyboard. And I noticed it wasn't every time I had turned on my computer it was "slow".

Imagine how frustrating it is to write your email address in a normal pace on the keyboard, just to find it spelled firstname1977gma@il.com instead of firstname1977@gmail.com? Hitting '@'had 0.5 to 1 second delay before it showed up on my screen, while the characters after displayed instantly.

The computer in question runs english Windows 10 x64 with an NVidia GTX1070 card from Asus, and using a norwegian/scandinavian keyboard (Logitech G710+, but model isn't the problem).

Throubleshooting led me to narrow the problem down to my ASUS GPU TweakII v1.4.0.8 (older version probably have the same problems). When I started the program, which was set to auto-start, I was suddenly no able to type @ as fast and often as I could. So far so good. I could just exit the program and all would be fine. But then I would have to start it every time I wanted to tune/overclock my GFX.. not the best workaround.

The problem was/is in the GPU TweakII settings. It seems the combination of scandinavian keyboard layout and keyboard shortcuts in GPU TweakII are the bad mix.

To illustrate it, I've pulled what should be a US and NO keyboard layout from Google images:

US keyboard layout
US keyboard layout

NO keyboard layout
NO keyboard layout
Notice that we Scandinavians have several extra characters mapped to one key (and a few extra letters, but thats not important here)? Where US only have one or two characters mapped (normally toggled with SHIFT), we have sometimes three. While lots of people press SHIFT+2 to get @, we have a special key ALT-GR where your right ALT key is. ALT-GR+2 gives us @. And as you can see, ALT-GR+3 is £ and ALT-GR+4 is $ and so on. They are all marked in blue.

I had problem with delayed displaying of @, £ and µ. Normally I wouldn't use £ and µ much so my main annoyance was @.

And if we look at the settings for GPU Tweak II keyboard shortcuts we see that numbers 1 through 3 and letters M,N,U,D are in use. Do you see the problem?

My problem keys @, £ and µ links to keys 2, 3 and M. Just turning off the shortcuts made the delay go away on the first iteration of the characters, but keeping the key pressed would not give me a second @. So the full solution is to
  1. Remap the shortcuts to completely different set of keys. I would recommend start from D and pick a new on to the right
  2. Disable the keyboard shortcuts all together after that.

Finally I have my @, £ and µ keys back ;-)


Jorte Widget setup for weekly calendar

This is my setup for the weekly calendar using Jorte Calendar for Android. Just so I don't have to guess every time I install it on different devices :)

Widget Type:        Weekly
Periode of display: This week
First Day Settings: Today

Style:              Jorte White (sometimes Black)
Background Image:   Show
Transparancy of the background: 50%

Keep the rest at defaults


Intel Rapid Storage Technology (iRST) driver for Windows 10 on older chipsets (7-series and older)

My computer is still more than fast enough even though it's over 4 years old. It's a Intel Core i7-3770K with 32GB DDR4-1600 RAM on an Asus ROG Maximus V Gene mainboard. The chipset is Z77 and so it was more or less the best to get at the time being. I started with two Samsung SSD 830 in RAID-9 and later upgraded to a OCZ RevoDrive3 X2 PCIe SSD for my OS disk.

Fast forward from Windows 7/8 to Windows 10 (v1607) and Intel seems to not have released any Windows 10 supported SATA controller drivers for Z77. Or have they?

It seems that as long as your BIOS has the Intel SATA controller set to AHCI-mode, Windows 10 will install and use the generic 'Standard SATA controller' and trying to install the latest iRST driver v15.2.0.1020 (latest version as of 2016-12-15) on an AHCI configured Z77-system only gives you an error:

Platform not supported

The good news is that Intel does have driver support for some of the older chipsets; those that have RAID capabilities, which luckily inlcudes Z77.


Sophos XG firewall once again kills backup with Crashplan Central (Cloud)

It seems such a long time ago I battled with Sophos XG firewall (v15.x) to get Crashplan Central (Cloud Backup) to work through it (#1). Last month I upgraded to v16.x and hey, what do you know? A new problem with connection to Crashplan Central.

To make a long story short (read the forum posts), there's a bug (what else is new when it comes to Crashplan and XG) in v16 (including v16.0.1.1) that blocks the crashplan traffic. It's confirmed by Sophos KB (#2) and they say:
In certain situations traffic being passed through the XG firewall may appear be passed through the proxy even when no Web Policy is enabled within the relevant firewall rule and HTTP/HTTPS scanning is disabled."
Both the KB and forumpost (#3) gives a workaround:

    1. Connect to the XG firewall via SSH and select option 4 (Device Console) from the menu
    2. run the below to disable this:
      system application_classification microapp-discovery off
    3. Restart Crashplan

    1. https://community.sophos.com/products/xg-firewall/f/firewall-and-policies/32111/anyone-successfully-running-crashplan-backups-through-an-xg/314571#pi2132219853=1
    2. https://community.sophos.com/kb/en-us/125458
    3. https://community.sophos.com/products/xg-firewall/f/firewall-and-policies/81482/crashplan-connectivity-issues-with-xg-16/310556?pi2132219853=2&pi2132219849=84
    PS! I have not checked, nor installed, v16.0.1.2 to confirm it's still there or not. Might do that soon, and update this post.


    Google kills Chrome backspace key for navigating. Fixed with extension

    So Google just killed the BACKSPACE key for navigating back on webpages. That sucks! I guess I'm one of the few 0.04% users who use it a lot..

    Luckily it seems the made an extension to re-add the feature to Chrome.

    Get it here: https://chrome.google.com/webstore/detail/go-back-with-backspace/eekailopagacbcdloonjhbiecobagjci

    Source (pic and extension): https://productforums.google.com/forum/#!topic/chrome/D4VMOXTxPwg


    Download Windows 10 v1511 ISO from Microsoft

    Short summary:

    1. https://www.microsoft.com/en-us/software-download/techbench
    2. CTRL+SHIFT+J (Chrome)
    3. Paste into Console and hit Enter:
    4. Select Windows 10 (1511 TH2) or another version
    5. Select Language (English International = UK/GB)
    6. Download 32- or 64-bit

    For better instructions (or using another browser) see TechJourney article here: https://techjourney.net/windows-7-8-1-10-iso-official-direct-download-links-from-microsoft-tech-bench/


    Blogpost of MDT 2013 Lite Touch Driver Management

    I found this blogpost about MDT 2013 and handling drivers.. I might have to check it out later in a lab environment.

    In MDT 2013 (Lite Touch), there are two types of drivers to worry about when deploying Windows. There are drivers for Windows PE 5.0 (the boot image) and there are drivers for the Windows Operating System that you deploy. 

    Driver management for the boot image is pretty straight , but driver management for the Operating Systems that you deploy is more complex. The real answer is it depends… To simplify I have broken down drivers for the Windows Operating system in to three core scenarios (see later in this post). But first, let’s start with the boot image drivers.

    Link: http://deploymentresearch.com/Research/Post/325/MDT-2013-Lite-Touch-Driver-Management


    Crapware installed from UEFI BIOS - Windows Platform Binary Table (WPBT)

    This is a interesting and describing forum post about Lenovo putting some Lenovo CrapWare in the UEFI BIOS which Windows will execute upon login (right before actually):


    Lenovo has issued a fix: https://support.lenovo.com/us/en/product_security/lse_bios_notebook
    and an article: http://news.lenovo.com/article_display.cfm?article_id=2013