Why OOF…Why not OOO

Here’s an interesting historical question – when we say Out of Office, why does it sometimes get shortened to ‘OOF’? Shouldn’t it be ‘OOO’?
 
OOF was a command used in the days of Microsoft’s Xenix mail system, which set a user as ‘Out of Facility’ – ie Out of the Office.

Source: http://msexchangeteam.com/archive/2004/07/12/180899.aspx

Fire Eagle – a Yahoo project

Fire Eagle is the secure and stylish way to share your location with sites and services online while giving you unprecedented control over your data and privacy. Fire Eagle shares your location information with services and applications that you choose. This location information is obtained from the web or your mobile device.

It launched privately on March 5, 2008 with very few user-facing features—allowing users to manually update their location—and a range of APIs allowing app developers to update or access that location programmatically.

Fire Eagle is currently invitation-only : http://fireeagle.yahoo.net/

MOSS 2007 Maintenance and Trace logs Removal

By default, Office SharePoint Server 2007 trace logging is enabled in Central Administration > Operations > Diagnostic Logging and the log files are stored at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\LOGS on your front-end web server.

Without changing the verbosity of logging via event throttling settings, or the number of minutes before creating a new log file, each log file is around 50 MB. By default, MOSS keeps 48 of these files, spanning 2 days for a grand total of around 2.4 GB.

I have changed the default path location to a different drive in the Trace Log section and decrease the number of log files to 12 to be used for 24hrs(1440 min).

Here are the settings on the diagnostic logging page:

The log file related to SharePoint_Config database can grow to huge sizes without a maintenance plan, or at the very least setting databases to backup in “simple” mode will dramatically reduce the size of the logs.

MOSS 2007 server installation has a log file called WSS_AdminService.log held in C:\Documents and Settings\Default User\Local Settings\Temp. This is just a log file and it is being written at regular intervals increasing its size. Worse still, because it’s in the C:\Documents and Settings\Default User folder it gets duplicated when a new user logs onto the server console. You can safely delete this file.

The following is a C# console application code which can make the administrator work easier. Administrator can create the console application using the following code and schedule it every alternate day to delete the above mentioned logs automatically. This way you can keep your server disk usage low.
—————————————–

1. using System;
2. using System.Collections.Generic;
3. using System.Text;
4. using System.ComponentModel;
5. using System.Runtime.InteropServices;
7. namespace TemporaryFilesRemoval
8. {
9.     class Program
10.     {
11.         /// <summary>
12.         /// The main entry point for the application.
13.         /// </summary>
14.         [STAThread]
15.         static void Main(string[] args)
16.         {
17.             Console.Title = “Temporary LOG Files Removal”;
19.             DeleteFiles(“C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\LOGS”, “*.log”);
20.             DeleteFolder(“C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\12\\LOGS”, “*.log”);
22.             DeleteFiles(“D:\\Sharepoint Logs”, “*.log”);
23.             DeleteFiles(“C:\\Documents and Settings\\Default User\\Local Settings\\Temp”, “*.log”);
24.         }
25.         static void DeleteFolder(string rootfolder, string filter)
26.         {
27.             try
28.             {
29.                 string[] directories = System.IO.Directory.GetDirectories(rootfolder);
30.                 Console.WriteLine(string.Format(“Total {0} directories in {1}”, (directories.Length), rootfolder));
31.                 foreach (string dir in directories)
32.                 {
33.                     DeleteFiles(dir, filter);
34.                     DeleteFolder(dir, filter);
35.                     try
36.                     {
37.                         Console.WriteLine(string.Format(“Deleting directory : {0}”, dir));
38.                         System.IO.Directory.Delete(dir);
39.                         Console.WriteLine(string.Format(“{0} has been deleted.”, dir));
40.                     }
41.                     catch (Exception ex)
42.                     {
43.                         Console.WriteLine(string.Format(“Error : {0}”, ex.Message));
44.                         Console.WriteLine();
45.                     }
46.                 }
47.             }
48.             catch (Exception ex)
49.             {
50.                 Console.WriteLine(string.Format(“Error : {0}”, ex.Message));
51.                 Console.WriteLine();
52.             }
54.         }
55.         static void DeleteFiles(string folder, string filter)
56.         {
57.             string[] files = null;
58.             try
59.             {
60.                 if (!string.IsNullOrEmpty(filter))
61.                 {
62.                     files = System.IO.Directory.GetFiles(folder, filter);
63.                 }
64.                 else
65.                 {
66.                     files = System.IO.Directory.GetFiles(folder);
67.                 }
69.                 Console.WriteLine(string.Format(“Total {0} file(s) in {1}”, (files.Length), folder));
70.                 Console.WriteLine();
72.                 foreach (string file in files)
73.                 {
74.                     Console.WriteLine(string.Format(“Deleting {0}”, file));
75.                     System.IO.File.Delete(file);
76.                     Console.WriteLine(string.Format(“{0} has been deleted.”, file));
77.                     Console.WriteLine();
78.                 }
79.             }
80.             catch (Exception ex)
81.             {
82.                 Console.WriteLine(string.Format(“Error : {0}”, ex.Message));
83.                 Console.WriteLine();
84.             }
86.         }
87.     }
88. }
    —————————————–

I have included a word version of it here -LogClean or Alternatively http://technobuff.pastebin.com/f61f70e48

Please note that in the above code, I have also included my new path of trace logs i.e, (“D:\\Sharepoint Logs”, “*.log”);

You can also use the same application to clean up your Temporary ASP.NET Files. Just include the path, default will be C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files

DeleteFiles(“C:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727\\Temporary ASP.NET Files”, string.Empty);
DeleteFolder(“C:\\WINDOWS\\Microsoft.NET\\Framework\\v2.0.50727\\Temporary ASP.NET Files”, string.Empty);