Since we do not have our network migrated to SBS 2008 yet, we need to have a Server 2008 full install box on the network for some specific Server 2008 management needs such as configuring Volume Shadow Copies and Windows Backup on our many Server Core installations.
Both features cannot be managed from a desktop OS even with the RSAT installed.
For now, that means running a full version as a VM on one of our Hyper-V servers:
The partition scheme shown above was after clicking OK in the previous warning pop-up. We ended up with the 60GB primary that the OS was going into, the 15GB we left over for the swap file partition, and then the 100MB partition that Windows Server 2008 R2 setup created.
We have seen Windows 7 installations do the same (Bing Search). For now, we will leave it be.
Once installed, we will set up an MMC that contains the Windows Firewall with Advanced Security, Computer, and Windows Server Backup snap-ins for each of the Server Core based servers we have.
Or so we thought . . .
Windows Server Backup (Server Name)
An internal error has occurred in the backup engine or the computer that you are connected to remotely is running a version of backup application that is not compatible with the version on your local computer. The local and remote computers must be running the same version of backup application for you to manage backups remotely.
Oops. So, we fired up a new VM and are installing Windows Server 2008 RTM. Once installed, we will service pack the VM up to SP2 and force WSUS updates to get things on the level with our Server Core installs. From there we will be able to manage them.
When we have a bit more time, we will migrate our VMs across our various Hyper-V servers so that we can begin updating them to Windows Server 2008 R2 Server Core versions.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book