profile
viewpoint
Greg Lindsay greg-lindsay Microsoft

MicrosoftDocs/memdocs 28

Enable Public Contributions

greg-lindsay/IntuneDocs 0

Public repo for Intune content in OPS

greg-lindsay/VSO-7442819 0

Use PXE to deploy Windows over the network with System Center Configuration Manager

greg-lindsay/windowsserverdocs 0

Public content repository for Windows Server 2016 content.

pull request commentMicrosoftDocs/windowsserverdocs

Update anycast.md

#sign-off @eross-msft

greg-lindsay

comment created time in a day

PR opened MicrosoftDocs/windowsserverdocs

Update anycast.md

This is an update per customer issue to add some missing steps. https://github.com/MicrosoftDocs/windowsserverdocs/issues/4918

+25 -13

0 comment

1 changed file

pr created time in a day

create barnchgreg-lindsay/windowsserverdocs

branch : update1

created branch time in a day

fork greg-lindsay/windowsserverdocs

Public content repository for Windows Server 2016 content.

fork in a day

issue commentMicrosoftDocs/windowsserverdocs

Corrections in BGP Peering and DNS IPs

Thanks for checking these steps.

  1. I had this configuration (including the default gateways) but apparently missed adding it to the article.
  2. The problem is that you cannot have DC002 configured as DNS on DC001 until DC002 exists. So the first domain controller will need to specify itself as DNS (DC001). You're right that DC002 needs to use DC001 to find the domain, but afterward you can switch it back to DC002. After both are added it doesn't matter which is used for DNS on either one - because they are authoritative and don't use their resolver settings to answer queries. But I should add a note saying to use DC001 at first when setting up DC002.
  3. Thanks, I see that the Remote Access Windows PowerShell module is one of the management tools that needs to be installed for the command to work.
  4. Thanks again I did add this at one point and I apparently forgot I did it.

PS C:> get-bgppeer

PeerName LocalIPAddress PeerIPAddress PeerASN OperationMode ConnectivityStatus


DC001 10.10.10.254 10.10.10.1 65511 Mixed Connected DC002 10.10.10.254 10.10.10.2 65511 Mixed Connected

  1. I never had to adjust the firewall, but I'll add a note to check this.
TomicaKaniski

comment created time in 2 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I've been told that any failure in a low level component up to completion of the Windows sign-in process can cause a 0x40017 failure. This often requires a kernel debugger to figure out what is going on. But maybe the system logs will help.

Sumitdhiman

comment created time in 4 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I'm told that kernelact.log warnings are not fatal and won't cause a rollback. However, you should check the System event logs. 40017 can occur due to a number of reasons so it's not extremely easy to troubleshoot.

Sumitdhiman

comment created time in 5 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

The first step to fix this error code is to perform a clean boot. Have they tried that? Also remove 3rd party antivirus or encryption if it is being used. This is also a common code when Citrix VDA is used - is that the case here?

Sumitdhiman

comment created time in 5 days

issue closedMicrosoftDocs/memdocs

Spelling error

Under Prerequisite section, the 4th bullet has "Physical devices with Ethernet connectivity are required to perform pre-provisiong. "

"provisioning" needs fixing...


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 5 days

JScottEvans

issue commentMicrosoftDocs/memdocs

Spelling error

Fixed, thanks! The change will publish later today

JScottEvans

comment created time in 5 days

issue closedMicrosoftDocs/memdocs

Blog attaching

[Enter feedback here] Would like to see a Blog section so blogs such as https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/trying-out-autopilot-hybrid-join-over-vpn-in-your-azure-lab/ba-p/1606723 can be easily discovered and shared.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 6 days

felizondojr

issue commentMicrosoftDocs/memdocs

Blog attaching

Many articles have a "Related topics" section which is better than a blogs section because all related topics are not always in blogs. The links added here would need to be approved and kept up to date, which is possible using the external author editing capability in GitHub. For example, if someone posted a non-Microsoft blog link this would need to be unapproved because we are not supposed to link to external blogs.

I'll add a "Related topics" section to this article so that it can be edited, and I'll add the link above. Thanks!

felizondojr

comment created time in 6 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

@Sumitdhiman are you there?

Sumitdhiman

comment created time in 6 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

Ping

Sumitdhiman

comment created time in 7 days

issue commentMicrosoftDocs/memdocs

What role is required to upload Autopilot devices?

Below is what I've added

Device enrollment can be done by an Intune Administrator or a Policy and Profile Manager. You can also create a custom Autopilot device manager role by using Role Based Access Control and creating this role. Autopilot device management only requires that you enable all permissions under Enrollment programs, with the exception of the four token management options.

scheblein

