Got this error (in vista when trying to uninstall nikon Capture 4):

The solution is to delete (in this case) the folder named 0701 from C:\Program Files\Common Files\InstallShield\Professional\RunTime\

However, I could not delete this but could rename it to 0701.bak.

After that I ran the installer to re-install then immediately ran it again to uninstall.

Arcobat 8 will not install on Vista.

This is (probably) caused by disabling User Account Control (UAC). There are three Adobe solutions:

Enable User Account Control

1. In Control Panels, choose User Accounts
2. Click "Turn User Account Control on or off"
3. Check the box to "Use User Account Control (UAC) to help protect your computer" and then click OK
4. Restart your computer
5. Install Adobe reader 8;

Create a new user account with administrator rights and install under this profile

1. In Control Panels, choose User Accounts
2. Click" Manage another account"
3. Click "Create a new user account"
4. Enter a new user name, select the Administrator radio button, then click Create Account
5. Log in to the computer with this new account and install Reader 8;

Run the Acrobat set up files extracted from the installer

1. Download the Adobe reader installer from adobe.com. When you are prompted to run or save the file, choose save. Save the file to your desktop
2. On the Desktop, double-click the AdbeRdr80_en_US file, click Run
3. Please wait while the Adobe Reader setup is being processed
4. When the "Open File - Security Warning dialog displays, do the following:
5. On the Windows task bar, choose Start
6. In the Start Search window, type c:users username AppDataLocalLowNetopsystems emp, then click on the link to open the temp folder
7. Drag the Adobe reader 8.0 folder to your desktop and close the search results window
8. Click Cancel in the Open File - Security Warning dialog
9. Click Cancel when" the operation was canceled by the user" dialog appears
10. Open the Adobe Reader 8.0 folder on your desktop
11. Double-click the AcroRead file to start the Adobe Reader installer
12. Click Run
13. Click Next
14. Click Install.

A similar, but unrelated problem results in teh folowing message:

In this case the MS solution is:

1. Start the installation as usual, do no dismiss the error message box.
2. Open explorer and copy the "Adobe Reader 8" directory from the following path to your root dir
"C:Users{username}AppDataLocalLowNetopsystems emp"
3. Run the setup.exe from the "Adobe Reader 8" directory on your root dir.

HKLM\Software\Microsoft\Exchange\ContentFilter
DWORD: ArchiveSCL
Value: 1

This can be updated automatically (by Microsoft Update, WSUS, etc) by adding the following registry key:

HKLM\SOFTWARE\Microsoft\Exchange
DWORD: ContentFilterState
Value: 1

Restart the SMTP service after.

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

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

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.