How to survive the "remote connection update problem" in a remote connection environment? Ryo Yamaichi's Microsoft EYE

How to survive the "remote connection update problem" in a remote connection environment? Ryo Yamaichi's Microsoft EYE

Solving business issues by integrating IT and management

What is Business + IT?

Login

New member registration

E-mail newsletter registration

What is Business + IT?

  • Sales Strategy
  • Cost reduction
  • Organizational reform
  • Production / manufacturing
  • crisis management
  • compliance
  • Energy saving and environmental friendliness
  • By industry / scale
  • Core system
  • Information system
  • Operation management
  • Security
  • network
  • mobile
  • hardware
  • development
  • Related genres

    How to survive the "remote connection update problem" in a remote connection environment?

    Ryo Yamaichi's Microsoft EYE

    Last time, I talked about the schedule of Windows Update in 2022, and mentioned that the update at the beginning of the year requires special attention. Early in the year, it was reported that the December 2021 regular update (B release) could have a significant impact on the stable operation of multiple versions of Windows Server, and an update was provided with a regular exception.

    Freelance writer Ryo Yamaichi

    Freelance writer Ryo Yamaichi

    A technical writer who writes mainly for IT magazines and Web media. He became a freelancer in 2008 after working as a system integrator, editor of an IT magazine, and system administrator of a local mid-sized company. In addition to contributing numerous articles to magazines and web media, he also produces technical documents (white papers) for several IT vendors and covers user cases. Received the Microsoft MVP --Cloud and Datacenter Management (former category: Hyper-V) every year since October 2008. He lives in Hanamaki City, Iwate Prefecture.Major books and translations "Inside Windows 7th Edition" (Translation, Nikkei BP, 2018) "Windows Sysinternals Thorough Explanation Revised New Edition" (Translation, Nikkei BP, 2017) "Windows Server 2016 Technology Introduction Complete Edition" (Nikkei BP, 2016) "Introduction to Windows Server 2012 R2 Technology" (Nikkei BP, 2014) "Introduction to Windows Server 2012 Technology" (Nikkei BP, 2012) "Introduction to Windows Server Virtualization Technology" (Nikkei BP) 2011) "Introduction to Windows Server 2008 R2 Technology" (Nikkei BP, 2009), etc.

    1. Issues affecting Remote Desktop Connection
    2. Command line if remote shell is available
    3. What if I can't connect remotely or start normally?
    4. No worries if prepared

    Issues affecting Remote Desktop Connection

    Microsoft released known issues that may occur in Windows Server 2012 R2, 2016, 2019, and 2022 on January 5, 2021, due to the impact of the December 2021 regular update (B release), on the same day. Has released a fixed exception update for Windows Server 2012 R2 and 2019. The next day, we released an exception update for the remaining versions. The only update that resolves the issue is available as a download from the Microsoft Update Catalog. Take action: Out-of-band update to address a Windows Server issue This issue is that after installing the December 2012 B release, the server becomes unreachable using Remote Desktop Connection, and in some cases the server responds. It causes issues that affect remote and local interactive logon, such as hangs, black screens, and slow performance and sign-in responsiveness. I wasn't affected by this issue in my environment, but if I were, I would have been busy with the New Year holidays. In particular, if you are affected by this issue in Microsoft Azure or another company's cloud environment, Remote Desktop Connection is virtually impossible to deal with. So what should we do in such a case? A fix for this issue is also included in the January 12, 2022 B release. The purpose of this article is not to solve this problem, but to show you how to solve the problem of the remote server that cannot connect to the remote desktop due to the influence of the update, or the update of the local / remote server that does not start normally. That is.

    Command line if remote shell is available

    PowerShell Remoting (Windows standard, need to be enabled) and SSH (Windows 10/11 and Windows Server 2019 or later support and enable OpenSSH clients and servers) for remote servers where remote desktop connection has become impossible. If you have access to a remote shell environment such as (requires configuration and setup), you can download and install updates from the command line. This update is only available as a download from the Microsoft Update Catalog. You can copy the URL from which you downloaded the update from the dialog box that appears when you find the desired update in the Microsoft Update Catalog and click the Download button (Screen 1). For PowerShell Remoting, use the wget (Invoke-WebRequest alias) command to download the MSU file, and then run the wusa.exe command (Windows Update standalone installer) with the / quiet option. When the installation is complete, you will be prompted to restart it with the restart-comptuer command (Screen 2). wget -uri-o wusa.exe. \ /quietrestart-computer If for some reason you cannot install the fix update or the installation fails, the problem update (in this case 2021 12) You can fix the problem by uninstalling (B release of the month). Use the DISM command to uninstall updates using the command line. Run "dism / online / get-packages" to identify the update package name (package ID) by referring to the release type "Security Update", the installation time, and the build number included in the package ID. .. For example, the Windows Server 2022 issue update build number was "20348.405". You can easily find the package name by running: You may find multiple packages, but the ones that start with the package ID "Package_for_RollupFix ~" are the updates you want (others are automatically installed, such as language packs). dism / online / get-packages | findstr 20348.405 After identifying the package name (package ID), run the following command line to uninstall the update and then reboot (Screen 3). dism / online / remove-package / packagename: Package_for_RollupFix ~ 31bf3856ad364e35 ~ amd64 ~~ 20348.405.1.6 restart-computer [Next page] What if remote connection is not possible or does not start normally?

    OS genre topics

    To List

    OS genre IT introduction support information

    To List

    PR

    SB Creative Co., Ltd.

    Business + IT is operated by SB Creative Corp. of SoftBank Group.

    Copyright © SB Creative Corp. All rights reserved.

    By registering as a business + IT member, you can subscribe to member-only content and e-mail newsletters, and invite you to special seminars!

    Registration merit Member registration (free)

    リモート接続環境での「リモート接続の更新プログラム問題」をどう切り抜けるか? 山市良のマイクロソフトEYE