Showing posts with label Microsoft Update. Show all posts
Showing posts with label Microsoft Update. Show all posts

Tuesday, 11 December 2018

OS Guide: Slipstream Updates Using DISM and OSCDImg *Updated

We have found out that we need to have the May Servicing Stack Update (SSU) KB4132216 _and_ the latest SSU which is currently KB4465659 in the Updates_WinServ folder we drop the Cumulative Update into for the Windows Server 2016 slipstream run.

image

Note that the current version of the script points to Server 2019. Please use that as a base to tweak and create a set of folders for Windows Server 2016 and Windows 10 updates.

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
www.s2d.rocks !
Our Web Site
Our Cloud Service

Tuesday, 13 November 2018

New PowerShell Guides and DISM Slipstream Process Updated

We've added two new PowerShell Guides:

We've also updated the page with some tweaks to using DISM to update images in the Install.WIM in Windows Server. The process can also be used to slipstream both Servicing Stack Updates (SSUs) and Cumulative Updates (CUs) for both Windows Server and Windows Desktop.

Thanks for reading! :)

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
www.s2d.rocks !
Our Web Site
Our Cloud Service

Thursday, 31 May 2018

OS Guide: Slipstream Updates and Drivers Using DISM and OSCDImg

We've posted another guide to our Web site.

Using the script on this page in an elevated CMD allows us to take the base Install.WIM for Windows Server 2016 and slipstream the latest Cumulative Update into it.

Then, the script copies the updated Install.WIM into two separate folders where we keep two sets of installer files/folders. One is a Bare version that has only the Windows installer files. The other contains a whole host of drivers, BIOS and firmware updates, and a copy of the newly minted .ISO file. We use the FULL version for our USB flash drives (blog post) that get permanently plugged into all server systems we deploy.

This script is constantly updated.

Another will be posted at a later date that also includes the ability to update the Install.WIM file with drivers.

UPDATE 2018-06-04: Fixed the link!

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Web Site
Our Cloud Service

Wednesday, 9 May 2018

Remote Desktop Client: An authentication error has occurred. *Workaround

Updates last night included one for CredSSP CVE-2018-0886.

For those of us that are hesitant to patch our servers the instant a patch is available we'll be seeing RD Clients unable to connect for the period prior to our regression testing and release cycle.

Remote Desktop Connection

An authentication error has occurred.
The function requested is not supported.

Remote Computer: SERVERNAME
This could be due to CredSSP encryption oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660

For now, the workaround on the remotely connecting RD Clients is to set the following registry key:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\CredSSP\Parameters]
"AllowEncryptionOracle"=dword:00000002

Copy and paste the above into Notepad and Save As "CredSSP.REG" in a quickly accessible location.

Double click on the created file and MERGE. An elevated Registry Editor session would also allow for import via the FILE menu.

Once the above registry setting is in-place reboot the client machine and the connection should work.

Happy Patching! :)

UPDATE 2018-05-09 @ 10:47 MST: A caveat:

It is better to update the server backend, if possible, before making the above registry change.

If that is _not_ possible, then after the updates have been applied on the server(s) make sure to _change_ the registry setting to its most secure setting.

UPDATE 2018-05-10 @ 17:38 MST:

Update sources:

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Web Site
Our Cloud Service

Thursday, 20 July 2017

Windows Server 2016 July 18, 2017 CU is Important!

The July 18, 2017-KB4025334 (OS Build 14393.1532) Update is _important_!

There are fixes in there for a lot of cluster specific products.
  • iSCSI
  • S2D
  • ReFS
  • DeDup
  • MPIO
  • NTFS
The specifics are in the Microsoft page linked to above as is a download link.

We are in the process of updating our base Install.WIM image (blog post) with this update as I write this!


Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service
Twitter: @MPECSInc

Monday, 15 May 2017

WannaCry Mitigation plus Windows XP and Server 2003 Patch

By now most of the world has heard about the WannaCry malware put together from purported NSA exploit "tools".

The simplest thing to do is to disable or remove SMBv1 on our networks: How to enable and disable SMBv1, SMBv2, and SMBv3 in Windows and Windows Server (Microsoft Support).

Dealing with SMBv1

