Enjoy

Of course there are various ways to interact with Storage Account that includes Portal, AzCopy, REST API etc. One of the ways is to use 3rd party software like Azure Storage Explorer available on Codeplex.

You can visit http://azurestorageexplorer.codeplex.com/ to download the software.

Once completed, launch Azure Storage Explorer. You need the Storage Account name and the access key that you can get it from the Azure Management Portal.

In my case, I already have Azure Storage Account configured in my Azure subscription. So, I will click on Add Account button.

Fill in the details in the box like Storage account name and Storage account key. Also, for security, check on Use HTTPS.

Note: You can find Azure Storage Account and Access Key over here

Once you get all the details, fill in the details in the Azure Storage Explorer.

Now click on Add Storage Account. Click on Yes on the following box.

And you are ready to go. Now you can manage your Blob storage for adding, deleting files easily.

Hope you enjoyed this post.

Thank you.

It’s been a long time I was waiting for my blog migration. Finally my blog has been migrated to Microsoft.com domain.

The blog has a fresh new theme, this is the default one and I have not done any customization so far.

With this change our Microsoft TechNet blog URL changes to the following URL. So update it accordingly!

http://blogs.technet.microsoft.com/aviraj

For any queries feel free to reach out to me at aviraj@microsoft.com

Thanks you.

Regards,
Aviraj Ajgekar
Microsoft Corporation
New York Metro District

You can find job descriptions to all the available Azure Solution Architect roles over here

If you are interested, do send me a note at aviraj@microsoft.com

Regards,
Aviraj Ajgekar
Microsoft New York

Building an Optimized Private Cloud using Windows Server “8” Server Core

Microsoft aims to reduce Windows Update restarts (An article from ZDNet)  Minimizing restarts after automatic updating in Windows Update Here is an excellent blog that explains different types of patches that we refer within Engineering. Each has its own significant purpose during the operating system’s lifecycle like update, patches or hotfixes will fix any vulnerabilities, Patch Tuesday offers critical patches every second Tuesday including security bulletin etc. And then we have Service Packs, Update Roll ups etc. GDR, QFE, LDR... WTH?  Then there was a query around do the patches grow a lot as OS becomes older n older. Well, the patches are nothing but when Engineering team finds any bugs or vulnerabilities or if these bugs/vulnerabilities/zero day exploits reported by people (customers, partners, IT Professionals, Developers, security researchers etc.) So the number patches will continue to come as the software is made of millions of lines of code, as and when it is detected or identifies we try to release the update or patch based upon the critical nature of the bug or vulnerability. As we move towards the next generation we are trying to offer various option for customers to reduce the overall attack surface by reducing the size of the operating system using different installation option. Server Core is classic example, which does not include GUI, Start, Internet Explorer, Control Panel etc. that means that code is not present in an OS so no patches/updates needed for those components. With the vNext releases, like Windows Server 2016, we have introduced Nano Server installation option that has a total footprint less 500 MB of an entire Server OS it means less attack surface and less patches/updates meaning less number reboot cycles in the long run. In the recent preview release we have published some numbers around the overall experience with number of patches/reboots in the release. Nano Server will allow customers to install just the components they require and nothing more. The initial results are promising.  Based on the current builds, compared to Server, Nano Server has:

• 93 percent lower VHD size

• 92 percent fewer critical bulletins

• 80 percent fewer reboots

You can find more around Nano Server here http://blogs.technet.com/b/windowsserver/archive/2015/04/08/microsoft-announces-nano-server-for-modern-apps-and-cloud.aspx Again, this post is my general observation while working with customers and with my personal experience. I am not using any fancy engineering terms but just trying to share the observation in simple for everyone to understand how are we heading in this space. Hope it helps. Regards Aviraj Ajgekar - Technical Specialist for Datacenter & Cloud covering Microsoft New York City.

Features

• Explore the arrangement of the nearly 3,000 names on the Memorial, which reflects where people were on 9/11 and relationships they shared with others who were lost that day.
• Listen to recorded remembrances of those who were lost, spoken by family and friends.
• Locate sponsored cobblestones on the Memorial plaza

