Merge remote-tracking branch 'refs/remotes/origin/master' into live
@ -6,6 +6,7 @@
|
||||
## [Ethernet adapters and Surface deployment](ethernet-adapters-and-surface-device-deployment.md)
|
||||
## [Manage Surface Dock firmware updates](manage-surface-dock-firmware-updates.md)
|
||||
## [Manage Surface driver and firmware updates](manage-surface-pro-3-firmware-updates.md)
|
||||
## [Manage Surface UEFI settings](manage-surface-uefi-settings.md)
|
||||
## [Surface Data Eraser](microsoft-surface-data-eraser.md)
|
||||
## [Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)
|
||||
### [Step by step: Surface Deployment Accelerator](step-by-step-surface-deployment-accelerator.md)
|
||||
|
BIN
devices/surface/images/manage-surface-uefi-fig2.png
Normal file
After Width: | Height: | Size: 20 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig3.png
Normal file
After Width: | Height: | Size: 13 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig4.png
Normal file
After Width: | Height: | Size: 65 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig5.png
Normal file
After Width: | Height: | Size: 57 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig6.png
Normal file
After Width: | Height: | Size: 104 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig7.png
Normal file
After Width: | Height: | Size: 36 KiB |
BIN
devices/surface/images/manage-surface-uefi-fig8.png
Normal file
After Width: | Height: | Size: 45 KiB |
BIN
devices/surface/images/manage-surface-uefi-figure-1.png
Normal file
After Width: | Height: | Size: 74 KiB |
@ -62,18 +62,22 @@ For more information on planning for, deploying, and managing Surface devices in
|
||||
<td><p>Explore the available options to manage firmware and driver updates for Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td><p>[Manage Surface UEFI settings](manage-surface-uefi-settings.md)<p></td>
|
||||
<td><p>Use Surface UEFI settings to enable or disable devices, configure security settings, and adjust Surface device boot settings.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Data Eraser](microsoft-surface-data-eraser.md)</p></td>
|
||||
<td><p>Find out how the Microsoft Surface Data Eraser tool can help you securely wipe data from your Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Surface Deployment Accelerator](microsoft-surface-deployment-accelerator.md)</p></td>
|
||||
<td><p>See how Microsoft Surface Deployment Accelerator provides a quick and simple deployment mechanism for organizations to reimage Surface devices.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<tr class="odd">
|
||||
<td><p>[Surface Diagnostic Toolkit](surface-diagnostic-toolkit.md)</p></td>
|
||||
<td><p>Find out how you can use the Microsoft Surface Diagnostic Toolkit to test the hardware of your Surface device.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<tr class="even">
|
||||
<td><p>[Surface Dock Updater](surface-dock-updater.md)</p></td>
|
||||
<td><p>Get a detailed walkthrough of Microsoft Surface Dock Updater.</p></td>
|
||||
</tr>
|
||||
|
138
devices/surface/manage-surface-uefi-settings.md
Normal file
@ -0,0 +1,138 @@
|
||||
---
|
||||
title: Manage Surface UEFI settings (Surface)
|
||||
description: Use Surface UEFI settings to enable or disable devices or components, configure security settings, and adjust Surface device boot settings.
|
||||
keywords: firmware, security, features, configure, hardware
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
ms.pagetype: devices, surface
|
||||
author: miladCA
|
||||
---
|
||||
|
||||
#Manage Surface UEFI settings
|
||||
|
||||
Current and future generations of Surface devices, including Surface Pro 4 and Surface Book, use a unique UEFI firmware engineered by Microsoft specifically for these devices. This firmware allows for significantly greater control of the device’s operation over firmware versions in earlier generation Surface devices, including the support for touch, mouse, and keyboard operation. By using the Surface UEFI settings you can easily enable or disable internal devices or components, configure security to protect UEFI settings from being changed, and adjust the Surface device boot settings.
|
||||
|
||||
>**Note:** Surface Pro 3, Surface 3, Surface Pro 2, Surface 2, Surface Pro, and Surface do not use the Surface UEFI and instead use firmware provided by third-party manufacturers, such as AMI.
|
||||
|
||||
You can enter the Surface UEFI settings on your Surface device by pressing the **Volume Up** button and the **Power** button simultaneously. Hold the **Volume Up** button until the Surface logo is displayed, which indicates that the device has begun to boot.
|
||||
|
||||
##PC information
|
||||
|
||||
On the **PC information** page, detailed information about your Surface device is provided:
|
||||
|
||||
- **Model** – Your Surface device’s model will be displayed here, such as Surface Book or Surface Pro 4. The exact configuration of your device is not shown, (such as processor, disk size, or memory size).
|
||||
- **UUID** – This Universally Unique Identification number is specific to your device and is used to identify the device during deployment or management.
|
||||
|
||||
- **Serial Number** – This number is used to identify this specific Surface device for asset tagging and support scenarios.
|
||||
- **Asset Tag** – The asset tag is assigned to the Surface device with the [Asset Tag Tool](https://www.microsoft.com/en-us/download/details.aspx?id=44076).
|
||||
|
||||
You will also find detailed information about the firmware of your Surface device. Surface devices have several internal components that each run different versions of firmware. The firmware version of each of the following devices is displayed on the **PC information** page (as shown in Figure 1):
|
||||
|
||||
- System UEFI
|
||||
|
||||
- SAM Controller
|
||||
|
||||
- Intel Management Engine
|
||||
|
||||
- System Embedded Controller
|
||||
|
||||
- Touch Firmware
|
||||
|
||||
*Figure 1. System information and firmware version information*
|
||||
|
||||

|
||||
|
||||
You can find up-to-date information about the latest firmware version for your Surface device in the [Surface Update History](https://www.microsoft.com/surface/en-us/support/install-update-activate/surface-update-history) for your device.
|
||||
|
||||
##Security
|
||||
|
||||
On the **Security** page of Surface UEFI settings, you can set a password to protect UEFI settings. This password must be entered when you boot the Surface device to UEFI. The password can contain the following characters (as shown in Figure 2):
|
||||
|
||||
- Uppercase letters: A-Z
|
||||
|
||||
- Lowercase letters: a-z
|
||||
|
||||
- Numbers: 1-0
|
||||
|
||||
- Special characters: !@#$%^&*()?<>{}[]-_=+|.,;:’`”
|
||||
|
||||
The password must be at least 6 characters and is case sensitive.
|
||||
|
||||
*Figure 2. Add a password to protect Surface UEFI settings*
|
||||
|
||||

|
||||
|
||||
On the **Security** page you can also change the configuration of Secure Boot on your Surface device. Secure Boot technology prevents unauthorized boot code from booting on your Surface device, which protects against bootkit and rootkit-type malware infections. You can disable Secure Boot to allow your Surface device to boot third-party operating systems or bootable media. You can also configure Secure Boot to work with third-party certificates, as shown in Figure 3. Read more about [Secure Boot](https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/secure-boot-overview) in the TechNet Library.
|
||||
|
||||
*Figure 3. Configure Secure Boot*
|
||||
|
||||

|
||||
|
||||
You can also enable or disable the Trusted Platform Module (TPM) device on the **Security** page, as shown in Figure 4. The TPM is used to authenticate encryption for your device’s data with BitLocker. Read more about [BitLocker](https://technet.microsoft.com/en-us/itpro/windows/keep-secure/bitlocker-overview) in the TechNet Library.
|
||||
|
||||
*Figure 4. Configure Surface UEFI security settings*
|
||||
|
||||

|
||||
|
||||
##Devices
|
||||
|
||||
On the **Devices** page you can enable or disable specific devices and components of your Surface device. Devices that you can enable or disable on this page include:
|
||||
|
||||
- Docking and USB Ports
|
||||
|
||||
- MicroSD or SD Card Slot
|
||||
|
||||
- Rear Camera
|
||||
|
||||
- Front Camera
|
||||
|
||||
- Infrared (IR) Camera
|
||||
|
||||
- Wi-Fi and Bluetooth
|
||||
|
||||
- Onboard Audio (Speakers and Microphone)
|
||||
|
||||
Each device is listed with a slider button that you can move to **On** (enabled) or **Off** (disabled) position, as shown in Figure 5.
|
||||
|
||||
*Figure 5. Enable and disable specific devices*
|
||||
|
||||

|
||||
|
||||
##Boot configuration
|
||||
|
||||
On the **Boot Configuration** page, you can change the order of your boot devices and/or enable or disable boot of the following devices:
|
||||
|
||||
- Windows Boot Manager
|
||||
|
||||
- USB Storage
|
||||
|
||||
- PXE Network
|
||||
|
||||
- Internal Storage
|
||||
|
||||
You can boot from a specific device immediately, or you can swipe left on that device’s entry in the list using the touchscreen. You can also boot immediately to a USB device or USB Ethernet adapter when the Surface device is powered off by pressing the **Volume Down** button and the **Power** button simultaneously.
|
||||
|
||||
For the specified boot order to take effect, you must set the **Enable Alternate Boot Sequence** option to **On**, as shown in Figure 6.
|
||||
|
||||
*Figure 6. Configure the boot order for your Surface device*
|
||||
|
||||

|
||||
|
||||
You can also turn on and off IPv6 support for PXE with the **Enable IPv6 for PXE Network Boot** option, for example when performing a Windows deployment using PXE where the PXE server is configured for IPv4 only.
|
||||
|
||||
##About
|
||||
|
||||
The **About** page displays regulatory information, such as compliance with FCC rules, as shown in Figure 7.
|
||||
|
||||
*Figure 7. Regulatory information is displayed on the About page*
|
||||
|
||||

|
||||
|
||||
##Exit
|
||||
|
||||
Use the **Restart Now** button on the **Exit** page to exit UEFI settings, as shown in Figure 8.
|
||||
|
||||
*Figure 8. Click Restart Now to exit Surface UEFI and restart the device*
|
||||
|
||||

|
@ -285,8 +285,7 @@ When you enable the **Don't search the web or display web results in Search** Gr
|
||||
|
||||
- For **Remote port**, choose **All ports**.
|
||||
|
||||
**Note**
|
||||
If your organization tests network traffic, you should not use Fiddler to test Windows Firewall settings. You should use a network traffic analyzer, such as WireShark or Message Analyzer.
|
||||
> **Note:** If your organization tests network traffic, you should not use Fiddler to test Windows Firewall settings. You should use a network traffic analyzer, such as WireShark or Message Analyzer.
|
||||
|
||||
### <a href="" id="bkmk-cortana-mdm"></a>1.2 Cortana MDM policies
|
||||
|
||||
@ -321,8 +320,7 @@ Starting with Windows 10, fonts that are included in Windows but that are not st
|
||||
|
||||
To turn off font streaming, create a REG\_DWORD registry setting called **DisableFontProviders** in **HKEY\_LOCAL\_MACHINE\\System\\CurrentControlSet\\Services\\FontCache\\Parameters**, with a value of 1.
|
||||
|
||||
**Note**
|
||||
This may change in future versions of Windows.
|
||||
> **Note:** This may change in future versions of Windows.
|
||||
|
||||
### <a href="" id="bkmk-previewbuilds"></a>5. Insider Preview builds
|
||||
|
||||
@ -408,8 +406,7 @@ Use either Group Policy or MDM policies to manage settings for Microsoft Edge. F
|
||||
|
||||
Find the Microsoft Edge Group Policy objects under **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Microsoft Edge**.
|
||||
|
||||
**Note**
|
||||
The Microsoft Edge Group Policy names were changed in Windows 10, version 1511. The table below reflects those changes.
|
||||
> **Note:** The Microsoft Edge Group Policy names were changed in Windows 10, version 1511. The table below reflects those changes.
|
||||
|
||||
| Policy | Description |
|
||||
|------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
|
||||
@ -453,10 +450,6 @@ You can turn off NCSI through Group Policy:
|
||||
|
||||
You can turn off the ability to download and update offline maps.
|
||||
|
||||
- In the UI: **Settings** > **System** > **Offline maps** > **Automatically update maps**
|
||||
|
||||
-or-
|
||||
|
||||
- Apply the Group Policy: **Computer Configuration** > **Administrative Templates** > **Windows Components** > **Maps** > **Turn off Automatic Download and Update of Map Data**
|
||||
|
||||
### <a href="" id="bkmk-onedrive"></a>12. OneDrive
|
||||
@ -617,10 +610,7 @@ Use Settings > Privacy to configure some settings that may be important to yo
|
||||
|
||||
To turn off **Let apps use my advertising ID for experiences across apps (turning this off will reset your ID)**:
|
||||
|
||||
**Note**
|
||||
When you turn this feature off in the UI, it turns off the advertising ID, not just resets it.
|
||||
|
||||
|
||||
> **Note:** When you turn this feature off in the UI, it turns off the advertising ID, not just resets it.
|
||||
|
||||
- Turn off the feature in the UI.
|
||||
|
||||
@ -660,8 +650,7 @@ To turn off **Turn on SmartScreen Filter to check web content (URLs) that Window
|
||||
|
||||
To turn off **Send Microsoft info about how I write to help us improve typing and writing in the future**:
|
||||
|
||||
**Note**
|
||||
If the telemetry level is set to either **Basic** or **Security**, this is turned off automatically.
|
||||
> **Note: ** If the telemetry level is set to either **Basic** or **Security**, this is turned off automatically.
|
||||
|
||||
|
||||
|
||||
@ -793,8 +782,7 @@ To turn off **Choose apps that can use your microphone**:
|
||||
|
||||
In the **Speech, Inking, & Typing** area, you can let Windows and Cortana better understand your employee's voice and written input by sampling their voice and writing, and by comparing verbal and written input to contact names and calendar entrees.
|
||||
|
||||
**Note**
|
||||
For more info on how to disable Cortana in your enterprise, see [Cortana](#bkmk-cortana) in this article.
|
||||
> **Note:** For more info on how to disable Cortana in your enterprise, see [Cortana](#bkmk-cortana) in this article.
|
||||
|
||||
|
||||
|
||||
@ -987,8 +975,7 @@ To change the level of diagnostic and usage data sent when you **Send your devic
|
||||
|
||||
- To change from **Enhanced**, use the drop-down list in the UI. The other levels are **Basic** and **Full**.
|
||||
|
||||
**Note**
|
||||
You can't use the UI to change the telemetry level to **Security**.
|
||||
> **Note:** You can't use the UI to change the telemetry level to **Security**.
|
||||
|
||||
|
||||
|
||||
@ -1107,6 +1094,10 @@ You can opt of the Microsoft Antimalware Protection Service.
|
||||
-or-
|
||||
|
||||
- Use the registry to set the REG\_DWORD value **HKEY\_LOCAL\_MACHINE\\Software\\Policies\\Microsoft\\Windows Defender\\Spynet\\SpyNetReporting** to 0 (zero).
|
||||
|
||||
-and-
|
||||
|
||||
From an elevated Windows PowerShell prompt, run **set-mppreference -Mapsreporting 0**
|
||||
|
||||
You can stop sending file samples back to Microsoft.
|
||||
|
||||
|
@ -78,7 +78,8 @@ After an app is published and available in the Store, ISVs publish an updated ve
|
||||
|
||||
5. Click **Save** to save your changes and start the app submission process.
|
||||
|
||||
For more information, see [Organizational licensing options]( http://go.microsoft.com/fwlink/p/?LinkId=708615) and [Distributing LOB apps to enterprises](http://go.microsoft.com/fwlink/p/?LinkId=627543).
|
||||
For more information, see [Organizational licensing options]( http://go.microsoft.com/fwlink/p/?LinkId=708615) and [Distributing LOB apps to enterprises](http://go.microsoft.com/fwlink/p/?LinkId=627543).<br>
|
||||
**Note** In order to get the LOB app, the organization must be located in a [supported market](https://technet.microsoft.com/en-us/itpro/windows/whats-new/windows-store-for-business-overview#supported-markets), and you must not have excluded that market when submitting your app.
|
||||
|
||||
### <a href="" id="add-lob-app-to-inventory"></a>Add app to inventory (admin)
|
||||
|
||||
|
@ -49,8 +49,7 @@ This school configuration has the following characteristics:
|
||||
- You install the Windows Assessment and Deployment Kit (Windows ADK) on the admin device.
|
||||
- You install the Windows Assessment and Deployment Kit (Windows ADK) on the admin device.
|
||||
- You install the 64-bit version of the Microsoft Deployment Toolkit (MDT) 2013 Update 2 on the admin device.
|
||||
|
||||
**Note** In this guide, all references to MDT refer to the 64-bit version of MDT 2013 Update 2.
|
||||
>**Note:** In this guide, all references to MDT refer to the 64-bit version of MDT 2013 Update 2.
|
||||
- The devices use Azure AD in Office 365 Education for identity management.
|
||||
- If you have on-premises AD DS, you can [integrate Azure AD with on-premises AD DS](http://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnect/).</li>
|
||||
- Use [Intune](http://technet.microsoft.com/library/jj676587.aspx), [compliance settings in Office 365](https://support.office.com/en-us/article/Manage-mobile-devices-in-Office-365-dd892318-bc44-4eb1-af00-9db5430be3cd?ui=en-US&rs=en-US&ad=US), or [Group Policy](http://technet.microsoft.com/en-us/library/cc725828%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396) in AD DS to manage devices.
|
||||
@ -140,7 +139,7 @@ Next, install MDT. MDT uses the Windows ADK to help you manage and perform Windo
|
||||
|
||||
You can use MDT to deploy 32-bit or 64-bit versions of Windows 10. Install the 64-bit version of MDT to support deployment of 32-bit and 64-bit operating systems.
|
||||
|
||||
**Note** If you install the 32-bit version of MDT, you can install only 32-bit versions of Windows 10. Ensure that you download and install the 64-bit version of MDT so that you can install 64-bit and 32 bit versions of the operating system.
|
||||
>**Note:** If you install the 32-bit version of MDT, you can install only 32-bit versions of Windows 10. Ensure that you download and install the 64-bit version of MDT so that you can install 64-bit and 32 bit versions of the operating system.
|
||||
|
||||
For more information about installing MDT on the admin device, see [Installing a New Instance of MDT](https://technet.microsoft.com/en-us/library/dn759415.aspx#InstallingaNewInstanceofMDT).
|
||||
|
||||
@ -225,13 +224,13 @@ You will use the Office 365 Education license plan information you record in Tab
|
||||
|
||||
To create a new Office 365 Education subscription for use in the classroom, use your educational institution’s email account. There are no costs to you or to students for signing up for Office 365 Education subscriptions.
|
||||
|
||||
**Note** If you already have an Office 365 Education subscription, you can use that subscription and continue to the next section, [Add domains and subdomains](#add-domains-and-subdomains).
|
||||
>**Note:** If you already have an Office 365 Education subscription, you can use that subscription and continue to the next section, [Add domains and subdomains](#add-domains-and-subdomains).
|
||||
|
||||
#### To create a new Office 365 subscription
|
||||
|
||||
1. In Microsoft Edge or Internet Explorer, type `https://portal.office.com/start?sku=faculty` in the address bar.
|
||||
|
||||
**Note** If you have already used your current sign-in account to create a new Office 365 subscription, you will be prompted to sign in. If you want to create a new Office 365 subscription, start an In-Private Window in one of the following:
|
||||
>**Note** If you have already used your current sign-in account to create a new Office 365 subscription, you will be prompted to sign in. If you want to create a new Office 365 subscription, start an In-Private Window in one of the following:<br/>
|
||||
- Microsoft Edge by opening the Microsoft Edge app, either pressing Ctrl+Shift+P or clicking or tapping **More actions**, and then clicking or tapping **New InPrivate window**.
|
||||
- Internet Explorer 11 by opening Internet Explorer 11, either pressing Ctrl+Shift+P or clicking or tapping **Settings**, clicking or tapping **Safety**, and then clicking or tapping **InPrivate Browsing**.
|
||||
|
||||
@ -256,7 +255,7 @@ Now that you have created your new Office 365 Education subscription, add the do
|
||||
|
||||
To make it easier for faculty and students to join your Office 365 Education subscription (or *tenant*), allow them to automatically sign up to your tenant (*automatic tenant join*). In automatic tenant join, when a faculty member or student signs up for Office 365, Office 365 automatically adds (joins) the user to your Office 365 tenant.
|
||||
|
||||
**Note** By default, automatic tenant join is enabled in Office 365 Education, with the exception of certain areas in Europe, the Middle East, and Africa. These countries require opt-in steps to add new users to existing Office 365 tenants. Check your country requirements to determine the automatic tenant join default configuration. Also, if you use Azure AD Connect, then automatic tenant join is disabled.
|
||||
>**Note:** By default, automatic tenant join is enabled in Office 365 Education, with the exception of certain areas in Europe, the Middle East, and Africa. These countries require opt-in steps to add new users to existing Office 365 tenants. Check your country requirements to determine the automatic tenant join default configuration. Also, if you use Azure AD Connect, then automatic tenant join is disabled.
|
||||
|
||||
Office 365 uses the domain portion of the user’s email address to know which Office 365 tenant to join. For example, if a faculty member or student provides an email address of user@contoso.edu, then Office 365 automatically performs one of the following tasks:
|
||||
|
||||
@ -265,7 +264,7 @@ Office 365 uses the domain portion of the user’s email address to know which O
|
||||
|
||||
You will always want faculty and students to join the Office 365 tenant that you created. Ensure that you perform the steps in the [Create a new Office 365 Education subscription](#create-a-new-office-365-education-subscription) and [Add domains and subdomains](#add-domains-and-subdomains) sections before allowing other faculty and students to join Office 365.
|
||||
|
||||
**Note** You cannot merge multiple tenants, so any faculty or students who create their own tenant will need to abandon their existing tenant and join yours.
|
||||
>**Note:** You cannot merge multiple tenants, so any faculty or students who create their own tenant will need to abandon their existing tenant and join yours.
|
||||
|
||||
All new Office 365 Education subscriptions have automatic tenant join enabled by default, but you can enable or disable automatic tenant join by using the Windows PowerShell commands in Table 3. For more information about how to run these commands, see [How can I prevent students from joining my existing Office 365 tenant](https://support.office.com/en-us/article/Office-365-Education-Self-Sign-up-Technical-FAQ-7fb1b2f9-94c2-4cbb-b01e-a6eca34261d6?ui=en-US&rs=en-US&ad=US#BKMK_PreventJoins).
|
||||
|
||||
@ -277,13 +276,13 @@ All new Office 365 Education subscriptions have automatic tenant join enabled by
|
||||
| Enable |`Set-MsolCompanySettings -AllowEmailVerifiedUsers $true`|
|
||||
| Disable |`Set-MsolCompanySettings -AllowEmailVerifiedUsers $false`|
|
||||
<p>
|
||||
**Note** If your institution has AD DS, then disable automatic tenant join. Instead, use Azure AD integration with AD DS to add users to your Office 365 tenant.
|
||||
>**Note:** If your institution has AD DS, then disable automatic tenant join. Instead, use Azure AD integration with AD DS to add users to your Office 365 tenant.
|
||||
|
||||
### Disable automatic licensing
|
||||
|
||||
To reduce your administrative effort, automatically assign Office 365 Education or Office 365 Education Plus licenses to faculty and students when they sign up (automatic licensing). Automatic licensing also enables Office 365 Education or Office 365 Education Plus features that do not require administrative approval.
|
||||
|
||||
**Note** By default, automatic licensing is enabled in Office 365 Education. If you want to use automatic licensing, then skip this section and go to the next section.
|
||||
>**Note:** By default, automatic licensing is enabled in Office 365 Education. If you want to use automatic licensing, then skip this section and go to the next section.
|
||||
|
||||
Although all new Office 365 Education subscriptions have automatic licensing enabled by default, you can enable or disable it for your Office 365 tenant by using the Windows PowerShell commands in Table 4. For more information about how to run these commands, see [How can I prevent students from joining my existing Office 365 tenant](https://support.office.com/en-us/article/Office-365-Education-Self-Sign-up-Technical-FAQ-7fb1b2f9-94c2-4cbb-b01e-a6eca34261d6?ui=en-US&rs=en-US&ad=US#BKMK_PreventJoins).
|
||||
|
||||
@ -336,7 +335,7 @@ Now that you have an Office 365 subscription, you need to determine how you will
|
||||
|
||||
In this method, you have an on-premises AD DS domain. As shown in Figure 4, the Azure AD Connector tool automatically synchronizes AD DS with Azure AD. When you add or change any user accounts in AD DS, the Azure AD Connector tool automatically updates Azure AD.
|
||||
|
||||
**Note** Azure AD Connect also supports synchronization from any Lightweight Directory Access Protocol version 3 (LDAPv3)–compliant directory by using the information provided in [Generic LDAP Connector for FIM 2010 R2 Technical Reference](https://technet.microsoft.com/en-us/library/dn510997.aspx?f=255&MSPPError=-2147217396).
|
||||
>**Note:** Azure AD Connect also supports synchronization from any Lightweight Directory Access Protocol version 3 (LDAPv3)–compliant directory by using the information provided in [Generic LDAP Connector for FIM 2010 R2 Technical Reference](https://technet.microsoft.com/en-us/library/dn510997.aspx?f=255&MSPPError=-2147217396).
|
||||
|
||||

|
||||
|
||||
@ -365,7 +364,7 @@ In this section, you selected the method for creating user accounts in your Offi
|
||||
|
||||
You can integrate your on-premises AD DS domain with Azure AD to provide identity management for your Office 365 tenant. With this integration, you can synchronize the users, security groups, and distribution lists in your AD DS domain with Azure AD with the Azure AD Connect tool. Users will be able to sign in to Office 365 automatically by using their email account and the same password they use to sign in to AD DS.
|
||||
|
||||
**Note** If your institution does not have an on-premises AD DS domain, you can skip this section.
|
||||
>**Note:** If your institution does not have an on-premises AD DS domain, you can skip this section.
|
||||
|
||||
### Select synchronization model
|
||||
|
||||
@ -426,7 +425,7 @@ In this section, you selected your synchronization model, deployed Azure AD Conn
|
||||
|
||||
You can bulk-import user and group accounts into your on-premises AD DS domain. Bulk-importing accounts helps reduce the time and effort needed to create users compared to creating the accounts manually in the Office 365 Admin portal. First, you select the appropriate method for bulk-importing user accounts into AD DS. Next, you create the .csv file that contains the user accounts. Finally, you use the selected method to import the .csv file into AD DS.
|
||||
|
||||
**Note** If your institution doesn’t have an on-premises AD DS domain, you can skip this section.
|
||||
>**Note:** If your institution doesn’t have an on-premises AD DS domain, you can skip this section.
|
||||
|
||||
### Select the bulk import method
|
||||
|
||||
@ -456,7 +455,7 @@ After you have selected your user and group account bulk import method, you’re
|
||||
|
||||
With the bulk-import source file finished, you’re ready to import the user and group accounts into AD DS. The steps for importing the file are slightly different for each method.
|
||||
|
||||
**Note** Bulk-import your group accounts first, and then import your user accounts. Importing in this order allows you to specify group membership when you import your user accounts.
|
||||
>**Note:** Bulk-import your group accounts first, and then import your user accounts. Importing in this order allows you to specify group membership when you import your user accounts.
|
||||
|
||||
For more information about how to import user accounts into AD DS by using:
|
||||
|
||||
@ -482,7 +481,7 @@ The bulk-add process assigns the same Office 365 Education license plan to all u
|
||||
|
||||
For more information about how to bulk-add users to Office 365, see [Add several users at the same time to Office 365](https://support.office.com/en-us/article/Add-several-users-at-the-same-time-to-Office-365-Admin-Help-1f5767ed-e717-4f24-969c-6ea9d412ca88?ui=en-US&rs=en-US&ad=US).
|
||||
|
||||
**Note** If you encountered errors during bulk add, resolve them before you continue the bulk-add process. You can view the log file to see which users caused the errors, and then modify the .csv file to correct the problems. Click **Back** to retry the verification process.
|
||||
>**Note:** If you encountered errors during bulk add, resolve them before you continue the bulk-add process. You can view the log file to see which users caused the errors, and then modify the .csv file to correct the problems. Click **Back** to retry the verification process.
|
||||
|
||||
The email accounts are assigned temporary passwords upon creation. You must communicate these temporary passwords to your users before they can sign in to Office 365.
|
||||
|
||||
@ -490,13 +489,13 @@ The email accounts are assigned temporary passwords upon creation. You must comm
|
||||
|
||||
Assign SharePoint Online resource permissions to Office 365 security groups, not individual user accounts. For example, create one security group for faculty members and another for students. Then, you can assign unique SharePoint Online resource permissions to faculty members and a different set of permissions to students. Add or remove users from the security groups to grant or revoke access to SharePoint Online resources.
|
||||
|
||||
**Note** If your institution has AD DS, don’t create security accounts in Office 365. Instead, create the security groups in AD DS, and then use Azure AD integration to synchronize the security groups with your Office 365 tenant.
|
||||
>**Note:** If your institution has AD DS, don’t create security accounts in Office 365. Instead, create the security groups in AD DS, and then use Azure AD integration to synchronize the security groups with your Office 365 tenant.
|
||||
|
||||
For information about creating security groups, see [Create and manage Office 365 groups in Admin Center Preview](https://support.office.com/en-us/article/Create-and-manage-Office-365-groups-in-Admin-Center-Preview-93df5bd4-74c4-45e8-9625-56db92865a6e?ui=en-US&rs=en-US&ad=US).
|
||||
|
||||
You can add and remove users from security groups at any time.
|
||||
|
||||
**Note** Office 365 evaluates group membership when users sign in. If you change group membership for a user, that user may need to sign out, and then sign in again for the change to take effect.
|
||||
>**Note:** Office 365 evaluates group membership when users sign in. If you change group membership for a user, that user may need to sign out, and then sign in again for the change to take effect.
|
||||
|
||||
### Create email distribution groups
|
||||
|
||||
@ -504,7 +503,7 @@ Microsoft Exchange Online uses an email distribution group as a single email rec
|
||||
|
||||
You can create email distribution groups based on job role (such as teachers, administration, or students) or specific interests (such as robotics, drama club, or soccer team). You can create any number of distribution groups, and users can be members of more than one group.
|
||||
|
||||
**Note** Office 365 can take some time to complete the Exchange Online creation process. You will have to wait until Office 365 completes the Exchange Online creation process before you can perform the following steps.
|
||||
>**Note:** Office 365 can take some time to complete the Exchange Online creation process. You will have to wait until Office 365 completes the Exchange Online creation process before you can perform the following steps.
|
||||
|
||||
For information about how to create security groups, see [Create and manage Office 365 groups in Admin Center Preview](https://support.office.com/en-us/article/Create-and-manage-Office-365-groups-in-Admin-Center-Preview-93df5bd4-74c4-45e8-9625-56db92865a6e?ui=en-US&rs=en-US&ad=US).
|
||||
|
||||
@ -542,7 +541,8 @@ To create and configure your Windows Store for Business portal, simply use the a
|
||||
#### To create and configure a Windows Store for Business portal
|
||||
|
||||
1. In Microsoft Edge or Internet Explorer, type `http://microsoft.com/business-store` in the address bar.
|
||||
2. On the **Windows Store for Business** page, click **Sign in with an organizational account**.<p>**Note** If your institution has AD DS, then don’t create security accounts in Office 365. Instead, create the security groups in AD DS, and then use Azure AD integration to synchronize the security groups with your Office 365 tenant.
|
||||
2. On the **Windows Store for Business** page, click **Sign in with an organizational account**.
|
||||
>**Note:** If your institution has AD DS, then don’t create security accounts in Office 365. Instead, create the security groups in AD DS, and then use Azure AD integration to synchronize the security groups with your Office 365 tenant.
|
||||
3. On the Windows Store for Business sign-in page, use the administrative account for the Office 365 subscription you created in the [Create a new Office 365 Education subscription](#create-a-new-office-365-education-subscription) section to sign in.
|
||||
4. On the **Windows Store for Business Services Agreement** page, review the agreement, select the **I accept this agreement and certify that I have the authority to bind my organization to its terms** check box, and then click **Accept**
|
||||
5. In the **Welcome to the Windows Store for Business** dialog box, click **OK**.
|
||||
@ -565,7 +565,7 @@ After you create the Windows Store for Business portal, configure it by using th
|
||||
|
||||
Now that you have created your Windows Store for Business portal, you’re ready to find, acquire, and distribute apps that you will add to your portal. You do this by using the Inventory page in Windows Store for Business.
|
||||
|
||||
**Note** Your educational institution can now use a credit card or purchase order to pay for apps in Windows Store for Business.
|
||||
>**Note:** Your educational institution can now use a credit card or purchase order to pay for apps in Windows Store for Business.
|
||||
|
||||
You can deploy apps to individual users or make apps available to users through your private store. Deploying apps to individual users restricts the app to those specified users. Making apps available through your private store allows all your users.
|
||||
|
||||
@ -596,11 +596,11 @@ Depending on your school’s requirements, you may need any combination of the f
|
||||
- Upgrade institution-owned devices to Windows 10 Education.
|
||||
- Deploy new instances of Windows 10 Education so that new devices have a known configuration.
|
||||
|
||||
**Note** Although you can use Windows 10 Home on institution-owned devices, Microsoft recommends that you use Windows 10 Pro or Windows 10 Education, instead. Windows 10 Pro and Windows 10 Education provide support for MDM, policy-based management, and Windows Store for Business. These features are not available in Windows 10 Home.
|
||||
>**Note:** Although you can use Windows 10 Home on institution-owned devices, Microsoft recommends that you use Windows 10 Pro or Windows 10 Education, instead. Windows 10 Pro and Windows 10 Education provide support for MDM, policy-based management, and Windows Store for Business. These features are not available in Windows 10 Home.
|
||||
|
||||
One other consideration is the mix of processor architectures you will support. If you can, support only 64-bit versions of Windows 10. If you have devices that can run only 32 bit versions of Windows 10, you will need to import both 64-bit and 32-bit versions of the Windows 10 editions listed above.
|
||||
|
||||
**Note** On devices that have minimal system resources (such as devices with only 2 GB of memory or 32 GB of storage), use 32-bit versions of Windows 10 because 64-bit versions of Windows 10 place more stress on device system resources.
|
||||
>**Note:** On devices that have minimal system resources (such as devices with only 2 GB of memory or 32 GB of storage), use 32-bit versions of Windows 10 because 64-bit versions of Windows 10 place more stress on device system resources.
|
||||
|
||||
Finally, as a best practice, minimize the number of operating systems that you deploy and manage. If possible, standardize institution-owned devices on one Windows 10 edition (such as a 64-bit version of Windows 10 Education or Windows 10 Pro). Of course, you cannot standardize personal devices on a specific operating system version or processor architecture.
|
||||
|
||||
@ -738,9 +738,7 @@ In addition, you must prepare your environment for sideloading (deploying) Windo
|
||||
|
||||
To help reduce the effort needed to deploy Microsoft Office 2016 desktop apps, use the Office Deployment Tool, as described in [Deploy Click-to-Run for Office 365 products by using the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219423.aspx?f=255&MSPPError=-2147217396).<br/><br/>
|
||||
|
||||
If you have Intune, you can deploy Windows desktop apps after you deploy Windows 10, as described in the [Deploy apps by using Intune](#deploy-apps-by-using-intune) section. This method provides granular deployment of Windows desktop apps, and you can use it for ongoing management of the apps. This is the preferred method for deploying and managing Windows desktop apps.<br/><br/>
|
||||
|
||||
**Note** You can also deploy Windows desktop apps after you deploy Windows 10, as described in the [Deploy apps by using Intune](#deploy-apps-by-using-intune) section.<br/><br/>
|
||||
If you have Intune, you can deploy Windows desktop apps after you deploy Windows 10, as described in the [Deploy apps by using Intune](#deploy-apps-by-using-intune) section. This method provides granular deployment of Windows desktop apps, and you can use it for ongoing management of the apps. This is the preferred method for deploying and managing Windows desktop apps.<br/><br/>**Note:** You can also deploy Windows desktop apps after you deploy Windows 10, as described in the [Deploy apps by using Intune](#deploy-apps-by-using-intune) section.<br/><br/>
|
||||
|
||||
For more information about how to create an MDT application for Window desktop apps, see [Create a New Application in the Deployment Workbench](https://technet.microsoft.com/en-us/library/dn759415.aspx#CreateaNewApplicationintheDeploymentWorkbench).
|
||||
|
||||
@ -897,7 +895,7 @@ Microsoft has several recommended settings for educational institutions. Table 1
|
||||
<tr>
|
||||
<td valign="top">Use of Microsoft accounts</td>
|
||||
<td>You want faculty and students to use only Azure AD accounts for institution-owned devices. For these devices, do not use Microsoft accounts or associate a Microsoft account with the Azure AD accounts.<br/><br/>
|
||||
**Note** Personal devices typically use Microsoft accounts. Faculty and students can associate their Microsoft account with their Azure AD account on these devices.<br/><br/>
|
||||
**Note:** Personal devices typically use Microsoft accounts. Faculty and students can associate their Microsoft account with their Azure AD account on these devices.<br/><br/>
|
||||
**Group Policy.** Configure the [Accounts: Block Microsoft accounts](https://technet.microsoft.com/en-us/library/jj966262.aspx?f=255&MSPPError=-2147217396) Group Policy setting to use the Users can’t add Microsoft accounts setting option.<br/><br/>
|
||||
**Intune.** Enable or disable the camera by using the **Allow Microsoft account**, **Allow adding non-Microsoft accounts manually**, and **Allow settings synchronization for Microsoft accounts** policy settings under the **Accounts and Synchronization** section of a **Windows 10 General Configuration** policy.
|
||||
</td>
|
||||
@ -1042,7 +1040,7 @@ Prior to deployment of Windows 10, ensure that you complete the tasks listed in
|
||||
|
||||
Use the Deployment Wizard to deploy Windows 10. The LTI deployment process is almost fully automated: You provide only minimal information to the Deployment Wizard at the beginning of the process. After the wizard collects the necessary information, the remainder of the process is fully automated.
|
||||
|
||||
**Note** To fully automate the LTI deployment process, complete the steps in the “Fully Automated LTI Deployment Scenario” section in the [Microsoft Deployment Toolkit Samples Guide](https://technet.microsoft.com/en-us/library/dn781089.aspx).
|
||||
>**Note:** To fully automate the LTI deployment process, complete the steps in the “Fully Automated LTI Deployment Scenario” section in the [Microsoft Deployment Toolkit Samples Guide](https://technet.microsoft.com/en-us/library/dn781089.aspx).
|
||||
|
||||
In most instances, deployments occur without incident. Only in rare occasions do deployments experience problems.
|
||||
|
||||
@ -1055,7 +1053,7 @@ In most instances, deployments occur without incident. Only in rare occasions do
|
||||
|
||||
After you have deployed Windows 10, the devices are almost ready for use. First, you must set up the printers that each classroom will use. Typically, you connect the printers to the same network as the devices in the same classroom. If you don’t have printers in your classrooms, skip this section and proceed to the [Verify deployment](#verify-deployment) section.
|
||||
|
||||
**Note** If you’re performing an upgrade instead of a new deployment, the printers remain configured as they were in the previous version of Windows. As a result, you can skip this section and proceed to the [Verify deployment](#verify-deployment) section.
|
||||
>**Note:** If you’re performing an upgrade instead of a new deployment, the printers remain configured as they were in the previous version of Windows. As a result, you can skip this section and proceed to the [Verify deployment](#verify-deployment) section.
|
||||
|
||||
#### To set up printers
|
||||
|
||||
|