Tag Archives: Ip address

How to re-enable Network Interface in Azure VM?

In Hyper-V or VMware virtualization environment, Enable/Disable NIC in a VM is not a big deal. Even if you do not have NIC or valid IP configure, administrators still can connect to VM as it does have “Console” access. Few weeks ago, I received an email from one of my regular blog readers. He accidently disabled NIC in azure vm and he lost RDP access to it. since there is no console access like other on-premises virtualization solution, of cause he was panicking. In this blog post I am going to share what you can do to re-enable your Azure VM NIC in such scenario. 

In my demo setup, I have an active azure VM running with private IP address. 


I logged in to VM as administrator and disable the NIC.

Now I need to regain the RDP access to server. in order to do that, log in to Azure Portal as Global Administrator and click on Cloud Shell button in right hand top corner. 


When window load up makes sure you are using PowerShell option. 


Now we need to find out the NIC details of the VM that we having issues with. We can do this using,

Get-AzureRmNetworkInterface -ResourceGroupName "REBELADMIN-DEMO" 

In this command, -ResourceGroupName represent the resource group that VM belongs to. In my demo setup I only have one VM under that resource group.  but if you have more VMs it can be hard to find the relevant info. In that case I recommend to use portal itself to view this info.

In here, note down the network interface name, IP address and allocation method you using. 


Now, we need to assign a new IP address to the same nic from same subnet. It can be done using,

$Nic = Get-AzureRmNetworkInterface -ResourceGroupName "REBELADMIN-DEMO" -Name "rebeladmin-vm1123"

$Nic.IpConfigurations[0].PrivateIpAddress = ""

$Nic.IpConfigurations[0].PrivateIpAllocationMethod = "Static"

$Nic.Tag = @{Name = "Name"; Value = "Value"}

Set-AzureRmNetworkInterface -NetworkInterface $Nic

In above commands, rebeladmin-vm1123 represent the network interface name. is the new ip address for the network interface. PrivateIpAllocationMethod define the ip allocation method. Set-AzureRmNetworkInterface cmdlet sets the network interface configuration. 


Great!! Now I got my RDP access back with new IP address.


But it is not the original IP it had, now we can change it back with,

$Nic2 = Get-AzureRmNetworkInterface -ResourceGroupName "REBELADMIN-DEMO" -Name "rebeladmin-vm1123"

$Nic2.IpConfigurations[0].PrivateIpAddress = ""

$Nic2.IpConfigurations[0].PrivateIpAllocationMethod = "Static"

$Nic2.Tag = @{Name = "Name"; Value = "Value"}

Set-AzureRmNetworkInterface -NetworkInterface $Nic2


Once it is applied, I can access server via RDP and now it has same private IP address it had.


If you using dynamic IP allocation method, you need to make it static, then change the ip and go back to dynamic mode. 

This marks the end of this blog post. If you have any questions feel free to contact me on rebeladm@live.com also follow me on twitter @rebeladm to get updates about new blog posts.

How to setup active directory sites, subnets, site-links?

In my previous article I explain the use of AD sites, subnets. If you still not read it you can find it here.

In this article let’s look in to sites and subnet setup and configurations.

In demo I am using the following setup.

Server Name


Operating System




Primary Domain Controller

Windows server standard 2012 R2

Site A (HQ)


Additional Domain Controller

Windows server standard 2012 R2

Site B (Branch Office)

In demo SRV1 server is located in Branch office which is located in different geographical location. It is connected to primary domain via 256kb link. Currently it is setup under default AD site.

In the demo I am going to create 2 sites called Site A and Site B. then assign the relevant servers to it along with the subnets.

To initiate the configuration we need to log in to the primary DC. The user account used for the configuration must be member of domain admin or enterprise admin security groups.

All the configurations will be done via “Active Directory Sites and Services” mmc.

To load it go to Server manager > Tools > Active Directory Sites and Services


As we can see below, both servers are under default AD site.


Create New Site  

1.    Right click on “Sites” and select “New Site”


2.    It will open new window and here type the new Site name. Also we need to select the Site link for the site. In here I will use the default site link. Click “Ok” to create site.


3.    Then it will give information windows and click ok to exit from window.


4.    Then I follow same steps and create SiteB.


Create Subnets

According to the table we need to create the subnets for each site and associate them.

1.    In Active Directory Sites and Services mmc right click on “Subnets” and click on New Subnet.


2.    In next window type the subnet with the relevant prefix. Also under “select a site object for this prefix” option select the relevant site it should associate. Then click OK.


3.    I did follow same steps and created the subnet and assign it with siteB.


Create Site Links

As per demo configuration I explain, Site A and Site B connected with 256kb link. We need to create new site link for it.

1.    In Active Directory Sites and Services mmc right click on “Inter-Site Transports > IP” and click on New Site Link.


2.    Then in next windows, type a name for the link and select the sites which will communicate between each other and click add to move them to “Sites in this site link”



3.    Then click ok to create the link.
4.    The link will be created with the default values but we can optimize it with our requirement. In order to change settings right click on the link and select properties.


5.    In here, the cost define the link bandwidth. You can find the cost in here https://technet.microsoft.com/en-us/library/cc782827%28v=ws.10%29.aspx according to Microsoft.


6.    Also we can define when to replicate changes between sites. To change the schedule click on “Change Schedule” button.


7.    In next window you can define the schedule. I have go ahead and did a custom schedule.


8.    Click ok to apply the changes.

Move Domain controllers to sites

Now we have sites, subnets an site links setup. Now we need to move the domain controllers in to relevant sites.

1.    In Active Directory Sites and Services mmc go to “Default-First-Site-Name > Servers”. Then right click on the DC server you need to move and select option move.


2.    In next window select the Site it should move to. According to demo I select SiteA and click ok.


3.    Then we can see its move to relevant site.


4.    I have followed same steps and move the SRV1 to SiteB.


This completes the configuration of sites, subnets and site links. If you have any questions about the post feel free to contact me on rebeladm@live.com