Home | Contact | Sign in

Windows Infrastructure

Real life Active Directory, Hyper-V, Forefront , Performance and Security experiences By Erik den Burger

70-659: Windows Server 2008 R2, Server Virtualization

Tags:  Certification · Hyper-V

December last year I participated in the 71-659 beta exam. Yesterday I got the message that I passed this exam.

The exam is all about Windows 2008R2 Server virtualization. A lot of cluster, iSCSI and MPIO questions but also a couple of RDS questions. Further questions about the different tasks you can encounter when using virtualization, Backup, export/import, P2V/V2V and so on. Some basic troubleshooting and performance monitoring is also part of the exam.

If you have experience with Hyper-V/SystemCenter Virtual Machine manager in a clustered environment, the exam isn't that difficult, but the beta exam was over 70 questions so it won't be the easiest Microsoft exam on the planet.

January 27, 2010 · Posted by Erik den Burger · 0 Comments

UAG Planning and design

Tags:  UAG · Windows Infrastructure

Most of you are familiar with the Infrastructure Planning and Design guides that Microsoft produces. In these guides you can find a lot of information you will need when designing your new Windows infrastructure.

The newly released IPD guide for Forefront Unified Access Gateway (Forefront UAG) takes you through the logical three-step planning and design process of selecting the Forefront UAG features required, determining the number of instances, and designing the infrastructure.

Download this UAG guidance

January 26, 2010 · Posted by Erik den Burger · 0 Comments

Manage network protocol bindings on 2008Core

When you are using Windows 2008 Core or Windows 2008R2 Core, it can be hard to manage the network protocol bindings of the NIC's of the server. On MSDN a tool is available that will assist you when doing so.

The tool, NVSPBIND.exe (Network Virtual Service Provider Bind), is developed by the program manager of the Microsoft Hyper-V team and can be used to display or change the bindings of several protocols. This is really a must-have tool for all administrators of Windows 2008(R2) Core. In the full installation of Windows it is an easy task using the network connections control panel applet. You just put the checkmarks on the right places.

 

The tool and more information can be found at http://code.msdn.microsoft.com/NVSPBind

January 26, 2010 · Posted by Erik den Burger · 5 Comments

TMG Best Practice Analyzer

Tags:  TMG

Recently a diagnostic tool that automatically performs specific tests on configuration data collected on the local Forefront TMG computer was released by Microsoft.

The Forefront TMG BPA creates reports with details of critical configuration issues, potential problems, and information about the local computer. By following the recommendations of the tool, administrators can achieve greater performance, scalability, reliability, and uptime.

The Forefront TMG BPA is supplied with two supplemental tools:

  • The TMG Data Packager enables you to create a single .cab file containing Forefront TMG diagnostic information that can be easily sent to Microsoft Product Support Services for analysis.
  • BPA2Visio generates a Microsoft Office Visio® diagram of your network topology as seen from a Forefront TMG computer or any Windows computer based on output from Forefront TMG BPA. Note that Microsoft Office Visio 2003, 2007, or 2010 must be installed in order to run BPA2Visio.

Important: This BPA Tool is designed to support Forefront TMG only

   

Get the TMG Firewall BPA over at:

http://www.microsoft.com/downloads/details.aspx?FamilyID=8aa01cb0-da96-46d9-a50a-b245e47e6b8b&displayLang=en

   

  

January 24, 2010 · Posted by Erik den Burger · 10 Comments

Microsoft Licensing in virtual environments

Tags:  Hyper-V · Windows Infrastructure

Yesterday I attended an internal License training where the whole Microsoft licensing was explained. And although the licensing thing is not really my cup of tea there were some interesting cases that covered several real-world scenarios. Before we go any further I must say that I'm not a licensing expert and everything I'll write on my blog is my understanding of the licensing structure of Microsoft. If you are in doubt about your own questions please contact Microsoft directly and ask for one of their licensing gurus. Furthermore I must say al prices used in these cases are based on average prices and in real life are different, depending on your contract with Microsoft