On Windows 7:

First, we need the following put into a text file:

sc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsi
sc.exe config mrxsmb10 start= disabled
pause
shutdown -r -t 0 -f

image

In Notepad click File then Save As and name exactly as follows:

"Windows7 SMBv1 DISABLE.BAT"

image

NOTE: The quotes " are necessary

Right click on the resulting BATCH file and Run As Administrator:

image

An administrator's username and password will be required for this step. A local admin or domain account would work.

A status window will show:

image

NOTE: Windows 7 should show SUCCESS for both steps

As the message says, press any key to continue.

NOTE: The script automatically reboots the machine so make sure users save and close before running.

On Windows 10:

  1. Click Start and type PowerShell
  2. Right click on the result and Run as Administrator
  3. Remove-WindowsOptionalFeature –Online –FeatureName SMB1Protocol
    • You should see:
    •      image

That fully removes the problematic component in Windows.

Windows Server

Open an elevated PowerShell window:

Remove-WindowsFeature –Name FS-SMB1

image

Backup & Restore

For users that almost exclusively work from their computer over server or cloud based resources with no local backup it's important that they back up their machines daily! They should have at least three 2.5" USB3 fast disk drives in rotation.

We use ShadowProtect Desktop by StorageCraft to back up our client's endpoints.

A critical component in the backup regime is an air-gap. Just as it is for the entire organization's server infrastructure.

Windows XP and Server 2003

Get the Security Updates ASAP and install them!

The files may be able to be set up to be delivered via your favourite patching mechanism. Please check that out to get these patches out to as many systems as is possible.

Windows Firewall

One mitigation step would be to set up a Group Policy object that denies File & Print (445) Inbound from any system but necessary such as servers and/or domain controllers.

Malware Mitigation

As always, the best form of mitigation is a well trained user. Patch and train the human is the best methodology going.

A a small plug, our xD mail sanitation and continuity service flags and renders inert links that say one thing but point to another location. This has put link shortening services like Bit.Ly at a disadvantage but we're willing to pay that price to keep our users sage. Just ask us how!

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Thursday, 27 April 2017

Surface Pro 4: Creator's Update Graphics Driver Issue

As an FYI, after updating to the Creator's Update Windows 10 version the graphics subsystems on the Surface Pro 4 seems to start behaving badly. This is especially true if connected to external monitors via a Surface Dock (Gen1 or Gen2).

An updated driver can be obtained here: Intel Iris 540 Driver for Windows 10

The SP4 had 15.44 while the download is 15.45 as of this writing!

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Wednesday, 15 March 2017

Windows Server 2016 March 2017 Update: Full & Delta Available

We can download both the full March Cumulative Update or there is now a Delta available.

image

Delta Update Windows Server 2016

The update is quite critical for those of us that run clusters on Windows Server 2016.

  • Addresses issue which could cause ReFS metadata corruption
  • Several fixes for Enable-ClusterS2D cmdlet for setting up Storage Spaces Direct
  • Addresses issue with Update-ClusterFunctionalLevel cmdlet during rolling upgrades if any of the default resource types are not registered
  • Optimization to the ordering when draining a S2D node with Storage Maintenance Mode
  • Addresses servicing issue where the Cluster Service may not start automatically on the first reboot after applying an update
  • Improved the bandwidth of SSD/NVMe drives available to application workloads during S2D rebuild operations.
  • Addresses issue with all flash S2D systems with cache devices where there was unnecessary read data from both tiers that would degrade performance

A full list is here: March 14, 2017—KB4013429 (OS Build 14393.953)

The Delta Update can be used to update our .WIM files for our Windows Server 2016 flash drive based installers (Blog post How-To).

Note that the last Cumulative Update took a good hour to run on our VMs and nodes. This one is sounding like it may take as long or longer depending on whether the Delta of full Cumulative Update gets installed.

Here’s a direct link to the Microsoft Update Page for KB4013429.

Happy Patching! ;)

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Tuesday, 10 January 2017

Server 2016 January 10 Update: KB3213986 – Cluster Service May Not Start Automatically Post Reboot

The January 10, 2017 update package (KB3213986) has a _huge_ caveat for those updating clusters especially with Cluster Aware Updating:

