For whatever reason, it’s quite possible to end up with a Symantec AntiVirus client which isn’t talking to the server – You may have accidentally uninstalled Symantec AV from you’re server, reinstalled the server or moved it on to another server. So how do you get those SAV clients to re-register in the console?

Well, I decided to use a logon script to sort out a number of clients in one hit. Download the following av-fix batch file:

Download: av-fix.bat

In the case of SBS 2003 – you need to place this file in the netlogon folder. Once in place, open up the file and place your Symantec server name in the correct place, replacing “\\yourserver”.

To make the logon script silent, I decided to use a small program called hstart. Download it from here and place in the netlogon folder. My script uses the widely available robocopy, so get yourself a copy of that and place it in the same folder.

Now, from your main logon batch script you just need to insert the following line:

hstart /NOCONSOLE “av-fix.bat”

This executes the batch file in hidden mode (the user won’t notice anything)

The av-fix.bat file places a grc.dat in the correct place on your client machines. It also updates the pki directory.

It’s tested to work on XP (but I’m unsure about Vista…)

Sit back and watch the Symantec Console repopulate as the clients login. Beautiful! I hope you find it useful!

Server Error in ‘/’ Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Unrecognized configuration section ‘connectionStrings’

Source Error:

Line 20: Line 21: </appSettings> Line 22: <connectionStrings>

Source File: D:\home\Default\website.com\htdocs\web.config Line: 22

Version Information: Microsoft .NET Framework Version:1.1.4322.2379; ASP.NET Version:1.1.4322.2379

Well, it turns out this is what happens if you try and run an ASP.NET 2.0 application using ASP.NET 1.1. So just follow these quick steps to cure the problem:

1. Click Start
2. Click Run
3. Type inetmgr (or open the IIS manager from the admin tools)
4. Expand the server object
5. Expand Default Websites
6. Select your website, eg website.com
7. Right click and go to Properties
8. Select ASP.Net Tab
9. ASP.Net version select version 2

If this option isn’t available make sure you have the dotnet framework 2.0 installed. Problem solved!