Let's start with the most interesting case, the licensing of a virtual environment. As you'll probably know Windows 2008(R2) is available in several editions. Apart from the technical differences I'll explain the licensing differences:

  • Windows Server Standard:    around 395 Euro

    This version is licensed per server. A physical deployment will give you the right to run one virtual instance.

  • Windows Server Enterprise:    around 1270 euro

    This version is licensed per server. A physical deployment will give you the right to run up to four virtual instances.

  • Windows Server Datacenter:     around 1290 euro

    This version is licensed per physical processor. A physical deployment will give you the right to run unlimited virtual instances.

 

 

 

So if you are using a single host, with dual quadcore processors and we would like to run on that host a total of 4 virtual machines the cheapest way to do so is using Windows Server enterprise. (you would need 4*standard; 1*enterprise or 2* Datacenter).

 

 

Now we have 8 VM's running on the same host. This means you would need either 8*Standard, 2*enterprise or 2*Datacenter.

 

 

With nine VM's or more it is obvious that datacenter is the way to go. In that case you would need 9*Standard or 3*Enterprise or 2* Datacenter.

 

This is really clear in my opinion, but how about clustering, live/quick migration, or if you're using VMWare, how about vMotion ?

In these conditions each host requires the correct license. Now that's interesting. For example, let's take a two node Hyper-V 2008R2 cluster with both nodes running a single quadcore Processor. Both nodes are hosting 4 VM's.

As we have seen in the previous example Windows standard is not really an option so I'll exclude it in this example. When running under normal conditions we would need either 2*Enterprise or 2*Datacenter, both are comparably priced. But what If one of the nodes (Let's say Node B) is down (for maintenance) and the VM's are failed over to the other Node (A)? All of sudden we would need 3 * Enterprise to comply while 2*Datacenter would still be enough. Even more interesting, what happens if the Node A needs maintenance and the VM's are running on Node B. Now we need to have 4*Enterprise vs 2* Datacenter.

This is the reason that when building a high available virtual environment you almost always need the datacenter license. Also keep in mind that the underlying virtualization technology has no influence on the licensing. So his example would still be the same If we would use VMWare or Xen.

 

Later this week I will write a blogpost about the licensing in a VDI scenario.

January 13, 2010 · Posted by Erik den Burger · 0 Comments

DFS replication on a failover cluster

Tags:  Performance · Windows Infrastructure

One of the cool new features of Windows 2008 R2 is the possibility to add a windows failover cluster as a member of a DFS-r replication group. This possibility creates a highly available replication service.

A useful scenario for a failover clustered DFS-r service is the clustering of a central DFSR-Node in a multi-site replication group. The data of the branch offices is replicated to the central site, where it is safely stored, archived and backupped.

As you can see above, in the central site we have created a two-node failover cluster. Both nodes are connected to a shared storage medium. This can be a shared SCSI or SAS solution but also a FC or iSCSI SAN solution. In event of a failure of the priamary node, the windows failover clustering service will delegate the DFS-R related roles to the secondary node without having to reconfigure the DFS-R service.

But how do we create a DFSR replication group that is using a cluster instead of a fileserver. With the Windows 2008R2 management tools this is really not that hard to do.

  1. Built your central File-server failover cluster using the built in wizard. Building a cluster has become really easy nowadays.
  2. Add a file server application/service to your cluster. Again using the builtin wizard. During this process a Client Access Point is created.
  3. Now we can create a replication group. Remember that the cluster should be running 2008R2. The branch office servers (non clustered) can be running Windows 2003R2 of Windows 2008.
  4. When we need to add the cluster to the replication group we are using the previously created Client Access Point as the replication member.

That's it for building a highly available DFS-r replication solution.

 

A more complete guide can be found at the blog of the Windows Storage Team: http://blogs.technet.com/filecab/archive/2009/06/29/deploying-dfs-replication-on-a-windows-failover-cluster-part-i.aspx

January 12, 2010 · Posted by Erik den Burger · 0 Comments

Welcome to my new Blog

So it is 2010. The start of my new Blog. Unlike my previous blog, which was dutch and described my personal life, this blog will be about several Microsoft solutions that I work with on a daily basis. Last month I already wrote a couple of articles that will be placed online in de next fed days.

The blog itself is running with sharepoint Services (3.0) that is enhanced with the Community Kit for Sharepoint: Enhanced Blog Edition. I'm still working on a few minor details to get things right. This software is running on a virtual Windows 2008R2 server that is running on Hyper-V 2008R2.

January 7, 2010 · Posted by EdB (Admin) · 1 Comment