Skip to content

Commit a9f2093

Browse files
committed
mvc7
2 parents 733ce4f + 8c7c27b commit a9f2093

File tree

161 files changed

+3446
-989
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

161 files changed

+3446
-989
lines changed

.openpublishing.redirection.json

Lines changed: 70 additions & 65 deletions
Large diffs are not rendered by default.

articles/active-directory/develop/howto-create-service-principal-portal.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ When programmatically signing in, you need to pass the tenant ID with your authe
9494
![Client ID](./media/howto-create-service-principal-portal/copy-app-id.png)
9595

9696
## Certificates and secrets
97-
Deamon applications can use two forms of credentials to authenticate with Azure AD: certificates and application secrets. We recommend using a certificate, but you can also create a new application secret.
97+
Daemon applications can use two forms of credentials to authenticate with Azure AD: certificates and application secrets. We recommend using a certificate, but you can also create a new application secret.
9898

9999
### Upload a certificate
100100

articles/app-service/app-service-web-tutorial-custom-domain.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ From the left menu, select **App Services**, and then select the name of the app
6565

6666
You see the management page of the App Service app.
6767

68-
<a name="checkpricing"></a>
68+
<a name="checkpricing" aria-hidden="true"></a>
6969

7070
### Check the pricing tier
7171

@@ -79,7 +79,7 @@ The app's current tier is highlighted by a blue border. Check to make sure that
7979

