By: Nicholas Dritsas
Reviewers: James Podgorski, Olivier Matrat, Sanjay Mishra
Azure’s Iaas VMs plus Virtual Networks can be used to configure easily a set of servers/VMs to host the main components of a BI solution. This process assumes you already have an Azure subscription plus access to add new VMs and Virtual Networks.
Setting up a virtual network
Creating a DC (this step must be done first before adding any other VM in the network you just created).
i. After you connect, ensure its IP is indeed 10.4.0.4 by running ipconfig in command prompt.
ii. Using the disk management found in server manager, format the new disk as F: (or any other drive letter you like) drive. Create 3 subdirectories there to host AD db, logs and sysvol files later on.
iii.Then, we need to promote to it to DC, look here for details. In simple terms, run the program dcpromo.exe from the command prompt and follow instructions to create a new forest.
iv. After it restarts, go to Windows Explorer, select Network and Enable file sharing and discovery.
v. Create a new domain admin account user too for future use
4. Now, you have a domain in azure. Create one new VM from the Gallery using SQL 2012. Then, join the domain you just created. Go to Windows Explorer, select Network and Enable file sharing and discovery. Now, you should be able to ping the DC by IP and name.
i. You have to open inbound ports in the vm that hosts ssas and sql server (or you disable the firewall for domain networks if you like). See here: http://msdn.microsoft.com/en-us/library/bb934283.aspx
ii. You can find the ssas ports or any process ports from this link: http://support.microsoft.com/kb/2466860. I added a new inbound rule to allow ports 1433 and 2383. 1433 is for sql server when 2383 is the port for the defaultssas instance.
5. Create another new VM from the Gallery using Windows 2008 R2. Then, join the domain you just created. Go to Windows Explorer, select Network and Enable file sharing and discovery. Now, you should be able to ping the DC.
Very useful. What would take it further is to use Azure Active Directory to offload the need for the DC within the stack.