Your email updates, powered by FeedBlitz

Click here to read this mailing online.

Here is a sample subscription for you. Click here to start your FREE subscription

"Small Business Susan" - 5 new articles

  1. Getting ready to do a dry run of my migration
  2. October patch status report – 10 days past release
  3. Got a few hours to watch some videos?
  4. Real patch pain metrics
  5. Getting ready for a test run
  6. More Recent Articles
  7. Search Small Business Susan
  8. Prior Mailing Archive

Getting ready to do a dry run of my migration

And figured that it was also a good time to double check that I could recover from my backups.  So I parked a backup onto an external usb drive that was attached to my new HyperV host.  I shared out the usb drive to “everyone” in order to get it from the domain over to a workgroup host (note to self this should be ‘unshared’ from this methodology in order to protect from cryptolocker later on).  I went across the network from my SBS box to the usb attached hard drive on the HyperV host (workgroup mode not domain ergo why I had to do the Everyone share).  So then I went to the hyperV host, set up a new virtual server with the drive settings that matched the other SBS box.  I then made the usb external drive “offline” in the parent’s  computer management [this is a key element, if you don't do this you can't attach the external usb drive to the child hyperV].  Then I went into the HyperV settings, added an IDE drive (not SCSI  – it has to be IDE) and then attached the physical external drive.

I then boot up with a matching media to whatever I’m trying to restore – Vista/SBS 2008 for SBS 2008 era, Windows 7 or SBS 2011 for SBS 2011 era and to go the repair computer section.  I say I’m going to make a full recovery and let it ‘find’ the backup.  If you’ve done this attaching to the child right it will find that backup and then let you do a full restore.

Upon rebooting remember that the nics will still be in ghost country and it will boot with a 169.x.x.x IP as your real IP is bound to the ghosted nic.

(Same process as ptov-ing) and then reassign your IP address to the new nic.

Now I’m all set to do a dry run migration.

And yes to get the virtual router to work I had to manually assign a static IP to the virtual nic otherwise it wouldn’t pick up an address.  Ah the lessons we learn

October patch status report – 10 days past release

Issues we are still tracking:

**** KB30000061 is a kernel update:
KB3000061 fails to install on Server 2012:   Also impacting Windows 8.   Cases opened: 114101711916740 and 114101711915623

Status:  See in that thread, Microsoft engineer in the forum is asking for cbs.log files from impacted machines.  Some recommendations have been made, no solution at this time.

Two issues with KB2984972 – this is a patch to update the RDP restricted admin mode

“Heads up, KB2984972 on Server 2008R2 RD server caused issues with our Wyse thinclients – it caused them all to span desktops across multiple monitors rather than presenting multiple monitors to the host OS. After uninstalling & rebooting clients are presented with multiple monitors again.”  <<<< will impact MultiPoint Server as well too <<<<<

Another thread on the issue here:

Status:  Unknown if this is being investigated by Microsoft.  Have seen some updates from the thin client vendors, so unsure if this will be patched from the vendor side or from the Microsoft side.    If someone has a serverfault reputation of greater than 50 can you post in there and ask them to email me at (change the -at- to @) to set up a support case?  I really am unsure if there are cases being worked on regarding the thin client impact and I’d love to make sure they are.
App v and KB2984972 impact:   << case opened on this issue SRX 114101611907865.

  Status:  Known issue now documented

Known issues with this security update

  • Symptoms After you install this security update, virtualized applications in Microsoft Application Virtualization (App-V) versions 4.5, 4.6, and 5.0 may experience problems loading. When the problem occurs, you may receive an error message that resembles the following:
    Launching MyApp 100%
    Note In this error message, MyApp represents the name of the App-V application. Depending on the scenario, the virtualized app may stop responding after it starts, or the app may not start at all. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
    322756 How to back up and restore the registry in Windows
    Resolution To resolve this known issue, configure the TermSrvReadyEvent registry entry on the computer where the Microsoft Application Virtualization Client is installed. For Microsoft Application Virtualization 5.0
    • Registry Key: HKLM\Software\Microsoft\AppV\Subsystem\ObjExclusions Value name: 93 (Or any unique value) Type: REG_SZ Data: TermSrvReadyEventExample For example, type the following command at an elevated command prompt to add the entry to a system running Application Virtualization 5.0:
      reg add HKLM\Software\Microsoft\AppV\Subsystem\ObjExclusions /v 93 /t REG_SZ /d TermSrvReadyEvent
    For Microsoft Application Virtualization 4.6
    • For all supported x86-based systems Registry Key: HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions Value name: 95 (Or any unique value) Type: REG_SZ Data: TermSrvReadyEvent Example For example, type the following command at an elevated command prompt to add the entry to an x86-based system running Application Virtualization 4.6:
      reg add HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent
    • For all supported x64-based systemsRegistry Key: HKLM\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions Value name: 95 (Or any unique value) Type: REG_SZ Data: TermSrvReadyEvent Example For example, type the following command at an elevated command prompt to add the entry to an x64-based system running Application Virtualization 4.6:
      reg add HKLM\SOFTWARE\Wow6432Node\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions /v 95 /t REG_SZ /d TermSrvReadyEvent

