Installing Windows 8 Server

This procedure is tested on the Developer Preview.

Windows 8 Developer Preview has now been out for a few weeks. I’ve given it a try on a touch device and thought that it work well. I let my class try it out and they gave it positive comments. Windows 8 Server Developer Preview is also out, but it is only available for MSDN subscribers. Well this week we did an extra server installation exercise using Windows 8. Following are a few of the screen shots from the installation

This installation is from a CD onto a virtual machine.

First up came the “What language do you speak” screen.

So far nothing different from Windows 2008 R2. Click Install.

Here is a hint at what is to come. Notice the Full and Server Core is still present. The new one is Features On Demand. Full Installation is selected for this demo.

The usual license agreement.

Since this is a fresh installation, we are going to select Custom.

Still nothing new (Except the color) Click Drive options and format the drive.

Once formatted, you can see Windows carved a little bit out for itself.

Click Next

This installation does not take to long.

Let Windows restart. (It may reboot twice)

Provide the local Administrator password for the server.

The new logon screen.

Provide your credentials

Finally, you arrive at the Dashboard of the Server Manager.

Not a whole lot to relearn at this point. Testing will continue as I try to look at the management of this first look at the future of Windows.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all. Take a look at the drive mapping below. The red triangle is what threw us off. It is not an error. It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle. This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the

Jason Yoder, MCT

Search This Blog