WSUS - Clients not updating

If WSUS clients are not connecting to the WSUS server and giving errors
such as "WARNING: GetAuthorizationCookie failure, error = 0x800710DD" in
the WindowsUpdate.log file - you probably have a permissions issue on the
IIS WSUS site. To check that the permissions are set correctly use this:
http://technet.microsoft.com/en-us/library/cc708545%28WS.10%29.aspx

And to check the IIS Anonymous user password is in-sync with IIS follow
this:
http://blog.montopolis.com/2007/06/02/easily-resync-iis-anonymous-user-account/

Exchange 2003 - Anti Spam Configuration

Exchange 2003 has some anti-spam functionality that can be implemented on
the server in a pinch:

Recipient Filtering
Sender Filtering
Intelligent Message Filtering (SCL Rating)
Connection Filtering (RBL Black lists)

These need to be configured and enabled on the SMTP virtual server before
it works.

This link will demostrate how to deal with an NDR type attack and shows how
to configure the filters inside the ESM
http://support.microsoft.com/kb/886208

http://support.microsoft.com/default.aspx?scid=kb;[LN];261087

Tarpitting is another mechanism used to prevent Directory Harvest attacks
http://support.microsoft.com/kb/842851/

If you need to dump the existing SMTP queue as it is filled with spam -
rename the Queue directory found here
http://support.microsoft.com/kb/822933

Acronis ABR10 - 'Not enough storage is available to process this command' errors

This is when the temporary snapshot file acronis creates cannot grow big
enough to complete the backup job.

The solution is to either move the snapshot file to a bigger volume or
increase its size or both as per http://kb.acronis.com/content/8032

SBS WMI Performance Monitoring Errors

If the server is sending alerts like this:

Processor : Critical condition. WMI Status: 2147749889 Enumeration failed.
Object not found. Data Collector is misconfigured. 0x80041001 :

Also

PagingFile : Critical condition. WMI Status: 2147749889 Enumeration failed.
Object not found. Data Collector is misconfigured. 0x80041001 :

And

Redirector : Critical condition. WMI Status: 2147749889 Enumeration failed.
Object not found. Data Collector is misconfigured. 0x80041001 :

You may need to rebuild the performance counter libraries as per
http://support.microsoft.com/?id=300956

Source URL:
http://www.winserverkb.com/Uwe/Forum.aspx/windows-server-sbs/23662/What-does-this-mean

Network Auto-Disconnect

Windows has a network auto-disconnect function that will do an OSI Layer 1 disconnect after 15min, to save power presumably. This can cause problems with certain applications, namely Outlook in some cases - that will start doing some strange things and will return to normal only after restarting the program.

A solution is to disable this feature by running the following in an administrator cmd session.

net config server /autodisconnect:-1

To make it permanent we need to edit the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
There should be a dword named "autodisconnect"
Set the value to 0xFFFFFFFF

Source URL: http://www.windowsitpro.com/article/john-savills-windows-faqs/how-do-i-configure-lan-autodisconnect-.aspx

Trend WFBS v7.0

The latest version of Trend has a couple of issues, namely it no longer supports Windows 2000 (This could be an issue if your site is still 2000 based) and the client agent does not upgrade properly on SBS 2003 servers.

After running the upgrade - the client agent is not installed properly and is not running on the server.

First make sure the latest critical patch is applied:
http://downloadcenter.trendmicro.com/index.php?clk=tbl&clkval=1815&regs=AUS&lang_loc=4#fragment-1831

Next we need to remove all traces of the client agent from the server using the removal tool:
ftp://transfer:data@techsupport.trendmicro-europe.com/WFBS/7.0/SA%20uninstall%20-%207.0.1343.zip

Now we should be able to install the latest client on the server without any further problems using the "\\Servername\ofcscan\autopcc.exe" method.


Source URL: http://community.trendmicro.com/t5/Business-Security-Forum/WFBS-7-0-installati-on-error-on-SBS-2003-servers/td-p/18164/page/6

Trend WFBS Download: http://downloadcenter.trendmicro.com/index.php?regs=AUS&clk=result_page&clkval=drop_list&catid=8&prodid=39

Trend WFBS Cleanup

Here is a tool that can be used to clean up the Trend WBFS Security Server.

http://esupport.trendmicro.com/0/Worry-Free-Business-Security-Standard-Advanced-Disk-Cleaner.aspx?print=true

PrintUI DLL - Automatically configure printer settings

You can use the printui.dll method to add/remove printers from users profiles quietly like this:

To add a printer run:
rundll32 printui.dll,PrintUIEntry /in /q /n "\\Servername\Printer Share"

and to remove an existing one run:
rundll32 printui.dll,PrintUIEntry /dn /q /n "\\Servername\Printer Share"

These can be added to logon scripts, etc.

Source URL: http://www.computerperformance.co.uk/Logon/logon_printer_computer.htm

N-Computing Troubleshooting II

Ensure that Windows Updates are disabled on the vSpace server.
Found that KB981957 (Windows 7 x86) caused the vSpace server to malfunction and terminals cannot connect. You should be able to uninstall this update and restart the server to get it going again.

N-Computing Troubleshooting

Running N-Computing 5 x L-130 terminals using a Windows 7 (32bit) PC as a server using vSpace 5.1.3.12. The system has Trend WFBS client agent installed and is a part of an SBS 2008 domain and has some end-user applications installed.

System appears to stop functioning every few month due to Trend or Windows updates that seem to break the system. This is due to the fact that the system is probably not fully Windows compatible or certified and appears that certain Windows updates overwrites critical files and settings.

Here are a few tips I have gathered while troubleshooting and resolving problems with this system:

1. Do not DISABLE the windows firewall. You can turn it off or configure exceptions that will allow the terminals to connect to the server without restriction - This will prevent the vSpace services from starting properly. It is also a good idea to allocate static IP addresses to the terminals.

2. Ensure EVERYONE is assigned the "Allow log on through Remote Desktop Services" right. This is accessed through the gpedit.msc and is a local Computer Policy.

3. Configure Anti-Virus exceptions for the vSpace services and executables. Otherwise the services won't start.

4. Make sure the logon settings for the vSpace services are set to "Local System account" and check the "Allow service to interact with desktop" is checked.

Support for N-Computing can be difficult to obtain but you can start with making sure you have the latest version of the vSpace server.
http://www.ncomputing.com/softwaredownload

There is a Knowledge Base located at http://www.ncomputing.com/kb/ and a forum here http://www.ncomputing.com/forum.