Windows 7 Network Controller Issues – KB4338818 (July 2018)

The July 2018 Windows Updates for Windows 7 SP1 and Windows Server 2008 R2 SP1 introduces a bug that could cause the network interface controller to stop working. The update referenced is KB4338818.

In case your systems run into this issue, the workaround from Microsoft is to do the following:

Please use your best judgement and evaluate the risks of applying this update to your Windows 7 SP1 and Windows Server 2008 R2 systems.

** Update **
According to an IT Pro who opened a support case with Microsoft, this is the information provided at this time:

“Regarding the known issue in the July monthly rollup about the network interface controller that will stop working. We are still looking at the data gathered from multiple customers and we do not have a list third party software that is causing the issue. What we do know until now, is that the issue is reproducing mainly on VM over VMware.”

Please like & share:

Remote Server Administration Tools (RSAT) For Windows 10 v1803

The latest version of the Remote Server Administration Tools (RSAT) for Windows 10 April 2018 Update v1803 have been released. The download is available here. You will find the following download files available for version 1.0 corresponding to x86 or x64 Operating Systems:

  • WindowsTH-RSAT_WS_1803-x64.msu (95.1MB)
  • WindowsTH-RSAT_WS_1803-x86.msu (69.9MB)
  • WindowsTH-RSAT_WS2016-x64.msu (92.3MB)
  • WindowsTH-RSAT_WS2016-x86.msu (69.5MB)

See here if you would like to determine if a computer is running 32-bit or 64-bit Windows OS.

Additional Information:

When to use WS_1803 RSAT Package: When managing Windows Server, version 1803 or Windows Server, version 1709
When to use WS2016 RSAT Package: When managing Windows Server 2016 or previous versions

Known Issues that may impact RSAT functionality:

Issue: DNS Tools missing
Impact: WS_1709 RSAT package users
Resolution: Use the WS_1803 or WS2016 RSAT package or apply this workaround

Issue: Cannot turn off individual RSAT components
Impact: WS_1803 and WS_1709 RSAT package users on Windows 10 1803/1709 (April 2018 Update/Fall Creators Update)
Resolution: Use the WS2016 RSAT package on Windows 10 1607 (Anniversary Update)

Issue: Tabs missing from MMC Properties
Impact: Windows 10 clients before 1607 (Anniversary Update)
Resolution: Update to the latest version of Windows 10 client and reinstall RSAT

Issue: Shielding Data File Wizard cannot create shielding data files
Impact: WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update)
Resolution: Use the WS_1803 RSAT package on Windows 10 1803 (April 2018 Update), or use the WS2016 RSAT package on Windows 10 1607 (Anniversary Update) to create shielding data files for Windows shielded VMs, or the built-in RSAT tools in Windows Server, version 1709 to create shielding data files for both Windows and Linux shielded VMs.

Issue: Template disks created from the Template Disk Wizard do not boot
Impact: WS_1709 RSAT package users on Windows 10 1709 (Fall Creators Update)
Resolution: Use the WS_1803 RSAT package on Windows 10 1803 (April 2018 Update), or use the WS2016 RSAT package on Windows 10 1607 (Anniversary Update) to create template disks for Windows shielded VMs, or the built-in RSAT tools in Windows Server, version 1709 to create shielding data files for both Windows and Linux shielded VMs.

