mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-27 16:23:36 +00:00
Merge branch 'master' of https://cpubwin.visualstudio.com/_git/it-client into win10soffer
This commit is contained in:
Celeste de Guzman
@ -23,6 +23,7 @@ This topic lists new and updated topics in the [Surface Hub Admin Guide]( surfac
|
||||
| [Windows updates](manage-windows-updates-for-surface-hub.md) | Changed deferral recommendations for Windows Updates |
|
||||
| [Set up and use Whiteboard to Whiteboard collaboration](whiteboard-collaboration.md) | Added Whiteboard URLs to prerequisites |
|
||||
| [Hybrid deployment](hybrid-deployment-surface-hub-device-accounts.md#skype-for-business-online) | Updated the Skype for Business Online requirements |
|
||||
| [Prepare your environment for Surface Hub](prepare-your-environment-for-surface-hub.md) | Added that Surface Hub supports 802.1X using PEAP-MSCHAPv2 |
|
||||
|
||||
## June 2017
|
||||
|
||||
|
||||
@ -9,7 +9,7 @@ ms.sitesec: library
|
||||
ms.pagetype: surfacehub
|
||||
author: jdeckerms
|
||||
ms.author: jdecker
|
||||
ms.date: 06/19/2017
|
||||
ms.date: 07/27/2017
|
||||
ms.localizationpriority: medium
|
||||
---
|
||||
|
||||
@ -23,13 +23,13 @@ This section contains an overview of setup dependencies and the setup process. R
|
||||
Review these dependencies to make sure Surface Hub features will work in your IT infrastructure.
|
||||
|
||||
| Dependency | Purpose |
|
||||
|-------------------------------------------------------|-------------------------------------------------------|
|
||||
|-------------|------------------|
|
||||
| Active Directory or Azure Active Directory (Azure AD) | <p>The Surface Hub's uses an Active Directory or Azure AD account (called a **device account**) to access Exchange and Skype for Business services. The Surface Hub must be able to connect to your Active Directory domain controller or to your Azure AD tenant in order to validate the device account’s credentials, as well as to access information like the device account’s display name, alias, Exchange server, and Session Initiation Protocol (SIP) address.</p>You can also domain join or Azure AD join your Surface Hub to allow a group of authorized users to configure settings on the Surface Hub. |
|
||||
| Exchange (Exchange 2013 or later, or Exchange Online) and Exchange ActiveSync | <p>Exchange is used for enabling mail and calendar features, and also lets people who use the device send meeting requests to the Surface Hub, enabling one-touch meeting join.</p>ActiveSync is used to sync the device account’s calendar and mail to the Surface Hub. If the device cannot use ActiveSync, it will not show meetings on the welcome screen, and joining meetings and emailing whiteboards will not be enabled. |
|
||||
| Skype for Business (Lync Server 2013 or later, or Skype for Business Online) | Skype for Business is used for various conferencing features, like video calls, instant messaging, and screen sharing.</br></br>If screen sharing on a Surface Hub fails and the error message **An error occurred during the screen presentation** is displayed, see [Video Based Screen Sharing not working on Surface Hub](https://support.microsoft.com/help/3179272/video-based-screen-sharing-not-working-on-surface-hub) for help. |
|
||||
| Mobile device management (MDM) solution (Microsoft Intune, System Center Configuration Manager, or supported third-party MDM provider) | If you want to apply settings and install apps remotely, and to multiple devices at a time, you must set up a MDM solution and enroll the device to that solution. See [Manage settings with an MDM provider](manage-settings-with-mdm-for-surface-hub.md) for details. |
|
||||
| Microsoft Operations Managmement Suite (OMS) | OMS is used to monitor the health of Surface Hub devices. See [Monitor your Surface Hub](monitor-surface-hub.md) for details. |
|
||||
| Network and Internet access | In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred. 802.1x Authentication is supported for both wired and wireless connections.</br></br>**802.1x authentication:** In Windows 10, version 1703, 802.1x authentication for wired and wireless connections is enabled by default in Surface Hub. If your organization doesn't use 802.1x authentication, there is no configuration required and Surface Hub will continue to function as normal. If you use 802.1x authentication, you must ensure that the authentication certification is installed on Surface Hub. You can deliver the certificate to Surface Hub using the [ClientCertificateInstall CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/clientcertificateinstall-csp) in MDM, or you can [create a provisioning package](provisioning-packages-for-surface-hub.md) and install it during first run or through the Settings app. After the certificate is applied to Surface Hub, 802.1x authentication will start working automatically.</br></br>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</br></br>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. Proxy credentials are stored across Surface Hub sessions and only need to be set once. |
|
||||
| Network and Internet access | In order to function properly, the Surface Hub should have access to a wired or wireless network. Overall, a wired connection is preferred. 802.1X Authentication is supported for both wired and wireless connections.</br></br></br>**802.1X authentication:** In Windows 10, version 1703, 802.1X authentication for wired and wireless connections is enabled by default in Surface Hub. If your organization doesn't use 802.1X authentication, there is no configuration required and Surface Hub will continue to function as normal. If you use 802.1X authentication, you must ensure that the authentication certification is installed on Surface Hub. You can deliver the certificate to Surface Hub using the [ClientCertificateInstall CSP](https://msdn.microsoft.com/windows/hardware/commercialize/customize/mdm/clientcertificateinstall-csp) in MDM, or you can [create a provisioning package](provisioning-packages-for-surface-hub.md) and install it during first run or through the Settings app. After the certificate is applied to Surface Hub, 802.1X authentication will start working automatically.</br>**Note:** Surface Hub supports 802.1X using PEAP-MSCHAPv2. We currently do not support additional EAP methods such as 802.1X using PEAP-TLS or PEAP-EAP-TLS.</br></br>**Dynamic IP:** The Surface Hub cannot be configured to use a static IP. It must use DHCP to assign an IP address.</br></br>**Proxy servers:** If your topology requires a connection to a proxy server to reach Internet services, then you can configure it during first run, or in Settings. Proxy credentials are stored across Surface Hub sessions and only need to be set once. |
|
||||
|
||||
Additionally, note that Surface Hub requires the following open ports:
|
||||
- HTTPS: 443
|
||||
|
||||
@ -52,8 +52,15 @@ You can watch the descriptive audio version here: [Microsoft Education: Configur
|
||||
|
||||
Your Microsoft Store for Education account is now linked to Intune for Education so let's set that up next.
|
||||
|
||||
<!--
|
||||
> [!div class="nextstepaction"]
|
||||
> [Use Intune for Education to manage groups, apps, and settings](use-intune-for-education.md)
|
||||
-->
|
||||
|
||||
> [!div class="step-by-step"]
|
||||
[<< Enable Microsoft Teams for your school](enable-microsoft-teams.md)
|
||||
[Use Intune for Education to manage groups, apps, and settings >>](use-intune-for-education.md)
|
||||
|
||||
|
||||
## Related topic
|
||||
[Get started: Deploy and manage a full cloud IT solution with Microsoft Education](get-started-with-microsoft-education.md)
|
||||
@ -46,8 +46,14 @@ To get started, IT administrators need to use the Office 365 Admin Center to ena
|
||||
|
||||
You can find more info about how to control which users in your school can use Microsoft Teams, turn off group creation, configure tenant-level settings, and more by reading the *Guide for IT admins* getting started guide in the <a href="https://aka.ms/MeetTeamsEdu" target="_blank">Meet Microsoft Teams</a> page.
|
||||
|
||||
<!--
|
||||
> [!div class="nextstepaction"]
|
||||
> [Configure Microsoft Store for Education](configure-microsoft-store-for-education.md)
|
||||
-->
|
||||
|
||||
> [!div class="step-by-step"]
|
||||
[<< Use School Data Sync to import student data](use-school-data-sync.md)
|
||||
[Configure Microsoft Store for Education >>](configure-microsoft-store-for-education.md)
|
||||
|
||||
|
||||
## Related topic
|
||||
|
||||
@ -142,7 +142,7 @@ After your cloud infrastructure is set up and you have a device management strat
|
||||
See <a href="https://support.office.com/en-us/article/Add-users-to-Office-365-for-business-435ccec3-09dd-4587-9ebd-2f3cad6bc2bc" target="_blank">Add users to Office 365</a> to learn more. Once you're done adding new users, go to the <a href="https://intuneeducation.portal.azure.com/" target="_blank">Intune for Education console</a> and verify that the same users were added to the Intune for Education groups as well.
|
||||
|
||||
## Connect other devices to your cloud infrastructure
|
||||
Adding a new device to your cloud-based tenant is easy. For new devices, you can follow the steps in [6. Set up Windows 10 devices](#6-set-up-windows-10-devices). For other devices, such as those personally-owned by teachers who need to connect to the school network to access work or school resources (BYOD), you can follow the steps in this section to get these devices connected.
|
||||
Adding a new device to your cloud-based tenant is easy. For new devices, you can follow the steps in [Set up Windows 10 education devices](set-up-windows-10-education-devices.md). For other devices, such as those personally-owned by teachers who need to connect to the school network to access work or school resources (BYOD), you can follow the steps in this section to get these devices connected.
|
||||
|
||||
> [!NOTE]
|
||||
> These steps enable users to get access to the organization's resources, but it also gives the organization some control over the device.
|
||||
@ -169,7 +169,7 @@ Adding a new device to your cloud-based tenant is easy. For new devices, you can
|
||||
|
||||
|
||||
|
||||
6. You can confirm that the new device and user are showing up as Intune for Education-managed by going to the Intune for Education management portal and following the steps in [6.3 Verify the device is Azure AD joined](#63-verify-the-device-is-azure-ad-joined).
|
||||
6. You can confirm that the new device and user are showing up as Intune for Education-managed by going to the Intune for Education management portal and following the steps in [Verify the device is Azure AD joined](#verify-the-device-is-azure-ad-joined).
|
||||
|
||||
It may take several minutes before the new device shows up so check again later.
|
||||
|
||||
|
||||
@ -45,8 +45,9 @@ You can watch the descriptive audio version here: [Microsoft Education: Set up a
|
||||
|
||||
As part of setting up a basic cloud infrastructure, you don't need to complete the rest of the Office 365 for Education setup so we will skip the rest of setup for now and start importing school data. You can pick up where you left off with Office 365 for Education setup once you've completed the rest of the steps in the walkthrough. See *Complete Office 365 for Education setup* in [Finish Windows 10 device setup and other tasks](finish-setup-and-other-tasks.md) for info.
|
||||
|
||||
> [!div class="nextstepaction"]
|
||||
> [Use School Data Sync to import student data](use-school-data-sync.md)
|
||||
> [!div class="step-by-step"]
|
||||
[<< Get started: Deploy and manage a full cloud IT solution with Microsoft Education](get-started-with-microsoft-education.md)
|
||||
[Use School Data Sync to import student data >>](use-school-data-sync.md)
|
||||
|
||||
|
||||
## Related topic
|
||||
|
||||
@ -21,9 +21,16 @@ To set up new Windows 10 devices and enroll them to your education tenant, choos
|
||||
- **Option 1: [Use the Set up School PCs app](https://docs.microsoft.com/en-us/education/windows/use-set-up-school-pcs-app)** - You can use the app to create a setup file that you can use to quickly set up one or more Windows 10 devices.
|
||||
- **Option 2: [Go through Windows OOBE and join the device to Azure AD](set-up-windows-education-devices.md)** - You can go through a typical Windows 10 device setup or first-run experience to configure your device.
|
||||
|
||||
|
||||
<!--
|
||||
> [!div class="nextstepaction"]
|
||||
> [Finish setup and other tasks](finish-setup-and-other-tasks.md)
|
||||
-->
|
||||
|
||||
|
||||
> [!div class="step-by-step"]
|
||||
[<< Use Intune for Education to manage groups, apps, and settings](use-intune-for-education.md)
|
||||
[Finish setup and other tasks >>](finish-setup-and-other-tasks.md)
|
||||
|
||||
|
||||
|
||||
## Related topic
|
||||
|
||||
@ -20,9 +20,7 @@ If you are setting up a Windows 10 device invidividually, and network bandwidth
|
||||
You can watch the video to see how this is done, or follow the step-by-step guide. </br>
|
||||
|
||||
<center><iframe src="https://www.youtube.com/embed/nADWqBYvqXk" width="960" height="540" allowFullScreen frameBorder="0"></iframe></center>
|
||||
<!--
|
||||
<div style="position:relative;height:0;padding-bottom:56.25%"><iframe src="https://www.youtube.com/embed/nADWqBYvqXk?ecver=2" width="640" height="360" frameborder="0" style="position:absolute;width:100%;height:100%;left:0" allowfullscreen></iframe></div>
|
||||
-->
|
||||
|
||||
You can watch the descriptive audio version here: [Microsoft Education: Set up a new Windows 10 education devices using the Windows setup experience (DA)](https://www.youtube.com/watch?v=_UtS1Cz2Pno)
|
||||
|
||||
## To set up Windows 10 devices using OOBE
|
||||
|
||||
@ -206,8 +206,15 @@ Now that you've bought the apps, use Intune for Education to specify the group t
|
||||
|
||||
You're now done assigning apps to all users in your tenant. It's time to set up your Windows 10 device(s) and check that your cloud infrastructure is correctly set up and your apps are being pushed to your devices from the cloud.
|
||||
|
||||
<!--
|
||||
> [!div class="nextstepaction"]
|
||||
> [Set up Windows 10 devices](set-up-windows-10-education-devices.md)
|
||||
-->
|
||||
|
||||
> [!div class="step-by-step"]
|
||||
[<< Configure Microsoft Store for Education](configure-microsoft-store-for-education.md)
|
||||
[Set up Windows 10 education devices >>](set-up-windows-10-education-devices.md)
|
||||
|
||||
|
||||
|
||||
## Related topic
|
||||
|
||||
@ -170,9 +170,14 @@ To learn more about the CSV files that are required and the info you need to inc
|
||||
|
||||
That's it for importing sample school data using SDS.
|
||||
|
||||
<!--
|
||||
> [!div class="nextstepaction"]
|
||||
> [Enable Microsoft Teams for your school](enable-microsoft-teams.md)
|
||||
-->
|
||||
|
||||
> [!div class="step-by-step"]
|
||||
[<< Set up an Office 365 education tenant](set-up-office365-edu-tenant.md)
|
||||
[Enable Microsoft Teams for your school >>](enable-microsoft-teams.md)
|
||||
|
||||
## Related topic
|
||||
[Get started: Deploy and manage a full cloud IT solution with Microsoft Education](get-started-with-microsoft-education.md)
|
||||
@ -9,6 +9,7 @@ ms.pagetype: edu
|
||||
ms.localizationpriority: high
|
||||
author: CelesteDG
|
||||
ms.author: celested
|
||||
ms.date: 07/28/2017
|
||||
---
|
||||
|
||||
# Take a Test app technical reference
|
||||
@ -74,6 +75,26 @@ When Take a Test is running, the following functionality is available to student
|
||||
- Ctrl+Alt+Del
|
||||
- Alt+F4 (Take a Test will restart if the student is using a dedicated test account)
|
||||
|
||||
## Policies
|
||||
|
||||
If the lock screen is disabled, Take aTest will not launch above lock. Be aware that if you set the following Group Policy, this breaks activation of Take a Test above lock.
|
||||
|
||||
**Group Policy path:** Computer Configuration\Administrative Templates\Control Panel\Personalization\ <br />
|
||||
**Group Policy name:** Do not display the lock screen <br />
|
||||
**ADML:** %SDXROOT%\shell\policies\ControlPanelDisplay.adml <br />
|
||||
**ADMX:** %SDXROOT%\shell\policies\ControlPanelDisplay.admx <br />
|
||||
|
||||
```
|
||||
<policy name="CPL_Personalization_NoLockScreen" class="Machine"
|
||||
displayName="$(string.CPL_Personalization_NoLockScreen)"
|
||||
explainText="$(string.CPL_Personalization_NoLockScreen_Help)"
|
||||
key="Software\Policies\Microsoft\Windows\Personalization"
|
||||
valueName="NoLockScreen">
|
||||
<parentCategory ref="Personalization" />
|
||||
<supportedOn ref="windows:SUPPORTED_Windows8" />
|
||||
</policy>
|
||||
```
|
||||
|
||||
|
||||
## Learn more
|
||||
|
||||
|
||||
@ -17,7 +17,7 @@ To automate the steps provided in [Get started with Upgrade Readiness](upgrade-r
|
||||
|
||||
For detailed information about using the Upgrade Readiness (also known as upgrade analytics) deployment script, see the [Upgrade Analytics blog](https://blogs.technet.microsoft.com/upgradeanalytics/2016/09/20/new-version-of-the-upgrade-analytics-deployment-script-available/).
|
||||
|
||||
> The following guidance applies to version 11.11.16 or later of the Upgrade Readiness deployment script. If you are using an older version, please download the latest from the [Download Center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409).
|
||||
> The following guidance applies to version 11.11.16 or later of the Upgrade Readiness deployment script. If you are using an older version, download the latest from the [Download Center](https://go.microsoft.com/fwlink/?LinkID=822966&clcid=0x409).
|
||||
|
||||
The Upgrade Readiness deployment script does the following:
|
||||
|
||||
@ -132,11 +132,12 @@ The deployment script displays the following exit codes to let you know if it wa
|
||||
</tr>
|
||||
<tr>
|
||||
<td>13 - Can’t connect to Microsoft - setting. </td>
|
||||
<td>An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).</td>
|
||||
<td>An error occurred connecting to https://settings.data.microsoft.com/qos. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing). Verify that the required endpoints are whitelisted correctly. See Whitelist select endpoints for more details.
|
||||
14 </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>14 - Can’t connect to Microsoft - compatexchange.</td>
|
||||
<td>An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc . This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).</td>
|
||||
<td>An error occurred connecting to https://compatexchange1.trafficmanager.net/CompatibilityExchangeService.svc. This error will prevent the collected data from being sent to Upgrade Readiness. To resolve this issue, verify that the required endpoints are correctly whitelisted. For more information, see [Enable data sharing](https://technet.microsoft.com/en-us/itpro/windows/deploy/upgrade-readiness-get-started#enable-data-sharing).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>15 - Function CheckVortexConnectivity failed with an unexpected exception.</td>
|
||||
@ -196,10 +197,10 @@ The deployment script displays the following exit codes to let you know if it wa
|
||||
</tr>
|
||||
<tr>
|
||||
<td>29 - Connectivity check failed for proxy authentication. </td>
|
||||
<td>Install the cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting.
|
||||
<td>Instal cumulative updates on the computer and enable the **DisableEnterpriseAuthProxy** authentication proxy setting.
|
||||
<BR>The **DisableEnterpriseAuthProxy** setting is enabled by default for Windows 7.
|
||||
<BR>For Windows 8.1 computers, set the **DisableEnterpriseAuthProxy** setting to **0** (not disabled).
|
||||
<BR>For more information on authentication proxy support, see [this blog post](https://go.microsoft.com/fwlink/?linkid=838688).</td>
|
||||
<BR>For more information on authentication proxy support, see [Authentication proxy support added in new version (12.28.16) of the Upgrade Readiness deployment script](https://go.microsoft.com/fwlink/?linkid=838688).</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>30 - Connectivity check failed. Registry key property **DisableEnterpriseAuthProxy** is not enabled.</td>
|
||||
@ -217,7 +218,7 @@ The deployment script displays the following exit codes to let you know if it wa
|
||||
</tr>
|
||||
<tr>
|
||||
<td>33 - **CompatTelRunner.exe** exited with an exit code </td>
|
||||
<td>**CompatTelRunner.exe** runs the appraise task on the machine. If it fails, it will provide a specific exit code. The script will return exit code 33 when **CompatTelRunner.exe** itself exits with an exit code. Please check the logs for more details.</td>
|
||||
<td>**CompatTelRunner.exe** runs the appraise task on the machine. If it fails, it will provide a specific exit code. The script will return exit code 33 when **CompatTelRunner.exe** itself exits with an exit code. Check the logs for more details. Also see the **Note** following this table for additional steps to follow.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>34 - Function **CheckProxySettings** failed with an unexpected exception. </td>
|
||||
@ -280,5 +281,47 @@ The deployment script displays the following exit codes to let you know if it wa
|
||||
<td>48 - **CommercialID** mentioned in RunConfig.bat should be a GUID.</td>
|
||||
<td>**CommercialID** is mentioned in RunConfig.bat, but it is not a GUID. Copy the commercialID from your workspace. To find the commercialID, in the OMS portal click **Upgrade Readiness > Settings**.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>50 - Diagtrack Service is not running.</td>
|
||||
<td>Diagtrack Service is required to send data to Microsoft. Enable and run the 'Connected User Experiences and Telemetry' service. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>51 - RunCensus failed with an unexpected exception.</td>
|
||||
<td>RunCensus explitly runs the process used to collect device information. The method failed with an unexpected exception. Check the ExceptionHResult and ExceptionMessage for more details. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>52 - DeviceCensus.exe not found on a Windows 10 machine.</td>
|
||||
<td>On computers running Windows 10, the process devicecensus.exe should be present in the <windows directory>\system32 folder. Error code 52 is returned if the process was not found. Ensure that it exists at the specified location. </td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>53 - There is a different CommercialID present at the GPO path: "HKLM:\SOFTWARE\Policies\Microsoft\Windows\DataCollection". This will take precedence over the CommercialID provided in the script.</td>
|
||||
<td>Provide the correct CommercialID at the GPO location. </td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
>[!NOTE]
|
||||
>**Additional steps to follow if you receive exit code 33**
|
||||
|
||||
>Check the exit code for any of these messages:
|
||||
>
|
||||
>- CompatTelRunner.exe exited with last error code: 0x800703F1
|
||||
>- CompatTelRunner.exe exited with last error code: 0x80070005
|
||||
>- CompatTelRunner.exe exited with last error code: 0x80080005
|
||||
>
|
||||
>
|
||||
>If the exit code includes any of those messages, then run these commands from an elevated command prompt:
|
||||
>
|
||||
>1. Net stop diagtrack
|
||||
>2. Net stop pcasvc
|
||||
>3. Net stop dps
|
||||
>4. Del %windir%\appcompat\programs\amcache.hve
|
||||
>5. reg delete "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags" /v AmiHivePermissionsCorrect /f
|
||||
>6. reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags" /v LogFlags /t REG_DWORD /d 4 /f
|
||||
>7. Net start diagtrack
|
||||
>8. Net start pcasvc
|
||||
>9. Net start dps
|
||||
>
|
||||
>Then run the Enterprise Config script (RunConfig.bat) again.
|
||||
>
|
||||
>If the script still fails, then send mail to **uasupport@microsoft.com** including log files from the RunConfig.bat script. These log files are stored on the drive that is specified in the RunConfig.bat file. By default this is set to **%SystemDrive%\UADiagnostics**. The log file is named with the format **UA_yyyy_mm_dd_hh_mm_ss_machineID.txt**. There will be some additional logs generated under your **<system drive>\Windows\Temp** directory with the names similar to **AslLog_....txt**. You should send those logs as well.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user