8080
If the App Service plan is not in the **F1** tier, close the **Scale up** page and skip to [Map a CNAME record](#cname).
8181

82-
<a name="scaleup"></a>
82+
<a name="scaleup" aria-hidden="true"></a>
8383

8484
### Scale up the App Service plan
8585

@@ -93,7 +93,7 @@ When you see the following notification, the scale operation is complete.
9393

9494
![Scale operation confirmation](./media/app-service-web-tutorial-custom-domain/scale-notification.png)
9595

96-
<a name="cname"></a>
96+
<a name="cname" aria-hidden="true"></a>
9797

9898
## Map your domain
9999

@@ -159,7 +159,7 @@ If you missed a step or made a typo somewhere earlier, you see a verification er
159159

160160
![Verification error](./media/app-service-web-tutorial-custom-domain/verification-error-cname.png)
161161

162-
<a name="a"></a>
162+
<a name="a" aria-hidden="true"></a>
163163

164164
### Map an A record
165165

@@ -210,7 +210,7 @@ When the records are added, the DNS records page looks like the following exampl
210210

211211
![DNS records page](./media/app-service-web-tutorial-custom-domain/a-record.png)
212212

213-
<a name="enable-a"></a>
213+
<a name="enable-a" aria-hidden="true"></a>
214214

215215
#### Enable the A record mapping in the app
216216

@@ -243,7 +243,7 @@ If you missed a step or made a typo somewhere earlier, you see a verification er
243243

244244
![Verification error](./media/app-service-web-tutorial-custom-domain/verification-error.png)
245245

246-
<a name="wildcard"></a>
246+
<a name="wildcard" aria-hidden="true"></a>
247247

248248
### Map a wildcard domain
249249

@@ -307,7 +307,7 @@ If you receive an HTTP 404 (Not Found) error when browsing to the URL of your cu
307307
- The custom domain configured is missing an A record and/or a CNAME record.
308308
- The browser client has cached the old IP address of your domain. Clear the cache and test DNS resolution again. On a Windows machine, you clear the cache with `ipconfig /flushdns`.
309309

310-
<a name="virtualdir"></a>
310+
<a name="virtualdir" aria-hidden="true"></a>
311311

312312
## Migrate an active domain
313313

articles/automation/tutorial-configure-servers-desired-state.md

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -151,6 +151,37 @@ $reports = Get-AzureRmAutomationDscNodeReport -ResourceGroupName 'MyResourceGrou
151151
$reports[0]
152152
```
153153

154+
## Removing nodes from service
155+
156+
When you add a node to Azure Automation State Configuration,
157+
the settings in Local Configuration Manager are set to register with the service
158+
and pull configurations and required modules to configure the machine.
159+
If you choose to remove the node from the service,
160+
you can do so using either the Azure portal
161+
or the Az cmdlets.
162+
163+
> [!NOTE]
164+
> Unregistering a node from the service only sets the Local Configuration Manager settings
165+
> so the node is no longer connecting to the service.
166+
> This does not effect the configuration that is currently applied to the node.
167+
> To remove the current configuration, use the
168+
> [PowerShell](https://docs.microsoft.com/en-us/powershell/module/psdesiredstateconfiguration/remove-dscconfigurationdocument?view=powershell-5.1)
169+
> or delete the local configuration file
170+
> (this is the only option for Linux nodes).
171+
172+
### Azure portal
173+
174+
From Azure Automation, click on **State configuration (DSC)** in the table of contents.
175+
Next click **Nodes** to view the list of nodes that are registered with the service.
176+
Click on the name of the node you wish to remove.
177+
In the Node view that opens, click **Unregister**.
178+
179+
### PowerShell
180+
181+
To unregister a node from Azure Automation State Configuration service using PowerShell,
182+
follow the documentation for the cmdlet
183+
[Unregister-AzAutomationDscNode](https://docs.microsoft.com/en-us/powershell/module/az.automation/unregister-azautomationdscnode?view=azps-2.0.0).
184+
154185
## Next steps
155186

156187
- To get started, see [Getting started with Azure Automation State Configuration](automation-dsc-getting-started.md)

articles/azure-monitor/app/asp-net-troubleshoot-no-data.md

Lines changed: 3 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -246,18 +246,10 @@ You can modify these parameters as needed.
246246
- **MaxCollectSec**. Set this parameter to prevent PerfView from running indefinitely and affecting the performance of your server.
247247
- **OnlyProviders**. Set this paramater to only collect logs from the SDK. You can customize this list based on your specific investigations.
248248

249-
Our full list of providers is:
250249

251-
- Microsoft-ApplicationInsights-Core
252-
- Microsoft-ApplicationInsights-Extensibility-DependencyCollector
253-
- Microsoft-ApplicationInsights-Extensibility-Rtia-SharedCore
254-
- Microsoft-ApplicationInsights-Extensibility-Web
255-
- Microsoft-ApplicationInsights-Extensibility-WindowsServer
256-
- Microsoft-ApplicationInsights-Web
257-
- Microsoft-ApplicationInsights-WindowsServer-TelemetryChannel
258-
259-
260-
For more information, see [Recording performance traces with PerfView](https://github.com/dotnet/roslyn/wiki/Recording-performance-traces-with-PerfView).
250+
For more information,
251+
- [Recording performance traces with PerfView](https://github.com/dotnet/roslyn/wiki/Recording-performance-traces-with-PerfView).
252+
- [Application Insights Event Sources](https://github.com/microsoft/ApplicationInsights-Home/tree/master/Samples/ETW)
261253

262254
## Still not working...
263255
* [Application Insights forum](https://social.msdn.microsoft.com/Forums/vstudio/en-US/home?forum=ApplicationInsights)

articles/azure-monitor/insights/azure-networking-analytics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -216,8 +216,8 @@ To use the updated solutions:
216216

217217
| Instead of: | Use: |
218218
| --- | --- |
219-
| NetworkApplicationgateways &#124; where OperationName=="ApplicationGatewayAccess" | AzureDiagnostics &#124; where ResourceType="APPLICATIONGATEWAYS" and OperationName=="ApplicationGatewayAccess" |
220-
| NetworkApplicationgateways &#124; where OperationName=="ApplicationGatewayPerformance" | AzureDiagnostics &#124; where ResourceType=="APPLICATIONGATEWAYS" and OperationName=ApplicationGatewayPerformance |
219+
| NetworkApplicationgateways &#124; where OperationName=="ApplicationGatewayAccess" | AzureDiagnostics &#124; where ResourceType=="APPLICATIONGATEWAYS" and OperationName=="ApplicationGatewayAccess" |
220+
| NetworkApplicationgateways &#124; where OperationName=="ApplicationGatewayPerformance" | AzureDiagnostics &#124; where ResourceType=="APPLICATIONGATEWAYS" and OperationName=="ApplicationGatewayPerformance" |
221221
| NetworkSecuritygroups | AzureDiagnostics &#124; where ResourceType=="NETWORKSECURITYGROUPS" |
222222

223223
+ For any field that has a suffix of \_s, \_d, or \_g in the name, change the first character to lower case

articles/azure-monitor/insights/network-performance-monitor-service-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -124,7 +124,7 @@ If you observe an abnormality, follow these steps:
124124
* If the application is running slow, determine whether poor application performance is because of the network or an issue on the application provider's end.
125125

126126
## GCC Office URLs for US Government customers
127-
For US Government Virginia region, only DOD URLs are built-in NPM. Customers using GCC URLs need to create custom tests and add each URL inidividually.
127+
For US Government Virginia region, only DOD URLs are built-in NPM. Customers using GCC URLs need to create custom tests and add each URL individually.
128128

129129
| Field | GCC |
130130
|:--- |:--- |

articles/azure-monitor/platform/alerts-activity-log-service-notifications.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Learn how to [Configure webhook notifications for existing problem management sy
8787
8888
## Alert with existing action group using Azure portal
8989

90-
1. Follow steps 1 through 7 in the previous section to create your service health notification.
90+
1. Follow steps 1 through 6 in the previous section to create your service health notification.
9191

9292
1. Under **Define action group**, click the **Select action group** button. Select the appropriate action group.
9393

articles/backup/backup-azure-arm-vms-prepare.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -65,6 +65,9 @@ In addition, there are a couple of things that you might need to do in some circ
6565

6666
![List of backup vaults](./media/backup-azure-arm-vms-prepare/rs-list-of-vaults.png)
6767

68+
> [!NOTE]
69+
> Azure Backup service creates a separate resource group (other than the VM resource group) to store snapshot, with the naming format **AzureBackupRG_geography_number** (example: AzureBackupRG_northeurope_1). The data in this resource group will be retained for the duration in days as specified in *Retain instant recovery snapshot* section of the Azure Virtual Machine Backup policy. Applying a lock to this resource group can cause backup failures.
70+
6871
### Modify storage replication
6972

7073
By default, vaults use [geo-redundant storage (GRS)](https://docs.microsoft.com/azure/storage/common/storage-redundancy-grs).

articles/backup/backup-azure-mars-troubleshoot.md

Lines changed: 25 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -36,9 +36,29 @@ We recommend you perform the below validation, before you start troubleshooting
3636

3737
## Invalid vault credentials provided
3838

39-
| Error details | Possible causes | Recommended actions |
40-
| --- | --- | --- |
41-
| **Error** </br> *Invalid vault credentials provided. The file is either corrupted or does not have the latest credentials associated with recovery service. (ID: 34513)* | <ul><li> The vault credentials are invalid (that is, they were downloaded more than 48 hours before the time of registration).<li>MARS Agent is unable to download files to the Windows Temp directory. <li>The vault credentials are on a network location. <li>TLS 1.0 is disabled<li> A configured proxy server is blocking the connection. <br> | <ul><li>Download the new vault credentials.(**Note**: If multiple vault credential files are downloaded previously, only the latest downloaded file is valid within 48 hours.) <li>Launch **IE** > **Setting** > **Internet options** > **Security** > **Internet**. Next, select **Custom Level**, and scroll until you see the file download section. Then select **Enable**.<li>You might also have to add these sites in IE [trusted sites](https://docs.microsoft.com/azure/backup/backup-configure-vault#verify-internet-access).<li>Change the settings to use a proxy server. Then provide the proxy server details. <li> Match the date and time with your machine.<li>If you get an error stating that file downloads are not allowed, it is likely that there are a large number of files in the C:/Windows/Temp directory.<li>Go to C:/Windows/Temp and check whether there are more than 60,000 or 65,000 files with the .tmp extension. If there are, delete these files.<li>Ensure that you have .NET framework 4.6.2 installed. <li>If you have disabled TLS 1.0 due to PCI compliance, refer to this [troubleshooting page](https://support.microsoft.com/help/4022913). <li>If you have anti-virus software installed on the server, exclude the following files from the anti-virus scan: <ul><li>CBengine.exe<li>CSC.exe, which is related to .NET Framework. There is a CSC.exe for every .NET version that's installed on the server. Exclude CSC.exe files that are tied to all versions of .NET Framework on the affected server. <li>Scratch folder or cache location. <br>*The default location for the scratch folder or the cache location path is C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch*.<br><li>The bin folder C:\Program Files\Microsoft Azure Recovery Services Agent\Bin
39+
**Error message**: Invalid vault credentials provided. The file is either corrupted or does not have the latest credentials associated with recovery service. (ID: 34513)
40+
41+
| Cause | Recommended Action |
42+
| --- | --- |
43+
| **The vault credentials are invalid** <br/> <br/> Vault credential files might be corrupt or may have expired (i.e. downloaded more than 48 hours before the time of registration)| Download a new credential from Recovery Services vault from the Azure portal (see *Step 6* under [**Download the MARS agent**](https://docs.microsoft.com/azure/backup/backup-configure-vault#download-the-mars-agent) section) and perform the below: <ul><li> If you have already installed and registered Microsoft Azure Backup Agent, then open the Microsoft Azure Backup Agent MMC console and choose **Register Server** from Action Pane to complete the registration with the newly downloaded credentials <br/> <li> If the new installation failed then try re-installing using the new credentials</ul> **Note**: If multiple vault credential files are downloaded previously, only the latest downloaded file is valid within 48 hours. Hence it is recommended to download fresh new vault credentials file.
44+
| **Proxy Server/firewall is blocking <br/>or <br/>No Internet connectivity** <br/><br/> If your machine or Proxy Server has limited Internet access then without listing the necessary URLs the registration will fail.| To resolve this issue, perform the below:<br/> <ul><li> Work with your IT team to ensure the system has Internet connectivity<li> If you do not have Proxy server, then ensure the proxy option is unselected when registering the agent, verify proxy settings steps listed [here](#verifying-proxy-settings-for-windows)<li> If you do have a firewall/proxy server then work with your networking team to ensure that below URLs and IP address have access<br/> <br> **URLs**<br> - *www.msftncsi.com* <br>- *.Microsoft.com* <br> - *.WindowsAzure.com* <br>- *.microsoftonline.com* <br>- *.windows.net* <br>**IP address**<br> - *20.190.128.0/18* <br> - *40.126.0.0/18* <br/></ul></ul>Try re-registering after you complete the above troubleshooting steps
45+
| **Anti-virus software is blocking** | If you have anti-virus software installed on the server, then add necessary exclusion rules for the following files from the anti-virus scan: <br/><ui> <li> *CBengine.exe* <li> *CSC.exe*<li> Scratch folder, the default location is *C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch* <li> Bin folder at *C:\Program Files\Microsoft Azure Recovery Services Agent\Bin*
46+
47+
### Additional recommendations
48+
- Go to *C:/Windows/Temp* and check whether there are more than 60,000 or 65,000 files with the .tmp extension. If there are, delete these files
49+
- Ensure the machine’s date and time is matching with local time zone
50+
- Ensure the [following](backup-configure-vault.md#verify-internet-access) sites are added to IE trusted sites
51+
52+
### Verifying proxy settings for Windows
53+
54+
- Download **psexec** from [here](https://docs.microsoft.com/sysinternals/downloads/psexec)
55+
- Run this `psexec -i -s "c:\Program Files\Internet Explorer\iexplore.exe"` command from elevated prompt:
56+
- This will launch *Internet Explorer* window
57+
- Go to *Tools* -> *Internet Options* -> *Connections* -> *LAN settings*
58+
- Verify proxy settings for *System* account
59+
- If no proxy is configured and proxy details are provided, then remove the details
60+
- If proxy is configured and proxy details are incorrect, then ensure *Proxy IP* and *port* details are accurate
61+
- Close *Internet Explorer*
4262

4363
## Unable to download vault credential file
4464

@@ -100,11 +120,11 @@ If scheduled backups don't get triggered automatically, while manual backups wor
100120

101121
`PS C:\WINDOWS\system32> Set-ExecutionPolicy Unrestricted`
102122

103-
- Ensure there are no missing or corrupted **PowerShell** module **MSonlineBackup**. In case there are any missing or corrupt file, to resolve this issue perform the below:
123+
- Ensure there are no missing or corrupted **PowerShell** module **MSonlineBackup**. In case there is any missing or corrupt file, to resolve this issue perform the below:
104124

105125
- From any machine having MARS agent that is working properly, copy the MSOnlineBackup folder from *(C:\Program Files\Microsoft Azure Recovery Services Agent\bin\Modules)* path.
106126
- Paste this in problematic machine in the same path *(C:\Program Files\Microsoft Azure Recovery Services Agent\bin\Modules)*.
107-
- If **MSOnlineBackup** folder is already exists in the machine, paste or replace the content files inside it.
127+
- If **MSOnlineBackup** folder is already existed in the machine, paste or replace the content files inside it.
108128

109129

110130
> [!TIP]

0 commit comments

Comments
 (0)