Recently, we announced lot of enhancements in Microsoft Azure. One of them being the cross-VNET connectivity between same subscription or different subscriptions. You can read more about it here http://msdn.microsoft.com/en-us/library/azure/dn690122.aspx

I am going to cover a sample test configuration that I have done in my subscription for your reference. Feel free to refer this along with the MSDN documentation.

So, let’s begin.

What you need?

Microsoft Azure Subscription x 2 (You can also refer the link above to perform the VNET to VNET configuration using a single subscription)
Windows Azure PowerShell Module

Let’s Begin – Here is my setup

I have 2 Azure Subscriptions…

NETWORK TOPOLOGY

This is how it will look like

Now, let’s start with steps.

Step 1: Create Affinity Groups in these 2 subscriptions.

AVIRAJ-CORP – Affinity Group: NYC
AVIDEMO-INTERNAL – Affinity Group: JPN

Step 2: Create Storage Accounts in these 2 subscriptions

AVIRAJ-CORP – Storage Account: nyc
AVIDEMO-INTERNAL – Storage Account: jpn

Step 3: Create DNS Server in both the subscriptions.

Creating DNS Server in subscription AVIRAJ-CORP in NYC as CROSS-VNET – 10.10.1.4   (This will be the first virtual machine created in VNET1 and it will be assigned 10.10.1.4 within IP Range 10.10.1.X, we will configure DC & DNS on that VM)
Creating DNS Server in subscription AVIDEMO-INTERNAL in JPN as CROSS-VNET – 10.10.1.4   (As we want our VNET2 VMs to talk to VNET1 VMs, we have to manually create DNS entry that will point to VNET1 VM with DNS)

NOTE: In the VNET to VNET Connectivity in the Same subscription, you do not need to create 2 DNS entries.

Step 4: Create VNET1 in AVIRAJ-CORP Subscription with Affinity Group NYC

Go to NEW –> NETWORK SERVICES –> VIRTUAL NETWORK –> CUSTOM CREATE

Enter Virtual Network Name: VNET1, select affinity group NYC. Click Next

Select DNS from drop down menu CROSS-VNET (10.10.1.4) and check mark on Configure a site-to-site VPN and click Next

On the next screen we are adding a LOCAL NETWORK VNET2 configuration for Virtual Network VNET1. VNET2 IP Configuration will act as a LOCAL NETWORK IP CONFIGURATION is this scenario. Refer the table in the beginning. Once configured click Next.

On this last screen, we will configure IP Address range for VIRTUAL NETWORK (VNET1) as per the table.

Add the Address Space as per table 10.10.0.0 and CIDR /16 (65536)

Create a new SUBNET called AD with IP Range 10.10.1.0 and CIDR /24 (256)

Click on add gateway subnet. Once done click on Check box to complete the wizard.

And it will look like this when it’s created

When you click on Configure tab, you will see the complete configuration that we just created

That’s done.

Step 5: Create VNET2 in AVIDEMO-INTERNAL Subscription with Affinity Group JPN

Repeat the steps like Step 4 and complete the VNET2 creation in the JPN affinity group in the AVIDEMO-INTERNAL subscription.

Enter Virtual Network Name: VNET2, select affinity group JPN. Click Next

Select DNS from drop down menu CROSS-VNET (10.10.1.4) and check mark on Configure a site-to-site VPN and click Next

On the next screen we are adding a LOCAL NETWORK VNET1 configuration for Virtual Network VNET2. VNET1 IP Configuration will act as a LOCAL NETWORK IP CONFIGURATION is this scenario. Refer the table in the beginning. Once configured click Next.

On this last screen, we will configure IP Address range for VIRTUAL NETWORK (VNET2) as per the table.

Add the Address Space as per table 192.168.0.0 and CIDR /16 (65536)

Create a new SUBNET called AD with IP Range 192.168.1.0 and CIDR /24 (256)

Click on add gateway subnet. Once done click on Check box to complete the wizard.

And it will look like this when it’s created.

When you click on Configure tab, you will see the complete configuration that we just created.

That’s done.

Step 6: Create Dynamic Routing VPN Gateways for VNET1 & VNET2. Note: Static Routing Gateways are not supported. Refer MSDN Link.

