Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. PowerShell commands do not return results on an RRAS server in Windows Server 2012 R2

PowerShell commands do not return results on an RRAS server in Windows Server 2012 R2

View products that this article applies to.

This article describes an issue that occurs on a Routing and Remote Access service (RRAS) server that is running Windows Server 2012 R2. A hotfix and an update rollup is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

Assume that you have a site-to-site virtual private network (VPN) deployment on a Windows 2012 R2-based RRAS server. In this scenario, a set of Windows PowerShell commands may not return results, and several powershell.exe processes are stuck on the server.

Note When this issue occurs, you may lose the ability to monitor the functionality of the Microsoft Azure Virtual Network service if you use a site-to-site VPN in a Microsoft Azure Virtual Network environment.

↑ Back to the top

Resolution

To resolve this issue, we have released an update rollup and a hotfix for Windows Server 2012 R2.

Shall I choose hotfix or update rollup?
The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.

Get the update rollup for Windows Server 2012 R2

To resolve this issue, install the update rollup that is dated November 2014.

Get the November 2014 update rollup for Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2

Get the hotfix for Windows Server 2012 R2

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this update, you must have update 2919355 installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

↑ Back to the top

More Information

File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Mprddm.dll6.3.9600.17396372,73608-Oct-201406:59x64

Additional file information

Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
File propertyValue
File nameAmd64_4262cc254daae703ba29ddcb35728f24_31bf3856ad364e35_6.3.9600.17397_none_968afd6628249b80.manifest
File versionNot applicable
File size699
Date (UTC)09-Oct-2014
Time (UTC)18:48
PlatformNot applicable
File nameAmd64_8b57d361dd3beb282b4ff13f20b6ebfb_31bf3856ad364e35_6.3.9600.17397_none_cd017076f7efe163.manifest
File versionNot applicable
File size701
Date (UTC)09-Oct-2014
Time (UTC)18:48
PlatformNot applicable
File nameAmd64_microsoft-windows-rasmprddm_31bf3856ad364e35_6.3.9600.17397_none_89cccb59a194d3a1.manifest
File versionNot applicable
File size24,889
Date (UTC)09-Oct-2014
Time (UTC)05:31
PlatformNot applicable
File nameX86_microsoft-windows-rasmprddm_31bf3856ad364e35_6.3.9600.17397_none_2dae2fd5e937626b.manifest
File versionNot applicable
File size24,885
Date (UTC)09-Oct-2014
Time (UTC)04:45
PlatformNot applicable

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

References

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 3004541
Revision : 1
Created on : 1/7/2017
Published on : 11/18/2014
Exists online : False
Views : 209