Merge pull request #5710 from TerryGLee/tglee-installation

[install] add JSON error info from DevComm

Author: PRMerger7

docs/install/automated-installation-with-response-file.md

@@ -153,3 +153,4 @@ The following example installs Visual Studio Enterprise with six common workload
 ## See also
 
 * [Visual Studio workload and component IDs](workload-and-component-ids.md)
+* [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)

docs/install/create-a-network-installation-of-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: "Create a network-based installation"
 description: "Learn how to create a network install point for deploying Visual Studio within an enterprise."
-ms.date: 10/11/2019
+ms.date: 10/29/2019
 ms.custom: "seodec18"
 ms.topic: conceptual
 helpviewer_keywords:
@@ -82,8 +82,9 @@ You must have an internet connection to complete this step. To create an offline
 
 ## Modify the response.json file
 
-You can modify the response.json to set default values that are used when setup is run.  For example, you can configure the `response.json` file to select a specific set of workloads selected automatically.
-See [Automate Visual Studio installation with a response file](automated-installation-with-response-file.md) for details.
+You can modify the response.json to set default values that are used when setup is run.  For example, you can configure the `response.json` file to select a specific set of workloads selected automatically. See [Automate Visual Studio installation with a response file](automated-installation-with-response-file.md) for details.
+
+And, if you run into a problem with the Visual Studio bootstrapper throwing an error when you pair it with a response.json file, see the "Failed to parse ID from parent process" section of the [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md#error-failed-to-parse-id-from-parent-process) page for more information on what to do.
 
 ## Copy the layout to a network share
 
@@ -213,7 +214,7 @@ Administrators can deploy Visual Studio onto client workstations as part of an i
 
 > [!IMPORTANT]
 > To prevent an error, make sure that your full layout path is less than 80 characters.
->
+
 > [!TIP]
 > When executed as part of a batch file, the `--wait` option ensures that the `vs_enterprise.exe` process waits until the installation is complete before it returns an exit code.
 >
@@ -281,6 +282,7 @@ We have other support options available, too. For a list, see our [Feedback](../
 
 - [Visual Studio administrator guide](visual-studio-administrator-guide.md)
 - [Update a network-based installation of Visual Studio](update-a-network-installation-of-visual-studio.md)
+- [Troubleshoot network-related errors when you install or use Visual Studio](troubleshooting-network-related-errors-in-visual-studio.md)
 - [Control updates to network-based Visual Studio deployments](controlling-updates-to-visual-studio-deployments.md)
 - [Visual Studio product lifecycle and servicing](/visualstudio/releases/2019/servicing/)
 - [Update Visual Studio while on a servicing baseline](update-servicing-baseline.md)

docs/install/troubleshooting-network-related-errors-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: "Troubleshoot network or proxy errors"
 description: "Find solutions for network- or proxy-related errors that you might encounter when you install or use Visual Studio behind a firewall or a proxy server."
-ms.date: 05/22/2019
+ms.date: 10/29/2019
 ms.topic: troubleshooting
 helpviewer_keywords:
   - "network installation, Visual Studio"
@@ -127,6 +127,19 @@ Enable connections for the following URLs:
   > [!NOTE]
   > Privately owned NuGet server URLs may not be included in this list. You can check for the NuGet servers that you are using in %APPData%\Nuget\NuGet.Config.
 
+## Error: "Failed to parse ID from parent process"
+
+You might encounter this error message when you use a Visual Studio bootstrapper and a response.json file on a network drive. The error's source is the User Account Control (UAC) in Windows.
+
+Here's why this error can happen: A mapped network drive or [UNC](/dotnet/standard/io/file-patch-formats#unc-paths) share is linked to a user's access token. When UAC is enabled, two user [access tokens](/windows/win32/secauthz/access-tokens) are created: One *with* administrator access, and one *without* administrator access. When network drive or share is created, the user's current access token is linked to it. Because the bootstrapper must be run as administrator, it won't be able to access the network drive or share if either the drive or the share isn't linked to a user access token that has administrator access.
+
+### To fix this error
+
+You can use the `net use` command or you can change the UAC Group Policy setting. For more information about these workarounds and how to implement them, see the following Microsoft support articles:
+
+* [Mapped drives are not available from an elevated prompt when UAC is configured to "Prompt for credentials" in Windows](https://support.microsoft.com/help/3035277/mapped-drives-are-not-available-from-an-elevated-prompt-when-uac-is-co)
+* [Programs may be unable to access some network locations after you turn on User Account Control in Windows operating systems](https://support.microsoft.com/en-us/help/937624/programs-may-be-unable-to-access-some-network-locations-after-you-turn)
+
 [!INCLUDE[install_get_support_md](includes/install_get_support_md.md)]
 
 ## See also