Can't Install .NET Framework 2.0

1. Download the .NET Framework cleanup tool and choose to cleanup the version of the .NET Framework that is causing problems on your system
2. Download and install the version of the .NET Framework that you cleaned up in step 1 (such as the .NET Framework 1.0, .NET Framework 1.1 or .NET Framework 2.0)
3. (optional) Download and run the .NET Framework verification tool to double-check that all .NET Framework files are correctly installed
4. Download and install the desired .NET Framework service pack (such as .NET Framework 1.0 SP3 or .NET Framework 1.1 SP1) by running the setup package directly instead of using Windows Update. Running it directly will allow the service pack setup to display error dialogs instead of having Windows Update suppress them

Error: "QuickBooks has a problem in reading this registration file: qbregistration.dat" after installing an update to Symantec Norton 360

What is happening

When starting QuickBooks, the "Loading QuickBooks..." screen appears temporarily, and then the following error message appears:

QuickBooks has a problem in reading this registration file. You need to ask your system administrator to REMOVE this file and re-install QuickBooks

C:\Documents and Settings\All Users\Application Data\Common Files\Intuit\QuickBooks\QBRegistration.dat

Why is this happening

This error usually occurs if there has been damage to the MSXML component of Windows.

Note: This has been known to occur after installing an update to Symantec's Norton 360 security software suite.
This error may also occur even if Norton 360 is not installed on the computer.

https://support.quickbooks.intuit.com/support/Pages/KnowledgeBaseArticle/1009799

In the Open field, type msiexec.exe /fvaum D:\Qbooks\msxml.msi (replace D with the letter assigned to your CD drive) and click OK

Background is white, Win XP

Control Panel, Accessibility options, Display, uncheck High Contrast.

