Azure & Office 365

Posts Tagged ‘Virtual’

Hi All,
I hope you all know that now we can create a SharePoint 2016 VM on Windows Azure. In case you have not tried it yet, you can follow below:

Select New on Windows Azure > Compute > Virtual Machine > From Gallery > Select SharePoint from left hand navigation > Select SharePoint Server 2016 IT preview


While I was working with this VM, I came across an issue where I was unable to configure a SharePoint 2016 farm using the SharePoint 2016 VM created in Windows Azure using one of their template. I found that root of issue was Active Directory. SharePoint cannot work without active directory and not everyone using Azure creates a VM with AD in Windows Azure itself. If you plan to create an AD forest in Azure and then add SharePoint 2016 VM to that domain, please follow my article:

Creating a Lab on Windows Azure
http://blogs.msdn.com/b/mvpawardprogram/archive/2015/02/09/creating-a-lab-on-windows-azure.aspx

 

If you are planning to use this VM only for learning purpose then you may want to create a SharePoint farm without Active Directory. Unlike previous versions of SharePoint, you cannot use Single Server install model to create a SharePoint farm without Active Directory or without installing SQL server.

 

 

To overcome this issue you need 1st install SQL Server and then use below PowerShell command to configure your SharePoint farm. You can download SQL server from below link

https://www.microsoft.com/en-in/download/details.aspx?id=42299 

 

Once SQL server is installed and your local admin account has access to SQL server, you can use SharePoint PowerShell to create tour SharePoint 2016 Farm.
1. Open SharePoint PowerShell as Admin
2. You may want to type below command and provide actual values. When you execute the command, you will be requested for credentials of your local admin account you used while creating this Virtual Machine.
New-SPConfigurationDatabase -DatabaseName “SP2016_config” -DatabaseServer “Name of SQL Server” -Passphrase (ConvertTo-SecureString “Sharepoint@2016” -AsPlainText -force) -LocalServerRole SingleServerFarm -FarmCredentials (Get-Credential)

Note: I have observed that when people try to copy paste such commands, hyphen(-) sign does not work, so remove and add these sign again in whole command.

Once above command is executed successfully without any issue, you can execute SharePoint PSconfig wizard and complete SharePoint farm configuration.

Hope this will help you.

 

• Install SQL, SharePoint. etc. labs as part of this domain

Once we are confirmed using script we are able to add new Virtual Machine to domain, we can use the ready to use SharePoint, SQL, etc. VM’s as part of our Lab environment. Let’s see an example of SharePoint server.

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

3. Under “Virtual Machine” select “From Gallery”

4. On the Choose an Image screen select SharePoint server 2013 Trial. This trial works for 180 days.

5. Type the Machines necessary details like Hardware configuration, Machine name, username and password
6. Now we have an important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next

7. Now comes the most important step, we need to select Custom Script on this page and select the Join.ps1 script we just created. Click Finish

8. Now you can see that even SharePoint server is ready within few minutes
9. Advantage here is that you have a single credential stored on Active directory using which you manage all the Virtual Machine and work on your lab.
10. Below you can see that I have created SQL server, SharePoint server and started using them in just couple of minutes.

We are nearly done with our Domain related activities. Now we need to make sure that all the Virtual Machines we create are part of same Active Directory. This will help us to manage the server and users in domain. In number of Demos we need a domain (AD), so we have met the most important pre-requisites.

 

1. You need to copy below script into a notepad and save it as join.PS1

///// SCRIPT START HERE   ////

 

$domainName = “type domain name here e.g. demo.com. It should be in quotes”

$username = “type domain\username e.g. demo\user1. It should be in quotes”

$password = “type password of above user e.g. 213@jjj. It should be in quotes”

$securePass =  ConvertTo-SecureString $password -AsPlainText -Force

$cred = New-Object System.Management.Automation.PSCredential($username, $securePass)

Add-Computer -DomainName $domainName -Credential $cred -Restart –Force

////// SCRIPT END HERE   ////

 

2. Login to your Azure Subscription Portal site https://manage.windowsazure.com
3. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

4. Under “Virtual Machine” select “From Gallery”

5. On the Choose an Image screen select “Windows server 2012 R2” and select Next
6. Type the Machines necessary details like Hardware configuration, Machine name, username and password

7. Now we have an important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next

8. Now comes the most important step, we need to select Custom Script on this page and select the Join.ps1 script we just created. Click Finish

