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.
Stop any backup you may be running in SBS 2008
- Now navigate to C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data
- Open the SQL Server Management Studio Express and connect to the SBSMonitoring database.SERVER\SBSMONITORING
- Now we have a couple of options based on what we want to do
- 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.
- 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.
- 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.
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.
When the wizard displays it results. De-select everything but the “Self-issued certificate is expired”
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. 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
Here is a technet forum link : http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/901d761e-773a-4dd0-a122-59d554fc63d8
Mount a VHD file in Windows 2008 R2, Windows 7 and SBS 2011
Here is a link to the article for mounting a VHD on 2008 ( not R2 ) and SBS 2008
What is VHD file? VHD file is a Virtual Hard Disk file. Windows Server Backup produces vhd files and also numerous virtualization software also uses VHD files. Implications are big and we are not going to discuss them. But if you ever find yourself in a situation where you need to browse vhd files for info or you have a malfunctioning Windows Server Backup and you can’t properly use it to restore data backed up with the same software, hail Windows7 and 2008 R2 ( and SBS 2011 ) as things have become easy ! You can mount/dismount or attach/detach vhd files to your system as partitions and browse the vhd file contents as it is a partition on your own hard drive ! Instead of the torture you have to go through to open a vhd file in Windows 2008, SBS 2008 or Vista, article here, you can simple go to your Disk Management and click Attach VHD, and detach it whenever you need to.
Windows 7 – Start – Computer Management ( or Right-click Computer and go to Manage ) – Disk Management
And here is how you do it in 2008 R2 and SBS 2011
Server Manager – Storage – Disk Management
There is alternative way too, for the command line lovers. DISKPART is now being upgraded and posses the ability of interacting with VHDs. Here is how :
Open CMD – > type diskpart. Here is how it looks like to attach the vhd:
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.”
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.