#note
MAPI over HTTP will be the sole connection protocol used by Exchange Online after October 31, 2017. All Outlook clients have to be updated to a version that supports MAPI over HTTP by that date.
31 lug 2017
21 lug 2017
Office build numbers
Office build numbers
Office 2016
Build Number (MSO) | KB | Description |
---|---|---|
16.0.4229.1024 | Office 2016 RTM | |
16.0.4266.1003 | Office 2016 RTM (Volume license) |
Office 2013
Build Number (MSO) | KB | Description |
---|---|---|
15.0.4420.1017 | Office 2013 RTM | |
15.0.4569.1506 | KB2850036 | Office 2013 SP1 32-bit 64-bit |
Office 2010
Build Number (MSO) | KB | Description |
---|---|---|
14.0.4760.1000 | Office 2010 RTM | |
14.0.6023.1000 | KB2510690 | Office 2010 SP1 32-bit 64-bit |
14.0.7015.1000 | KB2687521 | Office 2010 SP2 32-bit 64-bit |
Office 2007
Build Number (MSO) | KB | Description |
---|---|---|
12.0.4518.1014 | Office 2007 RTM | |
12.0.6213.1000 | KB936982 | Office 2007 SP1 |
12.0.6425.1000 | KB953195 | Office 2007 SP2 |
12.0.6607.1000 | KB2526086 | Office 2007 SP3 |
Office 2003
Build Number (MSO) | KB | Description |
---|---|---|
11.0.5614.0 | Office 2003 RTM | |
11.0.6361.0 | KB842532 | Office 2003 SP1 |
11.0.7969.0 | KB887616 | Office 2003 SP2 |
11.0.8173.0 | KB923618 | Office 2003 SP3 |
19 lug 2017
Windows Server 2008 R2: Verify WinRM 3.0 service is installed, running, and required firewall ports are open
#Note
Verify WinRM 3.0 service is installed, running, and required firewall ports are open
#Product affected
Windows Server 2008 R2
#Issue
Management from 2012 Server Manager return the error:
Windows Server 2008 R2: Verify WinRM 3.0 service is installed, running, and required firewall ports are open
#Resolution
To narrow down this issue, would you check if have you installed both Windows Management Framework 3.x and .NET Framework 4.x in Windows Server 2008 R2 SP1? If not, get the appropriate .msu from the following link and install them on Windows Server 2008 R2 SP1:
Windows Management Framework 3.0
http://www.microsoft.com/en-us/download/details.aspx?id=34595
Microsoft .NET Framework 4.5.1 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows Server 2008 SP2 Windows Server 2008 R2 SP1 and Windows Server 2012
http://www.microsoft.com/en-us/download/details.aspx?id=40779
After that, run winrm qc from PowerShell or cmd prompt and check is it persists.
If the issue persists
Running winrm id to see if WinRM was all installed correctly on each server.
Use netsh advfirewall firewall show rule name="Windows Remote Management (HTTP-In)" to verify that the firewall rules had port 5985 open on our current NLA profile.
Use netstat -a -b to confirm that if there is any local process that was actually bound to port 5985.
Finally, please run winrm enumerate winrm/config/listener to confirm that if WinRM is actually listening on the port.
Verify WinRM 3.0 service is installed, running, and required firewall ports are open
#Product affected
Windows Server 2008 R2
#Issue
Management from 2012 Server Manager return the error:
Windows Server 2008 R2: Verify WinRM 3.0 service is installed, running, and required firewall ports are open
#Resolution
To narrow down this issue, would you check if have you installed both Windows Management Framework 3.x and .NET Framework 4.x in Windows Server 2008 R2 SP1? If not, get the appropriate .msu from the following link and install them on Windows Server 2008 R2 SP1:
Windows Management Framework 3.0
http://www.microsoft.com/en-us/download/details.aspx?id=34595
Microsoft .NET Framework 4.5.1 (Offline Installer) for Windows Vista SP2, Windows 7 SP1, Windows 8, Windows Server 2008 SP2 Windows Server 2008 R2 SP1 and Windows Server 2012
http://www.microsoft.com/en-us/download/details.aspx?id=40779
After that, run winrm qc from PowerShell or cmd prompt and check is it persists.
If the issue persists
Running winrm id to see if WinRM was all installed correctly on each server.
Use netsh advfirewall firewall show rule name="Windows Remote Management (HTTP-In)" to verify that the firewall rules had port 5985 open on our current NLA profile.
Use netstat -a -b to confirm that if there is any local process that was actually bound to port 5985.
Finally, please run winrm enumerate winrm/config/listener to confirm that if WinRM is actually listening on the port.
17 lug 2017
RDS 2012 R2 error: “Licensing mode for the Remote Desktop Session Host is not configured.
#Note
RDS 2012 R2 Error: “Licensing mode for the Remote Desktop Session Host is not configured.
#Product aftected
Windows Server 2012 - Windows Server 2012 R2
#Issue
The error description reads (on RD Licensing Diagnoser): “Licensing mode for the Remote Desktop Session Host is not configured.”
#Solution
To fix the problem, run the following commands in powershell to set the licensing server properly on the rd session host using the WMI CIM provider:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj. SetSpecifiedLicenseServerList("licenseserver.domain.local")
and then, go into the registry and set the licensing mode:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core\LicensingMode
You need to change the DWORD to 2 for Per Device or 4 for Per User
Reboot
RDS 2012 R2 Error: “Licensing mode for the Remote Desktop Session Host is not configured.
#Product aftected
Windows Server 2012 - Windows Server 2012 R2
#Issue
The error description reads (on RD Licensing Diagnoser): “Licensing mode for the Remote Desktop Session Host is not configured.”
#Solution
To fix the problem, run the following commands in powershell to set the licensing server properly on the rd session host using the WMI CIM provider:
$obj = gwmi -namespace "Root/CIMV2/TerminalServices" Win32_TerminalServiceSetting
$obj. SetSpecifiedLicenseServerList("licenseserver.domain.local")
and then, go into the registry and set the licensing mode:
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\Licensing Core\LicensingMode
You need to change the DWORD to 2 for Per Device or 4 for Per User
Reboot
Iscriviti a:
Post (Atom)