comment created time in 8 days

issue closedMicrosoftDocs/memdocs

What role is required to upload Autopilot devices?

What role is required to upload Autopilot devices?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 8 days

scheblein

issue commentMicrosoftDocs/memdocs

What role is required to upload Autopilot devices?

I'll add this detail to the topic.

scheblein

comment created time in 8 days

issue commentMicrosoftDocs/memdocs

What role is required to upload Autopilot devices?

Generally this is done by an Intune Administrator, but you can create a custom role that only includes the enrollment permissions. See https://oofhours.com/2019/08/13/creating-a-windows-autopilot-role-in-intune/

scheblein

comment created time in 8 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

These both look to be the same log file (from panther). Can you upload setupact.log from panther and rollback?

Sumitdhiman

comment created time in 8 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

The links above seem to be bad. They don't match the text. I'll try copying the text instead of using the link.

Sumitdhiman

comment created time in 8 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

Any update?

Sumitdhiman

comment created time in 8 days

issue closedMicrosoftDocs/memdocs

Expand Acronym EAS

In the note at the bottom it mentions EAS policies - are these Exchange ActiveSync policies or something else? Why would they be used with Intune MDM?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 8 days

thommck

issue commentMicrosoftDocs/memdocs

Expand Acronym EAS

I have edited the doc to expand the acronym for clarity. This will publish later today.

thommck

comment created time in 8 days

issue commentMicrosoftDocs/memdocs

Expand Acronym EAS

I'm not familiar with the scenario, but Intune has an Exchange Online connector and you can use EAS polices. Yes, you have the acronym correct.

thommck

comment created time in 8 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I was hopeful that this would be our issue, but after looking at this DLL on one of my own VMs the results are confusing. Sigverif says that the DLL is unsigned, but sigcheck says it is signed. I think that it is really signed, and sigverif is reporting incorrect results. If I look at DXDIAG, I see "WHQL Logo'd: Yes" which means it is signed.

I think we are going to have to look somewhere else for the issue here, but let me know what you find out.


Display Devices

       Card name: Microsoft Remote Display Adapter
    Manufacturer: Microsoft
       Chip type: Unknown
        DAC type: Unknown
     Device Type: Display-Only Device
      Device Key: Enum\SWD\REMOTEDISPLAYENUM
   Device Status: 0180600A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_REMOVABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER] 

Device Problem Code: No Problem Driver Problem Code: Unknown Display Memory: 2047 MB Dedicated Memory: 0 MB Shared Memory: 2047 MB Current Mode: 1366 x 768 (32 bit) (32Hz) HDR Support: Not Supported Display Topology: Internal Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709 Color Primaries: Red(0.000000,0.000000), Green(0.000000,0.000000), Blue(0.000000,0.000000), White Point(0.000000,0.000000) Display Luminance: Min Luminance = 0.000000, Max Luminance = 0.000000, MaxFullFrameLuminance = 0.000000 Monitor Name: Generic Non-PnP Monitor Monitor Model: unknown Monitor Id: Native Mode: unknown Output Type: Other Monitor Capabilities: HDR Not Supported Display Pixel Format: DISPLAYCONFIG_PIXELFORMAT_32BPP Advanced Color: Not Supported Driver Name: c:\windows\system32\drivers\umdf\rdpidd.dll,c:\windows\system32\drivers\wudfrd.sys Driver File Version: 10.00.19041.0423 (English) Driver Version: 10.0.19041.423 DDI Version: 12 Feature Levels: 12_1,12_0,11_1,11_0,10_1,10_0,9_3,9_2,9_1 Driver Model: WDDM 1.3 Hardware Scheduling: Supported:False Enabled:False Graphics Preemption: DMA Compute Preemption: DMA Miracast: Not Supported Detachable GPU: No Hybrid Graphics GPU: Not Supported Power P-states: Not Supported Virtualization: Not Supported Block List: No Blocks Catalog Attributes: N/A Driver Attributes: Final Retail Driver Date/Size: 6/20/2006 5:00:00 PM, 243200 bytes WHQL Logo'd: Yes WHQL Date Stamp: Unknown Device Identifier: {D7B71AF4-43CC-11CF-E463-616AAFC2C735} Vendor ID: 0x1414 Device ID: 0x008C SubSys ID: 0x00000000 Revision ID: 0x0000 Driver Strong Name: rdpidd.inf:c14ce88470d6efe0:RdpIdd_Install.NT:10.0.19041.423:RdpIdd_IndirectDisplay Rank Of Driver: 00FF0000 Video Accel: Unknown DXVA2 Modes: Unknown Deinterlace Caps: n/a D3D9 Overlay: Not Supported DXVA-HD: Not Supported DDraw Status: Not Available D3D Status: Enabled AGP Status: Not Available MPO MaxPlanes: 0 MPO Caps: Not Supported MPO Stretch: Not Supported MPO Media Hints: Not Supported MPO Formats: Not Supported PanelFitter Caps: Not Supported PanelFitter Stretch: Not Supported

