"It's not what you can do, it's what you can get done."

Sunday, November 22, 2015

Managing Windows Server Core without a domain.

Testing out "Hyper-V Server", which is the free version of Server Core with the Hyper-V role pre-installed.

After re-installing the RSAT package (thanks to the November Win10 update removing/ignoring my previous install), discovered that Server Manager wouldn't play nice: "WinRM Negotiate authentication error". Several forum searches pointed to various bits of Voodoo, but none of them worked. (Were some of them needed or contributed? Who knows...who needs change management on a home server, right? Riiiigggght.

 Finally, found via this post, it's actually in the official documentation:

Set-Item wsman:\localhost\Client\TrustedHosts ServerHostname -Concatenate -Force

(Note this is with 2012R2, I haven't tried with 2016 yet, as the upgrade UI eventually displays a blank screen that is non-responsive.)

Monday, August 10, 2015

BTSync codes

This is more for myself, but folks are welcome to use them if they find it useful. (The more nodes, the faster! Just running on a couple desktops for now, will be adding to home router/server/nas later.) The shared links are, of course, read-only.

I've been using BittorrentSync since it was in 1.x beta, great to keep a collection of files (say, troubleshooting utils, patches, ISO's, whatever) locally accessible at various locations and only updated once.


First up is my collection of "Live" window utils - just the things I find myself always wishing for/downloading, or a couple obscure ones. Currently just under 300 megs, it's very nice to have on phone with you. (Provided you keep a USB cable handy!)

Using their kinda-obtuse link system:

And the QR for phone funsies. (I've put a copy of the code in the folder itself. SyncCeption!)

Sunday, July 26, 2015

Deltacopy rsync installer script for Windows.

From the readme:

Rsync is good. BackupPC is good. Rsync on Windows is...not so good. We (small-ish IT department) decided on using the DeltaCopy version of rsync (still using Cygwin) to allow our BackupPC server(s) to backup our windows clients. It's fairly quick'n dirty but works well enough for our purposes.

I've posted it on bitbucket in all it's "glory".  (https://bitbucket.org/TechMonkey/backuppcwinclient) Of course folks are welcome to submit patches, suggest changes and the like, but this is mostly an exercise in version control...

WEI/WinSAT on Windows 10 - D3D score is bogus.

Most of us know the Windows Experience Index was removed from the GUI in Win 8, and many are familiar with calculating/getting the scores from many posts like this one.

 I can rarely remember the steps (I prefer to open admin powershell, then "winsat formal", and then "Get-WmiObject Win32_WinSAT")

Something I noticed according to this Win32_WinSAT class entry:

"After Windows 8.1, WinSAT no longer assess the three-dimensional graphics (gaming) capabilities of the computer and the graphics driver's ability to render objects and execute shaders using this assessment. For compatibility, WinSAT report sentinel values for the metrics and scores, however these are not calculated in real time."

 Indeed, on a decent older-desktop with a Radeon 4670, it returns a 9.9 for D3D:

CPUScore : 5.3
D3DScore : 9.9
DiskScore : 5.9
GraphicsScore : 6.2
MemoryScore : 5.4
TimeTaken : MostRecentAssessment
WinSATAssessmentState : 1
WinSPRLevel : 5.3

Just another tidbit/gotcha to be aware of.

Wednesday, May 13, 2015

Linksys WRT320/E2000 conversion missing file.

Lots of copies of (apparently) this post, but the download links for the CFE files are borked, as is the CAPTCHA on the comment field.

I found a copy for the 320/2000 CFE at http://www.dd-wrt.com/phpBB2/viewtopic.php?p=715205, same SHA-1 hash. (db2d4cd117faac4c0a330afa4cdcdb5ad133d82a)

I've made a copy available at https://drive.google.com/file/d/0B8BlCCtbBj6edVhhdnRYbjN4cGM/view

Tuesday, April 14, 2015

Benign evenID's 120xx on WSUS

WSUS on a Server 2012 R2 CORE, working fine, but event ID's 12052 12042 12022 12032 12012 whenever healthcheck ran.

http://jackstromberg.com/2013/10/windows-update-services-multiple-errors-in-event-viewer-event-id-1205212042-12022-12032-12012-1200213042/ had the answer.

I'm not 100% sure what it does to fix the problem, but re-running "wsusutil.exe usecustomwebsite true" worked for me.

Saturday, October 4, 2014

ImageX /check vs /verify

Because I can never remember, and the Technet documentation is not helpful in this regard:

/Check - Calculate Checksums (Check.Checksum. Got it!)

/Verify - Just compares source and destination.

From http://windowsitpro.com/systems-management/deploying-and-error-checking-imagex

The /verify option works as you might imagine: It double-checks that either a capture or apply operation didn't accidentally drop any bits along the way. WIM files are pretty large, and although network and disk read/write operations already contain built-in checks, just one misplaced byte can render the image or system useless. The /verify option helps prevent that from happening. After either applying or capturing a windows image, ImageX compares the source data and its copy, searching for (and correcting) differences. ImageX enables the /verify option by default whenever applying or capturing over a network connection, but it doesn't do that when working with local external storage, so it's never a bad idea to add the /verify option. (It will, of course, slow things down a bit.)

The /check option has a similar purpose but a slightly different and perhaps more efficient approach. If you include /check when capturing an image, ImageX creates a hash of every 10MB chunk of ImageX data, then embeds those hashes in the resulting WIM. Including /check on an apply operation causes ImageX to check the applied image by re-computing hashes on that image, then comparing those computed hashes with the embedded ones. Thus, /check certifies not only that a WIM wasn't mis-copied during the apply operation but also that a WIM hasn't become corrupted while stored. Why use /verify, then? Why not just always use /check? The answer is that /check can't do its job on an apply operation if no one specified /check on the capture. If the WIM lacks embedded hashes, /check can't check the hashes. The /verify option, in contrast, doesn't need hashes, so it can always help.