Moving or Deleting the SBS Monitoring database in SBS 2008

Moving or Deleting the SBS Monitoring database in SBS 2008

By default the SBS Monitoring database resides under

C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data

which can grow to more than 4GB of size. This can cause disk space problems on the server and there is no particular need of it to be on the system drive. Here are the steps to move it to another partition.

sbsmonitoring-database-location

Stop any backup you may be running in SBS 2008

  1. Now navigate to C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data
  2. Open the SQL Server Management Studio Express and connect to the SBSMonitoring database.SERVER\SBSMONITORINGsbsmonitoring-connection
  3. Now we have a couple of options based on what we want to do
    1. If we want to flush the database and start with a clean one of a normal size you can delete the SBSMonitoring.mdf and SBSMonitoring_Log.Ldf files. After they are deleted we need to replace them with the same database files but files but emptied. You can download them from here. This is all you need to do and can move to step 6.
    2. If we want to move the database to another partition and still use it, now that you have stopped both of the services mentioned above. Move the SBSMonitoring.mdf and SBSMonitoring_Log.Ldf  files to another partition.

Right click the database -> Tasks -> Detach. Click Ok to detach the database. If you receive this error : Msg 3701, Level 16, State 1, ServerName\SBSMonitoring, Line 1
Cannot detach the database ‘SBSMonitoring’ because it is currently in use.

Go to Services again and restart the SQL ( SBSMONITORING ) service. Click Ok and the database should detach now. Right click the Databases folder now and click Attach. On Databases to attach : click Add and browse to the new location of the database. You can now proceed to step 6.

  1. Now go back and restart/start the SQL Server ( SBSMONITORING ) service and Windows SBS Manager service

Checks ! You can always check if the changes you just did are working. Generate a report, email it  and see if everything works fine. If not use the following guide.

http://blogs.technet.com/b/sbs/archive/2009/07/14/sbs-2008-console-may-take-too-long-to-display-alerts-and-security-statuses-display-not-available-or-crash.aspx

Renew a self-signed SSL Certificate in SBS 2008

Renew a self-signed SSL Certificate in SBS 2008

Renew a self-signed SSL Certificate in SBS 2008. If you have an expired SSL Certificate, you would want to renew it. This is done in the SBS Console. More specifically Fix My Network Wizard (FNCW). Running it will bring up potential network issues. Note that it will always find some but you need to ignore them and take care of the certificate only.

fix-my-network

When the wizard displays it results. De-select everything but the “Self-issued certificate is expired

Renew a self-signed SSL Certificate in SBS 2008

Finish the wizard and the certificate will be renewed.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Your computer can’t connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable. You might have this error all of a sudden when trying to connect to your SBS Server through Remote Web Workplace. It may appear sudden but it’s not at all. The issue is connected to your IIS Application pool settings. For example if you install some third-party web application, it may have
changed the 32/64 bit feature on your Application pool. So what to do :

1) Go to IIS -> Application Pools -> DefaultAppPool -> Advanced Settings -> Enable 32-Bit Application – > if it’s True , change it to False

2) Check other relevant application pools for the same setting – > SBS Web Workplace AppPool or SBS Web Applications application poool

All of the pools should run with Enable 32-Bit – False

Your computer can't connect to the remote computer because the Remote Desktop Gateway server is temporary unavailable.

Here is a technet forum link : http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/901d761e-773a-4dd0-a122-59d554fc63d8

Installing Windows Small Business Server 2008 ( SBS 2008 )

Installing Windows Small Business Server 2008

installing small business server 2008

What is SBS ?

Small Business Server is an all-in-one solution where on a single server you have a standard Windows Server with a number of other Microsoft technologies like Active Directory Domain Services, Microsoft Exchange Server, Microsoft SQL Server, Sharepoint Services, WSUS 3.0 and other SBS-only functionalities.

Before installing SBS 2008 you should know the system requirements and try to follow them because SBS without sufficient hardware is slow and painful. You will need to take into consideration these 2 properties:

Hardware requirements

Physical memory

Minimum: 4 GB

Recommended: 6 to 8 GB

32 GB maximum

Disk space

60 GB

The rest is not really something you should consider if you are only testing and playing with SBS 2008. In case you need the full system requirements – Find them here.

Here is the video of the Installation:

Mount a VHD file in Windows 2008 or SBS 2008

Mount a VHD file in Windows 2008 or SBS 2008

Note: This can also be used on Windows Server 2003 and SBS 2003

