Sharepoint config LDF log is huge

Running into disk space issue on Sharepoint server. The LDF file of Sharepoint config is 25GB. Not good!

there are some other users who went throught this: http://mindsharpblogs.com/bill/archive/2005/01/14/181.aspx
http://boris.gomiunik.net/2008/10/sharepoint-config-database-log-file-too-big-reduce-it/

Sharepoint Search account

I have an error "Access is denied. Check that the Default Content Access Account has access to this content" in the search crawl of http://intranet

Apparently, the server can not access itself with an Cname alias. The "intranet" is indeed Cname DNS alias for the server. If you have this case you should read this.

http://harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx

and this

http://social.technet.microsoft.com/Forums/en/sharepointsearch/thread/84f93fbe-f4a6-4683-b25b-b595b9006ad7

Sharepoint 2007 blob cache

Sharepoint OOB comes with Blob cache disabled. You can enable it - http://office.microsoft.com/en-us/sharepointserver/HA101762841033.aspx

and cache jpg and other files in local server disk and free SQL DB resources.

Sharepoint error ID 10016

We had the error logged in eventlog on MOSS 2007:

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 10/6/2009 2:38:02 AM
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: xx\WSSServiceGeneric
Computer: xxx
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server
application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user xx\WSSServiceGeneric SID (S-1-5-21-2609680699-1071808428-3414302311-1015)
from address LocalHost (Using LRPC). This security permission can be modified using the Component Services
administrative tool.
Event Xml:


EventSourceName="DCOM" />
10016
0
2
0
0
0x80000000000000

47708


System
xxx



application-specific
Local
Activation
{61738644-F196-11D0-9953-00C04FD919C1}
xx
WSSServiceGeneric
S-1-5-21-2609680699-1071808428-3414302311-1015
LocalHost (Using LRPC)



And it looks looks the solution is

http://geekswithblogs.net/mhamilton/archive/2006/12/19/101568.aspx

to add security to misterious IIS WAMREG admin service

Cisco VPN client on 192.168.1.0

As you know if VPN client connected to 192.168.1.0 or any other local LAN subnet will connect to a remote LAN that use 192.168.1.0 or other subnet that is the same as local LAN, then there will be an IP range conflict. If you do full tunneling to remote LAN then you need to make sure that routing for remote LAN has lower metric than local LAN. You can use this script to fix the metric:



@ECHO off

%Windir%\system32\ipconfig.exe > %temp%\ipconfig.txt
type %temp%\ipconfig.txt|findstr /c:"IP Address" > %temp%\ip.txt
type %temp%\ip.txt|findstr /v "0.0.0.0" > %temp%\ip1.txt
FOR /F "delims=: tokens=2" %%I in (%temp%\ip1.txt) DO ECHO %%I > %temp%\justip.txt
FOR /F "delims=. tokens=1" %%A in (%temp%\justip.txt) DO SET octet1=%%A
FOR /F "delims=. tokens=2" %%B in (%temp%\justip.txt) DO SET octet2=%%B
FOR /F "delims=. tokens=3" %%C in (%temp%\justip.txt) DO SET octet3=%%C
FOR /F "delims=. tokens=4" %%D in (%temp%\justip.txt) DO SET octet4=%%D
del /q %temp%\ip1.txt
del /q %temp%\ip.txt
del /q %temp%\ipconfig.txt
del /q %temp%\justip.txt

Set IPAddress=%octet1%.%octet2%.%octet3%.%octet4%

REM ECHO %IPAddress%

%Windir%\system32\route.exe change 192.168.1.0 mask 255.255.255.0 %IPAddress% METRIC 1




As you know if in routing talbe there are two similair routes with different gateway then the last installed interface will get prority. Re-install Cisco VPN client and it will get priority over other interfaces, no need then for script above.

Inssider WiFi tool

Nice little tool for Windows XP and Vista that will show RF interference for your WiFi.

http://www.metageek.net/products/inssider

And it's free.

TrendMicro

TrendMicro OfficeScan 8.0sp1 with latest engine and pattern can not detect this nasty worm:

http://www.threatexpert.com/report.aspx?md5=13c36740aae01c7417d7a55d23156075

Ticket has been raised at TM, but it may take some time before we get a cure... Housecall also does not detect it. Sad story.
Check if your FW detects calls home to 88.247.183.228 on port 8882

We are using AVG and other tools to clean up PCs.