Sumitdhiman

comment created time in 11 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

Thanks, please let me know how it turns out. FYI, I edited your comment above slightly. It turns out that some special characters in the file name don't display quite right on this page unless you use 'code' quotes.

Sumitdhiman

comment created time in 11 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

If possible, examine a system that is running the same version of Windows 10 and see what the name of that catalog is. Use the .\sigcheck -i c:\windows\system32\drivers\umdf\rdpidd.dll command shown above.

Sumitdhiman

comment created time in 12 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

Looks like your catalog might have a slightly different version number than mine

2020-09-23 18:58:54, Info MIG Excluding OS catalog based on name match: C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Desktop-Required-Package01~31bf3856ad364e35~amd64~it-IT~10.0.18362.1016.cat 2020-09-23 18:58:54, Info MIG Excluding OS catalog based on name match: C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Desktop-Required-Package01~31bf3856ad364e35~amd64~~10.0.18362.997.cat 2020-09-23 18:58:54, Info MIG Excluding OS catalog based on name match: C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Desktop-Required-Package02~31bf3856ad364e35~amd64~~10.0.18362.997.cat 2020-09-23 18:58:54, Info MIG Excluding OS catalog based on name match: C:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Desktop-Required-Package03~31bf3856ad364e35~amd64~~10.0.18362.1016.cat

Sumitdhiman

comment created time in 12 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

You need to check the status of C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Desktop-Required-Package01~31bf3856ad364e35~amd64~~10.0.19041.508.cat

See below. This driver should be signed.

C:\Sigcheck> .\sigcheck -i c:\windows\system32\drivers\umdf\rdpidd.dll

Sigcheck v2.80 - File version and signature viewer Copyright (C) 2004-2020 Mark Russinovich Sysinternals - www.sysinternals.com

c:\windows\system32\drivers\umdf\RdpIdd.dll: Verified: Signed Signing date: 1:16 PM 9/6/2020 Signing date: 1:16 PM 9/6/2020 Catalog: C:\WINDOWS\system32\CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Desktop-Required-Package01~31bf3856ad364e35~amd64~~10.0.19041.508.cat Signers: Microsoft Windows Cert Status: Valid Valid Usage: NT5 Crypto, Code Signing Cert Issuer: Microsoft Windows Production PCA 2011 Serial Number: 33 00 00 02 66 BD 15 80 EF A7 5C D6 D3 00 00 00 00 02 66 Thumbprint: A4341B9FD50FB9964283220A36A1EF6F6FAA7840 Algorithm: sha256RSA Valid from: 11:30 AM 3/4/2020 Valid to: 11:30 AM 3/3/2021 Microsoft Windows Production PCA 2011 Cert Status: Valid Valid Usage: All Cert Issuer: Microsoft Root Certificate Authority 2010 Serial Number: 61 07 76 56 00 00 00 00 00 08 Thumbprint: 580A6F4CC4E4B669B9EBDC1B2B3E087B80D0678D Algorithm: sha256RSA Valid from: 11:41 AM 10/19/2011 Valid to: 11:51 AM 10/19/2026 Microsoft Root Certificate Authority 2010 Cert Status: Valid Valid Usage: All Cert Issuer: Microsoft Root Certificate Authority 2010 Serial Number: 28 CC 3A 25 BF BA 44 AC 44 9A 9B 58 6B 43 39 AA Thumbprint: 3B1EFD3A66EA28B16697394703A72CA340A05BD5 Algorithm: sha256RSA Valid from: 2:57 PM 6/23/2010 Valid to: 3:04 PM 6/23/2035 Counter Signers: Microsoft Time-Stamp Service Cert Status: Valid Valid Usage: Timestamp Signing Cert Issuer: Microsoft Time-Stamp PCA 2010 Serial Number: 33 00 00 01 2D 2E 4D 41 CA 63 65 33 A0 00 00 00 00 01 2D Thumbprint: 9FCE5FC77E877BB174BE09B2525CF6C3CDA5D0B1 Algorithm: sha256RSA Valid from: 6:15 PM 12/18/2019 Valid to: 6:15 PM 3/16/2021 Microsoft Time-Stamp PCA 2010 Cert Status: Valid Valid Usage: All Cert Issuer: Microsoft Root Certificate Authority 2010 Serial Number: 61 09 81 2A 00 00 00 00 00 02 Thumbprint: 2AA752FE64C49ABE82913C463529CF10FF2F04EE Algorithm: sha256RSA Valid from: 2:36 PM 7/1/2010 Valid to: 2:46 PM 7/1/2025 Microsoft Root Certificate Authority 2010 Cert Status: Valid Valid Usage: All Cert Issuer: Microsoft Root Certificate Authority 2010 Serial Number: 28 CC 3A 25 BF BA 44 AC 44 9A 9B 58 6B 43 39 AA Thumbprint: 3B1EFD3A66EA28B16697394703A72CA340A05BD5 Algorithm: sha256RSA Valid from: 2:57 PM 6/23/2010 Valid to: 3:04 PM 6/23/2035 Company: Microsoft Corporation Description: Rdp Indirect Display Product: Microsoft« Windows« Operating System Prod version: 10.0.19041.423 File version: 10.0.19041.423 (WinBuild.160101.0800) MachineType: 64-bit C:\Sigcheck>

