Never noticed this file before until I got some trouble with several systems sharing parts of a roaming profile.
The content of my %USERPROFILE%\ntuser.ini file is this: [General]
ExclusionList=AppData\Local;AppData\LocalLow;$Recycle.Bin;Tracing;PrivacIE
[ProfileLoadType]
LastUploadState=Complete
[[The ntuser.ini file is used to set up the user roaming profile components that are not copied to the server.]]
Every now and then my Mac RDP program will suddenly turn on the CAPS LOCK on the connected Windows terminal.
It happens on different OS X versions, and different Windows versions. I haven’t figured out the steps to reproduce yet. I will amend this post when I have (:
I also have it occasionally fail when I RDP from a physical Windows system to another Windows system, but far less than from Mac OS X.
You work around it using the On Screen Keyboard tool in Windows like Josh Adams explains:
launch the On-screen Keyboard application (generally this can be done by choosing Start ==> All Programs ==> Accessories ==> Accessibility ==> On-screen Keyboard; as noted by DrFooMod2 in a comment below, you can also bring up the On-screen Keyboard by typing “osk” without the quotes in the Windows Run… box) and
toggle Caps Lock by clicking on the virtual “lock” button in the application.
The On-screen Keyboard application shows–and can change–the state of Caps Lock
The easiest way to start the On Screen Keyboard is to create a shortcut to this:
Two keys needed: one HKCU one HKLM. You need to be Administrative user with a CUA token to install the second one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Always an interesting read, and usually posted to his blog a while after the email blast gets out.
There is too much information to fully re-post here, so here is an abstract of the entries I already had benefits from, or have a high interest in:
ExplainShell – Amazing resource for learning how the shell works in *nix. A must for teaching anyone.
Interesting new CSS Postprocessor called Myth (note this actually is a pre-processor).
I\’ve talked about how I like ConEmu before. Now there\’s cmder, a portable system that wraps it with new settings, fonts, a generally makes it pretty. It\’s 90% of the console that I want on Windows.
Lately I moved more and more away from wget, mainly because out of the box, wget (and also aria2, which I like for the bittorrent support) handle https downloads so badly: you need to manually setup your CA store on each and every installed system.
You don’t even need to download the installer. Grabbing the stuff from the bin directory in the zip download is enough: it contains a prepackaged CA certificate set that works splendid.
The F keys on a Mac still perform the Mac OS X specific function, even in a full screen RDP session, but you can get their Windows functionality back with ease as MacRumors user blindzombie shows:
I got it to work with fn – command – F9
or just command – F9 if you set your keyboard preferences to use F1, F2, etc as standard function key
Just Works: if a user is logged in on the Windows machine, which usually is the case.
Next to that, it is used for internet browsing and remote desktop access to VMs in the various clouds: it is more than adequate for that with dual Dell UltraSharp U2407WFP monitors at 1920×1200. The extra 120 pixels over “modern” 1080p do make a difference you know.
I never bothered to upgrade the machine, as it works so nicely and I have had bad experience replacing systems that include embedded licenses: it usually doesn’t work.
Of course I could buy a new ScanSnap iX500, but I don’t want to increase the electronic waste unless I’ve researched if it is possible to get the ScanSnap S510 working on Windows 7 or 8.x, or even on one of my Macs.