From 4bb96da1142b39e4ef862b749f824619862d0377 Mon Sep 17 00:00:00 2001 From: Raffael Date: Thu, 12 Dec 2019 23:36:10 +0100 Subject: [PATCH 01/10] Connect-MSGraph should be used The other command does not exist anymore in the current version of the module. Connect-MSGraph needs to be used instead. If you run the command mentioned afterwards "Get-AutopilotProfile" then you even get in the error message the sentence "please connect first with Connect-MSGraph". --- windows/deployment/windows-autopilot/existing-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/existing-devices.md b/windows/deployment/windows-autopilot/existing-devices.md index e762a53ed9..f0281e329a 100644 --- a/windows/deployment/windows-autopilot/existing-devices.md +++ b/windows/deployment/windows-autopilot/existing-devices.md @@ -74,7 +74,7 @@ See the following examples. - In the following command, replace the example user principal name for Azure authentication (admin@M365x373186.onmicrosoft.com) with your user account. Be sure that the user account you specify has sufficient administrative rights. ```powershell - Connect-AutopilotIntune -user admin@M365x373186.onmicrosoft.com + Connect-MSGraph ``` The password for your account will be requested using a standard Azure AD form. Type your password and then click **Sign in**.
See the following example: From c3e67b75c56195e24a24d96c79a0d65fd18198d7 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Sat, 21 Dec 2019 18:56:22 +0500 Subject: [PATCH 02/10] CSV file verification information addition As mentioned by the user, I added a note regarding the CSV file. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5510 --- windows/deployment/windows-autopilot/add-devices.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/windows/deployment/windows-autopilot/add-devices.md b/windows/deployment/windows-autopilot/add-devices.md index 096ebe1151..9187f9991a 100644 --- a/windows/deployment/windows-autopilot/add-devices.md +++ b/windows/deployment/windows-autopilot/add-devices.md @@ -63,6 +63,9 @@ Note that the hardware hash also contains details about when it was generated, s Starting with System Center Configuration Manager current branch version 1802, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file. +>[!Note] +>Before uploading the CSV file on intune, please make sure that 1st row contains Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). + ### Collecting the hardware ID from existing devices using PowerShell The hardware ID, or hardware hash, for an existing device is available through Windows Management Instrumentation (WMI), as long as that device is running Windows 10 version 1703 or later. To help gather this information, as well as the serial number of the device (useful to see at a glance the machine to which it belongs), a PowerShell script called [Get-WindowsAutoPilotInfo.ps1 has been published to the PowerShell Gallery website](https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo). From df2ae5d78bb753a046e626385a92582c64730022 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Sun, 22 Dec 2019 21:35:10 +0500 Subject: [PATCH 03/10] Update windows/deployment/windows-autopilot/add-devices.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/windows-autopilot/add-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/add-devices.md b/windows/deployment/windows-autopilot/add-devices.md index 9187f9991a..eb0e05cb61 100644 --- a/windows/deployment/windows-autopilot/add-devices.md +++ b/windows/deployment/windows-autopilot/add-devices.md @@ -63,7 +63,7 @@ Note that the hardware hash also contains details about when it was generated, s Starting with System Center Configuration Manager current branch version 1802, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file. ->[!Note] +> [!Note] >Before uploading the CSV file on intune, please make sure that 1st row contains Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). ### Collecting the hardware ID from existing devices using PowerShell From 40f978edf603f8e71af18182f67b1b33ed6ada71 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Sun, 22 Dec 2019 21:35:19 +0500 Subject: [PATCH 04/10] Update windows/deployment/windows-autopilot/add-devices.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/windows-autopilot/add-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/add-devices.md b/windows/deployment/windows-autopilot/add-devices.md index eb0e05cb61..4952f77f8f 100644 --- a/windows/deployment/windows-autopilot/add-devices.md +++ b/windows/deployment/windows-autopilot/add-devices.md @@ -64,7 +64,7 @@ Note that the hardware hash also contains details about when it was generated, s Starting with System Center Configuration Manager current branch version 1802, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file. > [!Note] ->Before uploading the CSV file on intune, please make sure that 1st row contains Device Serial Number,Windows Product ID,Hardware Hash,Group Tag,Assigned User. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). +> Before uploading the CSV file on intune, please make sure that 1st row contains Device Serial Number, Windows Product ID, Hardware Hash, Group Tag, Assigned User. If there is any header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). ### Collecting the hardware ID from existing devices using PowerShell From 7ce5166c4e0832247a33cece6931d9fcbaf9ab8b Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Mon, 23 Dec 2019 11:58:01 +0500 Subject: [PATCH 05/10] Update windows/deployment/windows-autopilot/add-devices.md Co-Authored-By: Trond B. Krokli <38162891+illfated@users.noreply.github.com> --- windows/deployment/windows-autopilot/add-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/add-devices.md b/windows/deployment/windows-autopilot/add-devices.md index 4952f77f8f..86c2c3e316 100644 --- a/windows/deployment/windows-autopilot/add-devices.md +++ b/windows/deployment/windows-autopilot/add-devices.md @@ -64,7 +64,7 @@ Note that the hardware hash also contains details about when it was generated, s Starting with System Center Configuration Manager current branch version 1802, the hardware hashes for existing Windows 10 version 1703 and higher devices are automatically collected by Configuration Manager. See the [What’s new in version 1802](https://docs.microsoft.com/sccm/core/plan-design/changes/whats-new-in-version-1802#report-on-windows-autopilot-device-information) documentation for more details. The hash information can be extracted from Configuration Manager into a CSV file. > [!Note] -> Before uploading the CSV file on intune, please make sure that 1st row contains Device Serial Number, Windows Product ID, Hardware Hash, Group Tag, Assigned User. If there is any header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). +> Before uploading the CSV file on Intune, please make sure that the first row contains the device serial number, Windows product ID, hardware hash, group tag, and assigned user. If there is header information on the top of CSV file, please delete that header information. See details at [Enroll Windows devices in Intune](https://docs.microsoft.com/intune/enrollment/enrollment-autopilot). ### Collecting the hardware ID from existing devices using PowerShell From b99e1b5f1c39496fc7e16556575d2fd78903e3e0 Mon Sep 17 00:00:00 2001 From: illfated Date: Fri, 27 Dec 2019 01:14:06 +0100 Subject: [PATCH 06/10] Windows 2 Go/Kingston IronKey USB: URL updated Based on the suggestion from @jvsam in issue ticket #5562 (Erreur 404), all the 3 links used for Kingston IronKey USB drives should point to the same Kingston DataTraveler Workspace+B2:M22 support page https://www.kingston.com/support/technical/products?model=dtws Thanks to Efflamm for reporting the link as broken (error 404). Changes proposed: - Replace the 3 different go.microsoft.com/fwlink/ URLs with a common link pointing to the DataTraveler Workspace+B2:M22 support page. issue ticket closure or reference: Closes #5562 --- windows/deployment/planning/windows-to-go-overview.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/windows/deployment/planning/windows-to-go-overview.md b/windows/deployment/planning/windows-to-go-overview.md index ba83d6224b..d162aa111d 100644 --- a/windows/deployment/planning/windows-to-go-overview.md +++ b/windows/deployment/planning/windows-to-go-overview.md @@ -92,9 +92,9 @@ As of the date of publication, the following are the USB drives currently certif > [!WARNING] > Using a USB drive that has not been certified is not supported. -- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://go.microsoft.com/fwlink/p/?LinkId=618714)) -- IronKey Workspace W500 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w500.html](https://go.microsoft.com/fwlink/p/?LinkId=618717)) -- IronKey Workspace W300 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w300.html](https://go.microsoft.com/fwlink/p/?LinkId=618718)) +- IronKey Workspace W700 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w700.html](https://www.kingston.com/support/technical/products?model=dtws)) +- IronKey Workspace W500 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w500.html](https://www.kingston.com/support/technical/products?model=dtws)) +- IronKey Workspace W300 ([http://www.ironkey.com/windows-to-go-drives/ironkey-workspace-w300.html](https://www.kingston.com/support/technical/products?model=dtws)) - Kingston DataTraveler Workspace for Windows To Go ([http://www.kingston.com/wtg/](https://go.microsoft.com/fwlink/p/?LinkId=618719)) - Spyrus Portable Workplace ([http://www.spyruswtg.com/](https://go.microsoft.com/fwlink/p/?LinkId=618720)) From d0ff0b40fe9a1d1eaa5843c967c1007a82958fe9 Mon Sep 17 00:00:00 2001 From: Jack Lin Date: Sun, 29 Dec 2019 11:08:37 +1100 Subject: [PATCH 07/10] Fix spelling mistake in open-windows-firewall-with-advanced-security.md --- .../open-windows-firewall-with-advanced-security.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/windows-firewall/open-windows-firewall-with-advanced-security.md b/windows/security/threat-protection/windows-firewall/open-windows-firewall-with-advanced-security.md index 17d43619ee..cbf3fd9257 100644 --- a/windows/security/threat-protection/windows-firewall/open-windows-firewall-with-advanced-security.md +++ b/windows/security/threat-protection/windows-firewall/open-windows-firewall-with-advanced-security.md @@ -31,7 +31,7 @@ To complete this procedure, you must be a member of the Administrators group. Fo ## To open Windows Defender Firewall using the UI -Click Start, type **Windows Defender Firewall**, and the press ENTER. +Click Start, type **Windows Defender Firewall**, and then press ENTER. ## To open Windows Defender Firewall from a command prompt From 42a566b80d15c31a10da223519b79b93778ea8cc Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Mon, 30 Dec 2019 00:28:39 +0500 Subject: [PATCH 08/10] Command Upgrade With recent changes in how autopilot JSON file creation works, the command in action is Connect-MSGraph and has been updated in the doc. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5443 --- windows/deployment/windows-autopilot/existing-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/existing-devices.md b/windows/deployment/windows-autopilot/existing-devices.md index 9f4cdcfc25..d1699e9473 100644 --- a/windows/deployment/windows-autopilot/existing-devices.md +++ b/windows/deployment/windows-autopilot/existing-devices.md @@ -74,7 +74,7 @@ See the following examples. - In the following command, replace the example user principal name for Azure authentication (admin@M365x373186.onmicrosoft.com) with your user account. Be sure that the user account you specify has sufficient administrative rights. ```powershell - Connect-AutopilotIntune -user admin@M365x373186.onmicrosoft.com + Connect-MSGraph ``` The password for your account will be requested using a standard Azure AD form. Type your password and then click **Sign in**.
See the following example: From 4d3377d16814dd2b52d272cf4312cb8f2a3eabe4 Mon Sep 17 00:00:00 2001 From: ImranHabib <47118050+joinimran@users.noreply.github.com> Date: Mon, 30 Dec 2019 00:37:17 +0500 Subject: [PATCH 09/10] Broken Link Upgrade A broken link has been updated. Problem: https://github.com/MicrosoftDocs/windows-itpro-docs/issues/5752 --- .../threat-protection/intelligence/prevent-malware-infection.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/security/threat-protection/intelligence/prevent-malware-infection.md b/windows/security/threat-protection/intelligence/prevent-malware-infection.md index 7bce69882c..dd9d229a58 100644 --- a/windows/security/threat-protection/intelligence/prevent-malware-infection.md +++ b/windows/security/threat-protection/intelligence/prevent-malware-infection.md @@ -93,7 +93,7 @@ Microsoft provides comprehensive security capabilities that help protect against * [Automatic Microsoft updates](https://support.microsoft.com/help/12373/windows-update-faq) keeps software up-to-date to get the latest protections. -* [Controlled folder access](https://docs.microsoft.com/windows/security/threat-protection/windows-defender-exploit-guard/enable-controlled-folders-exploit-guard) stops ransomware in its tracks by preventing unauthorized access to your important files. Controlled folder access locks down folders, allowing only authorized apps to access files. Unauthorized apps, including ransomware and other malicious executable files, DLLs, and scripts are denied access. +* [Controlled folder access](https://docs.microsoft.com/windows/security/threat-protection/microsoft-defender-atp/enable-controlled-folders) stops ransomware in its tracks by preventing unauthorized access to your important files. Controlled folder access locks down folders, allowing only authorized apps to access files. Unauthorized apps, including ransomware and other malicious executable files, DLLs, and scripts are denied access. * [Microsoft Edge](https://docs.microsoft.com/microsoft-edge/deploy/index) browser protects against threats such as ransomware by preventing exploit kits from running. By using [Windows Defender SmartScreen](https://docs.microsoft.com/microsoft-edge/deploy/index), Microsoft Edge blocks access to malicious websites. From 9e3b64e80a2668f27fa2a582879657bb7bfc10c8 Mon Sep 17 00:00:00 2001 From: Mark Aldridge Date: Mon, 30 Dec 2019 16:05:34 +1100 Subject: [PATCH 10/10] Updated PowerShell command #5443 Connect-AutopilotIntune has been removed from the module. For more info see https://oofhours.com/2019/11/02/whats-new-with-the-windowsautopilotintune-powershell-module/ --- windows/deployment/windows-autopilot/existing-devices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopilot/existing-devices.md b/windows/deployment/windows-autopilot/existing-devices.md index 9f4cdcfc25..0fd535d10e 100644 --- a/windows/deployment/windows-autopilot/existing-devices.md +++ b/windows/deployment/windows-autopilot/existing-devices.md @@ -74,7 +74,7 @@ See the following examples. - In the following command, replace the example user principal name for Azure authentication (admin@M365x373186.onmicrosoft.com) with your user account. Be sure that the user account you specify has sufficient administrative rights. ```powershell - Connect-AutopilotIntune -user admin@M365x373186.onmicrosoft.com + Connect-MSGraph -user admin@M365x373186.onmicrosoft.com ``` The password for your account will be requested using a standard Azure AD form. Type your password and then click **Sign in**.
See the following example: