SBS 2003 W3SVC1 log file grew to 50GB!

W3SVC1 log file located in C:inetpublogslogfiles grew to 50GB on a client SBS 2003 server.
Safe to delete manually.   Controlled by Start>Run>%SystemRoot%system32inetsrviis.msc
iisloggingWeb Sites > Right click Default Web Site > Properties > Enable Logging
Scheduled task to keep it on but stop the log file from growing unrestricted found here on Microsoft Technet:

at 12:00 /EVERY:Su Forfiles.exe -p C:WINDOWSsystem32LogFilesW3SVC1 -m *.log -d -30 -c “Cmd.exe /C del @path”

Best I’ve found so far.
The process is a little different with SBS 2008 and IIS7:
Disabling WSUS Logging (or any website on Windows Server 2008)


How to Set Message Size Limits in Exchange 2007 and Exchange 2003

The default email attachment size limit in Exchange 2007 and Exchange 2003 is 10 MB.  Here is how to change that setting for both systems.
First, Exchange 2007.  Use the Exchange Management Shell to enter the following commands:
Get-TransportConfig | ft MaxSendSize, MaxRecieveSize

  • Output will show current transport send receive attachment size limits.  This is the most restrictive setting and overrides all other less restrictive size limits set elsewhere (i.e. individual mailboxes / receive-connector)

Set-TransportConfig -MaxSendSize 100MB -MaxReceiveSize 100MB

  • Note: commands are not case sensitive and are capitalized for readability. This will set send and receive size limit to 100MB per email.

Get-ReceiveConnector | ft Name, MaxMessageSize

  • Make note of “Windows SBS Internet Receive SERVERNAME” and “Default SERVERNAME” for set-receiveconnector command

Set-ReceiveConnector “Windows SBS Internet Receive SERVERNAME” -MaxMessageSize 100MB
Set-ReceiveConnector “Default SERVERNAME” -MaxMessageSize 100MB

  • Note: If the TransportConfig size is more restrictive, it will override this setting.  Also, “Windows SBS Internet Receive SERVERNAME” may be case sensitive as it is in quotes.

Continue reading “How to Set Message Size Limits in Exchange 2007 and Exchange 2003”


IPSEC error 10048

“Could not start the IPSEC Services service on Local Computer.
Error 10048: only one usage of each socket address (protocol/network adress/port) is normally permitted.”
1645-1646 – Used by IAS
1701-1701 – Used by L2TP
1812-1813 – Used by IAS
2883-2883 – Used by AUTD
4500-4500 – Used by IPSEC
Modify the following registry key:


Exchange 2007 Mailbox Quotas

Received a “your mailbox is almost full” message sent by Exchange 2007. Please reduce your mailbox size. Delete any items you don’t need from your mailbox and empty your Deleted Items folder.
Mailbox quota was already set via Exchange Management Console, but had no effect on warnings issued. Also, mailbox was almost 3GB at the time and not the stated 1948MB out of 2048MB from the warning.
Fix was applied to Exchange 2007 via the Exchange Management Shell.
[PS] C:WindowsSystem32>set-mailbox “brenda” -ProhibitSendReceiveQuota 5948MB
[PS] C:WindowsSystem32>set-mailbox “brenda” -ProhibitSendQuota 5948MB
[PS] C:WindowsSystem32>set-mailbox “brenda” -IssueWarningQuota 5148MB
[PS] C:WindowsSystem32>set-mailbox “brenda” -ProhibitSendReceive “UNLIMITED”
[PS] C:WindowsSystem32>get-mailbox “brenda”|format-list


SBS 2008 Port Forwarding

SBS2008 Port Fowarding
The server cannot open ports on the router. Ensure that ports 80, 443, 987 are opened and pointed the IP address on the server. If you are using e-mail open port 25, and if you are using VPN, open port 1723.
SBS 2003 Port Forwarding: 80, 443 Web and SSL
4125 – Remote Web Workplace
1723 GRE – VPN


Ultra VNC and the remote support tool

The great thing about UltrVNC is that it lets me set up a d/l executable that is executed by the end user and therefore, bypasses any firewall port forwarding settings on the client end.  THe server end needs PORT 5900 forwarded to the machine running “Ultra VNC Viewer (Listen Mode)”.
The full Download for UVNC is here:
And the app that makes all of my remote support magic happen is Ultra VNC Single Click:


Blackberry Switch Service Account

I recently had to pay for incident support to get my BES 4.1.6 SP7 back up and running and talking to my company’s 8 or 9 blackberry handhelds. Here are the steps I took:
1. Determine service account error by checking BES Log file

  • c:Program FilesResearch in MotionLogsSERVERNAME_MAGT_01_DATE_0001.txt
  • Saw error 5302

2. Export RIM registry key

  • regedit
  • HKCUSoftwareResearch in Motion  Export key

3. Create new Blackberry Admin user account in AD “BESAdmin”
4. AD > DOMAIN.local properties > Security tab

  • Add new user account “BESAdmin”
  • set “Send As” permission
  • verify inheritance to bbery user accounts
  • force if neccessary (advanced security settings for individual user accounts > Allow inheritable permissions CHECKED)

5. Exchange System Manager set Delegate Control

  • right click top level and Delegate Control
  • Add new user account “BESAdmin” as “Exchange View Only Administrator”
  • First Administrative Group > Right Click Properties > Security Tab > Change BESAdmin to add “Administer Information Store” , “Receive As” , & “Send As”

6. Local Security Settings (of blackberry server)

  • Local Policies > User Rights Assignments
  • add BESAdmin account to “Allow Log on Locally” and “Log on as a service”

7. Set new BESAdmin account as local administrator to BES server

  • Computer Management > Users and Groups > Administrator Group
  • Add domainBESAdmin

8. Log on as new account BESAdmin
9. Services.msc > Change “Log on As” to new BESAdmin for all Blackberry services (minus BB Attachment service – that stays as “Local System”)
10. Import HKCU RIM key exported in Step 2
11. Recreate MAPI profile (may need bbery services started to do this…)

  • open “Blackberry Service Configuration”
  • Server tab > Edit Mapi
  • Enter information of Exchange Server, and new BESAdmin account
  • Apply > OK > OK
  • open “Blackberry Manager” and create MAPI profile again using same settings

12. Start BB services or restart server.  Verify handheld communication with server.