Kaspersky Lockup Solved

So, this is a bit off the SBS highway. I started using Kaspersky’s 2009 Internet Security Suite for many of my non-server (family and friends) clients. I like it a lot. But a couple of times recently, I had an issue where Kaspersky would lock up while I was trying to use it or install it. In each case, once it locked up, I could do nothing but stop it from task manager.

 remember many years ago when I did a lot of software debugging to always reduce a problem down to its Lowest Cost Denominator (LCD).

Well, I finally had time to do that today, and determined that the LCD in this case was LogMeIn! In each case where I had Kaspersky locking up on me, I was connected to the computer remotely through LogMeIn. The solution was to add LogMeIn.exe to Kaspersky’s Trusted Site and click on the option to not have it control application activity. I believe I saw posts where a similar lockup occurs with the VNC-type remote access software.

Hope this helps!

SBS20008 Migration Documents

For those of you who may have missed it … new documentation for migrating to SBS 2008 is now available for viewing or download. This covers both SBS 2003 to SBS 2008, and SBS 2008 to SBS2008 scenarios.

Online Technet versions:
Migrate SBS2003 to SBS2008
Migrate SBS2008 to SBS2008
All SBS2008 Technet articles

Downloadable versions:
Migrating SBS2003 to SBS2008 (Word Doc – 77 pages)
Migrating SBS2008 to new hardware (Word doc – 58 pages)
SBS Migration & Setup (CHM file)

Happy migration!

Making Vista UAC Workable

I know I am not the only one who has considered completely disabling the User Account Control (UAC) in Windows Vista, or actually gone ahead and disabled that sucker! Recently I had a situation where UAC was preventing me from completing a project, and I had to disable UAC long enough to install and run a new app. Since then I have discovered tow possible workarounds to this issue.

Both solutions take the approach of letting you flag often-used applications and the level of security required to run them. It then stores that information so that the next time you execute the application, it already knows your response, and you can proceed without getting that annoying UAC prompt.

The first solution comes from the dailyApps blog, and is based on use of the Application Compatibility ToolKit from Microsoft. Click here to read the details. The second solution comes from NortonLabs, is is simply entitled UAC Tool. Their approach is to put a wrapper around Vista UAC, building a whitelist database of your frequently-used apps, while still relying on the UAC security system.

I’d be interested in finding out what others think of either or both solution.

SBS 2008 and Sharepoint Log file

If using SBS 2008, one of the things you want to do is to install and run the SBS 2008 Best Practices Analyzer (BPA) on a regular basis. At my first SBS 2008 installation, BPA recenlty reported that my Sharepoint log file was larger than 1gb in size. Strange, I thought, since this customer had not even started using sharepoint. Beyond that, BPA did not offer any suggestions for resolving this issue.

So, here are the instructions (from the SBS BPA team) on what to do:

Step 1: start up command prompt in administrator mode. You do this by clicking on Start, then right clicking on Command Prompt, then clicking ‘run as Administrator’

Step 2: From the command prompt:
1. Type: sqlcmd –E –S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query and press Enter
2. From the 1> prompt, type: select name from sys.databases and press Enter
3. From the 2> prompt, type: go and press Enter
This will display a list of all databases know to SQL server. One of them will look something like this:

Step 3: Now, with the actual name of the Sharepoint database, you will want to enter the following commands, replacing dbname with the actual name of the Sharepoint database. Be sure to leave the brackets [ ], parens ( ), and _log, as noted:

2> Go
1> Use [dbname]
2> Go
1> DBCC SHRINKFILE([dbname_log],2)
2> Go
1> Exit

For example, if your Sharepoint database was named SharePoint_Config_12345, then you would type in:

1> BACKUP LOG [SharePoint_Config_12345] WITH TRUNCATE_ONLY
2> Go
1> Use [SharePoint_Config_12345]
2> Go
1> DBCC SHRINKFILE([SharePoint_Config_12345_log],2)
2> Go
1> Exit

Hope this helps!

Facebook add-in to Outlook

I opened up a Facebook account earlier this year. You can imagine the shock on my daughter’s face when she discovered that Dad had a Facebook account!

So, I’ve used it and like many of the social networking features. However, it’s not second nature to me to logon to Facebook to update my status or see new posts. So, I just discovered a free Facebook add-in to Outlook called FBLook.

This product is certainly in it’s infancy, but it already makes it easier for me to do two things (see screenshot here):

  • I can update my Facebook status directly from the Outlook toolbar. That’s great, because I don’t have to open another window and login to accomplish this task.
  • It gives me a drop down list within Outlook to easily read the lastest posts from my friends. I can then click on one of those posts from wthin Outlook and it will open up Facebook so I can post a reply.

Give it a try. It works with both Outlook 2003/2007.

Uninstalling Live OneCare from SBS 2008

When SBS 2008 was first released, it included a 120 day trial of both Live OneCare (Server) and Forefront Security for Exchange (FSE). Since then, Microsoft has announced they would be dropping support for Live OneCare. When installing SBS 2008, you are asked whether you wanted to install the 120 day trial of these two products. If you did select to install them, and now wish to uninstall them, the process is very easy.

From the SBS console, click on Control Panel > Programs and Features. Click to highlight Live OneCare and then click Uninstall. The uninstall process is very straightforward, and no rebooting of the server is required to uninstall Live OneCare.

Uninstalling Forefront Security (FSE) from SBS 2008

In a previous blog post, I provided instructions for uninstalling Live OneCare (Server) from SBS 2008. That was pretty straightforward. If you wish to also uninstall the 120 day trial of Forefront Security for Exchange (FSE), there’s a preliminary step you must perform. If you try to simply uninstall FSE, you will get a warning message saying that you need to first manually stop all Exchange services and the FSE administrator, and then the uninstall process terminates.

So, here’s what you do:

1. Click on Start > Administrative Tools > Services, and then locate and stop the FSCController service, which will also stop the Exchange Transport Service and the Exchange Information Store Service.

2. Then go to Control Panel > Programs and Features, click to highlight Forefront Security for Exchange Server, and then click uninstall.

3. After FSE is uninstalled, you will be required to reboot your server.

Note: After uninstalling FSE, you may find that a Microsoft Forefront Security subfolder with some files and a Quarantine folder still remains within the Program Files (x86) folder. If you are not planning on reinstalling FSE, you may safely delete this Microsoft Forefront Security folder and its contents.