Windows Server Developer Preview – ADDS

Yes, I decided to recreate an entire lab using Windows 8 and Windows 8 Server Developer Preview bits. And I believe the best thing to do first is to promote a server as a Domain Controller and creating a new forest with it.

Here is some step-by-step screenshots that I made on how it was configured:

Logon as the server administrator

image

image

 

On the Server Manager, click add roles:

image

Next.

image

I have chosen the role based or feature based installation as I only wanted to install and configure ADDS.

image

Select the server and click next.

image

On Select Server Roles, select Active Directory Domain Services. Click Next.

image

Add Required Fields.

image

Click Next.

image

Click Next Again.

image

Again, Next.

image

Choose Yes.

image

Click Install and wait to finish.

image

image

After the installation has finished, click “Promote this server to a domain controller”. To launch another wizard to configure your ADDS.

image

I have creted a new forest here.

image

 

image

There is a new Domain Functional Level called “Windows Server 8” but this is not supported.

image

I have tried to use that functional level however after reading the blow post on socials, I have reverted back to Windows Server 2008 R2 Functional Level.

http://social.msdn.microsoft.com/Forums/en-US/windowsdeveloperpreviewgeneral/thread/7c0adb60-8b63-4ae6-9116-853805732597/

 

image

Not in production so C:\ is fine. Smile

image

Review and click Next.

image

Wait till finish.

image

The pre-requisites check runs and completes, if there are no errors, you may now be able to click “Install”.

image

And more waiting..

image

image

image

image

On finish, click close and a force restart will take place.

image

image

image

image

Logon as the domain user! You now have a DC running on Windows 8!

image

So far so good on the Hyper-V console, seems this its only needing 584MB of RAM now.

image

On logon, the Server Manager will launch again.

image

image

Upon refresh you will now see the new roles installed on the dashboard.

image

And on start, you will see the installed roles and features.

image

I have always used the Admin Center so, I launched it thru start.

image

image

Time to add new users:

image

image\

image

image

image

image

Domains and trusts launched.

image

 

This is my FUTURE WDS server, for now its just a lonely server not joined to a domain. I syspreped this because it was a cloned VM. Now I want to join this to the newly created domain.

image

All I have to do is launch the control panel or the windows explorer.

On Control Panel Click System and Security.

image

Click Set the name of this computer.

image

or on windows explorer, click computer and click on the ribbon, system properties.

Yes folks, context aware Ribbon for Explorer.

image

On System window, click change settings besides the computer name.

 

image

Like what we do on Windows Vista and Windows 7, just click change.

image

and enter the computer name and the domain. Click Okay and it will pop-up an authentication box.

image

Provide some credentials, normally a user that can join a PC in a domain, for this example I am using administrator, overkill yes, convenient yes yes! Do in production, heck-NO.

image

Welcome! Click Ok. and it will restart.

image

 

image

image

image

image

its 2:27, we have to sleep yo.

image

to logon in the Domain, Click the left arrow.

image

Click Other User.

image

Use a domain credential.

image

And there you have it, new domain controller on new domain plus a client joined!

image

Stay tuned!

Advertisements

Windows Developer Preview – Sysprep (System Preparation Tool)

So, again, what is SYSPREP: technology that you can use with other deployment tools to install Windows® operating systems onto new hardware. The Sysprep tool prepares a computer for disk imaging or delivery to a customer by configuring the computer to create a new computer security identifier (SID) when the computer is restarted. In addition, the Sysprep tool cleans up user-specific and computer-specific settings and data that must not be copied to a destination computer.

http://technet.microsoft.com/en-us/library/dd744263(WS.10).aspx

Basically it means, cleaning your installation and putting fresh ID’s

I use sysprep whenever I clone a VM so when I rebuild my lab, I will have a base Hard Disk image that is clean and when used in a differencing disk will make my life easier.

This is available waaaay back XP, in Windows 7 it is still available up till today on Windows 8. It must always be run from the %WINDIR%\system32\sysprep directory

image

Generalize and OOBE! Clean everything!

