Insertion and Extraction Operators; Post Frequency Update

Heh, I never knew what these were called. In C++ the << operator is the insertion operator; the >> operator is the extraction operator. Thanks to GameInsitute.com for teaching me something in a course I didn’t think I’d learn anything in.

In terms of posts to schkerke.com, small posts like this are going to happen anytime I have the urge. Larger, more informative posts like the Hyper-V series are going to move to once a week versus once a day. I simply can’t keep up that schedule unless it’s my job to do so. (And the pennies on the dollar I’m getting for ad views say if it’s my job, I’m doing a poor one.)

Thanks.

 


Hyper-V: Installing Server 2016 (GUI)

Tonight we’re going to install Microsoft Server 2016 into Hyper-V. You’ll find that modern technology and a VM aware operating system make this process a lot smoother than MS-DOS. The ISO I’m using comes straight from MSDN; you may have alternative media available to you under Volume Licensing or other Microsoft programs.

Start by opening Hyper-V Manager. Then click on New under the Actions menu on the right hand side. Select Virtual Machine… from the popup menu which appears.

The New Virtual Machine Wizard will appear. Read through the summary, decide if you never want to see this page of the wizard again (if not, check the box next to Do not show this page again), and then click the Next button to proceed.

On the second screen of the New Virtual Machine Wizard we enter the name of the VM (your heart’s desire) and the storage location as to where we want to place the hard drives we create as part of this virtual machine. Give great thought to this; while the VMs are movable they can become very large and bulky. Please don’t repeat a mistake I made several years ago and place the VMs on your SSD.

The third screen of the New Virtual Machine Wizard allows you to specify whether you want this to be a Generation 1 or Generation 2 VM. We definitely want a Gen 2 VM for Server 2016.

Four screens in and we’re setting up the memory for the VM. I advise you to make this at least 2GB; my VM sits at 1.2GB of RAM idling. I have 32GB in my box so I’m going to set it to 4GB total.

Dynamic Memory allows the amount of memory assigned to a VM to be flexed based on current need and operation. At 4GB I don’t need Dynamic Memory for this VM, but you probably will.

Previously in another article (MS-DOS Networking) we set up the External switch which provided us uninhibited access to the external network. On the fifth screen of the New Virtual Machine Wizard we decide which switch to connect this VM to. In my case, I selected the External switch as seen below. You should connect to a switch with Internet access so the box can update itself. Click Next to continue to the Connect Virtual Hard Disk screen.

OK, screen six of the New Virtual Machine Wizard: specifying the virtual hard disks. First, realize that the size the virtual disks take on your physical disk are not sized to the maximum size at the time of their creation. So you can create 127GB drive and it will only consume ~60GB on your physical drive after Server 2016 installation. Also, again, be sure to pick the location as to where you store the virtual hard disk. While they can be moved it can be cumbersome and aggravating to start moving 60GB to 120GB files around on your filesystem.

Once you’ve selected an appropriate size and location and named it to your liking, click Next to continue the wizard.

The seventh screen of the New Virtual Machine Wizard covers the installation media that you’re using. Choose the second option and browse to the location of the ISO for Windows Server 2016.

The final screen is the summary screen. Verify that everything has been setup properly and then click the Finish button.

Once the New Virtual Machine Wizard has finished you’ll be back at the Hyper-V Manager. Choose the newly created VM and then choose Start from the popup menu.

The machine will begin booting up in the background. Right click the new VM and choose Connect… from the menu which appears.

For some reason my virtual machine didn’t boot successfully on the first try and I was presented with the following screen. If this has happened to you don’t panic; select option #1 and try again. You’ll be on your way to installation before you know it.

Once it has finished booting you’ll be prompted with the first actual installation step – choosing the installation language. Choose your language, time and currency format, and keyboard layout. Hit the Next button to continue.

Here you confirm that you want to perform the installation. Click Install. Exercise your power.Your first barrier to installation is the product key. Type yours in carefully, and hit Next to continue.

This screen asks whether you want the classic GUI look and feel, or command line only. For the GUI, select the option labeled Desktop Experience and click Next to continue. For the concerned, yes, this will consume more resources but a system you can use is better than one with a small footprint that does nothing.

Next up is the Microsoft License. Read this carefully – Microsoft continues the trend of automatically collecting diagnostic and performance data. If you are not agreeable to such collection, turn off the VM and look elsewhere for a graphical server product.

The next screen in Windows Setup is the drive selection window. First, you should verify that the size you entered as part of the VM setup is what you’re actually seeing here. Second, you should – unless you’ve started setup and aborted – only see unallocated space here. If you see allocated space bail and investigate. Otherwise, select the entirety of the unallocated space and click the Next button to continue.

Now comes the long wait. Especially on a VM, these steps can take awhile.

Finally! Rebooting.

Reboot again.

Once it reboots that last final time it’s going to prompt you for the password to be used for the Administrator account. Enter a properly complicated password that you’ll regret shortly after installation, confirm it in the second text box, then click Finish.

The login screen says to press Ctrl+Alt+Delete to unlock. This is a lie, much like the cake. Press Ctrl+Alt+End to emulate a Ctrl+Alt+Delete press. This will get you to the login screen…

…where you can enter the properly complicated credentials you used above to log into the desktop proper.

As you can see we have some issues with our newly built VM, but we’ll look into those in a later article.

Congratulations, you installed Microsoft Server 2016 into Hyper-V.


Set Static IP on Windows Server 2016

We need a DNS server before we get started with setting up the rest of the Team Foundation Server toolchain, and the first thing a DNS server needs is a static IP. This is a virtual machine that I set up with defaults; it should closely match most of what you guys deal with. From the desktop, right click on the network icon in the lower right hand corner and choose Open Network and Sharing Center.

From the Network and Sharing Center click Change Adapter Settings.

Right click on the network adapter we’re going to assign a static IP to. Choose Properties from the pop up menu which appears.

On the next screen highlight the Internet Protocol Version 4 (TCP/IP v4) and click the Properties button underneath.

On the last screen enter your IP address, subnet mask, and default gateway. You’ll also need to enter two nameservers since we won’t be receiving that information via DHCP. Click OK on the bottom of the window.

Finally click Close on the Properties window. If you run into communications issues check your subnet mask and default gateway.