Archive for the ‘Windows Server 2008 R2’ Category
Posted by jpluimers on 2014/03/30
Read this very nice post on Nex7’s Blog: ECC vs non-ECC RAM: The Great Debate.
There is no debate. Use ECC dude.
Use ECC especially for server side things (storage, virtualization, databases, etc) where you employ some kind of redundancy/correction in the storage (ZFS, RAID, etc) side of things.
And think about using ECC for the rest of your stuff, especially when things stay in memory for a longer period of time (in-memory processing of data can speed up things a lot, but also increase the risk).
Summary:
There is no debate here. None.
[…]
if you think non-ECC RAM can compete with ECC RAM, you are mistaken. If you think there’s a risk/reward analysis here, you’re correct. The risk is not gigantic, and there’s a real cost to alleviating that risk. You have to decide if that cost is worth alleviating that risk.
[…]
If you believe there’s a risk/reward plan where you can take the reward and apply to to mitigate the risk, you are back to being mistaken. The only benefit of non-ECC RAM (and thus the only reward in its choice over ECC RAM) is it will make the solution cheaper. There is not, however, any way (that I’ve heard of, yet) you can use the cost savings to mitigate the risk using non-ECC RAM will introduce.
[…]
If you choose to use non-ECC RAM, you open yourself up to a new vector for data corruption/loss/downtime/errors/etc,
one that could (rarely) even cause you to lose your entire filesystem, and one ZFS does not (cannot) resolve for you. Indeed, one it likely can’t even see at all. If you choose to employ non-ECC RAM, or are forced to do so because of circumstance or environmental constraint, that’s potentially understandable (and even acceptable) – but do not then attempt to validate or explain away that choice with pseudoscience or downplaying the risk you’ve added. You are using an inferior solution with an extra vector for data corruption/loss that ECC RAM solutions simply do not have. It is that simple.
[…]
Hint 3: There’s a reason we’re so gung-ho about using ECC RAM for ZFS, and it’s not just because we’re paranoid about data loss (which goes hand in hand with being a ZFS zealot, really). It is because you likely don’t realize how at risk you are. Due to the nature of how ZFS handles writes, your incoming (write) data is at risk of RAM-related bit errors for likely significantly longer than traditional storage solutions or alternative filesystems. 5, 10, 30, 60 or more seconds in a state where it is at risk.
Read the rest of this entry »
Posted in *nix, ECC memory, Endian, ESXi4, ESXi5, ESXi5.1, ESXi5.5, Hardware, Hyper-V, Linux, Memory, Power User, SuSE Linux, VMware, VMware ESXi, Windows, Windows 7, Windows 8, Windows 8.1, Windows Server 2008, Windows Server 2008 R2 | Tagged: ECC RAM, ZFS | Leave a Comment »
Posted by jpluimers on 2014/03/29
The upside of findstr is that it is included with Windows since a long time (at least since Windows XP, later: indeed since Windows ME) and supports a form of regex.
But often it drives you crazy.
When it does, read What are the undocumented features and limitations of the Windows FINDSTR command? – Stack Overflow.
–jeroen
Posted in Power User, Windows, Windows 7, Windows 8, Windows 8.1, Windows ME, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2014/03/29
Brilliant piece of open source:
SmallestDotNet – SmallestDotNet.com is a single page site that does one thing. It tells you the smallest, easiest download you’d need to get the .NET Framework on your system.
Even on Mac OS X it is helpful and recommends Mono and on iOS it recommends looking at MonoTouch.
Thanks Scott Hanselman for making this available!
–jeroen
via:
Posted in .NET, .NET 1.x, .NET 2.0, .NET 3.0, .NET 3.5, .NET 4.0, .NET 4.5, Apple, Development, Mac, Mac OS X / OS X / MacOS, Mac OS X 10.4 Tiger, Mac OS X 10.5 Leopard, Mac OS X 10.6 Snow Leopard, Mac OS X 10.7 Lion, MacBook, MacBook Retina, MacBook-Air, MacBook-Pro, OS X 10.8 Mountain Lion, OS X 10.9 Mavericks, Power User, Software Development, Windows, Windows 7, Windows 8, Windows 8.1, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Tagged: .NET Framework, scott hanselman | Leave a Comment »
Posted by jpluimers on 2014/02/03
Once every while, a full screen app on your Mac hangs, and there is no way to Command-Tab to another application.
PC addicts then press Ctrl+Alt+Del, to either get to the Task Manager, or to logoff/reboot.
For a Mac, there are two:
- Force Quit Read the rest of this entry »
Posted in Apple, Keyboards and Keyboard Shortcuts, Mac, Mac OS X / OS X / MacOS, Mac OS X 10.4 Tiger, Mac OS X 10.5 Leopard, Mac OS X 10.6 Snow Leopard, Mac OS X 10.7 Lion, MacBook, MacBook-Air, MacBook-Pro, OS X 10.8 Mountain Lion, Power User, Windows, Windows 7, Windows 8, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2014/01/13
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.
This is what UWWI did to avoid token bloat: UWWI Token Bloat – IAM – UW Information Technology Wiki.
–jeroen
via:
Posted in Power User, Windows, Windows 7, Windows 8, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2014/01/02
Very interesting, especially since rdesktop.org works with Windows Server 2008 R2 and Windows 7 as well, and is stable on x64.
It provides three tools: rdesktop, rdpproxy and seamlessrdp.
Researching this, I also found about TSWindowClipper which allows you to seamlessly integrates remote apps on your client by integrating a DLL inside the MSTSC software using the official virtual channels.
Back to rdesktop: I really wish the documentation was better, but it contains some very interesting source code.
rdesktop is an open source client for Windows Remote Desktop Services, capable of natively speaking Remote Desktop Protocol (RDP) in order to present the user’s Windows desktop. rdesktop is known to work with Windows versions such as NT 4 Terminal Server, 2000, XP, 2003, 2003 R2, Vista, 2008, 7, and 2008 R2.
rdesktop currently runs on most UNIX based platforms with the X Window System, and other ports should be fairly straightforward.
rdesktop is released under the GNU Public Licence (GPL), version 3. Please send feedback, bug reports and patches to the appropriate mailing list. Patches can also be submitted to the SF patch tracker.
rdesktop is a project. See the Sourceforge rdesktop project info and the Wiki for more information.
Status
The latest stable version of rdesktop is 1.7.1 (edit: this was at the time of writing, for the current latest, check here). This versions solves major issues with 64bit version and smartcard support among a few minor fixes.
–jeroen
via rdesktop: A Remote Desktop Protocol client.
Posted in *nix, Development, Linux, Power User, Remote Desktop Protocol/MSTSC/Terminal Services, Software Development, SuSE Linux, Windows, Windows 7, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2013/12/20
Interesting as a complement to fsutil and mklink and FindLinks and Junction: Link Shell Extension and ln.exe.
It allows you to create and maintain “Hardlinks, Junctions , Volume Mountpoints , and Windows7/8’s Symbolic Links, (herein referred to collectively as Links) a folder cloning process” and more.
Note that Link Shell Extensions require NTFS5 or higher (NTFS.sys version 5, which corresponds with NTFS v3.1)
–jeroen
via: Link Shell Extension.
Posted in Power User, Windows, Windows 7, Windows 8, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2013/10/14
As a non-administrator, as of Windows Vista, you are not allowed to change the environment variables the regular way.
Various people have quoted the official Microsoft way of changing the environment variables as a regular user on Windows Vista and up (including Windows 7, Windows 8 and Windows Server 2008 and up).
It means going through the account settings doing half a dozen steps or so.
Quickest way however is to put this in a batch file to set/edit those environment variables like PATH:
"C:\Windows\System32\rundll32.exe" sysdm.cpl,EditEnvironmentVariables
Whereas for the full sysdm.cpl you need Administrator privileges, you don’t for this specific rundll32 call.
The cool thing is that Windows will automatically merge the user and system environment PATH in this format:
system-PATH;user-PATH
–jeroen
via: How can I set user environmental variables such as PATH from a non-administrator account on Windows 7 – Super User.
Posted in Power User, Windows, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008 R2, Windows Vista | Leave a Comment »
Posted by jpluimers on 2013/08/27
From The Old New Thing:
Recall that the library search path searches directories in the following order:
- The directory containing the application EXE.
- The system32 directory.
- The system directory.
- The Windows directory.
- The current directory.
- The PATH.
Note that the PATH environment variable has a limited length, which can be impacted by the installation programs you use and the Windows versions you use.
To be on the safe side, use 1024 or 1920.
I found various limitations: Read the rest of this entry »
Posted in Development, Microsoft Surface on Windows 7, Power User, Software Development, Windows, Windows 7, Windows 8, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Leave a Comment »
Posted by jpluimers on 2013/08/17
Programmers scale: time versus project completeness
I totally agree that Paint.NET is the best free image and photo editor on Windows.
Writing quality software takes time, not only when writing it in spare time like Rick Brewster does. Getting things “right” is a tedious process and often will set you back: just watch the graph on the right.
So I’m not surprised that it took a very long time after the first Paint.NET 4.0 idea in 2008 to get “close” to a release.
And indeed, it looks like Rick has become much closer which will please many people waiting for Paint .NET 4.
I’m really glad with the announcement that Paint.NET v3.5.11 BETA is now available – Paint.NET Discussion & Questions – Paint.NET Forum.
Edit: while writing this, the final Paint.NET v3.5.11 came out.
It paves the way for Paint .NET 4.0 update in the future, and fixes/improves quite a few things.
A few quotes from it:
This is probably not the update you were expecting I need to push out an update to v3.5 in preparation for the eventual release of v4.0 […] releasing a “beta” today […] I’ll be pushing out the Final/RTM in a few days.
The primary goal of this update is preparing for the v4.0 release: v3.5.10 will not be able to offer the v4.0 update, but v3.5.11 will. […]
Here are the changes for this release:
- Fixed: The Gaussian Blur effect was incorrectly calculating alpha values for non-opaque pixels. (http://forums.getpaint.net/index.php?/topic/18483-gaussian-blur-mistreats-alpha/)
- Improved performance of the Sharpen effect by about 25%
- Improved performance of the Median effect by about 30%
- Improved performance of the Fragment effect by about 40%
- Improved performance of the Unfocus effect by about 100%
- Reduced memory usage when many selection manipulation operations are in the history/undo stack (the undo data is now saved to disk)
- The built-in updater now supports upgrading to paint.net 4.0 (once it’s available)
There have been rumors floating around that Paint.NET is “dead.” This is not true!
–jeroen
via: Paint.NET Blog | The best free image and photo editor. By Rick Brewster..
Posted in .NET, .NET 3.5, .NET 4.0, Algorithms, Development, Floating point handling, Power User, Software Development, Windows, Windows 7, Windows 8, Windows Server 2000, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP | Tagged: computer, software, technology | Leave a Comment »
The Wiert Corner - irregular stream of stuff 