Known issues in this update:

Symptom
The Cluster Service may not start automatically on the first reboot after applying the update.

Workaround
Workaround is to either start the Cluster Service with the Start-ClusterNode PowerShell cmdlet or to reboot the node.

For those managing large cluster deploys this situation definitely leads to a need to evaluate the update procedure for this particular update.

Please keep this in mind when scheduling this particular update and have update resources set up to mitigate the problem.

Note that as of this writing, the cluster service stall on reboot is a one-time deal as far as we know. Meaning, once the update has been completed and the node has successfully joined the cluster there should be no further issues.

Philip Elder
Microsoft High Availability MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Our Cloud Service

Tuesday, 15 April 2014

Windows 8.1 and Windows Server 2012 R2 Update 1 Caveats

Whenever we hear about updates for any device firmware, application software, or operating system software it is _always_ a good idea to read the Release Notes (we probably all know the acronym that comes to mind here ;) ), README.TXT, _and_ do a search for the update to see if anyone is complaining about it. Unfortunately, this major update for Windows 8.1 and Windows Server 2012 R2 has its issues some of which are full-stop problems. The first place to start for this update is here:
There is a lot of information there.
  1. Update 1 is the new baseline for all updates going forward.
    • Meaning, no more updates to that OS if the bits are earlier than 8.1 U1 or 2012 R2 U1.
  2. Update 1 breaks SSL communications between endpoints and WSUS