Follow me (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

Remote Server Administration Tools (RSAT) For Windows 10 v1709

The latest version of the Remote Server Administration Tools (RSAT) for Windows 10 Falls Creators Update v1709 have been released. The download is available here. You will find the following download files available for version RS1-1.2, RS3-1.0 corresponding to x86 or x64 Operating Systems:

  • WindowsTH-RSAT_WS_1709-x64.msu (94.5MB)
  • WindowsTH-RSAT_WS_1709-x86.msu (69.9MB)
  • WindowsTH-RSAT_WS2016-x64.msu (92.3MB)
  • WindowsTH-RSAT_WS2016-x86.msu (69.5MB)

See here if you would like to determine if a computer is running 32-bit or 64-bit Windows OS.

Follow me (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

ADMX Template For Windows 10 Creators Update (1703) Now Available

To coincide with the release of Windows 10 Creators Update (1703), the following tools to support this latest release has been made available, which includes Windows 10 Administrative Templates (.ADMX) and Windows Assessment and Deployment Kit (ADK) as previously mentioned in this blog post. The previous Remote Server Administration Tools (RSAT) works just fine with Windows 10 Creators Update.

Windows 10 Administrative Template (.ADMX)

Remote Server Administration Tools for Windows 10 (RSAT)

Windows 10 Assessment and Deployment Kit (ADK)

Microsoft Office 2016 Administrative Templates and Office Customization Tool is also available for download.

Follow me (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

Remote Server Administration Tools (RSAT) Version 1.2 For Windows 10

rsat

The latest version of the Remote Server Administration Tools (RSAT) for Windows 10 have been released. The download is available here. You will find the following two download files available for version 1.2 corresponding to x86 or x64 Operating Systems:

  • WindowsTH-RSAT_WS2016-x64.msu (92.3MB)
  • WindowsTH-RSAT_WS2016-x86.msu (69.5MB)

See here if you would like to determine if a computer is running 32-bit or 64-bit Windows OS.

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

How To Fix: Bitlocker Recovery Key Prompts On Every Reboot

windows-10-bitlocker-featured

There are few reports of users having Bitlocker issues following the October 2016 patches.

The issue: On every reboot, the Bitlocker recovery key is required which is quite disruptive and cumbersome. As a workaround in order to solve this issue, the following steps can be taken:

On the next reboot and once in Windows, reset Bitlocker by disabling and re-enabling it.
In administraive command prompt, do the following:
manage-bde -protectors c:-disable
then do this:
manage-bde -protectors c:-enable

At this time, I’m not certain on which patch is causing the issue but I wanted to share this info to help. You can also discuss in this TechNet post.

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

System Center Operations Manager (SCOM) Console Crash

scom-gsx-solutions

** UPDATE**
(October 19, 2016)
A fix for the SCOM console crash issue as previously blogged below has been released. See the following KB320006 article to obtain the hotfix.

***************************************************************************************************

**Posted on October 18, 2016**

There is a widespread report of System Center Operations Manager (SCOM) 2012 R2 / 2016 console crashes due to some bugs in October 2016 Cummulative Updates, in particular with the following patches: KB3194798 / KB3192392 / KB3185330 / KB3185331.

The product team has acknowledged the issue on their blog post and is said to be working on releasing a fix soon. The current recommendation is to uninstall the problematic patches as a temporary workaround. According to the blog post, an announcement will be made on the SCOM Team blog when a fix has been made available. So, keep a close eye on it.

Links related to this post:

SCOM Product Team Console Issue Ackowledgement
TechNet Discussion
SCOM Product Team Blog
Microsoft Tech Community Discussion

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook and Twitter (@TechKonnect) to stay current on technology related matters.

Please like & share:

How To Reset WSUS Server

3d human try to press a button

Sometimes, for various reasons, one must perform a WSUS reset function to make the WSUS server happy again. The reset process forces a resync of each update in the WSUS server with Microsoft services. This task can take a long time to complete as each update will be re-evaluated and re-downloaded, so be patient.

Here’s the command to run from an administrator command prompt::
%SystemDrive%\Program Files\Update Services\Tools\WsusUtil.exe reset

Follow (@Hoorge) on Twitter and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share:

PowerShell 5.0 RTM Now Available

powershellheader2

PowerShell 5.0 has finally RTM-ed, just in time for Christmas as announced on the PowerShell team blog. Windows Management Framework (WMF) 5.0 RTM replaces WMF 5.0 Production Preview and it’s supported on Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 SP1, Windows 8.1, and Windows 7 SP1.

WMF 5.0 adds new management functionality which includes Just Enough Admin (JEA), PowerShell Classes, PackageManagement, PowerShellGet, and improvement to existing technologies such as Desired State Configuration (DSC), PowerShell Script Debugging, Software Inventory Logging and etc.

Download WMF 5.0 from the Microsoft Download Center. WMF 5.0 requires .NET Framework 4.5 or higher which you can also obtain from the Download Center.

**IMPORTANT**
Systems that are running the following server applications should not run Windows Management Framework 5.0 at this time:

    • Microsoft Exchange Server 2013
    • Microsoft Exchange Server 2010 SP3
    • Microsoft SharePoint Server 2013
    • Microsoft SharePoint Server 2010
    • System Center 2012 Virtual Machine Manager

Servers running System Center Configuration Manager 2012 (ConfigMgr) can install and run WMF 5.0.

If you would like to provide any feedback to the PowerShell team, you can do so by using the UserVoice site.

keep-calm-and-learn-powershell-13

*************************************************************************************************

The following is a post by Neema Saeedi on MSDN which I’ve added for additional details:

Download the correct package for your operating system and architecture:

Operating System Architecture Package Name
Windows Server 2012 R2 x64 W2K12R2-KB3094174-x64.msu
Windows Server 2012 x64 W2K12-KB3094175-x64.msu
Windows Server 2008 R2 x64 W2K8R2-KB3094176-x64.msu
Windows 8.1 x64 W2K12R2-KB3094174-x64.msu
Windows 8.1 x86 Win8.1-KB3094174-x86.msu
Windows 7 SP1 x64 W2K8R2-KB3094176-x64.msu
Windows 7 SP1 x86 Win7-KB3094176-x86.msu

To install WMF 5.0 from Windows Explorer (or File Explorer in Windows Server 2012 R2 and Windows 8.1):

  1. Navigate to the folder into which you downloaded the MSU file.
  2. Double-click the MSU to run it.

To install WMF 5.0 from Command Prompt:

  1. After downloading the correct package for your computer’s architecture, open a Command Prompt window with elevated user rights (Run as Administrator). On the Server Core installation options of Windows Server 2012 R2 or Windows Server 2012 or Windows Server 2008 R2 SP1, Command Prompt opens with elevated user rights by default.
  2. Change directories to the folder into which you have downloaded or copied the WMF 5.0 installation package.
  3. Run one of the following commands:
    • On computers that are running Windows Server 2012 R2 or Windows 8.1 x64, run W2K12R2-KB3094174-x64.msu /quiet.
    • On computers that are running Windows Server 2012, run W2K12-KB3094175-x64.msu /quiet.
    • On computers that are running Windows Server 2008 R2 SP1 or Windows 7 SP1 x64, run W2K8R2-KB3094176-x64.msu /quiet.
    • On computers that are running Windows 8.1 x86, run Win8.1-KB3094174-x86.msu /quiet.
    • On computers that are running Windows 7 SP1 x86, run Win7-KB3094176-x86.msu /quiet.

Additional Installation Notes for Windows Server 2008 and Windows 7:

Ensure following prerequisites have been met:

  • Latest service pack is installed.
  • WMF 4.0 is installed

WinRM Dependency: Windows PowerShell Desired State Configuration (DSC) depends on WinRM. WinRM is not enabled by default on Windows Server 2008 R2 and Windows 7. To enable WinRM, in a Windows PowerShell elevated session, run Set-WSManQuickConfig.

*************************************************************************************************

Follow me on Twitter (@Hoorge) and join Tech Konnect on Facebook to stay current on technology related matters.

Please like & share: