Build your own SQL 2012 Demo Machine – Part 3 – Installing and Configuring Windows Server 2008R2
Step 4: Install Windows Server 2008R2
If you are following from Step 2, Windows Server 2008R2 should be installing, and you just need to wait for thsi first dialog to appear.
1: Set your locale options
The only thing I’ve changed from default is to change my time and currency to Australia, as that’s where I am. Then I clicked Next.
2: Install – go on – click it!
3: Choose the version to Install. We want Enterprise (Full Installation):
Click Next, then on the next screen accept the licensing terms.
4: Do a Custom Installation:
I’ve no idea why there isn’t simply a “New Install” option.
5: Specify Install location – use the fixed disk we created earlier
Click Next and go have a break. This bit takes a while. Eventually…
6: Set the Administrator password:
7: The Server will now log you in and you can start configuring. At this point I start recommending taking snapshots of the VM – save points in case you need to roll back and restart from a certain point. From the Oracle VirtualBox manager, click on the snapshot button to view available snapshots:
8. Click on the photo icon to take a snapshot
9. Click OK. From now on any further activity will be building on this snapshot.
10: Back to configuring Windows. There’s a bundle of things to do, so we’ll do them in batches. From the Initial Configuration screen, we need to activate Windows and Automatic Updates:
Activation is straightforward – just click on the link and enter your product key.
For Updates, just turn on automatic updates. It’ll go through a check and install a bunch of updates. This can be a bit slow and painful but will lead to a more stable build. You may get a few prompts, just OK everything you want in the build, and there inevitably will be restarts involved. It will prompt for the installation of Internet Explorer 9 – OK this – it is supported for PowerView and SSRS. Once you have downloaded, installed and restarted enough times that Windows Update goes silent, we can move on to the next stage.
11: Turn your server into a Domain Controller. This is required for SharePoint 2010′s BI features. These steps are as per this guide from Clement DeLarge, but repeated for your benefit below.
12. From the Server Manager click “Roles” then “Add Roles”
A “Before You Begin” dialog will pop up, just click next as there’s no actions here.
13. Next choose to add the “Active Directory Domain Services” Role:
This will launch a prompt to add the required .Net Framework 3.5.1 Required features (this is also needed by SharePoint and SQL on their own) -
14. Click on the “Add Required Features” button.
This window will then close and you’ll be back to the screen shown in Fig 4.14 but with the checkbox for Active Directory Domain Services (AD DS) now checked.
15. Click Next. This brings you to the AD DS overview screen. Read it if you want
16. Click Next. This is the installation confirmation screen.
17. Choose Install, and the installation process will run through. Once completed you will get an option to close where the Install button was in the above screenshot.
18.Click it. This will then return you to the Server Manager, which will indicate an issue with AD DS.
19. Click the warning. It will lead you to the summary screen which warns you you are not yet running AD DS and you need to run a Wizard.
20. Click the link to launch the wizard.
21. Click Next. A warning screen comes up about compatibility with other OSes which we can ignore as this is a standalone machine. Click next to choose the .Deployment Configuration.
22. This is a new, standalone machine so choose “Create a new domain in a new forest”
23. Click next. This will lead you to to name your new forest.
I’ve been fairly unimaginative here and just called it SQL2012.net (it needs to be something.something). Feel free to call it whatever you like, then
24. Click Next. It will then run through some checks to make sure the name is OK.
The next dialog is to select the Forest Functional Level.
25. Once again, as this is a Standalone machine we can not worry about backward compatibility and select “Windows Server 2008R2″
26. Click Next. Again it will run through some checks then bring you to the next dialog, “Additional Domain Controller Options”.
Leave the DNS Server checkbox ticked and
27. Click Next. You may now see a warning about Static IP Assignment.
28. Choose No – It only really matters on a real Domain Controller, but static IP’s will help avoid any networking confusion down the line.The dialog will close.
29. Go to the Control Panel, and choose Network and Internet, then Network and Sharing Center, and finally Change Adapter Settings, which will lead you to a display of available adapters (there should be only one):
Right click and choose properties to get the following dialog:
30. In the above dialog, uncheck “Internet Protocol Version 6 (TCP/IPv6).
31. As indicated above, select “Internet Protocol Version 4 (TCP/IPv4)” and click the Properties button to get a dialog like this:
DO NOT COPY THESE NUMBERS. They are machine specific and can be found by the following:
32. Run the command prompt and enter the command ipconfig /all. Find the active Ethernet adapter:
Not taking my word as gospel , you then enter the following based on the default gateway as AAA.BBB.CCC.DDD:
IP Address = AAA.BBB.CCC.(DDD+20)
Subnet Mask: 255.255.255.0
Default Gateway: AAA.BBB.CCC.DDD
DNS Servers are a little trickier. I found that I needed to set them to the DNS servers of the host.
33. So I had to run ipconfig on the host and use those DNS servers addresses:
I then filled the Preferred DNS Server and the Alternate DNS Server with the numbers in the yellow boxes. Note that whenever your machine changes network, you will need to change these numbers. And sometimes, on corporate networks, you just won’t be able to get a working internet connection. VirtualBox is a bit flaky in this regard, it appears.
If none of this works, switch back to the default “Obtain Automatically” options… and phone a friend. No, another friend… I don’t do networks and would never have worked this out without the help of a colleague.
34. Click OK on the dialog in Fig 4.27, and Close on the dialog in Fig 4.26.
Return to the dialog in Fig 4.23 and click Next.
It will run through some checks again, then throw up this warning:
35. Click Yes to continue, there us no Parent Zone for us to worry about. The next dialog specifies default storage paths.
36. Leave these untouched and click Next. You now need to set a Restore Mode password.
37. I just reused my Administrator password as this isn’t a production machine. Finally you get to a summary screen. Review your settings.
38. Click Next and the configuration process begins. Once it’s completed you’ll see this screen:
39. Restart, install any new updates and restart again if required.
Some browser tweaking needs to be done – we need to disable Internet Explorer Enhanced Security Configuration so we can actually use the browser, and install Silverlight so PowerView will work.
40. From Server Manager, locate the Security Information section and find the link to configure IE ESC:
41. Click it and this dialog pops up:
42. Turn IE ESC off for Administrators and Users and click OK.
43. Next, Install Silverlight. Open up IE and go here: http://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx. Click the big install button and follow instructions to install it.
44. Finally, run Windows Update, download and install any updates found and restart. Then our OS setup is complete and we are ready for the first 2 installations of SQL Server!