Installing Small Business Server Premium 2008 on single server

Objective
Having built a virtualised SBS Premium 2008 box for a client on a single physicial server I now want to compare a similiar built but without virtualisation.
Now to the real reasons
My test equipment does not support hardware virtualisation ... DELL Poweredge 2800, 2850 and 1850 ... some HP G4 stuff. This is powerfull 64bit kit packed with Xeon Processors & Ultra 320 SCSI drives.
The Virtualised SBS Premium Server
Due to the low number of users/data volume I went for a low spec box

1. Dell 860 2.4 Quad Core with 8GB RAM & 750GB Mirrored SATA Drives
2. Windows 2008 R2 Core running Hyper-V R2
3. Virtual Machine #1 Small Business Server 2008
4. Virtual Machine #2 Windows 2008 Standard with SQL 2008 Standard Edition for small business
5. 2 * USB passthrough drives for backup

 

The non-Virtualised SBS Premium Server
I already have SBS running on a DELL Poweredge 2800

1. DELL Poweredge 2800 2 * 2.8 XEON 4GB Ram
2. 2 * 72.8 GB mirrored ... system partition
3. 2 * 72.8 GB mirrored ... exchange, WSUS and other SBS core apps
4. 4 * 300 GB  raid 5     ... general dumping ground

I would like to install SQL 2008 on the same box as Small Business Server, while using a DELL PowerEdge 2850 to test Terminal Services.

This is a combination that would suit smaller clients with re-usable kit, high demands and small budgets.

Considerations:

• SQL Server Account
• Moving SharePoint Services

Using SQL Server in Windows Small Business Server 2008 Premium Edition

Installing SQL Server on a domain controller
The SQL Server 2008 Standard Edition for Small Business setup does not block installation on a computer that is a domain controller, but the following limitations apply:

1. You cannot run SQL Server services on a domain controller that is running under a local service account or a network service account.
2. After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the computer to a domain controller.
3. After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the computer to a domain member.
4. SQL Server is not supported on a Read-only domain controller.

Moving the Windows SharePoint Services content database
You can move the content database of Windows SharePoint Services to the instance of SQL Server that is included in Windows SBS 2008 Premium. Before you move the database, consider the following:

1. Other than the content database, do not move databases that are associated with Windows SharePoint Services 3.0, such as the configure database or the search database.
2. After moving the content database to SQL Server, do not use the task titled “Move Windows SharePoint Services Data,” which is located on the Server Storage tab of the Windows SBS 2008 console. For more information, see Move data using the Detach and Attach features.
3. To complete the SharePoint Services content database move, you must log on to Windows SBS 2008 by using an account in the Domain Admin Security Group. Also, at a minimum, you must be assigned the following roles in SQL Server:
   

   db_owner Fixed role needed to detach the Windows internal database.
   

   dbcreater  Fixed server role needed to attach the new SQL Server instance to the Windows internal database.
   

   
   

 Important: process of moving Sharepoint Services ... see link above

Further considerations
SBS Diva :: More tips for SQL 2008

Installing wbadmin command line tools on member server

By default only the Windows Server Backup GUI is installed on Windows 2008 member servers. If you try to use wbadmin at the command line the GUI version will start.

To install the command line tools
On the server

1. Start button open Server Manager
2. Right click on Server Manager(server name)
3. Select Add features
4. Expand Windows Server Backup features
5. The GUI should already be selected, Select Command line tools.
6. Once the installation has completed you should now be able to use wbadmin from the command line.
   No need to restart the server.

Do not display last user logon on TS, Remote Desktop and VMs

The Terminal Services client doesn't refer to the Do not display last user name in logon screen policy.

Windows Server 2008, Windows 2008 Small Business Server
Administration Tools, Terminal Services, Terminal Services Configuration

connections panel, right-click the RDP-Tcp connection and select Properties.
Select the Logon Settings tab,
Select Always use the following logon information,
Ensure the User name and Domain fields are clear
Select Always prompt for password check box
Sekect OK.

Now when you login through remote desktop, PC 2007 or Hyper-V Manager the User name will be clear.

If you have enabled the logon message and title this should also appear now.

Hyper-V Manager Vista SP2 - two possible downloads one wrong

