fixing merge conflict
@ -12,6 +12,12 @@ localizationpriority: high
|
||||
---
|
||||
|
||||
# Block untrusted fonts in an enterprise
|
||||
**Applies to:**
|
||||
|
||||
- Windows 10
|
||||
|
||||
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare).
|
||||
|
||||
To help protect your company from attacks which may originate from untrusted or attacker controlled font files, we’ve created the Blocking Untrusted Fonts feature. Using this feature, you can turn on a global setting that stops your employees from loading untrusted fonts processed using the Graphics Device Interface (GDI) onto your network. Untrusted fonts are any font installed outside of the `%windir%/Fonts` directory. Blocking untrusted fonts helps prevent both remote (web-based or email-based) and local EOP attacks that can happen during the font file-parsing process.
|
||||
|
||||
## What does this mean for me?
|
||||
|
@ -14,6 +14,8 @@ author: brianlic-msft
|
||||
**Applies to**
|
||||
- Windows 10
|
||||
|
||||
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare).
|
||||
|
||||
Describes the best practices, location, values, policy management, and security considerations for the **Bypass traverse checking** security policy setting.
|
||||
|
||||
## Reference
|
||||
|
@ -15,7 +15,7 @@ author: brianlic-msft
|
||||
- Windows 10
|
||||
- Windows Server 2016
|
||||
|
||||
Introduced in Windows 10 Enterprise, Credential Guard uses virtualization-based security to isolate secrets so that only privileged system software can access them. Unauthorized access to these secrets can lead to credential theft attacks, such as Pass-the-Hash or Pass-The-Ticket. Credential Guard prevents these attacks by protecting NTLM password hashes and Kerberos Ticket Granting Tickets.
|
||||
Introduced in Windows 10 Enterprise and Windows Server 2016, Credential Guard uses virtualization-based security to isolate secrets so that only privileged system software can access them. Unauthorized access to these secrets can lead to credential theft attacks, such as Pass-the-Hash or Pass-The-Ticket. Credential Guard prevents these attacks by protecting NTLM password hashes and Kerberos Ticket Granting Tickets.
|
||||
|
||||
Credential Guard offers the following features and solutions:
|
||||
|
||||
@ -91,7 +91,7 @@ The PC must meet the following hardware and software requirements to use Credent
|
||||
<td>TPM 2.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Windows 10 version 1511 or later</td>
|
||||
<td>Windows 10 version 1511, Windows Server 2016, or later</td>
|
||||
<td>TPM 2.0 or TPM 1.2</td>
|
||||
</tr>
|
||||
</table>
|
||||
@ -114,7 +114,7 @@ The PC must meet the following hardware and software requirements to use Credent
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>Virtual machine</p></td>
|
||||
<td align="left"><p>For PCs running Windows 10, version 1607, you can run Credential Guard on a Generation 2 virtual machine.</p></td>
|
||||
<td align="left"><p>For PCs running Windows 10, version 1607 or Windows Server 2016, you can run Credential Guard on a Generation 2 virtual machine.</p></td>
|
||||
</tr>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
@ -169,7 +169,7 @@ First, you must add the virtualization-based security features. You can do this
|
||||
> You can also add these features to an online image by using either DISM or Configuration Manager.
|
||||
|
||||
|
||||
In Windows 10, version 1607, Isolated User Mode is included with Hyper-V and does not need to be installed separately. If you're running a version of Windows 10 that's earlier than Windows 10, version 1607, you can run the following command to install Isolated User Mode:
|
||||
In Windows 10, version 1607 and Windows Server 2016, Isolated User Mode is included with Hyper-V and does not need to be installed separately. If you're running a version of Windows 10 that's earlier than Windows 10, version 1607, you can run the following command to install Isolated User Mode:
|
||||
|
||||
``` syntax
|
||||
dism /image:<WIM file name> /Enable-Feature /FeatureName:IsolatedUserMode
|
||||
|
@ -144,6 +144,10 @@ The following table lists the Group Policy settings that you can configure for H
|
||||
## MDM policy settings for Windows Hello for Business
|
||||
|
||||
The following table lists the MDM policy settings that you can configure for Windows Hello for Business use in your workplace. These MDM policy settings use the [PassportForWork configuration service provider (CSP)](http://go.microsoft.com/fwlink/p/?LinkId=692070).
|
||||
|
||||
>[!IMPORTANT]
|
||||
>Starting in Windows 10, version 1607, all devices only have one PIN associated with Windows Hello for Business. This means that any PIN on a device will be subject to the policies specified in the PassportForWork CSP. The values specified take precedence over any complexity rules set via Exchange ActiveSync (EAS) or the DeviceLock CSP.
|
||||
|
||||
<table>
|
||||
<tr>
|
||||
<th colspan="2">Policy</th>
|
||||
|
@ -16,6 +16,7 @@ localizationpriority: high
|
||||
|
||||
- Windows 10, version 1607
|
||||
- Windows 10 Mobile
|
||||
|
||||
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare).
|
||||
|
||||
With the increase of employee-owned devices in the enterprise, there’s also an increasing risk of accidental data leak through apps and services, like email, social media, and the public cloud, which are outside of the enterprise’s control. For example, when an employee sends the latest engineering pictures from their personal email account, copies and pastes product info into a tweet, or saves an in-progress sales report to their public cloud storage.
|
||||
|
@ -16,6 +16,7 @@
|
||||
### [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
### [Customize Windows 10 Start and taskbar with ICD and provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
### [Customize Windows 10 Start with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
## [Create mandatory user profiles](mandatory-user-profile.md)
|
||||
## [Lock down Windows 10](lock-down-windows-10.md)
|
||||
### [Lockdown features from Windows Embedded 8.1 Industry](lockdown-features-windows-10.md)
|
||||
### [Set up a shared or guest PC with Windows 10](set-up-shared-or-guest-pc.md)
|
||||
|
@ -17,10 +17,12 @@ This topic lists new and updated topics in the [Manage and update Windows 10](in
|
||||
|
||||
| New or changed topic | Description |
|
||||
| --- | --- |
|
||||
| [Create mandatory user profiles](mandatory-user-profile.md) | New |
|
||||
| [Configure Windows 10 taskbar](configure-windows-10-taskbar.md) | Updated sample XML for combined Start and taskbar layout; added note to explain the difference between applying taskbar configuration by Group Policy and by provisioning package |
|
||||
| [Set up a kiosk on Windows 10 Pro, Enterprise, or Education](set-up-a-kiosk-for-windows-10-for-desktop-editions.md) | Updated instructions for exiting assigned access mode. |
|
||||
| Application development for Windows as a service | Topic moved to MSDN: [Application development for Windows as a service](https://msdn.microsoft.com/windows/uwp/get-started/application-development-for-windows-as-a-service)
|
||||
|
||||
|
||||
## RELEASE: Windows 10, version 1607
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1607 (also known as the Anniversary Update). The following new topics have been added:
|
||||
|
@ -31,9 +31,10 @@ To frame a discussion about telemetry, it is important to understand Microsoft
|
||||
|
||||
This article applies to Windows and Windows Server telemetry only. Other Microsoft or third-party apps, such as System Center Configuration Manager, System Center Endpoint Protection, or System Center Data Protection Manager, might send data to their cloud services in ways that are inconsistent with this guide. Their publishers are responsible for notifying users of their privacy policies, telemetry controls, and so on. This article describes the types of telemetry we may gather, the ways you might manage it in your organization, and some examples of how telemetry can provide you with valuable insights into your enterprise deployments. Microsoft uses the data to quickly identify and address issues affecting its customers.
|
||||
|
||||
|
||||
Use this article to make informed decisions about how you might configure telemetry in your organization. Telemetry is a term that means different things to different people and organizations. For the purpose of this article, we discuss telemetry as system data that is uploaded by the Connected User Experience and Telemetry component. The telemetry data is used to help keep Windows devices secure by identifying malware trends and other threats and to help Microsoft improve the quality of Windows and Microsoft services.
|
||||
|
||||
We are always striving to improve our documentation and welcome your feedback. You can provide feedback by contacting telmhelp@microsoft.com.
|
||||
|
||||
## Overview
|
||||
|
||||
In previous versions of Windows and Windows Server, Microsoft used telemetry to check for updated or new Windows Defender signatures, check whether Windows Update installations were successful, gather reliability information through the Reliability Analysis Component (RAC), and gather reliability information through the Windows Customer Experience Improvement Program (CEIP) on Windows. In Windows 10 and Windows Server 2016, you can control telemetry streams by using the Privacy option in Settings, Group Policy, or MDM.
|
||||
|
@ -1,102 +0,0 @@
|
||||
---
|
||||
title: Diagnostics for Windows 10 devices (Windows 10)
|
||||
description: Device Policy State log in Windows 10, Version 1607, collects info about policies.
|
||||
keywords: ["mdm", "udiag", "device policy", "mdmdiagnostics"]
|
||||
ms.prod: W10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Diagnostics for Windows 10 devices
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
(which SKUs?)
|
||||
|
||||
(this isn't really MDM-managed only, is it? It can be done locally/email?)
|
||||
|
||||
Two new diagnostic tools for Windows 10, version 1607, help IT administrators diagnose and resolve issues with remote devices enrolled in mobile device management (MDM): the [Device Policy State Log](#device-policy-state-log) and [UDiag](#udiag). Windows 10 for desktop editions and Windows 10 Mobile make it simple for users to export log files that you can then analyze with these tools.
|
||||
|
||||
## Export management log files
|
||||
|
||||
Go to **Settings > Accounts > Work access > Export your management log files**.
|
||||
|
||||

|
||||
|
||||
- On desktop devices, the file is saved to C:/Users/Public/Public Documents/MDMDiagnostics/MDMDiagReport.xml
|
||||
- On phones, the file is saved to *phone*/Documents/MDMDiagnostics/MDMDiagReport.xml
|
||||
|
||||
The MDMDiagReport.xml can be used with [Device Policy State Log](#device-policy-state-log) and [UDiag](#udiag) to help you resolve issues.
|
||||
|
||||
## Device Policy State Log
|
||||
|
||||
The Device Policy State Log collects information on the state of policies applied to the device to help you determine which sources are applying policies or configurations to the device. Help desk personnel can use this log to diagnose and resolve issues with a remote device.
|
||||
|
||||
After you obtain the management log file from the user's device, run the mdmReportGenerator.ps1 script on log to create report. (download mdmReportGenerator.ps1 and mdmDiagnoseHelpers.psm1) This PowerShell script asks you to enter the name of the management log file and a name for the report that it will create, as shown in the following example:
|
||||
|
||||

|
||||
|
||||
The script produces the report in html format. There are two sections to the report, Configuration and Policy Information.
|
||||
|
||||
The configuration section lists the GUID of the sources that are applying configurations to the device.
|
||||
|
||||

|
||||
|
||||
The policy information section displays information about the specific policies that are being enforced and on the device. For each policy, you will see the Area grouping, the Policy name, its default and current value, and the configuration source. You can compare the configuration source GUID in the policy information section to the GUIDs in the configuration section to identify the source of the policy.
|
||||
|
||||

|
||||
|
||||
|
||||
## UDiag
|
||||
|
||||
The UDiag tool applies rules to Event Tracing for Windows (ETW) files to help determine the root cause of an issue.
|
||||
|
||||
(download UDiag)
|
||||
|
||||
To analyze MDMDiagReport.xml using UDiag
|
||||
1. Open UDiag, and select Device Management.
|
||||
2. Select your source for the log files ("cab of logs" or "directory of logs")
|
||||
|
||||
Investigating log content, identifying patterns, and adding a root cause analysis to the database (Advanced users/providers)
|
||||
|
||||
1. While at the 'Root Causes List' panel, click the 'Diagnose' button at the bottom.
|
||||
2. You will then be brought to the Diagnosis panel where you can investigate and tag root causes from the content
|
||||
- Evidence Groups: When a set of logs are loaded into UDiag, the contents are processed (e.g. ETW) and organized into evidence groups.
|
||||
- Decision Tree View: This view shows the loaded decision tree for the current topic/topic area. When a decision node is selected, a user can modify the regular expression and add/edit/delete an RCA for that node. Any RCA matches found in the current log set will have an 'RCA' label that is either Red or Yellow.
|
||||
- Evidence View: Selecting an evidence group loads its content into this evidence view. Use this view to investigate issues and determine root causes. Drag and drop lines from the Evidence View into the Decision Tree View, to build your root cause analysis pattern. ([Learn more about techniques for root cause analysis.](https://technet.microsoft.com/en-us/library/cc543298.aspx))
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Can admin pull logs without user action? [DK] Yes via the diagnostic log CSP
|
||||
|
||||
|
||||
|
||||
"Run PowerShell script to process the file" – is that the user doing it? How can this workflow work in an enterprise where employees aren't computer-savvy? [DK] This is intended to be done by the help desk guy.
|
||||
|
||||
Where did (user|admin) get mdmReportGenerator.ps1? [DK] Publishing on DLC later this summer
|
||||
|
||||
In Viewing the report, how does the admin make sense of the source GUIDs? [DK] Correlates the value in the table with the entries at the top of the page.
|
||||
|
||||
UDiag – where does admin get this? [DK] Publishing on DLC later this summer
|
||||
|
||||
Can admins create custom rule sets? [DK] Right now, no. but open to feedback on this.
|
||||
|
||||
|
||||
|
||||
Link to [Diagnose MDM failures in Windows 10](https://msdn.microsoft.com/en-us/library/windows/hardware/mt632120%28v=vs.85%29.aspx)
|
||||
|
||||
[Diagnostics capability for devices managed by any MDM provider.](https://microsoft.sharepoint.com/teams/osg_core_ens/mgmt/OSMan Wiki/MDM Diagnostics - Generating and Processing Log files.aspx)
|
||||
|
||||
[Redstone spec](https://microsoft.sharepoint.com/teams/specstore/_layouts/15/WopiFrame.aspx?sourcedoc=%7b7E8742A2-03A1-451C-BA07-F2573B044CBF%7d&file=DM%20-%20MDM%20Diagnostics-RS.docx&action=default&DefaultItemOpen=1)
|
||||
|
||||
## Related topics
|
||||
|
||||
[DiagnosticLog CSP](https://msdn.microsoft.com/en-us/library/windows/hardware/mt219118.aspx)
|
||||
|
||||
[Diagnose MDM failures in Windows 10](https://msdn.microsoft.com/en-us/library/windows/hardware/mt632120.aspx)
|
Before Width: | Height: | Size: 848 B After Width: | Height: | Size: 870 B |
BIN
windows/manage/images/checklistdone.png
Normal file
After Width: | Height: | Size: 330 B |
BIN
windows/manage/images/copy-to-change.png
Normal file
After Width: | Height: | Size: 11 KiB |
BIN
windows/manage/images/copy-to-path.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
windows/manage/images/copy-to.PNG
Normal file
After Width: | Height: | Size: 54 KiB |
BIN
windows/manage/images/gp-branch.png
Normal file
After Width: | Height: | Size: 175 KiB |
BIN
windows/manage/images/gp-exclude-drivers.png
Normal file
After Width: | Height: | Size: 159 KiB |
BIN
windows/manage/images/gp-feature.png
Normal file
After Width: | Height: | Size: 171 KiB |
BIN
windows/manage/images/gp-quality.png
Normal file
After Width: | Height: | Size: 79 KiB |
BIN
windows/manage/images/sysprep-error.png
Normal file
After Width: | Height: | Size: 30 KiB |
BIN
windows/manage/images/waas-do-fig1.png
Normal file
After Width: | Height: | Size: 26 KiB |
BIN
windows/manage/images/waas-do-fig2.png
Normal file
After Width: | Height: | Size: 23 KiB |
BIN
windows/manage/images/waas-do-fig3.png
Normal file
After Width: | Height: | Size: 9.6 KiB |
BIN
windows/manage/images/waas-do-fig4.png
Normal file
After Width: | Height: | Size: 59 KiB |
BIN
windows/manage/images/waas-overview-patch.png
Normal file
After Width: | Height: | Size: 119 KiB |
BIN
windows/manage/images/waas-overview-timeline.png
Normal file
After Width: | Height: | Size: 85 KiB |
BIN
windows/manage/images/waas-rings.png
Normal file
After Width: | Height: | Size: 34 KiB |
BIN
windows/manage/images/waas-sccm-fig1.png
Normal file
After Width: | Height: | Size: 28 KiB |
BIN
windows/manage/images/waas-sccm-fig10.png
Normal file
After Width: | Height: | Size: 56 KiB |
BIN
windows/manage/images/waas-sccm-fig11.png
Normal file
After Width: | Height: | Size: 43 KiB |
BIN
windows/manage/images/waas-sccm-fig12.png
Normal file
After Width: | Height: | Size: 53 KiB |
BIN
windows/manage/images/waas-sccm-fig2.png
Normal file
After Width: | Height: | Size: 65 KiB |
BIN
windows/manage/images/waas-sccm-fig3.png
Normal file
After Width: | Height: | Size: 145 KiB |
BIN
windows/manage/images/waas-sccm-fig4.png
Normal file
After Width: | Height: | Size: 25 KiB |
BIN
windows/manage/images/waas-sccm-fig5.png
Normal file
After Width: | Height: | Size: 14 KiB |
BIN
windows/manage/images/waas-sccm-fig6.png
Normal file
After Width: | Height: | Size: 26 KiB |
BIN
windows/manage/images/waas-sccm-fig7.png
Normal file
After Width: | Height: | Size: 18 KiB |
BIN
windows/manage/images/waas-sccm-fig8.png
Normal file
After Width: | Height: | Size: 29 KiB |
BIN
windows/manage/images/waas-sccm-fig9.png
Normal file
After Width: | Height: | Size: 36 KiB |
BIN
windows/manage/images/waas-strategy-fig1.png
Normal file
After Width: | Height: | Size: 56 KiB |
BIN
windows/manage/images/waas-wsus-fig1.png
Normal file
After Width: | Height: | Size: 65 KiB |
BIN
windows/manage/images/waas-wsus-fig10.png
Normal file
After Width: | Height: | Size: 70 KiB |
BIN
windows/manage/images/waas-wsus-fig11.png
Normal file
After Width: | Height: | Size: 59 KiB |
BIN
windows/manage/images/waas-wsus-fig12.png
Normal file
After Width: | Height: | Size: 99 KiB |
BIN
windows/manage/images/waas-wsus-fig13.png
Normal file
After Width: | Height: | Size: 62 KiB |
BIN
windows/manage/images/waas-wsus-fig14.png
Normal file
After Width: | Height: | Size: 52 KiB |
BIN
windows/manage/images/waas-wsus-fig15.png
Normal file
After Width: | Height: | Size: 24 KiB |
BIN
windows/manage/images/waas-wsus-fig16.png
Normal file
After Width: | Height: | Size: 58 KiB |
BIN
windows/manage/images/waas-wsus-fig17.png
Normal file
After Width: | Height: | Size: 136 KiB |
BIN
windows/manage/images/waas-wsus-fig18.png
Normal file
After Width: | Height: | Size: 82 KiB |
BIN
windows/manage/images/waas-wsus-fig19.png
Normal file
After Width: | Height: | Size: 78 KiB |
BIN
windows/manage/images/waas-wsus-fig2.png
Normal file
After Width: | Height: | Size: 57 KiB |
BIN
windows/manage/images/waas-wsus-fig20.png
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
windows/manage/images/waas-wsus-fig3.png
Normal file
After Width: | Height: | Size: 74 KiB |
BIN
windows/manage/images/waas-wsus-fig4.png
Normal file
After Width: | Height: | Size: 114 KiB |
BIN
windows/manage/images/waas-wsus-fig5.png
Normal file
After Width: | Height: | Size: 125 KiB |
BIN
windows/manage/images/waas-wsus-fig6.png
Normal file
After Width: | Height: | Size: 123 KiB |
BIN
windows/manage/images/waas-wsus-fig7.png
Normal file
After Width: | Height: | Size: 40 KiB |
BIN
windows/manage/images/waas-wsus-fig8.png
Normal file
After Width: | Height: | Size: 77 KiB |
BIN
windows/manage/images/waas-wsus-fig9.png
Normal file
After Width: | Height: | Size: 23 KiB |
BIN
windows/manage/images/waas-wufb-gp-broad.png
Normal file
After Width: | Height: | Size: 86 KiB |
BIN
windows/manage/images/waas-wufb-gp-cb2-settings.png
Normal file
After Width: | Height: | Size: 91 KiB |
BIN
windows/manage/images/waas-wufb-gp-cb2.png
Normal file
After Width: | Height: | Size: 41 KiB |
BIN
windows/manage/images/waas-wufb-gp-cbb1-settings.png
Normal file
After Width: | Height: | Size: 100 KiB |
BIN
windows/manage/images/waas-wufb-gp-cbb2-settings.png
Normal file
After Width: | Height: | Size: 101 KiB |
BIN
windows/manage/images/waas-wufb-gp-cbb2q-settings.png
Normal file
After Width: | Height: | Size: 67 KiB |
BIN
windows/manage/images/waas-wufb-gp-create.png
Normal file
After Width: | Height: | Size: 82 KiB |
BIN
windows/manage/images/waas-wufb-gp-edit-defer.png
Normal file
After Width: | Height: | Size: 153 KiB |
BIN
windows/manage/images/waas-wufb-gp-edit.png
Normal file
After Width: | Height: | Size: 38 KiB |
BIN
windows/manage/images/waas-wufb-gp-scope-cb2.png
Normal file
After Width: | Height: | Size: 60 KiB |
BIN
windows/manage/images/waas-wufb-gp-scope.png
Normal file
After Width: | Height: | Size: 80 KiB |
BIN
windows/manage/images/waas-wufb-intune-cb2.png
Normal file
After Width: | Height: | Size: 22 KiB |
BIN
windows/manage/images/waas-wufb-intune-cbb1.png
Normal file
After Width: | Height: | Size: 50 KiB |
BIN
windows/manage/images/waas-wufb-intune-cbb2.png
Normal file
After Width: | Height: | Size: 57 KiB |
BIN
windows/manage/images/waas-wufb-intune-step11.png
Normal file
After Width: | Height: | Size: 26 KiB |
BIN
windows/manage/images/waas-wufb-intune-step19.png
Normal file
After Width: | Height: | Size: 64 KiB |
BIN
windows/manage/images/waas-wufb-intune-step2.png
Normal file
After Width: | Height: | Size: 41 KiB |
BIN
windows/manage/images/waas-wufb-intune-step7.png
Normal file
After Width: | Height: | Size: 26 KiB |
BIN
windows/manage/images/wufb-config1.png
Normal file
After Width: | Height: | Size: 68 KiB |
BIN
windows/manage/images/wufb-config2.png
Normal file
After Width: | Height: | Size: 64 KiB |
BIN
windows/manage/images/wufb-config3.png
Normal file
After Width: | Height: | Size: 66 KiB |
BIN
windows/manage/images/wufb-do.png
Normal file
After Width: | Height: | Size: 64 KiB |
BIN
windows/manage/images/wufb-groups.png
Normal file
After Width: | Height: | Size: 138 KiB |
BIN
windows/manage/images/wufb-pause-feature.png
Normal file
After Width: | Height: | Size: 116 KiB |
BIN
windows/manage/images/wufb-qual.png
Normal file
After Width: | Height: | Size: 161 KiB |
BIN
windows/manage/images/wufb-sccm.png
Normal file
After Width: | Height: | Size: 85 KiB |
@ -30,11 +30,9 @@ Learn about managing and updating Windows 10.
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Cortana integration in your business or enterprise](manage-cortana-in-enterprise.md)</p></td>
|
||||
<td align="left"><p>The world’s first personal digital assistant helps get things done, even at work. Cortana includes powerful configuration options specifically to optimize for unique small to medium-sized business and enterprise environments.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Manage corporate devices](manage-corporate-devices.md)</p></td>
|
||||
<td align="left"><p>You can use the same management tools to manage all device types running Windows 10 : desktops, laptops, tablets, and phones. And your current management tools, such as Group Policy, Windows Management Instrumentation (WMI), PowerShell scripts, Orchestrator runbooks, System Center tools, and so on, will continue to work for Windows 10 on desktop editions.</p></td>
|
||||
<td align="left"><p>The world’s first personal digital assistant helps users get things done, even at work. Cortana includes powerful configuration options specifically to optimize for unique small to medium-sized business and enterprise environments.</p></td></tr>
|
||||
<tr><td align="left"><p>[Manage corporate devices](manage-corporate-devices.md)</p></td>
|
||||
<td align="left"><p>You can use the same management tools to manage all device types running Windows 10: desktops, laptops, tablets, and phones. And your current management tools, such as Group Policy, Windows Management Instrumentation (WMI), PowerShell scripts, Orchestrator runbooks, System Center tools, and so on, will continue to work for Windows 10 on desktop editions.</p></td>
|
||||
</tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Windows Spotlight on the lock screen](windows-spotlight.md)</p></td>
|
||||
@ -44,6 +42,7 @@ Learn about managing and updating Windows 10.
|
||||
<td align="left"><p>[Manage Windows 10 Start layout options](windows-10-start-layout-options-and-policies.md)</p></td>
|
||||
<td align="left"><p>Organizations might want to deploy a customized Start screen and menu to devices running Windows 10 Enterprise or Windows 10 Education. A standard Start layout can be useful on devices that are common to multiple users and devices that are locked down for specialized purposes.</p></td>
|
||||
</tr>
|
||||
<tr><td><p>[Create mandatory user profiles](mandatory-user-profile.md)</p></td><td><p>Mandatory user profiles are useful when standardization is important, such as on a kiosk device or in educational settings.</p></td></tr>
|
||||
<tr class="odd">
|
||||
<td align="left"><p>[Lock down Windows 10](lock-down-windows-10.md)</p></td>
|
||||
<td align="left"><p>Enterprises often need to manage how people use corporate devices. Windows 10 provides a number of features and methods to help you lock down specific parts of a Windows 10 device.</p></td>
|
||||
@ -56,10 +55,7 @@ Learn about managing and updating Windows 10.
|
||||
<td align="left"><p>[Configure devices without MDM](configure-devices-without-mdm.md)</p></td>
|
||||
<td align="left"><p>Create a runtime provisioning package to apply settings, profiles, and file assets to a device running Windows 10 Pro, Windows 10 Enterprise, Windows 10 Education, Windows 10 Mobile, or Windows 10 Mobile Enterprise.</p></td>
|
||||
</tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Windows 10 servicing options](introduction-to-windows-10-servicing.md)</p></td>
|
||||
<td align="left"><p>This article describes the new servicing options available in Windows 10, Windows 10 Mobile, and Windows 10 IoT Core (IoT Core) and how they enable enterprises to keep their devices current with the latest feature upgrades. It also covers related topics, such as how enterprises can make better use of Windows Update, and what the new servicing options mean for support lifecycles.</p></td>
|
||||
</tr>
|
||||
<tr><td>[Windows 10 servicing options](introduction-to-windows-10-servicing.md)</td><td>This article describes the new servicing options available in Windows 10, Windows 10 Mobile, and Windows 10 IoT Core (IoT Core) and how they enable enterprises to keep their devices current with the latest feature upgrades. It also covers related topics, such as how enterprises can make better use of Windows Update, and what the new servicing options mean for support lifecycles.</td></tr>
|
||||
<tr class="even">
|
||||
<td align="left"><p>[Application Virtualization for Windows (App-V)](appv-for-windows.md)</p></td>
|
||||
<td align="left"><p>When you deploy Application Virtualization (App-V) in your orgnazation, you can deliver Win32 applications to users as virtual applications. Virtual applications are installed on centrally managed servers and delivered to users as a service – in real time and on as as-needed basis. Users launch virtual applications from familiar access points, including the Windows Store, and interact with them as if they were installed locally.</p></td>
|
||||
|
@ -15,6 +15,8 @@ localizationpriority: high
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare).
|
||||
|
||||
The world’s first personal digital assistant helps users get things done, even at work. Cortana includes powerful configuration options specifically to optimize for unique small to medium-sized business and enterprise environments.
|
||||
|
||||
## Cortana integration with Office 365
|
||||
|
@ -17,6 +17,8 @@ localizationpriority: medium
|
||||
- Windows 10
|
||||
- Windows 10 Mobile
|
||||
|
||||
>Learn more about what features and functionality are supported in each Windows edition at [Compare Windows 10 Editions](https://www.microsoft.com/en-us/WindowsForBusiness/Compare).
|
||||
|
||||
Wi-Fi Sense learns about open Wi-Fi hotspots your Windows PC or Windows phone connects to by collecting information about the network, like whether the open Wi-Fi network has a high-quality connection to the Internet. By using that information from your device and from other Wi-Fi Sense customers' devices too, Wi-Fi Sense builds a database of these high-quality networks. When you’re in range of one of these Wi-Fi hotspots, you automatically get connected to it.
|
||||
|
||||
The initial settings for Wi-Fi Sense are determined by the options you chose when you first set up your PC with Windows 10.
|
||||
|
171
windows/manage/mandatory-user-profile.md
Normal file
@ -0,0 +1,171 @@
|
||||
---
|
||||
title: Create mandatory user profiles (Windows 10)
|
||||
description: A mandatory user profile is a special type of pre-configured roaming user profile that administrators can use to specify settings for users.
|
||||
keywords: [".man","ntuser"]
|
||||
ms.prod: w10
|
||||
ms.mktglfcycl: manage
|
||||
ms.sitesec: library
|
||||
author: jdeckerMS
|
||||
---
|
||||
|
||||
# Create mandatory user profiles
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
> [!NOTE]
|
||||
> When a mandatory profile is applied to a PC running Windows 10, version 1511, some features such as Universal Windows Platform (UWP) apps, the Start menu, Cortana, and Search, will not work correctly. This will be fixed in a future update.
|
||||
|
||||
A mandatory user profile is a roaming user profile that has been pre-configured by an administrators to specify settings for users. Settings commonly defined in a mandatory profile include (but are not limited to): icons that appear on the desktop, desktop backgrounds, user preferences in Control Panel, printer selections, and more. Configuration changes made during a user's session that are normally saved to a roaming user profile are not saved when a mandatory user profile is assigned.
|
||||
|
||||
Mandatory user profiles are useful when standardization is important, such as on a kiosk device or in educational settings. Only system administrators can make changes to mandatory user profiles.
|
||||
|
||||
When the server that stores the mandatory profile is unavailable, such as when the user is not connected to the corporate network, users with mandatory profiles can sign in with the locally cached copy of the mandatory profile, if one exists. Otherwise, the user will be signed in with a temporary profile.
|
||||
|
||||
User profiles become mandatory profiles when the administrator renames the NTuser.dat file (the registry hive) of each user's profile in the file system of the profile server from `NTuser.dat` to `NTuser.man`. The `.man` extension causes the user profile to be a read-only profile.
|
||||
|
||||
<span id="extension"/>
|
||||
## Profile extension for each Windows version
|
||||
|
||||
The name of the folder in which you store the mandatory profile must use the correct extension for the operating system it will be applied to. The following table lists the correct extension for each operating system version.
|
||||
|
||||
| Client operating system version | Server operating system version | Profile extension |
|
||||
| --- | --- | --- |
|
||||
| Windows XP | Windows Server 2003 </br>Windows Server 2003 R2 | none |
|
||||
| Windows Vista</br>Windows 7 | Windows Server 2008</br>Windows Server 2008 R2 | v2 |
|
||||
| Windows 8 | Windows Server 2012 | v3 |
|
||||
| Windows 8.1 | Windows Server 2012 R2 | v4 |
|
||||
| Windows 10, versions 1507 and 1511 | Windows Server 2016 | v5 |
|
||||
| Windows 10, version 1607 (also known as the Anniversary Update) | N/A | v6 |
|
||||
|
||||
For more information, see [Deploy Roaming User Profiles, Appendix B](https://technet.microsoft.com/library/jj649079.aspx) and [Roaming user profiles versioning in Windows 10 and Windows Server Technical Preview](https://support.microsoft.com/kb/3056198).
|
||||
|
||||
## How to create a mandatory user profile
|
||||
|
||||
First, you create a default user profile with the customizations that you want, run Sysprep with CopyProfile set to **True** in the answer file, copy the customized default user profile to a network share, and then you rename the profile to make it mandatory.
|
||||
|
||||
**To create a default user profile**
|
||||
|
||||
1. Sign in to a computer running Windows 10 as a member of the local Administrator group. Do not use a domain account.
|
||||
|
||||
> [!NOTE]
|
||||
> Use a lab or extra computer running a clean installation of Windows 10 to create a default user profile. Do not use a computer that is required for business (that is, a production computer). This process removes all domain accounts from the computer, including user profile folders.
|
||||
|
||||
2. Configure the computer settings that you want to include in the user profile. For example, you can configure settings for the desktop background, uninstall default apps, install line-of-business apps, and so on.
|
||||
|
||||
>[!NOTE]
|
||||
>Unlike previous versions of Windows, you cannot apply a Start and taskbar layout using a mandatory profile. For alternative methods for customizing the Start menu and taskbar, see [Related topics](#related-topics).
|
||||
|
||||
3. [Create an answer file (Unattend.xml)](https://msdn.microsoft.com/library/windows/hardware/dn915085.aspx) that sets the [CopyProfile](https://msdn.microsoft.com/library/windows/hardware/dn922656.aspx) parameter to **True**. The CopyProfile parameter causes Sysprep to copy the currently signed-on user’s profile folder to the default user profile. You can use [Windows System Image Manager](https://msdn.microsoft.com/library/windows/hardware/dn922445.aspx), which is part of the Windows Assessment and Deployment Kit (ADK) to create the Unattend.xml file.
|
||||
|
||||
3. Use the [Remove-AppxProvisionedPackage](https://technet.microsoft.com/library/dn376476%28v=wps.620%29.aspx) cmdlet in Windows PowerShell to uninstall the following applications:
|
||||
|
||||
- Microsoft.windowscommunicationsapps_8wekyb3d8bbwe
|
||||
- Microsoft.BingWeather_8wekyb3d8bbwe
|
||||
- Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
|
||||
- Microsoft.Getstarted_8wekyb3d8bbwe
|
||||
- Microsoft.Windows.Photos_8wekyb3d8bbwe
|
||||
- Microsoft.WindowsCamera_8wekyb3d8bbwe
|
||||
- Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe
|
||||
- Microsoft.WindowsStore_8wekyb3d8bbwe
|
||||
- Microsoft.XboxApp_8wekyb3d8bbwe
|
||||
- Microsoft.XboxIdentityProvider_8wekyb3d8bbwe
|
||||
- Microsoft.ZuneMusic_8wekyb3d8bbwe
|
||||
|
||||
>[!NOTE]
|
||||
>Uninstalling these apps will decrease sign-in time. If your deployment needs any of these apps, you can leave them installed.
|
||||
|
||||
3. At a command prompt, type the following command and press **ENTER**.
|
||||
|
||||
`sysprep /oobe /reboot /generalize /unattend:unattend.xml`
|
||||
|
||||
(Sysprep.exe is located at: C:\Windows\System32\sysprep. By default, Sysprep looks for unattend.xml in this same folder.)
|
||||
|
||||
>[!TIP]
|
||||
>If you receive an error message that says "Sysprep was not able to validate your Windows installation", open %WINDIR%\System32\Sysprep\Panther\setupact.log and look for an entry like the following:
|
||||
|
||||
>
|
||||
|
||||
>Use the [Remove-AppxProvisionedPackage](https://technet.microsoft.com/library/dn376476%28v=wps.620%29.aspx) cmdlet in Windows PowerShell to uninstall the app that is listed in the log.
|
||||
|
||||
5. The sysprep process reboots the PC and starts at the first-run experience screen. Complete the set up, and then sign in to the computer using an account that has local administrator privileges.
|
||||
|
||||
6. Right-click Start, go to **Control Panel** (view by large or small icons) > **System** > **Advanced system settings**, and click **Settings** in the **User Profiles** section.
|
||||
|
||||
7. In **User Profiles**, click **Default Profile**, and then click **Copy To**.
|
||||
|
||||

|
||||
|
||||
8. In **Copy To**, under **Permitted to use**, click **Change**.
|
||||
|
||||

|
||||
|
||||
9. In **Select User or Group**, in the **Enter the object name to select** field, type `everyone`, click **Check Names**, and then click **OK**.
|
||||
|
||||
10. In **Copy To**, in the **Copy profile to** field, enter the path and folder name where you want to store the mandatory profile. The folder name must use the correct [extension](#extension) for the operating system version. For example, the folder name must end with “.v6” to identify it as a user profile folder for Windows 10, version 1607.
|
||||
|
||||
- If the device is joined to the domain and you are signed in with an account that has permissions to write to a shared folder on the network, you can enter the shared folder path.
|
||||
- If the device is not joined to the domain, you can save the profile locally and then copy it to the shared folder location.
|
||||
|
||||

|
||||
|
||||
9. Click **OK** to copy the default user profile.
|
||||
|
||||
|
||||
**To make the user profile mandatory**
|
||||
|
||||
|
||||
3. In File Explorer, open the folder where you stored the copy of the profile.
|
||||
|
||||
>[!NOTE]
|
||||
>If the folder is not displayed, click **View** > **Options** > **Change folder and search options**. On the **View** tab, select **Show hidden files and folders**, clear **Hide protected operating system files**, click **Yes** to confirm that you want to show operating system files, and then click **OK** to save your changes.
|
||||
|
||||
1. Rename `Ntuser.dat` to `Ntuser.man`.
|
||||
|
||||
## How to apply a mandatory user profile to users
|
||||
|
||||
In a domain, you modify properties for the user account to point to the mandatory profile in a shared folder residing on the server.
|
||||
|
||||
**To apply a mandatory user profile to users**
|
||||
|
||||
1. Open **Active Directory Users and Computers** (dsa.msc).
|
||||
|
||||
2. Navigate to the user account that you will assign the mandatory profile to.
|
||||
|
||||
3. Right-click the user name and open **Properties**.
|
||||
|
||||
4. On the **Profile** tab, in the **Profile path** field, enter the path to the shared folder without the extension. For example, if the folder name is \\\\*server*\profile.v6, you would enter \\\\*server*\profile.
|
||||
|
||||
5. Click **OK**.
|
||||
|
||||
It may take some time for this change to replicate to all domain controllers.
|
||||
|
||||
|
||||
|
||||
## Apply policies to improve sign-in time
|
||||
|
||||
When a user is configured with a mandatory profile, Windows 10 starts as though it was the first sign-in each time the user signs in. To improve sign-in performance for users with mandatory user profiles, apply the following Group Policy settings.
|
||||
|
||||
- Computer Configuration > Administrative Templates > System > Logon > **Show first sign-in animation** = Disabled
|
||||
- Computer Configuration > Administrative Templates > Windows Components > Search > **Allow Cortana** = Disabled
|
||||
- Computer Configuration > Administrative Templates > Windows Components > Cloud Content > **Turn off Microsoft consumer experience** = Enabled
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Windows 10 Start layout and taskbar options](windows-10-start-layout-options-and-policies.md)
|
||||
- [Lock down Windows 10 to specific apps](lock-down-windows-10-to-specific-apps.md)
|
||||
- [Windows Spotlight on the lock screen](windows-spotlight.md)
|
||||
- [Configure devices without MDM](configure-devices-without-mdm.md)
|
||||
|
||||
|
||||
|
@ -14,6 +14,7 @@ author: TrudyHa
|
||||
This topic lists new and updated topics in the [Plan for Windows 10 deployment](index.md) documentation for [Windows 10 and Windows 10 Mobile](../index.md).
|
||||
|
||||
|
||||
|
||||
## RELEASE: Windows 10, version 1607
|
||||
|
||||
The topics in this library have been updated for Windows 10, version 1607 (also known as the Anniversary Update).
|
||||
|
@ -15,11 +15,11 @@ Windows 10 provides new deployment capabilities, scenarios, and tools by buildi
|
||||
## In this section
|
||||
|Topic |Description |
|
||||
|------|------------|
|
||||
|[Windows 10 servicing options](windows-10-servicing-options.md) |Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process. |
|
||||
| [Windows 10 servicing overview](windows-10-servicing-options.md) | Windows 10 provides a new model for organizations to deploy and upgrade Windows by providing updates to features and capabilities through a continual process. |
|
||||
|[Windows 10 deployment considerations](windows-10-deployment-considerations.md) |There are new deployment options in Windows 10 that help you simplify the deployment process and automate migration of existing settings and applications. |
|
||||
|[Windows 10 compatibility](windows-10-compatibility.md) |Windows 10 will be compatible with most existing PC hardware; most devices running Windows 7, Windows 8, or Windows 8.1 will meet the requirements for Windows 10. |
|
||||
|[Windows 10 infrastructure requirements](windows-10-infrastructure-requirements.md) |There are specific infrastructure requirements to deploy and manage Windows 10 that should be in place prior to significant Windows 10 deployments within your organization. |
|
||||
|[Windows Update for Business](windows-update-for-business.md) |Get an overview of how you can implement and deploy a Windows Update for Business solution and how to maintain enrolled systems. |
|
||||
| [Windows Update for Business](windows-update-for-business.md) | Get an overview of how you can implement and deploy a Windows Update for Business solution and how to maintain enrolled systems. |
|
||||
|[Windows To Go: feature overview](windows-to-go-overview.md) |Windows To Go is a feature in Windows 10 Enterprise and Windows 10 Education that enables the creation of a Windows To Go workspace that can be booted from a USB-connected external drive on PCs. |
|
||||
|[Application Compatibility Toolkit (ACT) Technical Reference](act-technical-reference.md) |The Microsoft® Application Compatibility Toolkit (ACT) helps you determine whether the applications, devices, and computers in your organization are compatible with versions of the Windows® operating system. |
|
||||
|[Change history for Plan for Windows 10 deployment](change-history-for-plan-for-windows-10-deployment.md) |This topic lists new and updated topics in the Plan for Windows 10 deployment documentation for [Windows 10 and Windows 10 Mobile](../index.md). |
|
||||
@ -36,8 +36,3 @@ Windows 10 provides new deployment capabilities, scenarios, and tools by buildi
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|