You need to be able to view the web server’s Header information during the viewing of a SharePoint/WSS page.
 
With the Firefox web browser, you can install the Firebug extension to access the web server headers.
 
Once installed, click the little "bug" icon in the lower right corner of Firefox.
Select the "Net" tab and choose Enable.
 
Then surf to one of your SharePoint/WSS pages.
 
You’ll see under Firebug’s Net tab the Headers sub-tab. Look for a line similar to the one highlighted below.
 
 
Compare the number to this listing of SharePoint/WSS version numbers.

Advertisements
I was not able to install Live Mesh on my Windows Server 2008 R2 (full) system until I added the registry entry below:
 
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"DisableMSI"=dword:00000000
 
See this machine policy setting: DisableMSI
 
This entry was eluded to by the Live Mesh installation error message I was receiving. I though it might have been UAC or compatibility issues, but I only got it installed after the registry change.
 
Live Mesh is now running fine. (And I removed the registry entry after the successful install).
Currently, there are no drivers for the ATI FireGL V7200 for Windows Server 2008 R2 (or 2008). The OS installs, but uses generic VGA drivers with no dual monitor support. There are Windows 7 drivers for newer FireGL cards, but I tried the technique below to use them and just got reboots.  Using the Vista drivers and an INF file modification I was able to get full support for dual monitors with the ATI FireGL V7200 and Windows Server 2008 R2 (x64).
 
Download the Vista drivers. Go through the driver file extraction process. Modify the driver INF file as follows:
Ex.: C:\AMD\FirePro_8.583_Vista64_77160\Packages\Drivers\Display\LH6A_INF\CH_77160.inf
 
Copy these two lines under the [ATI.Mfg.NTadm64.6.0] section:
 
"ATI FireGL V7200" = ati2mtag_R520GL, PCI\VEN_1002&DEV_7104
"ATI FireGL V7200 Secondary" = ati2mtag_R520GL, PCI\VEN_1002&DEV_7124
to the [ATI.Mfg.NTamd64.6.1] section.
 
You will now have this section as follows:
[ATI.Mfg.NTamd64.6.1]
"ATI FireGL V7200" = ati2mtag_R520GL, PCI\VEN_1002&DEV_7104
"ATI FireGL V7200 Secondary" = ati2mtag_R520GL, PCI\VEN_1002&DEV_7124
 
Now continue the installation (or rerun setup.exe from the extracted files location).  You may have to force the selection of the driver, you can use Update driver under Device Manager and specifically point to the edited INF file.
 

Bottom line on top…  first impression on Microsoft Security Essentials (MSSE) has been excellent.

I had a coworker bring me their home computer (“It started to run really slow and I get these popups.”) I thought it would be a good opportunity to try out the beta of Microsoft Security Essentials and he was willing to give it a try. 

I booted to a new WinPE 3.0 (Windows 7) environment I setup and ran the command-line version of McAfee using their latest 5400 beta 2 engine.

McAfee VirusScan for Win32 v5.40.0
Copyright (c) 1992-2008 McAfee, Inc. All rights reserved.
(408) 988-3832  LICENSED COPY – Apr 16 2009

Scan engine v5.4.00 for Win32.
Virus data file v5654 created Jun 22 2009
Scanning for 530565 viruses, trojans and variants.

06/23/2009  05:14:32

Options:
/ADL /CLEAN /NOD /AFC=64 /STREAMS /PROGRAM /SECURE /EXCLUDE X:\*.* /REPORT X:\VIRUSCK.TXT

Summary report on C:\*.*
File(s)
        Total files: ………..  300323
        Clean: ……………..  293811
        Possibly Infected: …..       6
        Cleaned: ……………       0
        Deleted: ……………     319
Non-critical Error(s):                 2
Master Boot Record(s): ………       2
        Possibly Infected: …..       0
Boot Sector(s): …………….       1
        Possibly Infected: …..       0

Time: 01:45.37

The results were what I expected, even found 2 new unknown trojans/malware.  The system has multiple logons for his family and the infections were scattered among them.