Sumitdhiman

comment created time in 12 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

Re-opening issue until we can get the root cause figured out and documented.

Sumitdhiman

comment created time in 12 days

IssuesEvent

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I see error 1900101-40017 on line 15668. I ran setupdiag again but it didn't find a match. However, the 1900101-40017 error is almost always associated with a driver problem. Can you run sigverif to see if there are any unsigned drivers on the system?

If unsigned drivers are present, it there could be a corrupt or missing catalog file. I do see some problems with cab files in Windows\System32\spool\drivers\W32X86\PCC.

Sumitdhiman

comment created time in 13 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I'm in the middle of writing this now. The tools you should check out, if you haven't already tried them, are sigverif, sigcheck and driverquery.

Sumitdhiman

comment created time in 13 days

issue closedMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

[Enter feedback here] Hi, Is the Feature update troubleshooting document also valid for version 2004(or are there any plans to update)? I see some things in the logs of version 2004 which were not present in earlier logs.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 13 days

Sumitdhiman

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I'm going to follow up by adding information to the resolution procedures on how to locate unsigned drivers. At this point, I don't think I can do much more than that, so I'm closing the issue. I appreciate bringing the issue up so that I can add more depth to the resolution procedures.

Sumitdhiman

comment created time in 13 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

You're welcome! I contacted an expert here and he says that the rollback setupact.log (from %systemdrive%$Windows.~bt\Sources\Panther\Rollback) is needed to diagnose this, but the first thing to try is to find any unsigned drivers and remove or update them. He provided the following link, but said we don't recommend 3rd party tools, so watch out for these: https://www.blogsdna.com/27914/how-to-find-unsigned-drivers-installed-on-windows.htm#:~:text=How%20to%20Find%20Unsigned%20Drivers%20on%20Windows%2010.,scanned%20and%20verified%20as%20digitally%20signed%E2%80%9D.%20More%20items

Sumitdhiman

comment created time in 13 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

I ran setupdiag on your logs and it wasn't able to match a rule. However, we have a solution for this error code in the article which says it is a driver issue. Have you tried disabling encryption and antivirus, and performing a clean boot?

Sumitdhiman

comment created time in 13 days

issue closedMicrosoftDocs/windows-itpro-docs

Autopilot reset Important text