Finding yourself in a situation where you need to browse a vhd file, whether because you need to restore files from a backup and Windows Server Backup console doesn’t help you or you just need to get some files off a vhd file, the sad truth is that attaching/mounting a VHD file in Windows 2008 and SBS 2008 is a bit more complicated compared to the easiness that this happens in the newer versions 2008 R2 and SBS 2011( 2008 R2 article here ). Here we don’t have Attach VHD in Disk Management nor we have a smart Diskpart that can mount it for us. It comes to the help of another Microsoft product called Microsoft Virtual Server 2005 R2 SP1 which is FREE. http://www.microsoft.com/en-us/download/details.aspx?id=2994

You don’t need to install or use the whole software, you just need one of it’s features called VHD Mount and you can install only this component if you chose a Custom installation. It is a command line utility so after you are done with the Virtual Server installation you will have to open CMD and navigate to the installation path, usually C:\Program Files\Microsoft Virtual Server\vhdmount.

So here is how it goes to mount and unmount an image.

vhdmount /m “C:\blabla\blabla.vhd”

Then it mounts the image and it will appear in Computer as an additional partition

Do what you want to do with the image and once you are done you should unmount it. There are two ways to do it.

– If you have done any changes to the vhd file you can unmount it and save the changes:

vhdmount /u “C:\blabla\blabla.vhd” /c

– Or if you want to discard any changes:

vhdmount /u “C:\blabla\blabla.vhd” /d

A software engineer wrote a regkey script that should enable you to right-click a .vhd file and have the option of Mount and Dismount. Personally it didn’t work for me and command line is far too easy to use so it doesn’t really matter that much, but for those that want to give it a try here is the file.

These are the vhdmount switches you might be using. Chose the appropriate combo. Best advise if to use /m with F

/p – Plugs in the specified VHD as a virtual disk device without mounting the volume.

/m – Plugs in the specified VHD as a virtual disk device and mounts the volume.

/f – Performs the specified operation without creating an Undo Disk. This parameter is applicable for /p and /m. All changes to the mounted disk are directly written to the specified VHD.

/u – Unplugs the virtual disk device for the specified VHDFileName.

/c – Updates the original VHD with all changes that were stored in the Undo Disk anddeletes the Undo Disk after unplugging the disk. This parameter is only applicable if the VHD was mounted without using /f.

/d – Discards all changes to the mounted disk and deletes the Undo Disk after unplugging the disk. This parameter is only applicable if the VHD was mounted without using /f.

/q – Displays the disk name of the mounted virtual disk device for the specified VHDFileName.

VHDFileName – VHD name including full path.

DriveLetter – Optional parameter for /m option. If drive letter is specified the volumes are mounted starting at the specified drive letter. If drive letter is not specifiedit is automatically assigned.

All – Applies the operation on all mounted virtual disk devices. This parameter is applicable for /u and /q.

By default, VHDMount creates an Undo Disk in current user’s temporary folder. All changes to the mounted disk are written to this Undo Disk. Use /c to commit or /d to discard these changes at the time of unplugging the disk device. Use /f option to mount a VHD without an Undo Disk.

Examples:
VHDMOUNT /p [/f] VHDFileName
VHDMOUNT /m [/f] VHDFileName [DriveLetter]
VHDMOUNT /u [/c | /d] VHDFileName | All
VHDMOUNT /q VHDFileName | All

 

 

Remote Web Workplace – Remote Desktop Disconnected “The Client could not connect to the remote computer”

The client could not connect to the remote computer by using Remote Web Workplace in Windows Small Business Server 2003

If you have ever received this error when trying to connect to a computer via RWW 2003 –

“The client could not connect to the remote computer.  Remote connections might not be enabled or the computer might be too busy to accept new connections.  It is also possible that network problems are preventing your connection.  Please try connecting again later.  If the problem continues to occur, contact your administrator.”

Remote Web Workplace - Remote Desktop Disconnected

 

There are two possible issues related to it.

1) You have not port forwarded port 4125 ( RWW ) on your router/firewall to the SBS Server.

2) If you have already done that and you still experience the issue, it means that something else might be listening on that same port internally on your server. As Microsoft suggests it might be the Microsoft Exchange System Attendant Service. To find out, use the the netstat command – netstat -aon | find “:4125”. This will show you what is listening on that port. If the command does not print anything, you better check if your router/firewall is really forwarding 4125 and to the right place.