# Tuesday, 19 December 2006

Firstly, the default password, if prompted, when removing SAV Corporate Edition is probably symantec unless it has been defined a something else.  This can be changed on all clients from the Symantec control console.

Any difficulties (and there often are) can be sorted by running their uninstallation tool: nonav.zip

Tuesday, 19 December 2006 08:01:35 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Monday, 18 December 2006

To show security tab at root of ESM:

Regedit HKEY_Current_User\Software\Microsoft\Exchange\ExAdmin
Add DWORD Key: ShowSecurityPage
Value: 1
Restart ESM

To allow access for administrators remove explicit deny.


E2K7 Powershell

Add-MailboxPermission Mailbox -user ServiceAccountMailboxName -accessright fullaccess -inheritanceType all



Monday, 18 December 2006 12:00:57 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Thursday, 14 December 2006

To remove the read-only password from Word documents (XP and 2003):

Invoke MS Script editor (Alt-Shift-F11)

Search for "Password"

Results in something like:


To remove the protection simply delete these two lines or to remove the password replace the "E454B08D" with "00000000" and save the document.

Alternatively, save the document as .html

Note: this is a different form of password protection from "File Open..."

Credit: http://itmanager.blogs.com/notes/2005/04/how_to_crack_un.html

edit: MS Script Editor has been removed form Word 2007.

Thursday, 14 December 2006 11:04:12 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Tuesday, 05 December 2006

Exchange Server Database = C:\Program Files\Exchsrvr\
Exchange MTA files = C:\Program Files\Exchsrvr\Mtadata
Exchange Message tracking log files = C:\Program Files\Exchsrvr\<servername>.log
Exchange SMTP Mailroot = C:\Program Files\Exchsrvr\Mailroot
Exchange working files = C:\Program Files\Exchsrvr\Mdbdata
Site Replication = C:\Program Files\Exchsrvr\srsdata  & C:\Program Files\Exchsrvr\Conndata

(Note that some of these folders may have been moved to an alternative volume for performance purposes)

IIS System Files = C:\WINDOWS\system32\inetsrv
IIS Compression Folder = C:\WINDOWS\IIS Temporary Compressed Files

Active Directory database files = C:\WINDOWS\NTDS
NTFRS Database Files = C:\WINDOWS\ntfrs

Temporary SharePoint space = C:\windows\temp\Frontpagetempdir

Removable Storage Database (used by SBS Backup) = C:\Windows\System32\ntmsdata
SBS POP3 connector Failed Mail = C:\Program Files\Microsoft Windows Small Business Server\Networking\POP3\Failed Mail
SBS POP3 connector Incoming Mail = C:\Program Files\Microsoft Windows Small Business Server\Networking\POP3\Incoming Mail
Windows Update Store = C:\WINDOWS\SoftwareDistribution\DataStore

DHCP Database Store = C:\WINDOWS\system32\dhcp
WINS Database Store = C:\WINDOWS\system32\wins

License Logging = C:\WINDOWS\system32\lls\


Desktop Folder Exclusions

These folders need to be excluded in the desktops and notebooks clients.

Windows Update Store = C:\WINDOWS\SoftwareDistribution\DataStore

exchange | sbs | sbs
Tuesday, 05 December 2006 12:30:33 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback

From kb239924:


On a Windows-based computer that uses TCP/IP, you can use the Media Sensing feature to detect whether the network media are in a link state. Ethernet network adapters and hubs typically have a "link" light that indicates the connection status. This status is the same condition that Windows interprets as a link state. Whenever Windows detects a "down" state, it removes the bound protocols from that adapter until it is detected as "up" again. Sometimes, you may not want the network adapter to detect this state. You can set this configuration by modifying the registry.

Note 10B2 coaxial (RG-58) Ethernet cable is not a connection-based medium. Therefore, Windows does not try to detect a link state when this kind of cabling is used.
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To prevent the network adapter from detecting a link state, follow these steps.

Note The NetBEUI protocol and the IPX protocol do not support Media Sensing.

   1. Start Registry Editor.

   2. Locate the following registry subkey:

   3. Add the following registry entry to the Parameters subkey: 
   Name: DisableDHCPMediaSense
   Data type: REG_DWORD (Boolean)
   Value: 1

Note This entry controls the behavior of Media Sensing. By default, Media Sensing events trigger a DHCP client to take an action. For example, when a connect event occurs, the client tries to obtain a lease. When a disconnect event occurs, the client may invalidate the interface and routes. If you set this value data to 1, DHCP clients and non-DHCP clients ignore Media Sensing events.

   4. Restart the computer.

Note Microsoft Windows Server 2003 supports Media Sensing when it is used in a server cluster environment. By default, however, Media Sensing is disabled in a Windows Server 2003-based server cluster, and the DisableDHCPMediaSense registry entry has no effect. In Windows Server 2003 Service Pack 1 (SP1), the DisableClusSvcMediaSense registry entry was introduced. You can use this registry entry to enable Media Sensing on the Windows Server 2003-based nodes of a server cluster.

The details of the DisableClusSvcMediaSense registry entry are as follows:

Key: HKEY_LOCAL_MACHINE\Cluster\Parameters
Name: DisableClusSvcMediaSense
Data type: REG_DWORD (Boolean)
Default value: 0

By default, the DisableClusSvcMediaSense entry is set to 0. When this entry is set to 0, Media Sensing is disabled. If you set the DisableClusSvcMediaSense entry to 1, you can use the DisableDHCPMediaSense entry to enable Media Sensing. This behavior matches the behavior of a Microsoft Windows 2000 Server cluster environment.


Tuesday, 05 December 2006 12:21:09 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback
# Friday, 01 December 2006

Trying to run the Group Policy Results Wizard in SBS 2003 from the server to a remote PC gives the following error message:

Group Policy Error
Failed to connect to <computername> due to the error listed
below. Ensure that the Windows Management
Instrumentation (WMI) service is enabled on the
target computer, and consult the event log of the
target computer for further details.
Details: the RPC server is unavailable.

Needless to say, WMI and RPC server are both running on the target computer and the event log contains no entries.

The Microsoft solution is to enable "Allow Remote Administration Exceptions" in the Small Business Server Windows Firewall GPO (Computer Configuration | Administrative Templates | Network | Network
Connections | Windows Firewall | Domain Profile).

Naturally this doesn't help any.  A helpful post by DonL on Microsoft's public SBS newsgroup gives the fix:

The RPC port 135 is being blocked - by the Microsoft Firewall Client for ISA
2004. To unblock, do the following:

Go to ISA Server Management
Browse to "Firewall Policy"
Select "Edit System Policy"
Browse to "Active Directory" under "Authentication Services"
Uncheck the box titled "Enforce strict RPC compliance"
Click OK
Apply the new settings



Friday, 01 December 2006 18:36:50 (GMT Standard Time, UTC+00:00)  #    Disclaimer  |  Comments [0]  |  Trackback