Mundy.net.au

Problem: Total Protection Service 5.0 fails to update. If a manual update is run, the local user interface reports "Searching for an internet connection" instead of updating. Note: Applies to Total Protection Service 5.0 only.

Source: https://kc.mcafee.com/corporate/index?page=content&id=KB66454&actp=search&searchid=1255293656227

Direct link to fix: https://kc.mcafee.com/resources/sites/MCAFEE/content/live/CORP_KNOWLEDGEBASE/66000/KB66454/en_US/FixTpsUpdates_exe.zip

Right click on the network icon in the system tray, and select "turn off notification of new networks"

Source: http://forums.whirlpool.net.au/forum-replies-archive.cfm/1131596.html

Seems like a hack to me, if anyone knows a better solution I'd love to hear it!

This can also be set via the registry:

• On a per user basis
  • Set the value "Show" (REG_DWORD) to 0 in
    HKCU\Software\Microsoft\Windows NT\CurrentVersion\Network\NwCategoryWizard
• At the system level
  • Create a new Registry key (without any value) NewNetworkWindowOff in HKLM\SYSTEM\CurrentControlSet\Control\Network\NewNetworkWindowOff

Windows Media Player 11 wouldn't open. Downloading it again and reinstalling didn't help. When you double click on the icon, or try to open a video file, nothing happens. It is not even listed in Task Manager.

The fix:

1. Open a Command Prompt (as Administrator)
2. Type: regsvr32 jscript.dll
3. Then type: regsvr32 vbscript.dll

This also fixed some problems we were having with certain websites playing up in Internet Explorer.

Outlook remembers names and addresses you type, this feature is called AutoComplete. When you move to a new computer this is lost, but it can be backed up and moved.

The NK2 file is where these addresses are stored. You can back them up simply by copying the file from the old PC to the same location on the new PC. This file is named based on the profile, eg if my profile name was Daniel, and my logon ID was dmundy, then it would be stored in:

C:\Documents and Settings\dmundy\Application Data\Microsoft\Outlook\Daniel.nk2

If you have changed the name of the Outlook profile, remember to rename the file.

After uninstalling the old version of McAfee and installing the new one, some PCs were displaying this message when Outlook was opened:

The Add-in "Exchange Scan" (C:\Program Files\McAfee\Managed VirusScan\VScan\OtlkUI.20091023152755.dll) cannot be loaded and has been disabled by Outlook. Please contact the Add-in manufacturer for an update. If no update is available, please uninstall the Add-in.

The first thing to try when fixing Outlook plugin errors, particularly after uninstalling/reinstalling antivirus programs, is to delete the extend.dat file from C:\Documents and Settings\username\Local Settings\Application Data\Microsoft\Outlook.

If deleting extend.dat does not work, try the following:

1. Click Tools, Trust Center
2. At the bottom there is a selection list called "Manage", from there select "Exchange Client Extensions" and click Go
3. Uncheck "Exchange Scan"

You may receive the following error message in the event log:

Message:  System log generated Error Event 7028 on reception.managed.sla2.ljkg

For more information see http://www.eventid.net/display.asp?eventid=7028&source=Service Control Manager

Log: System
Type: Error
Event: 7028
Agent Time: 12:06:49 pm 8-Oct-09
Event Time: 1:36:49 am 8-Oct-09 UTC
Source: Service Control Manager
Category: None
Username: N/A
Computer: RECEPTION
Description: The wuauserv Registry key denied access to SYSTEM account programs so the Service Control Manager took ownership of the Registry

Check this registry value:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\BITS\ImagePath

It will probably be set to: "%fystemRoot%\system32\svchost.exe -k netsvcs" (without quotes)

Set it to: "%SystemRoot%\System32\svchost.exe -k netsvcs" (without quotes)

You will probably not have permission to do this. Open the properties of the BITS key, and give yourself the "Set Value" privilege. Remove this privilege after making the change.

