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.

AMD & Service Pack 3 Issue/Fix

Boot up in Safe Mode. Sign in as Administrator.

Enter the Registry & find the following route:
HKey Local Machine\system\currentcontrolset\services\intelppm

Locate "Start" and identify the value. If AMD computer, change the value to 4

Value for AMD: 4
Value for Intel: 1

On an Intel-based system it will say 0x1. Do NOT set it to 0x4 on an Intel based system!!!



Extras
If you have an AMD based system and the Start value is set to anything other than 0x4, run this command:

reg add hklm\system\currentcontrolset\services\intelppm /t REG_DWORD /v Start /d 0x4 /f

CAUTION: don't set the Start value to 0x4 on an Intel-based computer! It may not boot properly if you do.

Win Media Player ripping issues

1. click the small arrow under sync, then select more options, then highlight audio Cd, click properties, then tick the "use error correction box

2. HKEY_LOCAL_MACHINESoftwareMicrosoftMediaPlayerSettingsMp3Encoding
Delete LowRateSample value,
Restart computer

Norton 08Product key doesn't fit empty boxes

Click on Help and Support, then activation. Enter product key.
Note: In case Help and support shows blank screen, then first remove and reinstall Framework. net.

One or more rules could not be uploaded to Exchange server and have been deactivated. This could be because some of the parameters are not supported o

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


http://support.microsoft.com/?scid=ph;en-us;2520&sid=216

Outlook 2003 on Exchange Server 2003: You have exceeded the size limit on your mailbox

When you perform a Send/Receive operation in Microsoft Office Outlook 2003, you may receive the following error message in the Mailbox Cleanup wizard:

You have exceeded the size limit on your mailbox. You can find types of items to delete or more, empty the deleted items folder, or your can have Outlook transfer items to an archive file.

CAUSE
This issue may occur if the following conditions are true:

•	You are using Outlook 2003 in Cached Exchange Mode.
•	Your mailbox contains corrupted items.
•	The mailbox is synchronized with the Offline Folder (.ost) file.

RESOLUTION

To resolve this issue, follow these steps.

Note These steps must be performed by a Microsoft Exchange Server 2003 administrator.

1.	Create a new user account. Then, create a test mailbox for this account.
2.	Test the test mailbox to make sure that the symptom that is described in the "Symptoms" section does not occur.
3.	Use the Microsoft Exchange Mailbox Merge tool (Exmerge.exe) to copy the mailbox that was used to perform the Send/Receive operation to a Personal Folders (.pst) file. Note In the Exmerge log, non-fatal errors may appear. These errors indicate that the corrupted items were discovered and were either fixed or deleted by Exmerge.exe.
4.	Use Exmerge.exe to merge the data from the .pst file into the test mailbox. Note You have to rename the .pst file to the name that you used for the test mailbox.
5.	Test the test mailbox again to make sure that the issue that is described in the "Symptoms" section does not occur.
6.	Make sure that mailbox retention is enabled on the mailbox stores that contain the following mailboxes: • The test mailbox • The mailbox that was used to perform the Send/Receive operation
7.	Start Exchange System Manager, and then delete the following mailboxes: • The test mailbox • The mailbox that was used to perform the Send/Receive operation
8.	Run the Mailbox Cleanup Agent so that a red X appears next to both mailboxes.
9.	Reassociate the test mailbox with the affected user account.
10.	Make sure that the test mailbox that you reassociated with the user account in step 9 has the correct information for the alias, for SMTP addresses, and for other parameters.