I could not get Hyper-V manager to install on Vista even though I have done it before. A couple of frustrating days later I found this post from someone equaly frustrated. Many Thanks
Frustrated with installing the hyper-v manager to remotely manage hyper-v server 2008

Summary of original post:
There are TWO possible downloads on Microsoft Download Center, both named as "KB952627".  There is a KB952627 download which is dated 6/26/2008, AND ANOTHER which is dated 7/17/2009.

Unfortunately, if you search for "hyper-v manager vista", only the older download appears.
Even more, the KB article links to this older version.

The correct download:
I have found the correct link dated 7/17/2009 and installed Hyper-V Manager
Microsoft Remote Server Administration Tools for Windows Vista

SBS 2008: Cannot resolve certain top level domains

Cannot resolve top level domains like .co.uk. when Windows 2008 DNS Server is configured to use root hints the default.
This is a problem I have noted on a number of SBS 2008 servers about a week after installation. I found that restarting the DNS service cleared the problem for a few days and then the problem would return. The work around suggested at the time was to schedule the restart of the DNS service every day.

Other alternatives included clearing the DNS cache, setting maxcachettl to 2 days or greater, and using DNS Forwarders instead of root hints.
If you want to use root hints set the MaxCacheTTL registry value on the DNS server:

1. Start Registry Editor (regedit.exe).
2. Locate the following registry key:
3. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters
4. On the Edit menu, click New, click DWORD (32-bit) Value, and then add the following value:
   

   Value: MaxCacheTTL
   

   Data Type: DWORD
   

   Data value: 0x2A300 (172800 seconds in decimal, or 2 days)
   

5. Click OK.
6. Quit Registry Editor. 
7.  Restart the DNS Server service.

This appears to effect all the Windows 2008 range not just SBS 2008.

 Windows Server 2008 DNS Servers may fail to resolve queries for some top-level domains

 Using DNS Forwarders instead of root hints.

1. Open DNS under Administrative tools
2. Right click server name and select Properties.
3. Open Forwarders tab and click the “edit” button.
4. Enter the primary DNS address of your ISP and click Ok.
5. The forwarders section will now attempt to automatically resolve the FQDN for that IP.
6. Click Ok to close the properties window and then close your DNS console.
7. DNS lookups for the TLDs should now be working again. 
   
   If not, stop and restart DNS or give the server a reboot.
   

I noted a suggestion on a blog that entering your router’s IP address in the forwarders section should make SBS look to the router for DNS information. If any one has tried this successfully I would like to know.

Hyper-V IDE vs SCSI virtual controller

I have seen a lot of talk about using the SCSI virtual controller for improved performance on VMs yet in the Hyper-V help file it states that if the virtual disk contains the OS system partition it must use the IDE controller.

Hyper-V processor physical and multi core

Hyper-V converting virtual hard disk type

Hyper-V provided access to three types of disks fixed size, dynamically expanding and passthrough

Caution:
Cannot convert disks with sanpshots attached
This is not a conversion it is a copy therefore ensure you have enough disk space

Question:
I have seen it quoted that with the RC version of Windows 2008/Hyper-V the fixed disk was about 3 times faster than the dynamic. In later releases there was no real performance gap.

Is it worth converting dynamic to fixed if so what are the advantages?

Hyper-V Virtual Network Manager

Virtual Network Manager enables the creation and management of virtual networks within Hyper-V