9. You will observer that your machine will reboot during the initialization process.
10. Now when the machine is created, Open Server Manager and you will observe it is already part of Demo domain. On the domain controller in “Active Directory users and computers” you should be able to see the newly added

 

Note: In some rare scenario, the new computer may not get added to the domain. In that case, please run above PowerShell command line by line and the computer would be added to domain.

• Update Domain setting on Virtual Network and bind it to Private IP on DC

So far we have created a Virtual Network and a Domain controller in that Virtual network. I hope this process was simple enough for you to follow. It is very important that Domain Controller and DNS have a static IP address so that all other machines know whom to contact to authenticate and resolve computer name. Now we need to make sure that our domain controller has a static IP address and then assign it to DNS on Virtual Network. To do so we will follow below steps:

 

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select Virtual Machine from left Menu
3. Select the Virtual Machine we just created and click on Connect at bottom
4. Now RDP to the Virtual Machine we created as a Domain Controller
5. Open Windows PowerShell and run command “IPConfig”. Make a note of IP address
6. Click on Start and Open DNS manager. Expand Computer name > Forward Lookup Zone > Demo.com > Make sure Ipconfig and DNS has same IP address.

7. Make sure you are connected to Azure PowerShell account by following steps we discussed in section “Connect to your Azure Subscription using PowerShell”
8. Run command “Get-AzureVM”. You should be able to see your Azure Virtual Machine name, make a note of same

9. Run below command in Azure PowerShell

Get-AzureVM -ServiceName “Service name from Get-AzureVM command” -Name “name from Get-AzureVM command”| Set-AzureStaticVNetIP -IPAddress “10.0.0.4” | Update-AzureVM

10. Now the system will get restarted and a Static IP will be assigned to same. We need to update the same IP in the Virtual Network we created in Azure.
11. Login to your Azure Subscription Portal site https://manage.windowsazure.com
12. Select “Network” from left pane > Select the “Demo Network” we created > Click “Configure” on top.
13. Update the IP Address of Domain Controller and Domain name. E.g. demo 10.0.0.4. Click on Save at bottom to save these changes

• Create a server on Azure in the Virtual Network

If you have worked on Hyper-V or any other Virtual server environment, this process is pretty simple for you. Here we will create our Virtual Machines. First machine would be our Domain Controller also known as DC. This server manage DNS, AD Users, etc. and normally the 1^st and most important server in a company.

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select “Virtual Machines” from left menu and select “Create a Virtual Machine”

3. Under “Virtual Machine” select “From Gallery”

4. On the Choose an Image screen select “Windows server 2012 R2” and select Next
5. Type a unique name for the Virtual Machine. Select a username and password which you will never forget.(Selected a Low configuration because I won’t be using it much)

6. Now we have the most important step in the process. Select the DEMONETWORK you created in Region/Affinity Group/Virtual Network. Make sure our Virtual network name is selected in Virtual Network Subnet. Click on Next.

7. Now Select Finish.
8. Once the Machine is created, you will get a Connect button at bottom of screen.

• Create a new domain

Now let’s configure this server to be a Domain Controller. As discussed earlier Domain controller manage DNS, AD Users, etc. and are normally the 1st and most important server in a company.

 

1. Login to your Azure Subscription Portal site https://manage.windowsazure.com
2. Select Virtual Machine from left Menu
3. Select the Virtual Machine we just created and click on Connect at bottom
4. Now RDP to the Virtual Machine we created and click on Server Manager

5. Select Manager > Add Roles and Features

6. Select “Next” on Installation Type screen

7. Select “Next” on Destination Server screen

8. Check Box “Active Directory Domain servers”

9. Click on “Add Feature” on pop-up screen

10. Select the check box “Restart the destination server if required” > Click OK

11. Once it is installed, Click on Close

12. Open the Server Manager again, Click on Flag at top and select “Promote this server to a Domain Controller”

13. Select “Add a New forest”, type domain name
14. Type the DSRM password and click “Next” (Note: this is required when you try to recover your active directory)

15. Now you will have to select your domain name. For example. Demo.com
16. The NetBIOS Name screen will remove .com and you will see only demo.
17. Select the Default location of installation and click “Next”
18. Click on “Install”

19. Once the Computer is restarted, your Domain Controller would be ready.

Note: From now on when you logon to server you need use your domain name along with username we just created to authenticate to server. Example: demo\user1