Release Notes for Windows Intune
Updated: November 1, 2013
Applies To: Windows Intune
Windows Intune is an integrated, cloud-based client management solution that provides tools, reports, and upgrade licenses to the latest version of Windows, and helps keep your computers up-to-date and secure. In addition, Windows Intune lets you manage mobile devices on the network either through Exchange ActiveSync or directly through Windows Intune. The following release notes describe important information and known issues in Windows Intune.
Installation, Deployment, and Enrollment
Windows Intune Exchange Connector
Installation, Deployment, and Enrollment
The following issues can occur during client software deployment, client device preparation for Windows Intune, or device enrollment.
When you use Multi-Factor Authentication and enroll a device with Windows Intune, you receive the error “This request couldn’t complete”
Issue: The error This request couldn’t complete is returned when you attempt to enroll a Windows RT or Windows Phone device to Windows Intune, and the Windows Azure subscription in use with Windows Intune is configured to use Windows Azure Multi-Factor Authentication. The current release of Windows Intune does not support Windows Azure Multi-Factor Authentication and fails to enroll applicable devices when Windows Azure Multi-Factor Authentication is enabled. Windows Azure Multi-Factor Authentication is supported by some services that use Windows Azure and that might share the Azure subscription with Windows Intune, such as Office 365. When Windows Azure Multi-Factor Authentication is enabled for Windows Azure, it is active for all services that share the subscription. For more information about Multi-Factor Authentication, see Securing access to cloud services - Information for Administrators.
Workaround: Turn off Windows Azure Multi-Factor Authentication for the Windows Azure subscription you use with Windows Intune.
When you enroll a Windows 8.1 device that must authenticate to a proxy server, the enrollment process fails with no visible indication as to the cause of the failure
Issue: When you enroll a Windows 8.1 device and the device must authenticate to a proxy server during the enrollment process, the enrollment fails if the device has not cached the proxy server credentials. When the credentials for the proxy server are not cached on the device, the enrolment process must wait for the user to enter the credentials. However, the prompt to provide the proxy server credentials does not display during the enrollment process. The result is that the enrollment process cannot authenticate to the proxy server and there is no visible indication of this failure presented to the user.
Workaround: For Windows 8.1 devices that must enroll on a network that requires use of an authenticated proxy server, configure and save the credentials for the proxy server prior to enrollment of the device. To configure and save the credentials on a Windows 8.1 device:
On the Windows 8.1 device, open Internet Explorer.
When prompted for the proxy server credentials, enter the credentials and then select the option Remember my credentials.
Enroll the device.
When you specify policies or applications to Windows Intune groups, devices that are members of the Ungrouped Devices group do not receive policy or applications
Issue: Windows Intune does not correctly apply policies and applications to a device that remains in the Ungrouped Devices group. This occurs even when the policy or application is specified to a group other than the Ungrouped Devices group. There are no errors displayed for this problem.
Workaround: Remove the devices from the Ungrouped Devices group, and ensure the devices remain as members of at least one other group that receives policy and applications.
Windows Intune Exchange Connector
The following issues can occur with the Windows Intune Exchange Connectors.
Every two hours the Exchange Connector logs a recurring error in the svclog
Issue: When you use the On-Premises Connector for Exchange with Windows Intune, approximately every two hours the following recurring error is logged in the svclog on the computer that runs the Exchange Connector service:
'System.Management.Automation.Remoting.PSRemotingTransportException' exception was thrown. Error code is '31'. FullyQualifiedErrorId 'System.Management.Automation.Remoting.PSRemotingDataStructureException' Error record 'Connecting to remote server failed with the following error message : Fail to create runspace because you have exceeded your budget to create runspace.
This error does not represent an operational issue for the Connector, and can be ignored.
Workaround: If the recurrence of this error is a cosmetic burden on the svclog, use the Service to Service Connector instead of the On-Premises Connector.
The following issues can occur with Windows Intune software distribution.
Software publishing feature requires additional registry key values to exist in order to work with Windows XP SP3
Issue: If you try to publish software on a computer that is running Windows XP SP3, you must change the registry for software publishing to work. The software publishing process uses the Microsoft Enhanced RSA and AES Cryptographic Provider. On Windows XP SP3, the name of the registry key that contains information about this provider has the string "(Prototype)" appended to it. The code that looks up the provider requires that the registry key not contain the string "(Prototype)."
Workaround: Create a new registry key that registers the cryptographic provider by using the expected name. The correct registry entries are as follows.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Defaults\Provider\Microsoft Enhanced RSA and AES Cryptographic Provider] "Image Path"="rsaenh.dll" "Type"=dword:00000018 "SigInFile"=dword:00000000
|Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.|
The following are known issues with alerts in this release of Windows Intune.
Remote assistance is not available on computers that run Windows 8 or Windows 8.1
Issue: In this release, the remote assistance feature is not available on computers that run Windows 8 or Windows 8.1.
Alert notifications for recipients that are automatically added may not work
Issue: If a recipient is automatically added to an alert notification, they may not always receive a notification.
Workaround: To make sure that recipients will receive message notification, you should manually add recipients to alert notifications.
This document is provided "as-is". Information and views expressed in this document, including URL and other Internet website references, may change without notice.
This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes.
© 2012 Microsoft Corporation. All rights reserved.
Microsoft, ActiveX, BranchCache, Excel, Forefront, IntelliMirror, Internet Explorer, MS-DOS, Silverlight, SpyNet, Windows, Windows Intune, Windows Live, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.