Saturday, February 13, 2016

Miscellaneous Apple bites

Looks like I am literally picking low-hanging fruit from my “to-blog” tree branches.

I previously reported this on my the struggles GSD post but am reposting here for topic inclusion.

The takeaway was to quit Process Explorer. I’ve seen a few other software installations where I have needed to close out Process Explorer entirely to make sure it doesn’t get in the way of some installations. Weird.

Of course, iTunes wanted to be updated, so I used the Apple Software Updater but it complained about the “iPod Service” not being able to start so the install kept failing. I then tried to download and run the iTunes package rather than using the updater but that failed at the same point.
I found this post Service ‘iPod Service’ (iPod Service) could not be installed... over in the Apple Support forums and followed “rickybpta” steps.

  • close SysInternals's Process Explorer ( if you have it and it's open )
  • close all Task Manager(s)
  • close Windows Services console ( services.msc )
  • close all command prompts ( cmd.exe )
  • open a cmd.exe as Admin
    • run: sc create "iPod Service" binpath= "C:\Program Files\iPod\bin\iPodService.exe"
    • close all command prompts ( cmd.exe )
  • open Windows Services console ( services.msc )
    • look for "iPod Service", see if it's not Disabled. If so, start it
    • close Windows Services console ( services.msc )
  • Run iTunes.msi again ( previously downloaded via the Apple Software Update's Only Download function )

That did the trick and it went on without any other fuss.

I had purchased a Yeti Blue USB microphone a while back to up my audio recording game. I had hoped to be able to eventually use it with my iPad/iPhone but there were some challenges reported so I’ve just stuck it out with my Windows 7 laptops where it has done a rocking-cool job of upping my audio game. Couple that with Audacity and The Levelator from The Conversations Network and while I am no audio-engineer, I can do a fine good job for most recording needs.

So it was exciting to see this news:

I need to update this post Claus’s iPhone App List - Updated 01/2014 as I’ve gone through some serious changes with the iOS apps I carry. I have purchased more than a few as well…so they must be that good! “Hey Siri! Remind me to update that post!”

Apps of note to get (or are recommended)

Music Memos – Apple – This one looks interesting but I’m not sure it might really meet my audio-recording needs on my Apple gear.

GarageBand for iOS – Apple – This looked good too, but maybe there is a better audio mixing app for “studio” mixing.

Due – Apple App Store – This is the best reminder/count-down timer/recurring event reminder app ever. Period. Buy it.

Round – Apple App Store – Because Due doesn’t currently handle recurring reminder events of less than a day (that I am aware of), you can’t yet use it to set medication dosing reminders. This looks to be designed specifically for that need.

Mighty Timer – Apple App Store – free app to help with brewing your tea. Alvis and her husband gave Lavie and I some very nice porcelain cups along with some fancy Matcha style tea. It has to be brewed very carefully but is super good!

Cheers.

--Claus Valca

Windows Update Agent Utility (WUAUclt.exe)

Just some sysadmin notes…nothing to see here.

  • Windows Update Agent Utility (wuauclt.exe) - pauby.com
  • wuauclt - Windows Update - Windows CMD | SS64.com
  • Appendix H: The wuauclt Utility – Windows Server TechNet page
  • wuauclt commands to force reporting of status? – Windows Server TechNet page
    • The /reportnow function is a very tricky beast, and it somewhat requires an understanding of the natural behaviors of the WUAgent.

      When the WUAgent performs activities, it queues up all of those completed activities as 'events'. When the WUAgent quits working, an idle timer is engaged, and when the WUAgent has been idle for ~20 minutes, it invokes a call to the ReportingWebService. You can see these calls in the WindowsUpdate.log and compare their timestamps with the entries just previous.

      If the /reportnow action is invoked after the WUAgent becomes idle and before the regular call to the ReportingWebService, an immediate call to the ReportingWebService will be invoked. You can also see this in the WindowsUpdate.log.

      However, the call to the ReportingWebService is not the end of the line. Those events reported in that call are loaded into a buffer, and the WSUS server then processes those events asynchronously. If the WSUS server is also busy doing other things or other clients are also reporting at the same time, there will be an additional delay until the results are visible in the WSUS console.

      The real thing to remember is that, at best, the /reportnow task isn't going to save you much more than 20-30 minutes, so usually just waiting is the more efficient approach to the whole thing.

      as commented by Lawrence Garvin

  • wuauclt and other questions about WSUS – Windows Server TechNet page
  • When run from the command prompt on a client in the form of "wuauclt.exe /resetauthorization /detectnow", this command will kick off a manual check in with the configured WSUS server (or WindowsUpdate website, if you're using that instead of WSUS).  You can verify this occurs by opening the windowsupdate.log file located in the Windows directory.

    If you manually run wuauclt.exe with the above listed switches, it will check in with WSUS, and then behave based on your update configuration, either configured locally on each client, or through Group Policy.  So, if you have your clients configured to download any available updates, it will do so.  Or, if you have your clients configured to just check in and inform you there are updates without downloading, it will do that also.

    The windowsupdate.log file, located on the individual clients, will have all the information pertaining to how wuauclt runs on their individual systems.

    as commented by John

    and…

    To expand on John's answer...

    There are three functional uses for the WUAUCLT.EXE command.

    1. wuauclt /detectnow  -- initiates a detection event to the assigned update services resource (AU or WSUS).

    2. wuauclt /resetauthorization /detectnow -- this is actually a special case version of the previous command. The /resetauthorization parameter forces the targeting cookie to be immediately expired. Normally the cookie has an ~60 minute expiration. Typically this form of the command is used when server-side targeting is being used, and a client system has just been reassigned to new group(s) via the WSUS console. Use of this command forces the WUAgent to discard any previously known group memberships and to requery the WSUS server for the current memberships. This command should also be used when the SusClientID has been deleted and a detection was performed within the previous hour to ensure the WUAgent does not use the SusClientID that is cached in the targeting cookie. Also note that the order of these parameters is critical -- the /resetauthorization flag must be the first of these flags on the command line.

    3. wuauclt /reportnow -- IF a recent event has completed and there are PENDING EVENTS to be reported to the WSUS server, this command will force the immediate flushing of that reporting event queue. If there are no pending events to be reported, this command does nothing.

    No other parameters are supported or documented -- although many are defined in the source code and have been extracted via reflection. Some of them have experimental functionality, but should not be used in a production environment.

    as commented by Lawrence Garvin

And the commands for copy-paste.

  • wuauclt /ResetAuthorization /DetectNow
    • wuauclt /a /d
  • wuauclt /ReportNow
    • wuauclt /r

moving on…

--Claus Valca

Enhanced Mitigation Experience Toolkit (EMET) version 5.5

Just a quick post.

A few weeks ago, Microsoft issued a release-version update to EMET.

Enhanced Mitigation Experience Toolkit (EMET) version 5.5 is now available - Security Research & Defense. From that post:

Today we are pleased to announce the release of EMET 5.5, which includes the following new functionality and updates:

  • Windows 10 compatibility
  • Improved configuration of various mitigations via GPO
  • Improved writing of the mitigations to the registry, making it easier to leverage existing tools to manage EMET mitigations via GPO 
  • EAF/EAF+ pseudo-mitigation performance improvements
  • Support for untrusted fonts mitigation in Windows 10

Get the stuff:

You still can’t seem to “upgrade” to the new version. I had to uninstall the previous EMET version (after exporting the custom settings I have). Then I installed the new version and imported my XML file back in.

It seems to be running just fine on our Windows 7 and 8.1 systems.

And yes, I do live dangerously and run it concurrently with Malwarebytes Anti-Exploit in a “yes I will run with scissors and you can’t stop me” sort of attitude.

Cheers.

--Claus Valca

Open Live Writer – we will (eventually) get through this

I could blame the significantly reduced GSD blog posting on competing time drains of late:

  • Downton Abbey on PBS
  • Friday Night Curling televised matches
  • Sysadmin work at the church-house
  • Deep-dive problem solving for some pernicious Windows issues
  • Multiple projects at work
  • Tech-fatigue
  • Providing more quality time to family and friends

All of those do compete quite strongly with my blogging time.

However after considerable reflection, I must put the greatest challenge against the shut-down of the Microsoft Live Writer application (via the Google blogger API changes) and the painful switch to Open Live Writer.

For some background: Windows Live Writer Goes Open - Hurray - WLW breaks - Booo! – GSD blog post

That particular “break” was quickly fixed over the holidays when version 0.5.1.4 was released.

Before anything else, let me say that I deeply appreciate and am humbly grateful to the developers volunteering their time to get Open Live Writer dialed in.

But when I get the urge to compose a blog post, my current enthusiasm drops.

Here is my current process.

  1. Go into the bookmarked topic hopper and pick the post’s subject/theme.
  2. Launch Open Live Writer (OLW).
  3. Compose my post.
  4. Copy all my content and past it into Notepad++ Home in which I’ve…
    1. added spell check functionality
    2. via http://aspell.net/win32/
  5. Run the spell checker and then fix the spelling issues back in OLW.
  6. Add tags to the post by…
    1. opening up my blog home page
    2. reviewing my tags in the side-bar
    3. typing them in manually in the tag bar in OLW
  7. Publish the post to Blogger

It’s not that bad, but the original WLW had built-in spell-checking and was able to download and provide me a pick-list of my blog post tags automatically.

Note, Scott Lovegrove has offered a (temporary) build version that seems to support Blogger categories.

I’ll try it soon on my “non-production” home system and post an update.

It looks to be ready for inclusion in the next release version – whenever that will be. Current release version as of the time of this blog post is 0.5.1.4.

Is this process a deal-breaker…of course not, but the steps required have kinda taken some of the free-form blogging away and made it a more deliberate exercise.  That could be a Good Thing ™ but it does take away the spontaneity from the process.

Likewise, it seems that the OLW team already has plans to integrate spell-checking in the next release version also.

Open Live Writer “Watch List”

So I will need to work on gaining confidence again in my blogging process and embrace it until these minor application issues can be addressed in an upcoming release.

Cheers.

--Claus Valca

Giving it Away

I saw this a few months ago and it inspired me to do some “e-waste” disposal over the weekend.

Living in Houston’s greater-Metro area would lead one to think that there are a lot of great e-waste disposal locations to pick from.  Well there are but most all of them are on the other side of the greater-Metro area from where I live.

Luckily, Goodwill will let me drop off my older computer equipment at any of their area stores (one is just 10 minutes away from home) and ship it (if needed) to their main computer sales store. Sweet.

I’ve got a Compaq Presario V2575US Notebook PC that runs OK but probably could use a new battery and definitely needs a new A/C brick.

There is also a Gateway MA3 laptop that I’ve had a A/C plug resolder service done on the mainboard.  The solder cracked again, but it might be good for parts…or someone willing to do a mainboard swap.

I’ve got several old PCI and AGP video cards.

I’ve got a few old PATA HDD’s that are less than 500 GB in size. I still have an old PATA external drive enclosure but it already has a 500 GB drive in so there isn’t much sense on holding onto any of the others I’ve “collected” over the years. They will be wiped and donated too.

I found Lavie and my old Palm Pilot III’s. Now I’ve got to figure out if I can charge them somehow and wipe them. Oh the memories of early PIM/PDA technology.

I’m still not quite ready to part with my Shuttle SK41G. It’s like a child for some reason. Since I now have a USB-DVD player, I should be able to dump the very slow (but working) Win 7 OS and finally try out LXLE Desktop on it. Sadly, my new Raspberry Pi 2 seems faster than the Shuttle and is whisper quiet.

I’ve got two Samsung 930B flatscreen monitors. They work great but really can’t seem to handle the “modern” resolutions that most systems display at now-days. I’ve considered donating them as well but since they support both DVI and VGI inputs, they might still be handy troubleshooting display issues with laptops or other systems…so those will hang around for a bit longer. Just in case.

I think that is the hardest part to get past as a techie. Experience has taught me that there is just a chance that I might encounter a situation where a piece of older hardware might come in handy. So it is tempting to hold on to things that aren’t really needed.

Not electronic but also exiting news was this.

I’ve checked on this situation too and while the local pharmacies are helpful about services I can pay for to responsibly pay for to dispose of unused medications, it is neither cheap or convenient. However I am not comfortable flushing them down the toilet or tossing them in the trash. FDA advice here.

Cheers.

--Claus Valca

Saturday, December 12, 2015

The Struggles

Fittingly I had this post fully composed and was cleaning up the formatting in the Blogger WYSIWYG in Chromium when the browser page jumped back and I lost it all…maybe I brushed the laptop touch pad and it interpreted it as a gesture action. Don’t know. This current build of Chromium seems jumpy. I had the same thing happen on some general web-page browsing as well.

So my new blog posting process is to compose fully in WLW (at least that works). Then copy/paste into the Blogger WYSIWYG editor. Using anything but Chromium. We’ll see how that works.

So what I was trying to post is that these past two days have been filled with struggling against a series of random events during normal pc maintenance around the Valca home.

I spent several hours last night working on updating Lavie’s Dell Inspiron laptop; mostly Windows updates and third-party browser updates. Then I went through her “Programs & Features” and worked though each of those seeing if they had updated versions. Many did. So I took care of those.

I discovered that while the WiFi was working normally again under Win 8.1, the “Dell Wireless WiFi + Bluetooth Driver” install package listed in “Programs and Features” was corrupted. I couldn’t remove it. I wanted to be sure I had the installer package on hand in case a future Win 10 upgrade borked it again. Luckily I both found it - Dell Wireless 1703 WiFi+ Bluetooth Driver Driver Details – and was able to use it to do a repair/reinstall to get it on clean again under Win 8.1.

Of course, iTunes wanted to be updated, so I used the Apple Software Updater but it complained about the “iPod Service” not being able to start so the install kept failing. I then tried to download and run the iTunes package rather than using the updater but that failed at the same point.

I found this post Service ‘iPod Service’ (iPod Service) could not be installed... over in the Apple Support forums and followed “rickybpta” steps.
  • close SysInternals's Process Explorer ( if you have it and it's open )
  • close all Task Manager(s)
  • close Windows Services console ( services.msc )
  • close all command prompts ( cmd.exe )
  • open a cmd.exe as Admin
    • run: sc create "iPod Service" binpath= "C:\Program Files\iPod\bin\iPodService.exe"
    • close all command prompts ( cmd.exe )
  • open Windows Services console ( services.msc )
    • look for "iPod Service", see if it's not Disabled. If so, start it
    • close Windows Services console ( services.msc )
  • Run iTunes.msi again ( previously downloaded via the Apple Software Update's Only Download function )
That did the trick and it went on without any other fuss.

While I was doing all this work Lavie’s laptop seemed sluggish. In fact it has seemed that way to me for some time (Lavie shrugs) and I’ve been considering upgrading it to a SSD drive.  I was monitoring the performance using System Explorer’s process tree and Task Manager graphs but not really seeing any clues.

Then I opened up Resource Monitor and focused in on the file activity. I was shocked to see that the process that was doing all the file reads/writes was Classic Shell. To see if this could be responsible I closed out Classic Shell and the system sprang to life again. It seemed much more responsive and snappy again.

Lavie is going to see if the system seems better with Classic Shell after all the clean up work and then with it turned off before she considers letting me disable/remove it.

I’ve also followed this tip to add a semblance of a Start – All Programs list to the task bar. It’s a great tip and one I like to do for our Win 8.1 tablet users.
That service work alone on Lavie’s laptop should have been enough for the weekend.

However, I ran into a new round of issues on my workbench laptop this morning.

First off, VMware Workstation Player offered me an update to 12.1.0.  Sure.

Only the installer failed and left me with an error that “"Service VMware Authorization failed (VMAuthdService") could not be installed. Verify that you have sufficient privileges to install system services.”

I tried a few more times with no success.

I then downloaded the setup file directly from VMware and tried an install with the /clean switch but it said it couldn’t find an installed version.

Checking the Windows Services found a series of VMware related services that were “present” but looked like they were marked for deletion.

I walked though this VMware KB: Cleaning up after an incomplete uninstallation on a Windows host KB but wasn’t finding any remnants at all of the previously working installation.  So it looked like it had been taken off ok.

So I just rebooted the system and indeed the VMware service items were gone.  I tried the installer again with fingers crossed and the installer went on smoothly and the app ran again with no issues.

Whew!

And no sooner had I completed that task than GlassWire wanted to update to a new version as well.

So I went though the download/install process and it seemed to go on OK, but when it opened up it could not reconnect to the Glasswire service.

When I checked the Windows Service for it again it also showed marked for deletion.

So I uninstalled Glasswire, rebooted reinstalled Glasswire but again it could not attach to the service.

I checked the service again. It was present and set to Automatic but stopped. When I clicked “start” the service launch crashed with an error I didn’t capture.

Rinse-repeat-same result.

The updated Glasswire version 1.1.36b was doing fine on the upgrade process on Lavie’s laptop and my other Win 7 x64 laptop so I’m not sure what was the issue here.

Next I found an even newer version 1.1.4.850b. Same issues.

Finally I found the original Glasswire version 1.1.32b on one of my duplicated (but not recently sync’ed) USB drives.

That installed fine. The Glasswire service started automatically, and the app reconnected with no issues. So I’m leaving it there for the moment on this system.

Bother!

Claus Valca.



Windows Live Writer Goes Open - Hurray - WLW breaks - Booo!

Well I was all set to excitedly post news about the announcement that Windows Live Writer has gone to an Open Source project release.

Hurray!


Only I got an account/password error during installation when configuring it up to the Blogger system.

Oh well, let me just launch my original WLW installation and go from there...

Nopes.
Turns out it looks like Google has timed it's depreciation of the WLW authentication method so it now will not work.

Booo!


Per a comment in the thread by "Hirschy" earlier today...

The issue is well known and is being worked on as part of the Open Live Writer project, please see https://github.com/OpenLiveWriter/OpenLiveWriter/issues/5 for progress
The reason it's not working is that a few years ago Google deprecated the authentication process that Live Writer uses,  i.e. Google declared it as obsolete because it is not secure enough for the modern web, and developers should stop using it ASAP. Unfortunately Live Writer was not updated to use the new more secure OAuth 2 standard. Google removed support for it back in about May this year, then temporarily re-enabled it for Blogger / WLW, now it looks like they have pulled it for good.
It's not straightforward to fix, certainly more than a couple of lines of code. If you want to comment, please post to the GitHub issue via the link above, as that will be read by the developers. They will not generally be following the MS forums as it's no longer an MS product.
Convert Google Blogger ClientLogin to OAuth 2.0 · Issue #5 - OpenLiveWriter/OpenLiveWriter · GitHub

And as "ronmartmsft commented on the issue page:
This could not have happened at a worse time given how many bloggers rely on the holiday season for income. It seems that Google has taken the release of this product as a green light to finally deprecate the legacy auth leaving Blogger users stranded.
Track here - https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/blogger/lw_sNsyySKI/FyMxf1DBBwAJ
I must agree.

The initial excitement I had at a new WLW release...even if missing spellchecking at this stage was heavily tamped down with the breaking of the original WLW posting to Blogger.

It's not clear to me yet if other alternative blogging clients that can interface with Blogger will also hit that brick wall.

I'm composing this post in the Blogger web page UI but that won't do for regular posting.

So until this sorts out -- please be patient while the blog posting at GSD slows down.

Bummed for the moment.

--Claus Valca