From 28379e7722fb925dcca58782aef51776bdaeed82 Mon Sep 17 00:00:00 2001 From: Pedro Lopes Date: Mon, 8 Jul 2019 12:49:56 -0700 Subject: [PATCH] Update register.md --- .../sql-server-extended-security-updates/register.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/samples/manage/sql-server-extended-security-updates/register.md b/samples/manage/sql-server-extended-security-updates/register.md index 05ca6b4f..3c5015e8 100644 --- a/samples/manage/sql-server-extended-security-updates/register.md +++ b/samples/manage/sql-server-extended-security-updates/register.md @@ -9,8 +9,7 @@ ## Register a single SQL Server instance It's required that at least one SQL Server instance is registered in order to download an ESU package (if and when available). -> [!IMPORTANT] -> It's not required to register a SQL Server instance for ESUs when running an Azure Virtual Machine that is configured for Automatic Updates. For more information, see [Manage Windows updates by using Azure Automation](https://docs.microsoft.com/azure/automation/automation-tutorial-update-management). +**Important**: It's not required to register a SQL Server instance for ESUs when running an Azure Virtual Machine that is configured for Automatic Updates. For more information, see [Manage Windows updates by using Azure Automation](https://docs.microsoft.com/azure/automation/automation-tutorial-update-management). ### Steps to register an instance 1. To register a new SQL Server instance, click the ***+ Register*** button in the top bar. @@ -62,8 +61,7 @@ It's required that at least one SQL Server instance is registered in order to do ## Bulk register SQL Server instances Bulk registering SQL Server instances to download an ESU package (if and when available) is done through uploading a CSV file. -> [!IMPORTANT] -> It's not required to register SQL Server instances for ESUs when running Azure Virtual Machines that are configured for Automatic Updates. For more information, see [Manage Windows updates by using Azure Automation](https://docs.microsoft.com/azure/automation/automation-tutorial-update-management). +**Important**: It's not required to register SQL Server instances for ESUs when running Azure Virtual Machines that are configured for Automatic Updates. For more information, see [Manage Windows updates by using Azure Automation](https://docs.microsoft.com/azure/automation/automation-tutorial-update-management). Customers that already have an inventory application that holds the required registration information can generate a CSV file from that inventory, following the the [CSV formatting requirements](#csv) later in this page. @@ -102,8 +100,7 @@ The CSV file **must** be generated with the following format: 1 Only for Azure Virtual Machine registrations -> [!TIP] -> For example Powershell scripts that can generate the required SQL Server instance registration information into a CSV file, see [ESU registration script examples](scripts.md). +**Tip**: For example Powershell scripts that can generate the required SQL Server instance registration information into a CSV file, see [ESU registration script examples](scripts.md). ### CSV Example 1 - on-premises @@ -129,4 +126,4 @@ ServerUS2\SQL02,2008,Enterprise,8,Azure Virtual Machine,61868ab8-16d4-44ec-a9ff- SalesServer\SQLProdSales,2008 R2,Developer,8,Azure Virtual Machine,61868ab8-16d4-44ec-a9ff-f35d05922847,RG,VM3,2008 R2 ``` -Refer to [MyAzureVMs.csv](./scripts/MyAzureVMs.csv) for an Azure VM targetted CSV file example. \ No newline at end of file +Refer to [MyAzureVMs.csv](./scripts/MyAzureVMs.csv) for an Azure VM targetted CSV file example.