When you have multiple network connections, sometimes you want to prefer one to be used as “default” (i.e. because it has higher speed or lower latency).
Windows already tries to accommodate for that by assigning “metrics” to your network connections. They depend on the kind of network (wired over wireless) and speed of the connection.
To see the current default network routes and their metrics, you use the route print command and filter it with findstr like this:
route print | findstr /C:"Metric" /C:" 0.0.0.0"
The “0.0.0.0” string is to filter out the default routes, and “Metric” includes the header line.
For one of my XP machines, the result is this:
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
Now, even though both metric are 10, my 192.168.71.1 gateway is much slower than my 192.168.171.1 gateway, so I want to prefer the last one. Read the rest of this entry »
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.]]
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.
This can happen when your Windows Security Token bloat has struck:
… the problem could be minor, or relatively major. You may get weird access denied messages, applications crashing, or strange entries in your event logs. Or worse yet a SID for a group that has a ‘deny permission’ on an object could be dropped into the virtual bit bucket, allowing a user to access a resource they are not supposed to access.
…
Summary of fixes for token bloat:
Use global or universal groups instead of domain local.
Increase the MaxTokenSize on all computers
Convert security groups to distribution groups if they are only used for email lists.
…
There is a hard-coded limit of 1,024 SIDs for the Kerberos PAC (privilege attribute certificate)
…
Kerberos token size still remain to 64k in windows7 / win2008r2.
The Wiert Corner - irregular stream of stuff 