You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/windows/windows-azure-guest-agent.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,7 +135,7 @@ These error entries indicate that the VM can't reach the WireServer IP address,
135
135
136
136
1. Connect to the VM by using Remote Desktop, and then test connectivity to 168.63.129.16. See the [Troubleshoot connectivity](/azure/virtual-network/what-is-ip-address-168-63-129-16?tabs=windows#troubleshoot-azure-ip-connectivity) section of [Azure IP address 168.63.129.16 overview](/azure/virtual-network/what-is-ip-address-168-63-129-16).
137
137
1. If you have only one private IP on your VM's network adapter, we highly recommend that you have DHCP enabled on the guest VM. If you need a static private IP address, you should configure it through the Azure portal or PowerShell, and make sure the DHCP option inside the VM is enabled. To make sure that the IP configuration always matches the configuration on the VM in Azure, [learn how to set up a static IP address](/azure/virtual-network/ip-services/virtual-networks-static-private-ip-arm-ps) by using PowerShell.
138
-
1. If you have multiple private IPs assigned to your VM's network adapter, make sure that you carefully follow the steps to [assign the IP configurations correctly](/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal#os-config). After you finish the steps, if Guest Agent can't communicate with 168.63.129.16, check that the primary IP in Windows [matches the primary IP in your VM's network adapter in Azure](/troubleshoot/azure/virtual-machines/windows/no-internet-access-multi-ip).
138
+
1. If you have multiple private IPs assigned to your VM's network adapter, make sure that you carefully follow the steps to [assign the IP configurations correctly](/azure/virtual-network/ip-services/virtual-network-multiple-ip-addresses-portal#os-config). After you finish the steps, if Guest Agent can't communicate with 168.63.129.16, check that the primary IP in Windows [matches the primary IP in your VM's network adapter in Azure](no-internet-access-multi-ip.md).
139
139
1. Check for any issues that a firewall, a proxy, or another source might cause that could block access to IP address `168.63.129.16`.
140
140
1. Check whether Windows Firewall or a third-party firewall is blocking access to ports `80` and `32526`. For more information about why this address shouldn't be blocked, see [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16)
Copy file name to clipboardExpand all lines: support/azure/virtual-machines/windows/windows-update-errors-requiring-in-place-upgrade.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ms.custom:
18
18
> [!IMPORTANT]
19
19
> This article doesn't cover Windows Client scenarios.
20
20
21
-
For Virtual Machines (VMs) that are running on Azure, certain Windows Update errors require an in-place upgrade of the OS to restore the servicing stack to a healthy condition in which updates can be installed. Other options, such as WinRE, are available to possibly mitigate this issue. However, such processes aren't possible unless the VM is connected to a nested virtualization environment, as described in [Troubleshoot a faulty Azure VM by using nested virtualization in Azure](/troubleshoot/azure/virtual-machines/windows/troubleshoot-vm-by-use-nested-virtualization). Although you do an in-place upgrade, you use the installation media of the current OS to reinstall the system. This article provides the steps to identify the specific upgrade errors that require this action.
21
+
For Virtual Machines (VMs) that are running on Azure, certain Windows Update errors require an in-place upgrade of the OS to restore the servicing stack to a healthy condition in which updates can be installed. Other options, such as WinRE, are available to possibly mitigate this issue. However, such processes aren't possible unless the VM is connected to a nested virtualization environment, as described in [Troubleshoot a faulty Azure VM by using nested virtualization in Azure](troubleshoot-vm-by-use-nested-virtualization.md). Although you do an in-place upgrade, you use the installation media of the current OS to reinstall the system. This article provides the steps to identify the specific upgrade errors that require this action.
22
22
23
23
## Prerequisites
24
24
@@ -112,5 +112,5 @@ To resolve this issue, we recommend that you perform an in-place upgrade of Wind
112
112
## References
113
113
114
114
1.[In-place upgrade for VMs not running Windows Server in Azure](/windows-server/get-started/perform-in-place-upgrade)
115
-
1.[Troubleshoot a faulty Azure VM by using nested virtualization in Azure](/troubleshoot/azure/virtual-machines/windows/troubleshoot-vm-by-use-nested-virtualization)
115
+
1.[Troubleshoot a faulty Azure VM by using nested virtualization in Azure](troubleshoot-vm-by-use-nested-virtualization.md)
116
116
1.[In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade)
Copy file name to clipboardExpand all lines: support/developer/dotnet/framework/general/secure-applications.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.custom: sap:Common Language Runtime (CLR)
11
11
12
12
This article discusses important considerations for securing applications that are built on Microsoft .NET Framework.
13
13
14
-
For important consideration when deploying applications that are built on the .NET Framework, see the related [Deploy applications that are built on the .NET Framework](/troubleshoot/developer/dotnet/framework/installation/deploy-applications).
14
+
For important consideration when deploying applications that are built on the .NET Framework, see the related [Deploy applications that are built on the .NET Framework](../installation/deploy-applications.md).
15
15
16
16
_Applies to:_ .NET Framework
17
17
@@ -71,7 +71,7 @@ Many ASP.NET applications don't allow anonymous access. An ASP.NET application t
71
71
72
72
ASP.NET includes Forms authentication. This unique method authenticates users without creating Windows accounts. ASP.NET also includes the ability to grant or deny access to different web resources for these users.
73
73
74
-
For more information about how to control access to web resources on a per-user basis, visit [Restrict specific users from gaining access to specified web resources](/troubleshoot/developer/webapps/aspnet/configuration/restrict-users-access-web-resource).
74
+
For more information about how to control access to web resources on a per-user basis, visit [Restrict specific users from gaining access to specified web resources](../../../webapps/aspnet/configuration/restrict-users-access-web-resource.md).
75
75
76
76
## Limit the web services protocols that a server permits
77
77
@@ -81,7 +81,7 @@ By default, ASP.NET supports three methods for web services clients to issue req
81
81
82
82
ASP.NET web services provide a browser-friendly interface to make it easier for developers to create web services clients. This friendly interface permits anyone who can reach the web service to view the complete details of the methods that are available and any required parameters. This access is useful for public web services that include only publicly available methods. However, it might reduce the security of private web services.
83
83
84
-
For more information about how to control access to web resources on a per-user basis, see [Restrict specific users from gaining access to specified web resources](/troubleshoot/developer/webapps/aspnet/configuration/restrict-users-access-web-resource).
84
+
For more information about how to control access to web resources on a per-user basis, see [Restrict specific users from gaining access to specified web resources](../../../webapps/aspnet/configuration/restrict-users-access-web-resource.md).
Copy file name to clipboardExpand all lines: support/developer/dotnet/framework/installation/deploy-applications.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.topic: how-to
9
9
---
10
10
# Deploy applications that are built on .NET Framework
11
11
12
-
This article discusses important considerations for deploying applications that are built on .NET Framework. For information about how to secure applications that are built on .NET Framework, see [Secure applications that are built on the .NET Framework](/troubleshoot/developer/dotnet/framework/general/secure-applications).
12
+
This article discusses important considerations for deploying applications that are built on .NET Framework. For information about how to secure applications that are built on .NET Framework, see [Secure applications that are built on the .NET Framework](../general/secure-applications.md).
13
13
14
14
_Applies to:_ .NET Framework
15
15
@@ -19,13 +19,13 @@ _Original KB number:_ 818016
19
19
20
20
The `Web.config` file is an XML file that contains application-specific settings that override system defaults. Although most ASP applications that are built on .NET Framework are deployed by having a `Web.config` file, the `Web.config` file is optional. You may have to create a `Web.config` file to override default settings on an application-by-application basis.
21
21
22
-
For more information about how to create a `Web.config` file for an application that doesn't already have one, see [Edit the configuration of an ASP.NET application](/troubleshoot/developer/webapps/aspnet/development/edit-web-config).
22
+
For more information about how to create a `Web.config` file for an application that doesn't already have one, see [Edit the configuration of an ASP.NET application](../../../webapps/aspnet/development/edit-web-config.md).
23
23
24
24
## Configure an ASP.NET application
25
25
26
26
All systems on which .NET Framework is deployed have system-wide ASP.NET configuration settings that are defined in the `<system.web>` element of the `Machine.config` file. You can modify these settings on an application-by-application basis. In fact, such a modification is frequently necessary.
27
27
28
-
For more information about how to override .NET framework default configuration settings for a specific application, see [Edit the configuration of an ASP.NET application](/troubleshoot/developer/webapps/aspnet/development/edit-web-config).
28
+
For more information about how to override .NET framework default configuration settings for a specific application, see [Edit the configuration of an ASP.NET application](../../../webapps/aspnet/development/edit-web-config.md).
29
29
30
30
## Minimum client installation requirements
31
31
@@ -45,7 +45,7 @@ For more information about how to enable and disable ASP.NET functionality for v
45
45
46
46
Many sites change IIS default error message to display a user-friendly page or to notify an administrator. By default, if errors occur in an ASP.NET application that's built on .NET Framework and deployed to a server that has IIS 5.0 custom error messages, the errors don't trigger the custom messages. However, you can configure the application to return the custom messages.
47
47
48
-
For more information about how to configure custom error messages for ASP applications that are built on .NET Framework, see [Create custom error reporting pages in ASP.NET by using Visual Basic .NET](/troubleshoot/developer/webapps/aspnet/development/custom-error-reporting-page).
48
+
For more information about how to configure custom error messages for ASP applications that are built on .NET Framework, see [Create custom error reporting pages in ASP.NET by using Visual Basic .NET](../../../webapps/aspnet/development/custom-error-reporting-page.md).
49
49
50
50
## Application-specific and directory-specific configuration settings
51
51
@@ -55,7 +55,7 @@ The most common way to override system defaults for a whole ASP.NET application
55
55
56
56
- Add more `Web.config` files to subfolders
57
57
58
-
For more information about how to apply changes that affect specific applications and directories, see [Make application and directory-specific configuration settings in an ASP.NET application](/troubleshoot/developer/webapps/aspnet/development/application-directory-configuration).
58
+
For more information about how to apply changes that affect specific applications and directories, see [Make application and directory-specific configuration settings in an ASP.NET application](../../../webapps/aspnet/development/application-directory-configuration.md).
59
59
60
60
## Configure session state management
61
61
@@ -83,7 +83,7 @@ ASP.NET supports Windows authentication and can impersonate the user in much the
83
83
84
84
You can deploy your ASP.NET web application by using the MS-DOS `xcopy` command-line tool. However, it's a good idea to deploy your project instead of using `xcopy`. Similar to the Copy Project command, `xcopy` doesn't register or verify the location of assemblies. Also, for web projects, `xcopy` doesn't automatically configure IIS directory settings.
85
85
86
-
For more information, see [Deploy an ASP.NET web application by using Xcopy deployment](/troubleshoot/developer/visualstudio/language-compilers/deploy-aspnet-app-xcopy-command).
86
+
For more information, see [Deploy an ASP.NET web application by using Xcopy deployment](../../../visualstudio/language-compilers/deploy-aspnet-app-xcopy-command.md).
87
87
88
88
## Set up multiple server ASP.NET web applications and web services
0 commit comments