This sentence makes no sense to me: "The feature for Autopilot Reset will stay grayed out, unless you reset the device using Autopilot (either using Fresh Reset or manually sysprep the device)." Maybe it's trying to clarify that Autopilot Reset is only available for devices that have an actual Autopilot device object in Intune? Also, Fresh Reset should be Fresh Start, but I don't see just executing that or syspreping it does not magically create an Autopilot device object (at least, not in all scenario's).


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 13 days

WoutVergauwen

issue commentMicrosoftDocs/windows-itpro-docs

Autopilot reset Important text

The original author of the comment is no longer with the company and nobody understand what is being conveyed here so I'm removing the statement. I've read about the reset option being greyed out, but only when the OS version is not sufficient, and there is a note about that already.

WoutVergauwen

comment created time in 13 days

issue commentMicrosoftDocs/windows-itpro-docs

Autopilot reset Important text

Hi, I'm getting clarification now about this comment. You're right it doesn't make sense.

WoutVergauwen

comment created time in 15 days

issue commentMicrosoftDocs/windows-itpro-docs

This needs to be updated for new Endpoint Manager

I will do another run through and update this as soon as I can. I'll leave the issue open until I can get this completed.

frehnejc

comment created time in 15 days

issue closedMicrosoftDocs/windows-itpro-docs

So no .exe file allowed ????

[Enter feedback here]


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 15 days

fbifido

issue commentMicrosoftDocs/windows-itpro-docs

So no .exe file allowed ????

Please provide a more descriptive feedback, I don't know what the issue is with the doc.

fbifido

comment created time in 15 days

issue closedMicrosoftDocs/windows-itpro-docs

VDA rights Activation with CSP

Windows 10 E3 with VDA rights is available in CSP. This article should address that scenario. What can or can't be done with that license and VDA activation is needed information.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 15 days

montereyharris

issue commentMicrosoftDocs/windows-itpro-docs

VDA rights Activation with CSP

That scenario is here: https://docs.microsoft.com/en-us/windows/deployment/windows-10-enterprise-e3-overview

montereyharris

comment created time in 15 days

issue commentMicrosoftDocs/windows-itpro-docs

Update documentation for 2004

Can you please try using the SetupDiag tool? I will try to use it to analyze these logs myself also.

Sumitdhiman

comment created time in 15 days

issue commentMicrosoftDocs/windows-itpro-docs

problems with the "Create a bootable USB stick" section

Thanks for all the hints, I will get these into the document. Sorry it has taken so long to get to this. I didn't see the issue and it wasn't assigned to me. I have assigned it now.

jszabo98

comment created time in 15 days

issue closedMicrosoftDocs/windows-itpro-docs

翻譯錯誤

[請在此輸入您的意見]

"隨著此改進,OS 可以偵測到較高級別的 SMM 合規性,讓裝置更容易受到 SMM 入侵與漏洞的侵害。 這項功能是向前看,目前需要您提供新的硬體。" 這句機器翻譯翻反了,enabling devices to be even more hardened against SMM exploits and vulnerabilities 應該是 "讓裝置更容易抵禦 SMM 入侵與漏洞的侵害" 才對,怎麼會是升級讓自已最容易被入侵。forward-looking翻"向前看"有點不知所云


文件詳細資料

請勿編輯此區段。 這是 docs.microsoft.com ➟ GitHub 問題連結的必要項。

closed time in 15 days

cole945

push eventMicrosoftDocs/windows-itpro-docs

Baard Hermansen

commit sha ef68e5d0a4f82a1e480069cce526a8f1f933c7b2

Update introduction-vamt.md Added markdown for Notes. Added line breaks before lists and after headings.

view details

Greg Lindsay

commit sha fdc154000a12c053fbebd770a6c20930fbc03c99

Merge pull request #8334 from baardhermansen/patch-8 Update introduction-vamt.md

view details

push time in 19 days

PR merged MicrosoftDocs/windows-itpro-docs

Reviewers
Update introduction-vamt.md deployment

Added markdown for Notes. Added line breaks before lists and after headings.

+18 -16

0 comment

1 changed file

baardhermansen

pr closed time in 19 days

push eventMicrosoftDocs/windows-itpro-docs

Baard Hermansen

commit sha 38b1ff8182711c98abc28d0dd520aa93f000f50a

Update activate-using-key-management-service-vamt.md Added retail link for activating Windows 10. Added markdown for Notes. Corrected a nested list error, which incorrectly indented a numbered list item. Modified spacing inside numbered list so that text is rendered as author seemed to intend.

view details

Baard Hermansen

commit sha 1827a91d202ee729ffd2e41a24090a15d357264a

Update windows/deployment/volume-activation/activate-using-key-management-service-vamt.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>

view details

Baard Hermansen

commit sha ed4c3e5a5fa6ac565a1ba309620e6487f1943a0b

Update windows/deployment/volume-activation/activate-using-key-management-service-vamt.md Co-authored-by: JohanFreelancer9 <48568725+JohanFreelancer9@users.noreply.github.com>

view details

Greg Lindsay

commit sha c24ae349df326a98c375a85506e3f4119ada0e95

Merge pull request #8335 from baardhermansen/patch-9 Update activate-using-key-management-service-vamt.md

view details

push time in 19 days

PR merged MicrosoftDocs/windows-itpro-docs

Update activate-using-key-management-service-vamt.md deployment

Added retail link for activating Windows 10. Added markdown for Notes. Corrected a nested list error, which incorrectly indented a numbered list item. Modified spacing inside numbered list so that text is rendered as author seemed to intend.

+52 -46

1 comment

1 changed file

baardhermansen

pr closed time in 19 days

push eventMicrosoftDocs/windows-itpro-docs

MaratMussabekov

commit sha fad551604070e6eaa7014ed2268eb9bdf2f117e6

Update whats-new-windows-10-version-1909.md

view details

Greg Lindsay

commit sha 010f76e6eab113302c0a64e0d0013462760c1108

Merge pull request #8349 from MaratMussabekov/patch-213 removed link to non-existing article

view details

push time in 19 days

PR merged MicrosoftDocs/windows-itpro-docs

removed link to non-existing article what's new

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8294

+0 -1

1 comment

1 changed file

MaratMussabekov

pr closed time in 19 days

issue commentMicrosoftDocs/memdocs

Mention that blocking login.live.com will break autopilot

This URL is actually included in https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide which is a requirement, but I can add a specific mention of this URL to make it clear.

hpsin

comment created time in 22 days

issue commentMicrosoftDocs/memdocs

Setting doesn't exist

"The Autopilot Reset option will not be enabled in Microsoft Intune for devices not running Windows 10 build 17672 or higher."

Can you verify the build #?

ezapper2

comment created time in 22 days

issue closedMicrosoftDocs/windows-itpro-docs

Broken links

The link to the M365 deployment advisor is broken.

Correlation ID:ncu#01cb2dc3-ec62-4187-9a14-9ce91a2fef9a

| Error code:0


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 25 days

iloving

issue commentMicrosoftDocs/windows-itpro-docs

Broken links

@iloving yes those are the locations you should see with those links.

iloving

comment created time in 25 days

issue commentMicrosoftDocs/windows-itpro-docs

error 0x800705b4

I've added a link to the networking requirements section pertinent to white glove and self-deploying mode into the articles for these scenarios. Hopefully this will help.

goxia

comment created time in a month

issue commentMicrosoftDocs/windows-itpro-docs

Licence

I believe that F3 used to be required, but later F1 was added. Now you can have either.

KoenBekaert

comment created time in a month

issue closedMicrosoftDocs/Devices-docs

edit page to say 50-inch

[Enter feedback here] This page title should be edited to make it clear it applies only to the 50-inch Surface Hub 2S (and not the new 85" Hub 2S)


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in a month

luriep

issue commentMicrosoftDocs/Devices-docs

edit page to say 50-inch

I've added this - thanks! It will show up later today ~ 5PM PST

luriep

comment created time in a month

issue closedMicrosoftDocs/memdocs

typo in doc

Windows 10 version 1803 and above adds event log entries. You can use the og entries to see details related to the Autopilot profile settings and OOBE flow. These entries can be viewed using Event Viewer [Enter feedback here]


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in a month

soupman98

issue commentMicrosoftDocs/memdocs

typo in doc

fixed in https://github.com/MicrosoftDocs/memdocs-pr/pull/2131

soupman98

comment created time in a month

issue closedMicrosoftDocs/windows-itpro-docs

MFA Issue more detailed info

Multi-factor authentication ...

If the device is running Windows 10, version 1809 or later:

Windows 10, version 1809 must be updated with KB4497934. Later versions of Windows 10 automatically include this patch.

When the user signs in on a Hybrid Azure AD joined device with MFA enabled, a notification will indicate that there is a problem. Click the notification and then click Fix now to step through the subscription activation process. See the example below:

Can you elaborate on this MFA Issue? Does this "Fix now" process have to be done once per device? Every time a user logs in? Has it been addressed in 1903, 1909 or 2004 so that it's no longer a problem?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in a month

mattsmacblog

issue commentMicrosoftDocs/windows-itpro-docs

MFA Issue more detailed info

I received a response back and no, there's no change to the behavior. This is the expected thing to see if MFA is enabled, because it's needed to secure the device.

mattsmacblog

comment created time in a month

issue commentMicrosoftDocs/windows-itpro-docs

MFA Issue more detailed info

I'm checking to see if the behavior is expected, or if there has been a change. I'll post back here what I find out.

mattsmacblog

comment created time in a month

issue closedMicrosoftDocs/memdocs

Is Wi-Fi Supported or not?

The prerequisites state, "Wi-fi connectivity isn't supported because of the requirement to choose a language, locale, and keyboard to make that Wi-fi connection"

The user flow section states, "Connect to a network (if using Wi-Fi)."

Which is it.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in a month

liskajoe

issue commentMicrosoftDocs/memdocs

Is Wi-Fi Supported or not?

I suppose it's not made expressly clear, but the requirements section applies to pre-provisioning, i.e. the technician flow.

At the very end of the white glove process the user gets the device and at that point they can connect to wi-fi or ethernet, it doesn't matter. I'll try to make this clearer in the text.

liskajoe

comment created time in a month

push eventMicrosoftDocs/windows-itpro-docs

Baard Hermansen

commit sha 98f3d9c90c1bfd28acaf1979a8da62398c0a5388

Update windows-10-poc-sc-config-mgr.md Added markdown code for code snippets. Corrected an URL. Multiple small edits, like removing trailing spaces, extraneous line shifts, etc..

view details

Baard Hermansen

commit sha e334e2adce321b5703e10afc489daa5c508eb2d6

Update windows-10-poc-sc-config-mgr.md Converted HTML table to markdown.

view details

Greg Lindsay

commit sha 92d0de2323a9151df2d2a25e35497dafe6496385

Merge pull request #8262 from baardhermansen/patch-11 Update windows-10-poc-sc-config-mgr.md

view details

push time in a month

PR merged MicrosoftDocs/windows-itpro-docs

Update windows-10-poc-sc-config-mgr.md deployment

Added markdown code for code snippets. Corrected an URL. Multiple small edits, like removing trailing spaces, extraneous line shifts, etc..

+211 -204

0 comment

1 changed file

baardhermansen

pr closed time in a month

issue commentMicrosoftDocs/windows-itpro-docs

MFA Issue more detailed info

Hi,

The content says "Later versions of Windows 10 automatically include this patch." So you don't need to download the patch, but the user still needs to enter MFA credentials. This is a security precaution. AFAIK this is by design so although it is referred to as 'fixing' something it really is just a normal MFA requirement.

mattsmacblog

comment created time in a month

push eventMicrosoftDocs/memdocs

AzureMentor

commit sha 000a6338722755f78e3eef0e4b5641c72311d0c8

Fixed missing closing bracket in content Fixed missing closing bracket in content.

view details

Greg Lindsay

commit sha 3140955eb87b35b3b35ca6eb6611c56204ae040e

Merge pull request #705 from AzureMentor/patch-2 Fixed missing closing bracket in content

view details

push time in 2 months

PR merged MicrosoftDocs/memdocs

Fixed missing closing bracket in content Change sent to author do-not-merge w10/prod

Fixed missing closing bracket in content.

+2 -2

1 comment

1 changed file

AzureMentor

pr closed time in 2 months

PullRequestReviewEvent

push eventMicrosoftDocs/memdocs

Herman Arnedo Mahr

commit sha 0f46e527c5b226a2439eeff4a880ff13adb2b27d

Update user-driven.md A Domain Join configuration profile including on-premises Active Directory domain information is a requirement to support user-driven hybrid Azure AD joined deployment using Windows Autopilot

view details

Greg Lindsay

commit sha 626ef1a8407b350ca71070d3dc9451e36debcfeb

Merge pull request #701 from hermanarnedo/patch-3 Update user-driven.md

view details

push time in 2 months

PR merged MicrosoftDocs/memdocs

Update user-driven.md Change sent to author do-not-merge w10/prod

A Domain Join configuration profile including on-premises Active Directory domain information is a requirement to support user-driven hybrid Azure AD joined deployment using Windows Autopilot

+3 -2

1 comment

1 changed file

hermanarnedo

pr closed time in 2 months

PullRequestReviewEvent

issue closedMicrosoftDocs/windows-itpro-docs

Clarification on the Connect app deprecation

[Enter feedback here]

In the section where the article states that the Connect app is being changed to an optional feature, the document links to a MS Docs article where the feature to connect a computer to a Miracast display is explained. But, in fact, what the Connect app does is to allow a PC to be the receiver of a Miracast stream, which is the opposite of what the linked article explains.

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 2 months

miguedevel

issue commentMicrosoftDocs/windows-itpro-docs

Clarification on the Connect app deprecation

I agree, this is confusing. The article talks about sending a stream not receiving one. I'm removing the link. This change should publish this afternoon. Thanks for catching this.

miguedevel

comment created time in 2 months

push eventMicrosoftDocs/microsoft-365-docs

StuEwen

commit sha ff1dcb334ed6755fd27d102937798f6d1246b84d

Update access-admin-portal.md

view details

StuEwen

commit sha b0a9fc216395ceb8d4f0002b4ae11b2a5424fbf9

Update access-admin-portal.md

view details

Jaime Ondrusek

commit sha dbec8009f699d81aa8e24df9b69cd6114adb2a4f

Update access-admin-portal.md Slight edits.

view details

Greg Lindsay

commit sha 4fcb884be8615c0a14bf2306dff8f1078aa39533

Merge pull request #2519 from StuEwen/patch-4 Update access-admin-portal.md

view details

push time in 2 months

issue commentMicrosoftDocs/windows-itpro-docs

Table Confusion

https://github.com/MicrosoftDocs/windows-itpro-docs/pull/8162

newark123

comment created time in 2 months

push eventMicrosoftDocs/windows-itpro-docs

MaratMussabekov

commit sha 2e5b0521c3e181bc2428b2f8ffce3c49e02b4003

Update usmt-scanstate-syntax.md

view details

Greg Lindsay

commit sha 8e11cc270100d33e59a91ee2be8dc6ab705715f1

Merge pull request #8162 from MaratMussabekov/patch-194 fixed table inconsistency

view details

push time in 2 months

PR merged MicrosoftDocs/windows-itpro-docs

fixed table inconsistency deployment

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/8080

+1 -1

1 comment

1 changed file

MaratMussabekov

pr closed time in 2 months

issue commentMicrosoftDocs/Devices-docs

Error CSP Policy

I think you are correct - thanks for catching the error. Although I'm listed as author I didn't actually write this so I'll submit the change to the person that did.

Egoorbis

comment created time in 2 months

issue closedMicrosoftDocs/windows-itpro-docs

Detailed and crisp

[Enter feedback here]


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 2 months

Hsadikot95S

issue commentMicrosoftDocs/windows-itpro-docs

Detailed and crisp

Thank you, please let me know if there are any actions to take on the referenced article.

Hsadikot95S

comment created time in 2 months

push eventMicrosoftDocs/memdocs

AzureMentor

commit sha 4748d16c741a8eea9d4052770bb43f88fb962c79

Provided correction for the Preparation section. Provided correction for the Preparation section.

view details

Greg Lindsay

commit sha bbe3d31fbd284b3dd41dafe7ca26f761a7c1c8f7

Merge pull request #646 from AzureMentor/patch-1 Provided correction for the Preparation section.

view details

push time in 2 months

PR merged MicrosoftDocs/memdocs

Provided correction for the Preparation section. Change sent to author do-not-merge w10/prod

Provided correction for the Preparation section.

+1 -1

1 comment

1 changed file

AzureMentor

pr closed time in 2 months

PullRequestReviewEvent

push eventMicrosoftDocs/windows-itpro-docs

VARADHARAJAN K

commit sha 559afbf615f99ae595b6b9f8ef3867c5f8aa2f5d

added missing windows versions as per the user issue #8086 , so i added missing windows 10 and server versions like 1909 , 2004

view details

Greg Lindsay

commit sha 4159f24a957e36d1102bd0d4757d4cc7289bd978

Merge pull request #8088 from RAJU2529/patch-82 added missing windows versions

view details

push time in 2 months

PR merged MicrosoftDocs/windows-itpro-docs

added missing windows versions deployment

as per the user issue #8086 , so i added missing windows 10 and server versions like 1909 , 2004

+2 -1

0 comment

1 changed file

RAJU2529

pr closed time in 2 months

issue closedMicrosoftDocs/windows-itpro-docs

make and model values dell

Hi,

Just want to mention that the %make% Value for Dell should be "Dell Inc." Instead of Dell. It cost me a few hours to figure out why my drivers weren't injected. Can you change this in the instructions? It might help other people.

Page: https://docs.microsoft.com/en-us/windows/deployment/deploy-windows-mdt/deploy-a-windows-10-image-using-mdt Subject: Create the logical driver structure in MDT

Kind Regards, Frank van Es


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

closed time in 2 months

frenkeh

issue commentMicrosoftDocs/windows-itpro-docs

make and model values dell

Will do, thanks for the catch!

frenkeh

comment created time in 2 months

issue commentMicrosoftDocs/windows-itpro-docs

TCP / IP pipeline and hybrid authentication

本主题讨论MDT数据库。除了本地MDT服务器上的身份验证外,没有其他身份验证。请说明您认为需要更改或添加的内容。

jackadam1981

comment created time in 2 months

issue commentMicrosoftDocs/windows-itpro-docs

TCP / IP pipeline and hybrid authentication

This topic talks about the MDT database. There is no authentication other than that on the local MDT server. Please clarify what you think needs to be changed or added.

jackadam1981

comment created time in 2 months

issue closedMicrosoftDocs/memdocs

Few changes

[Enter feedback here]

Kindly change the intune portal to Endpoint Manager

Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

  • ID: ea4a659b-65d0-26ec-c36a-9a21a72a09a8
  • Version Independent ID: bff44b73-9021-6659-e212-66349c759989
  • Content: Adding devices
  • Content Source: memdocs/autopilot/add-devices.md
  • Product: w10
  • GitHub Login: @greg-lindsay
  • Microsoft Alias: greglin

closed time in 2 months

theg00d1

issue commentMicrosoftDocs/memdocs

Few changes

I've added a clarification in the doc it should publish later today. Thanks!

theg00d1

comment created time in 2 months

issue commentMicrosoftDocs/memdocs

Few changes

I think I see where the confusing lies. MEM is a combination of Intune and SCCM. Device enrollment is an Intune function, but when you do it, you use the MEM manager interface. This is still Intune, however. Maybe I can clarify that in the documentation.

theg00d1

comment created time in 2 months

more