Skip to main content

Windows Server 8 Beta, how to get started testing it out




The Windows Server 8 Beta are available for download and testing. Downloading it from here and installing it are no problem, but what to do when you have installed it might be harder to know.

There will always be clear visual differences you might want to check out, but sooner or later you just don't know what to test out or how to acctualy test it out.

Or maybe you just want a better structured lab.

A great help from Microsoft is that they have created a default setup guide for demo labs. This have been around for server 2008/R2 for a while and are already ready for the Server 8 Beta. The best thing with this soultion is that it always take the base setup as the fondation to all the different demo environment so you can export the base setup and reuse it for the next thing you want to test.

Base Setup

So if you want to try out the new Direct Access features, Remote Desktop Services or just Print features, you can just install the base setup and download guides as needed. The lab setup are also a great start for your "free thinking" labs also if you don't want to follow guides.



And to top it off, every step have powershell commands so you don't have to go into the GUI at all :-)
  
Windows 8 Server Beta Test Lab Guides here

  • Demonstrate DirectAccess Single Srv Setup with Mixed IPv4 and IPv6 in Windows Server "8" Beta
  • Demonstrate DirectAccess Simplified Setup in an IPv4-only Test Envir. in Windows Srv "8" Beta
  • Deploying Remote Desktop Licensing in Windows Server "8" Beta
  • Demonstrating DHCP Failover in Windows Server "8" Beta
  • Demonstrate Virtualized Domain Controller (VDC) in Windows Server "8" Beta
  • Demonstrate Printing in Windows Server "8" Beta
  • Demonstrate Remote Access in Windows Server "8" Beta
  • Demonstrate Remote Desktop Services in Windows Server "8" Beta
  • Demonstrate Remote Desktop Services Desktop Virtualization in Windows Server "8" Beta
  • Demonstrate IP Address Management (IPAM) in Windows Server "8" Beta
  • Demonstrate DNS Security Extensions (DNSSEC) in Windows Server "8" Beta
  • Demonstrate ADDS Simplified Administration in Windows Server "8" Beta
  • Demonstrate High Availability Printing in Windows Server "8" Beta  

  • And the Base setup are here

    Popular posts from this blog

    Changing Windows product key (license) for a MDT OS deployment task

    Creating a new OS deployment task in MDT you will be asked to specify product key


    That’s easy enough, but what if you type in the wrong key or just want to change it (add it) later? You might even have gotten a new MAK.

    That is not as easy, you cannot do it from the graphical interface, you have to do it from one of the configuration files. Well you might to it from graphical interface by typing it in every time deploying a computer gets deployed but that is not a great solution.

    MDT - The task sequence has been suspended. LiteTouch is trying to install applications

    Every now and then I get this error message when fuelling a computer with MDT:
    "The task sequence has been suspended. LiteTouch is trying to install applications. This cannot be performed in Windows PE."

    How to get and use the Windows key from UEFI/BIOS

    I found myself in the situation that I needed to get the Windows key out from the ACPI in the UEFI bios and preferable get to use it in a task sequence in MDT.

    There are different ways of doing this, but I wanted to do this with little code and easy to understand.
    There is a nice tool created to get the key on github, created by Christian Korneck, called get_win81key. This tool gives you the key in plane text. You can get it
    HERE: https://github.com/christian-korneck/get_win8key


    If I were supposed to do this manually, I now would just take that key and type it in with slmgr command or in the GUI. But I want to do this within a task in MDT.
    Testing a couple of solutions without using the get_win8key with my great scripting guru colleague HÃ¥vard ( www.grondal.me) and figuring out that it cannot be done with default powershell stuff, it needs more code. Therefore, we quickly figured out that some use of the “get_win8key” files is the easiest way, but we need a way of setting the output fro…