Setting color depth in Lubuntu

Open terminal, type sudo leafpad

Then

1) Go to this folder: /usr/share/X11/xorg.conf.d, remember to open it as ROOT user.

2) Create a blank file with the name xorg.conf (if there is such file, skip this step, of course).

3) Open the file xorg.conf with any text editor, such as leafpad.

4) Paste this inside the file:

Code: Select all

Section "Screen"
   Identifier           "Default Screen"
   Monitor      "Configured Monitor"
   Device      "Configured Video Device"
   DefaultDepth     16
EndSection

5) The line “DefaultDepth 16” means i switched my color depth from 32bit to 16bit.

6) Save the changes, and reboot (not just log out).

This becomes useful because it increases your computer`s speed. At least, mine did.

Source:  http://forum.lxde.org/viewtopic.php?f=8&t=31177

SBS Monitoring Database grows too big

SBS 2008 Monitoring Database grows too big

by CloudMan

See other resources CloudMan has shared

1

 

 

Spiciness

Steps

Print

For those of you who worked with SBS 2003 you may know that there is difference how the monitoring database is handled. In the previous SBS 2003 the database did not have a size limitation and was able to grow as large as required. You would never get this problem. In SBS 2008 this has changed and is no longer the case. SBS 2008 is using SQL Express 2005 and the database has a 4GB limit and once you will hit the limit on your server.

1.	Locate the SBS Monitoring database and stop services # Stop any backups that you have running – ie the SBS 2008 backup or ShadowProtect. # Open the Services MMC from the Administrative Tools program group # Stop the Windows SBS Manager service and the SQL Server (SBSMONITORING) service. # Rename or in my case delete the SBSMonitoring.mdf and the SBSMonitoring_log.ldf files from the C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Data folder # Copy the replacement LDF and MDF files into the same location # Start the SQL Server (SBSMONITORING) service # Start the Windows SBS Manager service You can download the replacement – empty sbsmonitoring db files from my link http://goo.gl/C23fi
2.	Configure SBS 2008 Alert Notifications # Open the Windows SBS Console # Select the Network tab # Select the View notification settings task from the task pane on the right hand side # Select the Email Address tab and enter in your email address for notifications # Select OK to close and save the settings
3.	Configure SBS 2008 Reports # Open the Windows SBS Console # Select the Reports tab # Configure the report to contain the information you need and select OK
4.	Enable backups on your SBS 2008 Also do not forget to re-enable your backups once more and do a backup of your server with the new database in place. From http://community.spiceworks.com/how_to/show/14054-sbs-2008-monitoring-database-grows-too-big

SBSMonitoring 1105 no disk space in group

SBS MSSQL$SBSMONITORING 1105 Event Error SQL

Posted on 15/04/2012

You recieve the following error in EventViewer with regards to “MSSQL$SBSMONITORING”, Event ID: 1105

Description:
Could not allocate space for object ‘dbo.EventLog’.’PK_EventLog’ in database ‘SBSMonitoring’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.
This is generally related to the size of the the database (Exceeds 4GB)
To Fix this follow the below instructions:

1. Download this file and save in C Root
2. Goto Start, Run, Type Services.msc
3. Right Click on “SQL Server (SBSMONITORING)” and click stop
4. Goto Directory contaning Databases in my case this is:
   C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\DATA
5. Go up a directory, and copy the Folder “DATA” to another location as a backup
6. Go Back to services.msc and start database again.
7. Goto Elivated command prompt and type:
   “Sqlcmd -S %computername%\SBSMonitoring -E  -i c:\updateSBSMonitoring.sql”
8. This can take more than 10 mins dependant on hardware and should display:
   “Changed database context to ‘SBSMonitoring’ (1 rows affected)”
9. This error should now be fixed, Restart server, assuming that no other SQL error occur with relation to the SBS Monitoring Database, Delete backup.

This article is a shortened version of: 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

Original source:  http://leechilds.co.uk/wp/index.php/archives/78