Just an unofficial survey for myself.
Is RWW or RWA as important these days? Or do you use RDgateway/RDP with RDS cals to provide anywhere access to your SMB networks?
Or is it via VPN?
What’s the process that you make sure that your clients can remotely access their network at any time?
Or are they all in the cloud already and don’t need access to an on premises server?
Okay so it all started with a new server. One that I want to use as a test, so I’m putting an exact copy of my real server on it in order to do this test. But obviously it cannot be on the same IP range as the real server. So no problem, I’ll put in a virtual router in order to do this. So I put in a Sophos virtual router in order to facilitate this. http://fastvue.co/sophos/blog/how-to-deploy-sophos-utm-on-hyper-v-in-7-simple-steps/
If you follow that blog post, the DHCP broadcast from the real DHCP server will bleed through to the virtual server set up in the test bed. So while those blog post instructions get you most of the way, you’ll need to set up the virtual switch with the internal nic being set as “private”, not connected to a external network as shown there.
But that’s where I ended up hitting a bit of a brick wall. No matter what I did, the connections would not get out to the Internet nor with they even do the most basic of ping commands.
In looking around the web, I found that my dear friend Broadcom nics were nailing me again and that PowerShell would come to my rescue.
For background read here:
How To Avoid Common Networking Issues In Hyper-V | Aidan Finn, IT Pro:
Hyper-V 2012R2 failing network connectivity using fully converged networking SOLVED! | MS Sec by Ben:
And review this KB
Poor network performance on virtual machines on a Windows Server 2012 Hyper-V host if VMQ is enabled:
and and this KB:
I had to go into PowerShell and disable the Vmq on each nic.
Set-NetAdapterVmq -Name “NIC 1″ -Enabled $False
Set-NetAdapterVmq -Name “NIC 2″ -Enabled $False
Mind you I have a later network driver, but even with the most recent HP/Broadcom driver I still was having no ability to even ping from any virtual machine set up on the virtual switch.
I also set the MAC addresses to dynamic to ensure that wasn’t nailing me as well.
Set-VMNetworkAdapter –ManagementOS -Name <VirtualNetworkAdapterName> -DynamicMacAddress
Then I ripped out all the networking/virtual switches and rebuilt them and then I finally got the setup I needed.
One virtual SBS server on a private IP range not connecting at all to the real internal lan network.
One Sophos router that is able to provide internet access to the private network.
Now we're set.
And lesson learned, even WITH the latest drivers, Broadcom network cards and HyperV lead to a lot of head banging.
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
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: http://forums.mydigitallife.info/threads/57448-KB2984972-breaks-concurrent-RDP-patch?p=960999#post960999
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.
https://serverfault.com/questions/637251/what-would-cause-wyse-c10le-thin-clients-to-suddenly-be-unable-to-use-dual-displ/637429#637429?newreg=ab71e335f34e48c2b161992751a39282 If someone has a serverfault reputation of greater than 50 can you post in there and ask them to email me at susan-at-msmvps.com (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:
https://social.technet.microsoft.com/Forums/en-US/c90212b0-b32c-4488-9753-fb952112828c/warning-kb2984972-and-autodeskrelated-46-appv-packages?forum=mdopappv << case opened on this issue SRX 114101611907865.
Status: Known issue now documented
Known issues with this security update
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:
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:
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
For Microsoft Application Virtualization 4.6
How to back up and restore the registry in Windows
- For all supported x86-based systems Registry Key: HKLM\SOFTWARE\Microsoft\SoftGrid\4.5\SystemGuard\ObjExclusions
Value name: 95 (Or any unique value)
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)
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: https://social.technet.microsoft.com/Forums/en-US/bc191121-94ab-483f-ae9f-d5056ca3aae5/kb2949927-fails-to-install-if-bitlocker-fvevol-service-is-disabled?forum=w7itproinstall
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.
More Recent Articles