Skip to content

Commit 41a7f78

Browse files
Merge pull request MicrosoftDocs#81781 from genlin/ci01
Fix issues 7/10
2 parents c5e0de9 + 4dccec8 commit 41a7f78

File tree

3 files changed

+13
-11
lines changed

3 files changed

+13
-11
lines changed

articles/billing/billing-how-to-change-azure-account-profile.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,11 +81,17 @@ To opt out of receiving marketing emails:
8181
1. Go to the [request form](https://account.microsoft.com/profile/permissions-link-request) to submit a request by using your profile email address. You'll receive a link by email to update your preferences.
8282
2. Select the link to open the **Manage communication permissions** page. This page shows you the types of marketing communications that the email address is opted in to. Clear any topics that you want to opt out of, and then select **Save**.
8383

84-
8584
![Example of the page for managing communication permissions](./media/billing-how-to-change-azure-account-profile/manage-communication-permissions.png)
8685

8786
When you opt out of marketing communications, you still receive service notifications, based on your account.
8887

88+
## Change the subscription name
89+
90+
1. Sign in to the [Azure portal](https://portal.azure.com), select **Subscription** from the left pane, and then select the subscription that you want to rename.
91+
1. Select **Overview**, and then select **Rename** from the command bar.
92+
![Example of renaming Azure subscription](./media/billing-how-to-change-azure-account-profile/rename-sub.png)
93+
1. After you have changed the name, select **Save**.
94+
8995
## Need help? Contact us.
9096

9197
If you have questions or need help, [create a support request](https://go.microsoft.com/fwlink/?linkid=2083458).
Loading

articles/virtual-machines/troubleshooting/troubleshoot-activation-problems.md

Lines changed: 6 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,6 @@ For the VM that is created from a custom image, you must configure the appropria
7979
8080
3. Make sure that the VM is configured to use the correct Azure KMS server. To do this, run the following command:
8181
82-
8382
```powershell
8483
Invoke-Expression "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /skms kms.core.windows.net:1688"
8584
```
@@ -88,30 +87,27 @@ For the VM that is created from a custom image, you must configure the appropria
8887
8988
4. Verify by using Psping that you have connectivity to the KMS server. Switch to the folder where you extracted the Pstools.zip download, and then run the following:
9089
91-
9290
```
9391
\psping.exe kms.core.windows.net:1688
9492
```
95-
96-
9793
In the second-to-last line of the output, make sure that you see: Sent = 4, Received = 4, Lost = 0 (0% loss).
9894
9995
If Lost is greater than 0 (zero), the VM does not have connectivity to the KMS server. In this situation, if the VM is in a virtual network and has a custom DNS server specified, you must make sure that DNS server is able to resolve kms.core.windows.net. Or, change the DNS server to one that does resolve kms.core.windows.net.
10096
10197
Notice that if you remove all DNS servers from a virtual network, VMs use Azure’s internal DNS service. This service can resolve kms.core.windows.net.
10298
103-
Also verify that the guest firewall has not been configured in a manner that would block activation attempts.
99+
Also make sure that the outbound network traffic to KMS endpoint with 1688 port is not blocked by the firewall in the VM.
104100
105-
1. After you verify successful connectivity to kms.core.windows.net, run the following command at that elevated Windows PowerShell prompt. This command tries activation multiple times.
101+
5. After you verify successful connectivity to kms.core.windows.net, run the following command at that elevated Windows PowerShell prompt. This command tries activation multiple times.
106102
107103
```powershell
108104
1..12 | ForEach-Object { Invoke-Expression "$env:windir\system32\cscript.exe $env:windir\system32\slmgr.vbs /ato" ; start-sleep 5 }
109105
```
110106
111-
A successful activation returns information that resembles the following:
112-
113-
**Activating Windows(R), ServerDatacenter edition (12345678-1234-1234-1234-12345678) …
114-
Product activated successfully.**
107+
A successful activation returns information that resembles the following:
108+
109+
**Activating Windows(R), ServerDatacenter edition (12345678-1234-1234-1234-12345678) …
110+
Product activated successfully.**
115111
116112
## FAQ
117113

0 commit comments

Comments
 (0)