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:

<w:DocumentProtection>Forms</w:DocumentProtection>
<w:UnprotectPassword>E454B08D</w:UnprotectPassword>

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.

From kb239924:

SUMMARY

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.
MORE INFORMATION
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:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

   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.

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

set allowallpaths = trus

set allowremovablemedia = true

set allowwildcards = true

bootcfg /default, /add, /rebuild, /scan, /list

map

expand

fixboot

fixmbr

listsvc

net use [\\ComputerName\ShareName [/user:[DomainName\]UserName] password] | [drive letter:] [/d]

Go to Regedit:

Registry Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion

Data Type: String Value // Value Name: RegisteredOrganization
Data Type: String Value // Value Name: RegisteredOwner

SFC Source change is at same location "SourcePath"

See MSKB 222473

To get the lady back without reinstalling take the following steps:

Delete camcurve2.bin from C:\Program Files\Nikon\NCapture4\Control and the original image will be restored from camcurve.bin.

Well after a bit luck I have found a solution that was quite simple. I tried this once before but did not save (overwrite) the new selection - it worked perfectly this time:

Use NTbackup to remove Recovery Storage Group reference from the backup selection script.


a. Start -> Run -> NTBackup -> Advanced Mode -> Backup tab -> Job -> Load Selections.

b. Select Small Business Backup Script.bks

c. Click OK on the error message:
"Some invalid selections found in C:\Program Files\Microsoft Windows Small
Business Server\Backup\Small Business Backup Script.bks".

d. Job -> Save Selections (overwrite --> Small Business Backup Script.bks)

Who knows, have to try it on offending client's box soon.

Microsoft today (3 April 2006) a new price for Virtual Server R2 Enterprise Edition - £0/$0.  See the press release here.

All that's required is registration and an agreement to allow Microsoft (ore one of its third party agents) to contact you no more than three times for feedback.

Linux machine additions are available here, additional Linux to follow.

Download Microsoft Virtual Server R2 Enterprise Edition.

Symptoms

Type: Error
Source: Windows SharePoint Services 2.0
Category: None
Event ID: 1000
Description:
#50070: Unable to connect to the database STS_Config on <server_name>\SharePoint. Check the database connection information and make sure that the database server is running.

Cause

This issue may occur when the SharePoint Timer Service tries to contact the configuration database when the computer starts or shuts down. By default, the configuration database in Windows SharePoint Services is named STS_config.

Resolution

The error message that is mentioned in the "Symptoms" section does not affect the functionality of Windows SharePoint Services or of Windows Small Business Server 2003. If you can connect to the Windows SharePoint Services Web site successfully, you can safely ignore this error message.

Workaround

To work around this issue, add the DependOnService registry entry to the following registry subkey on the server, and then set the DependOnService registry entry to MSSQL$SHAREPOINT:

Links

http://support.microsoft.com/?id=840685