You may wish to set up a test environment in Hyper-V for playing around with SBS 2008. You probably want it to have Internet access so that you can test things like WSUS. But supposing you already have an SBS server in production then you'd be worried about having two DHCP servers on the same LAN.

The thing with DHCP is that it works by using broadcast packets that are sent out to all devices on the same "physical" subnet. Essentially, to isolate two DHCP servers from one another, there must be a router in between. So we turn the Hyper-V host into a router.

This process fills the following requirements:

• Allows the Hyper-V guest to access the internet
• Allows the guest to access other machines on the physical LAN
• Allows other machines on the LAN to access the guest machine
• Allows the guest machine to be exposed and accessed from the Internet (after setting up port forwarding on the "default gateway" router)
• The guest is on a different subnet than the LAN machines, therefore broadcast packets (eg. DHCP) are isolated
• Additional subnets can be created as required (testing branch office scenarios, etc)

For the purposes of this example, assume the following:
Hardware router (default gateway) is 192.168.0.1
The Hyper-V Host is 192.168.0.10

Create a Virtual Network

We will be using "Internal Virtual Networks" in Hyper-V. With this configuration the guest can see other guests on the same virtual network, and can also see the host.

First, create the virtual network on the Hyper-V host:

1. Add an Internall Only Virtual Network in the Hyper-V Virtual Network Manager - I called mine "Internal 192.168.16.0"
2. Go to the Network and Sharing Center and then Change Adapter Settings
3. If you sort by Details, you'll see a network device with a Device Name of "Internal 192.168.16.0"
4. Open it's properties, and set the IPv4 address to 192.168.16.1 with a subnet of 255.255.255.0

Enable IP Routing

The following 6 steps show you how to install RRAS to provide the routing. Read past these steps, though, and I'll show you an easier way that doesn't require an additional role to be installed.

Steps to install Routing and Remote Access:

1. Server Manager > Add Role
2. Select "Network Policy and Access Service", click Next
3. Select "Remote Access Service" and "Routing", click Next
4. Select "Custom Configuration", click Next
5. Select "LAN Routing Only", click Next
6. Start the service when prompted

You don't actually have to use RRAS to enable routing between internal interfaces. Instead, set IPEnableRouter to "1" in regedit:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]
"IPEnableRouter"=dword:00000001

Finally, and critically (ie. don't skip this step like I did initially, and expect it to work!) you'll need to add a static route on the "default gateway" router for the physical LAN - usually an ADSL modem or other edge device.

In my case it was a Netgear ADSL router, so I browse to http://192.168.0.1 and configure a static route to 192.168.16.0 mask 255.255.255.0 through 192.168.0.10.

Configure the Guest's Network Adapter

Now you can configure a virtual machine's network adapter to use this "Internal 192.168.16.0" network, give it a static IP address of eg. 192.168.16.2, with a default gateway of 192.168.0.1.

This should be all that is required!

Additional Subnets

You can add as many of these "Internal Only" networks as you want. They will all be able to talk to each other (if they know the IP address) and they will all have access to the Internet. You can even forward ports from the Internet to any of these "Internal Only" networks... But since they are on different subnets they will not interfere with each other when it comes to broadcasts (eg. DHCP).

I currently have SBS 2003 in my production LAN, and two virtual networks comprising of SBS 2003 and SBS 2008 on Hyper-V, and they do not clash.

More Reading

• Nicola Delfino's blog uses the RRAS technique - exact same steps but to achieve a different goal: using Hyper-V with a wireless network connection.
• Chris Blankenship's article taught me the IPEnableRouter trick to replace RRAS

Caching mailboxes that are either larger than 2GB in size or contain more than 5,000 items can negatively affect Outlook performance. Instead of deleting old emails or archiving them to PST, if this is not an option, you can set a filter on a particular folder so that it is not stored in the OST cache, but is still available when connected to the Exchange folder (and backed up).

1. Right click on the folder and select Properties
2. In the Synchronization tab, click on the Filter button
3. Go to the More Choices tab
4. Set "Size (kilobytes) less than 0"