Go to Networks –> VNET1 –> Dashboard. Click on CREATE GATWAY –> Dynamic Routing. And click on Yes.

Once you click Yes, you will the dashboard status like this…

That’s done. We will wait for the gateway to be created.

Similarly, let’s create a gateway for VNET2. Go to Networks –> VNET2 –> Dashboard. Click on CREATE GATWAY –> Dynamic Routing. And click on Yes. Once you click Yes, you will the dashboard status like this…

NOTE: It will take somewhere between 15-20 mins. before you see the Gateway IP in the Dashboard.

Once completed, you will see gateway ip address for VNET.

Here is VNET1

Here is VNET2

That’s done.

Step 7: Replace the temporary placement IP Address in the Local Networks VNET1 & VNET2 VPN Device IP Address with the actual Gateway IP address that we just obtained.

Go to Networks –> VNET1 –> Dashboard. Copy the Gateway IP Address 137.116.XX.XX.

Go to Network –> LOCAL NETWORKS. Click on VNET1 with IP Address 1.0.0.0. Click on Edit

Replace the VPN Device IP Address 1.0.0.0 with the VNET1 Gateway IP Address 137.116.XX.XX.  On the next page do not change anything click Next and Finish.

Done.

Now, similarly we will do this for other network

Go to Networks –> VNET2 –> Dashboard. Copy the Gateway IP Address 207.46.XX.XX.

Go to Network –> LOCAL NETWORKS. Click on VNET2 with IP Address 2.0.0.0. Click on Edit

Replace the VPN Device IP Address 2.0.0.0 with the VNET2 Gateway IP Address 207.46.XX.XX.  On the next page do not change anything click Next and Finish.

Done.

Once both the LOCAL NETWORKS VPN DEVICE IP ADDRESSES updated, it will look like this.

Step 8: Set the IPsec/IKE pre-shared keys for both the subscriptions.

For this configuration, we will use PowerShell. I am assuming that you understand how to configuration Microsoft Azure Subscriptions using PowerShell. Refer this blog for basics.

In order to configured shared keys I will run the following PowerShell cmdlets

Set-AzureVNetGatewayKey -VNetName VNet1 -LocalNetworkSiteName VNet2 -SharedKey A1B2C3D4
Set-AzureVNetGatewayKey -VNetName VNet2 -LocalNetworkSiteName VNet1 -SharedKey A1B2C3D4

As soon as you set the shared keys for both the subscriptions’ VNETs, you will see in few moments that the VNET to VNET Connection gets established.,

Step 9: Verifying connectivity between Cross-Subscription VNET to VNET.

Go to Networks –> VNET1 –> Dashboard. Observe the connection established.

Similarly, go to Networks –> VNET2 –> Dashboard. Observe the connectivity.

Enjoy

Step 10: Create 2 Virtual Machines in each Subscription connected to respective VNETs and see how they communicate.

First create a Windows Server 2012 R2 VM in Subscription (AVIRAJ-CORP) using VNET1.

Next, select the appropriate subscription AVIRAJ-CORP and choose VNET1. And select storage account nyc.

Continue and create VM.

Similarly, create a Windows Server 2012 R2 VM in Subscription (AVIDEMO-INTERNAL) using VNET2.

Next, select the appropriate subscription AVIDEMO-INTERNAL and choose VNET2. And select storage account jpn.

Continue and create VM.

NOTE: It will take about 10 mins. to create 2 VMs.

Once VMs are ready you will see their status like this.

Let’s check the configuration from the dashboard for WS2012R2-NYC in AVIRAJ-CORP Subscription

Similarly, check the configuration from the dashboard for WS2012R2-JPN in AVIDEMO-INTERNAL Subscription

That’s ready.

Once the VMs are fully provisioned, you can check the VMs within the Virtual Network dashboard page.

VNET1

Go to Networks –> VNET1 –> Dashboard.

VNET2

Go to Networks –> VNET1 –> Dashboard.

Finally, let’s RDP into the VMs and see their IP Configuration and connectivity between VMs between different VNETs within Cross-Subscription