I next booted to the installed OS in Safe Mode without any network connected.  I took a look around with msconfig for a quick check of anything that you wouldn’t want to auto start on a full bootup or login (things looked good). 

He had been running McAfee VirusScan 8.5i as part of our home-use site license. On booting to the full OS I found McAfee disabled (nicely infected for sure) but the Windows XP firewall still active (with expected active exceptions).  I uninstalled McAfee and plugged into my NAT’ed network and began the install of Security Essentials from my USB key. You can find elsewhere plenty of screenshots of the installation and main dialogs, so I’ll just show the goodies – what it looks like on an infected system.  After stepping through the installation wizard and getting the first signature updates, I chose to run a full scan – here’s the surprising results:

ms-se-found-virus

Microsoft Security Essentials found a number of infected (and nasty) files that McAfee missed (all under one users profile and not the one I was logged under). I let Security Essentials clean the computer and after running the recommended actions I had a clean system again (well, as far as Microsoft and McAfee knew…).

ms-se-fixed-virus

After another reboot and another quick scan using MSSE and my WinPE McAfee command-line scanner the system was coming up clean. I let my friend try out surfing and the system was back to its original speeds (still slow… it’s 6 yr old, ahhh).  With him understanding that it’s only safe after this kind of infection to format and reinstall he’s taking my advice that it’s time and makes sense for his type of usage and he’s getting a new computer. For the time being I at least set all their logons to regular users and created a new “Install-Admin” account.

I’ve been setting up for and pointing people to Avast for free home-use anti-virus software.  While I use it personally and have not had anyone complain about it (well, after I showed them how to turn off all the popup messages and voice prompts) I plan to start setting them up with Microsoft Security Essentials. I like the simple interface, low memory and CPU usage I’ve been seeing, and the experience from the first install.

Vista and Windows Server 2008 increase the security on the creation of HTTP listeners (HttpListener). If you try to run the Lansweeper service under a non-administrator account as you can with Windows Server 2003, you will encounter the error below:
 
5/21/2009 4:00:53 PM: Access is denied
   at System.Net.HttpListener.AddAll()
   at System.Net.HttpListener.Start()
   at LansweeperService.Listen.DoListen()
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Threading.ThreadHelper.ThreadStart()
 
To workaround this issue under Vista or Windows Server 2008, you can authorize (reserve) your service account to create the HTTP listener the Lansweeper service needs.
 
At an admin command prompt enter the following command:
 
netsh http add urlacl url=http://*:<port#>/ user=domain\service-account
 
ex.:  netsh http add urlacl url=http://*:9524/ user=contoso\svc-lansweeper
 
After applying the netsh command and given your Lansweeper service account modify rights to the installation folder (for write permissions to the log file) and "Log On As A Service" right in the Local Security Policy, you will then be able to start the Lansweeper service under an non-admin domain account.
 
To display the reserved HTTP listener URL enter the following command:
netsh http show urlacl
 
You should see similar output as below:
Reserved URL            : http://*:9524/
    User: CONTOSO\svc-lansweeper
        Listen: Yes
        Delegate: No
        SDDL: D:(A;;GX;;;S-1-5-21-1308237860-4193317556-336787646-243859)
 
"IPsec can encrypt data transmitted between servers, but you need to know the basics before you start. This primer takes you through terms and processes and ends with a walk-through of how to configure an IPsec policy that prevents data transmitted between two servers from being captured." – Russell Smith, Windows IT Pro
This is my goal on my new file server role out this summer. I would like to implement this with my client PCs. I need to look at performance impact and how to deal with other unit’s client PCs that I have to share files with, but I think I’ll be able to secure most of the connections.
 

Wolfram Alpha will chuck all the answers it can in a fight for our searches.

I fed Wolfram Alpha the tongue-twister "How much could a woodchuck chuck ifa woodchuck could chuck wood?" and I wasn’t disappointed by the answer as Wolfram Alpha gave back the proper tongue-twister response of "A woodchuck would chuck all the wood he could if a woodchuck could chuck wood."