This last one is a deal breaker for many enterprises, medium enterprises, and especially in our own SMB/SME environments where WSUS is virtually everywhere for patch management.
We just stood up a new cluster on 2012 R2. After our Cluster-Aware Update run:
image
Our cluster nodes now have the update. Since this cluster setup is Greenfield with WSUS ultimately ending up _on_ the cluster the nodes were updated via Microsoft Update.
The workaround for this situation is to enable TLS 1.2 as instructed in the above blog post. Since we are deploying Windows Server 2012 R2 into client sites we will have no choice but to make this change.
Then, when Microsoft releases an update to the update to hopefully fix the problem we will need to test that update extensively _especially_ in a cluster setting!
Yo Microsoft! There is a huge pool of folks willing to test and break this stuff for you! Please get us involved in the early bits for operating systems, applications, and updates again. This ongoing situation of releasing patches and updates to the public without testing them on disparate systems is a _bad_ thing. :(
EDIT: Updated the Gladiator link since between Live Writer and Blogger it got mangled.
Philip Elder
Microsoft Cluster MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book
Chef de partie in the SMBKitchen ASP Project
Find out more at
Third Tier: Enterprise Solutions for Small Business



Monday, 14 April 2014

A Small Chunk of Bandwidth for Windows Server 2012 R2 and Windows 8.1 Pro/Enterprise with Update 1

Okay, so here we go updating our ISO library:

image

image

And:

image

image

And finally:

image

image

Note that all Windows 8.1/Server 2012 R2 operating systems in the field _must_ be updated to Update 1 or they will not receive any further starting with Patch Tuesday this coming May!

That does not give us a lot of time to test the patch setup. But test we must! :(

By the way, is there any need to download the 32-bit version of a desktop OS anymore? We've not had to use one in ages!

Philip Elder
Microsoft Cluster MVP
MPECS Inc.
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen ASP Project
Find out more at
Third Tier: Enterprise Solutions for Small Business

Monday, 9 September 2013

Windows Server 2012 and Essentials: Error 80073718 on Update(s)

We may be seeing some issues in Windows Server 2012 and W2012E:

In the end the problem points to a "servicing stack corruption" with the OP needing to re-install the operating system from scratch.

While this may be a possible suggestion for a new server setup, those that have had their systems in production for any amount of time are left in a bit of a conundrum.

At this time there is no "fix" for the "problem".

So given that Microsoft would not recommend a third party action, our suggestion for those that have a full server setup in production is to look into running a Swing Migration. Fellow MVP Jeff Middleton's methodologies will preserve Active Directory, Group Policy, and more.

If the setup is a VM then there are a number of options one can pursue to Swing the AD off and back on again.

This method would save a good chunk of time as one would not need to migrate the local profiles over to the rebuilt domain nor have to deal with Group Policy Tattoos if one rebuilds with the same domain name. Plus, if there are on-premises services running in Exchange, SQL, and other Line of Business applications the time savings would be _huge_.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Wednesday, 13 March 2013

Windows 7 and Server 2008 R2 New Cumulative Enterprise Hotfix Rollup Released

Microsoft has released a series of updates that aggregate a number of hotfixes released since Windows 7/Server 2008 R2 Service Pack 1 into one spot. Note that this spot is not Microsoft Update _or_ WSUS.

Normally for hotfixes we would have to link into each hotfix’s download site and go through the e-mail return with password protected ZIP archive (in most cases) process for _each_ hotfix contained in this one update set.

To get the updates we are required to step out of our normal update routines and download them from the Windows Catalogue site.

  1. Go to the Windows Update Catalogue site.
    • Note for users running as Standard User a UAC with admin credentials will be required due to a plug-in requesting install rights.
    • image
    • IE10 on Win8 with Compatibility mode enabled ends up with:
      • image
  2. Type 2775511 in the Search field and click Search.
    • image
  3. We can then add the required update download files to our “Basket”.
    • image
  4. Click the View Basket link.
  5. Click the Download button.
    • image
  6. Click the Browse button and choose a folder to download the updates to.
    • A UAC Prompt will happen at this point.
    • Though, Win7 with IE9 seems to have stalled at this point on our download attempts. :(
    • image
  7. We ended up needing to Run As Admin and elevating Internet Explorer when starting the browser before we finally saw this:
    • image
    • But, then we get this:
    • image

Oh well, we tried Win8 with IE10, Win7 with IE9, and Win7 with IE8 with all failing.

image

We tried Run As Admin with UAC via the domain admin account to start all of the IE versions on each OS and still hit a roadblock.

We shall try again later. :(

Once we do have the files we will be able to see about how we will deploy them at client sites.

Hat Tip: Susan Bradley the SBS Diva

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Chef de partie in the SMBKitchen
Find out more at
www.thirdtier.net/enterprise-solutions-for-small-business/

Windows Live Writer

Thursday, 10 January 2013

Update KB2750149 Breaks Hyper-V 2012 Failover Clusters

It seems that a recent update is wreaking havoc on Hyper-V 2012 Failover Clusters.

If updates have not been run as of yet then avoid this one.

If things are not working as expected after a round of updates and this one was included uninstall and hopefully things come up as they should.

Error quote from the Forums post:

A weak event was created and it lives on the wrong object, there is a high chance this will fail, please review and make changes on your code to prevent the issue.

Version=1
EventType=AppHangB1
EventTime=130022261829914481
ReportType=1
Consent=1
ReportIdentifier=26cc3e6a-5a82-11e2-93f7-782bcb53a584
IntegratorReportIdentifier=26cc3e6b-5a82-11e2-93f7-782bcb53a584
NsAppName=mmc.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=mmc.exe
Sig[1].Name=Application Version
Sig[1].Value=6.2.9200.16384
Sig[2].Name=Application Timestamp
Sig[2].Value=50109efd
Sig[3].Name=Hang Signature
Sig[3].Value=5707
Sig[4].Name=Hang Type
Sig[4].Value=138496
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.2.9200.2.0.0.400.8
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=5707c224bfa37e5b267a1680ece79add
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=c8c0
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=c8c0bc8698a6964e5cded02ffc06ca16
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=5707
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=5707c224bfa37e5b267a1680ece79add
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=c8c0
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=c8c0bc8698a6964e5cded02ffc06ca16
UI[3]=Microsoft Management Console is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Management Console
AppPath=C:\Windows\System32\mmc.exe
ReportDescription=A problem caused this program to stop interacting with Windows.
NsPartner=windows
NsGroup=windows8

We tend to wait on updates with our managed clients.

It seems that regression testing for updates has not been up to the same standard it has been in the past at Microsoft.

So, we test here in-house beforehand. It is a part of our service offering.

Hat Tip: SBS Diva

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

Monday, 31 December 2012

Microsoft Surface RT: WiFi Connection Error/Won’t Connect

Both of our home based Microsoft Surface RT units recently became unable to connect to any wireless connection.

It seems that the recent December updates that were supposed to _fix_ WiFi connectivity issues on the Surface RT actually broke ours that had nary a problem before.

Our home wireless setup is three Cisco WAP4410N APs set up with the same SSID and three separate channels. All APs have WPA2-Personal AES encrypted keys and all three radio bands B/G/N enabled.

All three APs are connected to a power supply (not using PoE).

After some searching and questions out and about in the forums we participate in the following seems to be true:

  • Wireless N is the problem.
  • Surface RT will connect on B and/or G.
  • Surface RT WiFi connector forced into G will connect.
  • WAPs switched to B/G Only will allow Surface RT to connect.

On one Surface RT uninstalling, rebooting, and then re-installing the MARVELL WiFi device seemed to get things straight.

On the other though nothing worked. We tried all manner of getting the unit to connect with no success.

So, we logged into all three AP Web consoles and switched the APs over to B/G Mode and tried to connect the Surface RT. Sure enough, the unit connected almost instantaneously.

We then switched the APs back to B/G/N Mode and rebooted the troublesome Surface RT.

To date it has stayed connected to the wireless network.

For now, we at least know what to do to get the units to cooperate again.

Hopefully whatever was broken with the last round of updates will be fixed in the next round! :P

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

Monday, 22 October 2012

Windows 8 App Updates This Morning

When we logged into one of our shop systems our now RTM Windows 8 Enterprise Store Live Tile showed a number on it:

image

Now, the above number came _after_ we had already jumped in to the Store and clicked the Updates (10) link in the top right corner of the Store window.

image

This is what we saw:

image

We clicked the Install button at the bottom of the above list and ended up with the Store saying we had three updates to do again:

image

Once done, the Apps look to be the same. We will need to dig into the product support site to find the release notes for the revision notes.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

Windows Live Writer

Thursday, 12 July 2012

Windows Phone 7 Update 7.10.8112.7

We just got offered the following:

image

The more info link takes us to this page:

Note that the latest listed update on the Windows Phone site says 7.10.8773.98 and ours says 7.10.8112.7. That's quite the difference.

A bit of searching brought us to this page:

According to the above site 7.10.8773.98 is Tango and provide an update method though we are a bit wary of using a third party tool to run this process.

Of course, the above was written while the update was running. Once it was completed though the following showed up:

image

It seems that Tango will be on the phone today.

We shall see if it makes a difference with the phone.

From what I can see, nothing outright. Still no mobile hot spot. :(

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Monday, 9 April 2012

Microsoft Updates for Hyper-V RSS Feeds

Here are some Microsoft updates Web lists with RSS feeds for the Hyper-V Role and Server:

There will be additional feeds once Windows Server 8 gets its name and is released to manufacturing.

Hat Tip: Susan Bradley

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Tuesday, 24 January 2012

Stuck at Configuring Windows updates – Do not turn off your computer. Try This First Before Anything Else

Lately when setting up a new server or updating a production server that has been up for a few months we have been seeing the following:

image

Windows Server 2008 R2 Enterprise

Configuring Windows updates
32% complete
Do not turn off your computer.

What we have discovered is that after waiting five minutes we can CTRL+ALT+DLT and the log on screen will show up. Sometimes it may take 10, 20, or even 30 minutes or more before we see the log on screen but it does eventually come up.

For whatever reason though the server can be left all to itself in the above state and stay there until we hit the keys.

This is our first step now before running into the update recovery steps that may be required if this does not work.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer

Wednesday, 9 November 2011

A Live Wiki Based Microsoft Update List for Hyper-V

Microsoft has a TechNet Wiki that lists all of the relevant updates and hotfixes for the Hyper-V Role or Hyper-V Server 2008 RTM/R2.

The last update to the Wiki was October 26, 2011.

Also, the Wiki has an RSS feed:

A snip of the Wiki page:

image

//

image

The second from the bottom update dated October 20th looks to be one of the latest on this list as of this writing.

For those of us running virtualization solutions on Hyper-V and failover clusters on Hyper-V this list is very important to monitor.

Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book

*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.

Windows Live Writer