As soon as you RDP into the VMs. Make sure to open wf.msc and enable Inbound Rules. File and Printer Sharing (Echo Request – ICMPv4-In & ICMPv6-In) This will enable Ping command.

Now, let’s see the IP Configuration of WS2012R2-NYC in AVIRAJ-CORP Subscription. As you can see, IP Address is picked up from the 10.10.1.X IP Range and DNS is picked up as defined i.e. 10.10.1.4

Now, let’s see the IP Configuration of WS2012R2-JPN in AVIDEMO-INTERNAL Subscription

FINAL TEST. Ping each other.

At this stage, I will configure Domain Controller on WS2012R2-NYC machine and it will serve as a DNS for my VMs connected to VNET1 & VNET2.

And friends, that’s Cross-Subscription VNET to VNET connectivity within Microsoft Azure. This is one of many coolest features that we announced during Microsoft TechEd North America 2014. For more details visit https://channel9.msdn.com to explore more around Microsoft Azure Networking.

Hope you enjoy this post and have a great day.

Thanks You & Happy Networking

And that’s the exact problem we will be discussing today. Whether we are building a production environment or a test environment, we have to manage the Windows Product Activation. And it’s not just for the physical hosts managing virtual machines but even for the guest virtual machines running on those boxes.

The Challenge: How to deal with the Windows Product Activation issues in an effective manner?? How to deal with the following problem…

Solution:

Well, we have solved this problem with Windows Server 2012 R2. We have introduced a new feature in Windows Server 2012 R2. This is called as Automatic Virtual Machine Activation.

You can read about it here http://technet.microsoft.com/en-us/library/dn303421.aspx

Automatic Virtual Machine Activation (AVMA) acts as a proof-of-purchase mechanism, helping to ensure that Windows products are used in accordance with the Product Use Rights and Microsoft Software License Terms.

AVMA lets you install virtual machines on a properly activated Windows server without having to manage product keys for each individual virtual machine, even in disconnected environments. AVMA binds the virtual machine activation to the licensed virtualization server and activates the virtual machine when it starts up. AVMA also provides real-time reporting on usage and historical data on the license state of the virtual machine. Reporting and tracking data is available on the virtualization server.

So, in short what do you need to get going??

Supported HOST OS: All you need is a fully activated virtualization host you need Windows Server 2012 R2 DATACENTER. Well, that’s it.

Supported GUEST OS: In order to leverage AVMA feature in guest virtual machine, you need Windows Server 2012 R2 Datacenter, Standard or Essentials edition.

Now, how to get your VMs, activated if you are running any of the listed guest operating system. Here is what you need to do. When you install the supported guest operating system, all you need to do is to install the AVMA Key within the virtual machine. You will find the appropriate AVMA key in the TechNet Link

In this above example I am running Windows Server 2012 R2 Datacenter edition as a guest virtual machine, so I will run the following command.

slmgr /ipk Y4TGP-NPTV9-HTC2H-7MGQ3-DV4TW

And that’s done. Click on OK & you are ready  

Open up Computer Properties & you will notice that the guest virtual machine is automatically activated.

You can embed the AVMA key as a part of your virtual gold image, so that whenever the Windows Server 2012 R2 based guest virtual machine (VM) is running on an activated Windows Server 2012 R2 Datacenter HOST box, the VMs are always activated.

NOTE: In this scenario, the guest VMs are NOT required to be connected to the Internet. This solution works in an offline mode. INTERNET connection is not required for GUEST VMs. Windows Server 2012 R2 Datacenter supports Unlimited number of Guest Virtual Machines

You can read more about this feature including the key tracking, events etc. on the TechNet article. It’s a really small thing but makes a really big difference when you deal with hundreds & thousands of Virtual Machines on daily basis.

Enjoy!

Today, I am sharing couple of useful resources around Windows Azure available on Microsoft Download site.

First one is Windows Azure Datacenter IP Ranges…This file contains the Compute IP address ranges (including SQL ranges) used by the Windows Azure Datacenters. Each section specifies the geographic region and the IP address ranges associated with that region.

DOWNLOAD HERE

Second one is about Windows Azure mini case studies featuring ISVs for your reference.

DOWNLOAD HERE