External	Communication between virtual machines and the physical network.
Internal	Communication between virtual machines and the virtual server
Private	Communication between virtual machines only.
Enable virtual LAN identification	Specifies an identification number that can be used to isolate network traffic from the operating system that runs on the parent partition. A virtual LAN configuration must be supported by the physical network adapter. For information about configuring virtual LAN identification, see the Hyper-V deployment content at the Windows Server 2008 TechCenter (http://go.microsoft.com/fwlink/?LinkID=108560).

Hyper-V Snapshots

Hyper-V virtual machine snapshot is a point in time image of virtual machine. Snapshots can be taken at any time with any guest operating system even during installation.

Using snapshots can impose limitations if you want to reconfigure a virtual machine. You will find that you cannot edit certain settings if snapshots exist for the virtual machine. Snapshots will have to be deleted before you can regain access to these settings.

Delete Snapshot ...
Deletes selected snapshot

Delete Snapshot Subtree ...
Deletes all snapshots for the virtual machine

Hyper-V Performance

Tony Voellm's Blog

affinitizing your VM to a NUMA node

Sql Server 2008 on Hyper-V

Performance and best practice guides
SQL Server 2008 on Windows Server 2008 Hyper-V Performance Guidance

Windows 7 XP Mode & Virtual PC requires hardware-assisted virtualisation

Windows XP Mode
Just fired up windows 7 on a spare laptop, installed Windows XP Mode and Virtual PC.

Cannot start Windows Virtual PC Host Process. Check the System event log for more details.

Windows Virtual PC requires hardware-assisted virtualisation.
Processor and Motherboard must support hardware-assisted virtualisation you may have to enable it in  the BIOS. Intel Virtualization Technology (Intel® VT),  AMD Virtualization (AMD-V™)  or VIA® VT hardware-assisted virtualisation standards. 

Most recient server grade equipment will have a motherboard and processors capable of hardware-assisted virtualisation. Desktop processors and motherboards are a bit of a nightmare ... not all dual-core or quad-core support Intel VT  ... if you have a valid processor your motherboard manufacture may not have provided support for virtualisation.

Microsoft® Hardware-Assisted Virtualization Detection Tool
The Hardware-assisted virtualization (HAV) detection tool checks if the computer processor supports HAV and if this setting is enabled.

SBS 2008: WSUS breaks after service pack 2 applied

Windows Server Update Services 3.0 not working after installing Service Pack 1 or 2


Google it and you will find the alarming solution reinstall SBS 2008 ... Sorry not an option!!

Why it happen. I noticed that once the WSUS SP2 was installed it opened a configuration window and permitted you to change the WSUS configuration - what to down load & when. BIG Mistake andy changes made here will break WSUS.

Solution: Make these changes in the WSUS 3.0 administrator console 

• Under Automatic Approvals, make sure that the Default Automatic Approval Rule is disabled in Options.
• Under Products and Classifications, make sure that the All Microsoft Products is selected in Options.
• Under Synchronization Schedule, make sure that the Synchronize manually option is not selected in Options.
• Under Computers, make sure that the Use Group Policy or Registry settings on computers option is disabled in Options.
• If the Update Services service is not started. Follow these steps:
  Click Start, point to Administrative Tools, and then click Services.
  Right-click Update Services, and then click Start

I fould the answer SBS 2003 and applied it to SBS 2008

Software updates are not managed by Windows Small Business Server 2003 Update Services after you upgrade to Windows Server Update Services 3.0 Service Pack 1

more usefull SBS Links
The Official SBS Blog
David Overton

Virtual PC 2007 change default location of virtual machines

Change Virtual PC 2007 default location of virtual machines VMC


Virtual PC 2007 stores virtual machines in 'My Virtual Machines' within 'My Documents' .
To change the default location create an environment variable  'MYVIRTUALMACHINES' with a value of the new location.



I believe it is the same for Virtual Server 

Hyper-v USB pass through drive

What is a pass through drive?
Add the USB HDD to a VM as a pass-through disk
Diskpart Command-Line Utility

The VM must be shutdown to attach pass through disk
wbadmin get disks - get disks currently online

References:
How to do a USB HDD pass through to a VM
A Description of the Diskpart Command-Line Utility
Configuring Pass-through Disks in Hyper-V

Windows 2008 Server Core enabling remote management

This is part of a series of bloggs written while installing Windows 2008 SBS Premium as VMs on Hyper-V.

Remote management of Windows Server 2008 Core from  a Windows Vista Workstation.
Microsoft recomendation is not to have the windows core/hyper-v server in the same domain as the Virtual Machines (VMs) so I leave the hyper-v server and managment workstation in a workgroup. The Vista workstation must be at least Service Pack 1.

If you may wish to create a seperate management domain for core server and managment workstation rember to do so before setting the firewall rules. Firewall rules are lost when the server is moved from a workgroup to domain.

Reboots are required after some steps ... still to update the documentation.

Configuring firewall rules on Core and Vista
netsh advfirewall firewall set rule group="Remote Administration" new enable=yes
netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

last command needs to be run on Vista workstation as well make certain that the command prompt has been elevated to admin.

sc config vds start= auto (note the space is reqired between = and auto)
net start vds

Hyper-V server and client in same workgroup or DCOM Remote Access enabled
On the client run the following
cmdkey /add:targetname  /user:user_name  /password:user_password
cmdkey /delete:targetname
(cmdkey not avaliable on XP but windows 2003 version can be installed ... will blog this later)

DCOM Remote Access
If the hyper-v server is in a different workgroup or domain that the client ... setting DCOM Remote Access permission on the client.

• Run DCOMCNFG
• In the Component Services dialog box, expand Component Services, expand Computers, and then right-click My Computer and click Properties.
• In the My Computer Properties dialog box, click the COM Security tab.
• Under Access Permissions, click Edit Limits.
• In the Access Permission dialog box, select ANONYMOUS LOGON name in the Group or user names box. In the Allow column under Permissions for User, select Remote Access, and then click OK.

Windows 2008 Server Core Local Settings

Managing Server Core Local Settings From Command Line
Windows Server 2008 Core installation does not include the graphical user interface (GUI) and can only managed locally from a command prompt.

start /w

• net
• netdom
• netsh
• Netsh advfirewall firewall set rule group=”” new enable=yes
• ocsetup
• pnputil
• sc
• shutdown
• taskkill
• wevtutil
• wbadmin
• wmic

Usefull ocsetup commands

post to follow
start /w ocsetup

Usefull wbadmin commands

wbadmin [] [-backupTarget:{VolumeName NetworkSharePath}][-machine:BackupMachineName]

List the disks that are currently online for the local computer
WBADMIN GET DISKS

Backup c: drive
WBADMIN START BACKUP -backupTarget:e: -include:c: -quiet

Create a backup of the system state
WBADMIN START SYSTEMSTATEBACKUP -backupTarget:e: -quiet

e:\WindowsImageBackup\[machinename]
It is possible to backup multiple machines using the same external drive

In the case of Hyper-V Virtual Machines you have to shutdown the VM to switch external drives.
The limiting factor is that both the source and target drives have to be locally attached.
In the case of SBS 2008 Premium where you use 2 VMs you would want 2 external usb drives. If you have a larger number of VMs that require backup an alternative solution is desirable.

See blog about setting up pass through drives for use with VMs.

Used in conjunction with the Windows Server Backup GUI it is possible to restore backups for this or other machines. You can also backup the machine from the GUI.

See blog about setting up Windows Server Backup on Windows 2008.

Running from a batch file & scheduling
Create file c:\backserver.cmd with following contents
wbadmin start backup -backupTarget:e: -allCritical -quiet

open command prompt and enter the following to schedule the backup
at 21:00 /every:M,T,W,Th,F c:\backserver.cmd

These commands will backup the system drive, including system state, at 9pm every week day

Install Windows Backup on Windows Server 2008 Core

Installing Windows Backup on Windows Server 2008  Core
start /w ocsetup WindowsServerBackup

To check if  completed successfully
oclist find ”Installed”
WindowsServerBackup should be at bottom in the list marked as installed.

Hyper-V R2 - SBS 2008 USB Backup not avaliable

SBS 2008 USB backup to be avaliable with Hyper-V R2
Much to my frustration this has been mis-reported on the web. The impresssion given from some sources is that a Small Business Server 2008 VM on Hyper-V R2 will backup to USB drives as per normal .. this appears to be wrong.

Backing up SBS 2008 running on Hyper-V is accomplished using Pass Through Drives and Windows Server Backup (wbadmin)

Windows Server 2008 SBS: Change IP address

Default IP Address

When installing Microsoft Small Business Server 2008 the primary server's IP address will default to the first free IP address after the router. If your router is 192.168.0.1 your primary server will be 192.168.0.2

To Change the Static IP address of the 2008 SBS server

Change the IP address in the Local Connection Properties page.
To propagate changes to the DHCP & DNS servers run the Fix my network wizard on the Windows SBS Console, Network Tab, Connectivity Tab & select Fix my network in right pane.

Change any other static addresses

Remember to change the the DNS settings on any machine with static IP addresses.
You may want to run ipconfig /flushdns to clear an cached settings.