ERROR: Unable to create Cab Installer Object (when updating Total Protection for Small Business

Step 1 - Obtain the values stored in szDownloadServer and szXMLDataServer to use in Step 2:

1. Click Start, Run, type: regedit and click OK.
2. Navigate to the following location:
   [HKLM\Software\McAfee\Managed Services\Agent]
3. Locate the keys szDownloadServer and szXMLDataServer.
   
   NOTE: The Domain name specified is being used for regional Network Centre (NOC).
   
   Example
   Key values for Germany would be:
   
   - szDownloadServer: http://vs.mcafeeasap.com/MC/DEU/VS40
   
   - szXMLDataServer: http://vs.mcafeeasap.com
   

Step 2 - Check the correct Network Centre Domain is also listed in the SecureObjectSites section

The aim in this step is to verify the following locations are both specified:

• http://vs.mcafeeasap.com
• https://vs.mcafeeasap.com (Secure Socket layer (SSL) reference)
  

1. Navigate to the following location:
   [HKEY_LOCAL_MACHINE\Software\McAfee\ManagedServices\SecureObjectSites]
   
   Example registry key:
   "http://mcafeeasap.com"=dword:00000000
   "https://mcafeeasap.com"=dword:00000000
   "https://mycio.com"=dword:00000000
   "http://mycio.com"=dword:00000000
   "https://nai.com"=dword:00000000
   "http://nai.com"=dword:00000000
   "https://mcafee.com"=dword:00000000
   "http://mcafee.com"=dword:00000000
   "file://dontcare"=dword:00000000
   "myui://dontcare"=dword:00000000
   "myrm://dontcare"=dword:00000000
   
   NOTE: In this example both keys values are populated but with this issue the keys will be missing.
   
   
2. While in the SecureObjectSites section, in the right pane right-click and select New then DWORD Value.
   
3. For the DWORD, enter the http Domain name extracted from the SzDownloadServer entry in Step 1.
   Example: http://mcafeeasap.com
   NOTE: Ensure to remove the vs from the Domain name obtained in Step 1 (http://vs.mcafeeasap.com)
   
   
4. Remaining in the SecureObjectSites section, in the right pane again, right-click and select New then DWORD Value.
   
5. For the DWORD, enter the https Domain name extracted from the SzDownloadServer entry in Step 1.
   Example: https://mcafeeasap.com
   NOTE: Ensure to remove the vs from the Domain name obtained in Step 1 (https://vs.mcafeeasap.com)

Unable to open Wab Outlook Express

If there is no path shown in the Address Book under Help | About Address Book, that means OE is sharing the Contacts folder in Outlook, and so no *.wab file is being used. Sharing allows OE to display only the Contacts folder in the default *.pst in Outlook's default Profile. You can't access other Outlook folders, just the Contacts folder, and there is no support for using Shared Contacts amongst multiple OE Identities. To turn off sharing and revert to using a *.wab, click Tools | Options (which appears only in OE5/5.5 and only if Outlook98/2000 is installed and configured in Internet Mail Only mode). However, starting with OE6 and Outlook 2002 (Outlook XP) and Outlook 2003, sharing is no longer officially supported. If you install as an upgrade and sharing is already enabled, it will remain enabled after the upgrade (or at least, it should). Therefore the Tools | Options has been removed from OE6. In that case, you can still manually enable (or disable) sharing by editing this registry key after closing Outlook Express:

| HKEY_CURRENT_USER
|----Software
|-------Microsoft
|----------WAB
|--------------WAB4

Create a new DWORD value named UseOutlook, or modify that value if it already exists. To enable sharing, so that OE no longer uses a *.wab, set UseOutlook to 1. To disable sharing, set its value to 0. The change will be reflected the next time you open OE.

Howto configure Internet Access in SBS2003

http://support.microsoft.com/kb/825763

Connect Remote WS to a Domain

1. Login as administrator on the workstation and create a VPN-connection to the SBS-server. Make sure you enable this connection for ‘All users’. After the setup has finished, go to the Properties of this connection and check the ‘include Windows login domain’ in the tab Options.
2. Connect to the SBS-server with that VPN-connection using the administrator’s credentials.
3. Right click My Computer, Properties, Network Identification.
4. Enable ‘Domain’ and fill in the name of the SBS-domain (on XP you might need to add the .local suffix, so company.local).
5. Fill in the login name and password of an account that is allowed to join a workstation to the domain.
6. After a while you will get the ‘Welcome to domain’ message and the remark that you will have to reboot the workstation. Make sure you don’t reboot yet!
7. OK out of the Network Identification and don’t reboot before you have added the domain user to the local Administrators Group of the workstation.
8. Go to Control Panel, Users and Groups, and click Add.
9. Fill in the name of the user and the domain name or use Browse and make sure you choose the SBS-domain from the drop down box, than select the domain user.
10. Make sure that the added user is given the ‘Administrator’ right on the workstation.
11. OK out of it and reboot.
12. After reboot, fill in the name of the domain user, password and make sure the SBS-domain is selected in the domain field. Check the ‘use dialup connection’-box.
13. After OK, choose the VPN-connection to connect to the SBS. When authorized into the SBS-domain, the login script will run.
14. After the login script has finished and if you have Premium, you will see the ‘Install Firewall Client’-icon on the desktop. Double-click it and let it install.
15. The login script will also have added the ‘Remote E-mail access’ and ‘Remote Server Access’. It will have set the homepage in the IE-settings to the Companyweb.
16. You can modify these favorites to make them available for the remote user. In Documents and Settings\Favorites right click the link and choose Properties. Modify the link to ‘http://servername/exchange’ to the proper link needed for accessing OWA from the internet. Example: https://FQDN/exchange or https://IP/exchange and https://FQDN/remote or https://IP/remote.
17. If Premium, go to the LAN-settings of IE and uncheck the ‘use proxy’. Disable the Firewall client by right clicking the Firewall Client icon in the system tray (as the Firewall client will prevent the user to access the Internet when not connected to the SBS).
18. Disconnect the VPN-connection and reboot as the domain user without dialing up to the SBS-domain. Check all links and check the default Internet access. Check the vpn-connection.