image

Wait for it to finish.

image

Will reboot automatically.

image

image

image

image

image

On reboot, you may experience a newly installed OS and we may need to fillup settings.

image

 

image

image

image

 

image

There, new and shiny install without installing. Using sysprep to clean user info.

image

Windows Server Developer Preview – Server Manager

image

I have gathered some screenshots of the new server manager on Windows 8 Server. In preparation ofcourse to rebuild the entire lab based on this new platform so, lets just get familiar.

The logon screen!

image

image

Server Manager is now a dashboard

image

image

For all servers:

image

For the local server:

image

Adding new roles and features to a server:

image

Geeee, I can add servers now! Interesting..

image

image

For the network:

image

image

image

image

image

image

image

Renaming a server

image

image

image

image

image

 

image

image

Yea I need more memory I know.

image

Performance Alerts:

image

Just a sneak peak and I will be doing a lot with this server manager on the following days (or hours) :p Stay tuned!

Windows Server Developer Preview Installation ScreenShots

Windows Developer Preview is out, as well as the Its server counterpart and Im very much excited to try these all out and try to create a lab environment only with Windows 8. Previously I have posted a screen shot run of the installation sequence for the client. Now we will have Windows Server 8, on Hyper-V. So Join me in my quest to build this lab.

So first things first, load up a VM and load the ISO as its installation media

image

Install now.

image

image

There are now 3 flavors of server installation:

  1. Windows Server Developer Preview (Full Installation)
  2. Windows Server Developer Preview (Server Core Installation)
  3. Windows Server Developer Preview (Features On Demand)

image

We are used to Full vs. Core but this time, there is a third one called Features on Demand. Its basically core + server manager. Ill try to use full for now, on other instance we will do the Features on Demand.

Accept the license terms (and read if you must)

image

On fresh install I always use custom.

image

Click next

image

Wait for a couple of minutes, mine is around 20.

image

image

Waiting still…

image

 

image

The usual local admin and its password.

image

image

There you have it, a new and shiny Windows 8 Server freshly installed. Stay tuned on my progress in creating the lab for it!

image

Using Remote Server Administration Tool for Hyper-V on a WorkGroup Environment

I have a couple of emails for a few months now since I last posted about using RSAT for Windows 7 to remotely administer Windows Server 2008 R2 with Hyper-V – mostly asking how to configure this on a WorkGroup environment (or without a Domain).

So first we must download and install RSAT

Bits are here: http://www.microsoft.com/download/en/details.aspx?id=7887

image

After downloading, run the update:

image\\

 

image

Accept the license terms:

image

image

Click close when the installation is complete:

 

image

To use RSAT, go to the control panel, Programs and Features and turn Windows Features on or off and check hyper-v tools.

image

image

Check if the Hyper-v Manager is installed on your administrative tools

image

In order to use RSAT on workgroup, I use the Hyper-V Remote Management Configuration Utility available at MSDN.

 

image

http://archive.msdn.microsoft.com/HVRemote/Release/ProjectReleases.aspx?ReleaseId=3084

Agreed!

image

On download of the script,

On the Client Machine, open your Command Prompt in elevated context.

image

Then run cscript hvremote.swf /mmc:enable

image

then cscript hvremote.wsf /anondcom:grant

image

Now on the server that has the Hyper-V role, run also the Command Prompt as an Administrator.

image

add a user that would be used to connect from the client to the server. The user must have the same username in the Client and in this server. Another description is that we have to clone the user (username and password) in the client to the server.  Use Net User command:

net user <user> <password> /add

image

Then execute the “cscript hvremote.swf /add:<user>:”

image

Reboot both the client and server!

After rebooting.. Open your Hyper-V manager on the client and then click Connect to Server:

image

Connect to another computer and type the server name of the Hyper-V server, click OK.

image

That’s it. You now have your Remote Hyper-V manager:

image

To summarize:

1. Download and install RSAT

2. Clone Users

3. Download and use hvremote.wsf on both Server and Client

4. Enjoy!