KB2949927 – the SHA-2 update: Also seeing issues with KB2949927 getting installed:  and

STATUS:  KB2949927 has been pulled from Microsoft update on 10/17/2014

Then KB2995388 8.1 cumulative update causing issues with VMware workstation:

Workstation 10 issue with recent Microsoft Windows 8.1 Update | VMware Workstation Zealot – VMware Blogs:
We noticed that a recent Windows 8.1 Update (KB2995388) may cause issues when running VMware Workstation on a Windows 8.1 host with this update installed. User will see an error message “not enough physical memory” when booting up a virtual machine

STATUS:  per the thread reinstalling vmware 10 will fix the issue, unsure if this patch will be redone or merely the recommendation will be to reinstall VMware

2990942 ASP. MVC security update
Microsoft Asp.Net MVC Security Update MS14-059 broke my build! – .NET Web Development and Tools Blog – Site Home – MSDN Blogs:

Windows Azure Pack: Cannot create Plans.:

Status:  Lots of upset developers.

Driver Patch released by vendor bricks users chips

FTDI appears to have used a recent Windows update to deliver the driver update to brick all cloned FTDI FT232s.

FTDI’s surprise new driver reprograms the USB PID to 0, killing the chips instantly.

The hardware hackers at Hack A Day first reported that a recent driver update deployed over Windows Update is bricking cloned versions of the very common FTDI FT232 [USB to UART] chip

Status:  A driver update delivered through Windows update supplied by a vendor was designed to nuke non genuine chips.  If suddenly your clients/customers start complaining that their USB devices are missing/won’t work, it may be due to this.  The vendor used the MU driver update channel to nuke unlicensed chips  (Susan note:  despite what the Microsoft folks say I use the driver updates offered up to me via MU as indicators I need to look for vendor drivers, I do not install them on production machines due to too many years of being burnt by them)



Adobe update 11.0.9 causes problems with opening files across network shares.  Error message received is
“There was an error opening this document. The network path was not found.”

Status:  Workaround to issue – disable protected mode (which is not acceptable), otherwise use Foxit or CutePDF reader as an alternative.

Got a few hours to watch some videos?

Lots of great videos here on this page:

Derbycon 2014 Videos (Hacking Illustrated Series InfoSec Tutorial Videos):

I highly recommend spending a few hours looking around the videos here!



Real patch pain metrics

Humor me please?

If you can recall a patch directly causing impact to your systems please email me directly – email (change the -at- to @) with the KB number and what it impacted please?  I would love to put together a list of real patch pain, and not just perceived patch pain.

Fact:  There have been a lot of non security updates that are impacting our patching views.

(I’m looking at you Exchange)

Case in point:
8/26/2014    CU 6 for Exchange 2013

Fact:  There have been a lot of click to run issues impacting our patching views:

6/13/2014    Click to run        Uninstall/reinstall
5/22/2014    Click to run        Activation issues

Fact:  There have been hiccups in Office releases – especially in regards to Outlook:
8/13/2014    Outlook 2013    KB2881011    Replaced with KB2889859

Lord knows KB2919355 has impacted my view of this year.

Off the top of my head these are recent pulled patches:
MS14-045 pulled and rereleased.
KB2949927 pulled

Anytime you see a Kernel update, expect slight turbulence especially in the consumer side.  Kernel updates interact with malware infected machines, pirated machines and antivirus vendors that get a little too much protection efforts.

I see the problem as a bit like the Ebola scare in the USA.  We’re scared because of a lack of communication.

There’s a lack of post release follow up and communication as I see it.  We have no idea how many machines are impacted, we just see the social echo of headlines and twitter feeds.

I am concerned that it seems like it’s taking longer to get investigations done.

We’re a week after release date and I still haven’t a clue why KB3000061 is failing, if the RDP patch is going to get a fix or if the fix should be expected from the vendors or what.

While security patches have a known issue section, other patches need a “we’re investigating” section with follow up.

So?  Can you help me out with a feel on REAL patch pain versus perceived patch pain?  I don’t want to know “I heard about an issue on a random blog/twitter account that someone was impacted”… I want to know exactly what patch gave you pain.

Getting ready for a test run

Getting ready for a migration at the office from the 2008 R2 era HyperV to a 2012 R2 era hyperV

iphone 064

And as the server sounds like a jet engine taking off…

it always makes me laugh how small the drives are, and how big the unit it

iphone 065

Makes ya wanna buy more hard drives and fill that sucker up.

So one of the things I’m doing this time is rather than doing a router in front of the server to separate out from the production network, I’m trying a virtual router

Fastvue Sophos Reporter How to Deploy Sophos UTM on Hyper-V in 7 Simple Steps:

So far it’s not as simple as that leads one to think it is.  I obviously have networking/binding to the nics mucked up because it won’t find the web console address.

I’ll try again tomorrow and let you know how I get along with a virtual router.


More Recent Articles

Click here to safely unsubscribe from "Small Business Susan." Click here to view mailing archives, here to change your preferences, or here to subscribePrivacy