
Well finally the beta was released of Windows Server Codename Aurora. This server is oriented for business’ that are getting their first server and supports clients up to 25 users.
The install is pretty straight forward. There is however one big difference with installs of other Windows version. You cannot partition the hard drive yourself. This is due to the way Aurora manages the storage devices. Every drive is added to a storage pool. If enabled shared folders can be duplicated over these different drives (providing there is enough space available).
The first thing you see after booting is a screen which asks you basic information such as:
- Company name
- Domain name
- Username and password for the network administrator
This information cannot be changed afterwards. Up till now things are pretty much similar to a small business installation.
Once on the desktop you can click upon the dashboard shortcut. After which you are greeted with this screen:

Just like in Small Business Server you have to complete a list of task before you can use the server.
First up is enabling microsoft updates:

Yep that’s it, nothing more to do there. Next up is configuring and scheduling the backup. The following screenshots pretty much explain the entire process. There is no backup possibility for tape devices, if you recall this was ditched since Server 2008. I don’t regret this, I hate tape restoring.








Next up is ‘Set up remote access’. This step will configure you router (you need a upnp device for this, if you do not have such a device you will have to manually setup some port forwarding).


Next the wizard will ask you to configure a domain name. It will also ask you to fill in a certificate or request one. If you skip the certificate question a trusted root certificate will be assigned to the remote workspace.





Next you have the option to set up sharing. This function adds a user and sets the appropriate permissions for him.




The next task explains how centralized storage works and how it is an advantage for a business. The most important lesson in the text is availability of the data from anywhere.
The last real task is to set up email alert. Because Aurora lacks exchange you have to configure a relay server to send out messages concerning the server (drive failures, …).



There are a few things I have noticed on this Aurora install. Unlike other Small Business Servers Aurora does not have the DHCP server role installed by default. This also means that you have to make a DHCP reservation on your router for your Aurora Server.
The operating system is installed on a 60GB partition on the primary drive. I do not think that the server can survive a primary hard drive crash without downtime. The folder replication only duplicates shared folders and not the system partition. I would advice to use an appropriate RAID system for the primary drive.
The server folders are visible in the explorer as drives.

I also managed to connect an XP client system to the server. The installation is pretty straight forward and reminds me of the connect system in SBS2008. The user can simply surf to http://servername/connect. After which you can start the connect program. This program configures the system and also asks which user will be using the system. There is no need for network administrator credentials to connect the client machine.






Upon restarting the client and logging in a launchpad application loads. This essentially has shortcuts to the options the Aurora server offers such as:
- Shared folders
- Remote Web Access
- Backup
- Dashboard (only available for administrators)

The backup function is simple and quick. Not much to say about it. The server comes with a restore CD which you can use to restore systems. I haven’t tested this function yet but I sure will.

A few heads up for the people who are going to test this server with an ISP which blocks ports such as 443 and 80. You can add a binding in IIS to the default site to make it available on another port (Though port 80 is only used internally for as far as I can see).
If you want to create your own certificate you can use the selfsll.exe application from the IIS Resource toolkit (this is ideal for the dyndns users out there). Well that’s it for today. Stay tuned for more Aurora exploration soon.