http://support.microsoft.com/kb/328010 How to configure
Automatic Update settings via RegEdit even when its tab on the System app
in Control Panel is greyed out. This appears to be necessary when using WSUS
because the DAY and TIME for the installation of automatic updates can not
be set any other way. Can it?+

http://www.avg.com/faq.keyw-serverCan't login to Exchange
Server from XP client The AVG firewall doesn't automatically allow the
Windows RPC Service to communicate, even if you are set as a PC in a
Domain.+

http://support.microsoft.com/kb/810489 Turning off the
stupid Exchange MTA warnings: Event ID: 2000 "Verify that the Microsoft Exchange
MTA service has started. Consecutive ma-open calls are failing with error
3051." MTA is only used when the server is a transport bridgehead to Exchange
Server 5.5 servers, or running the GroupWise, Notes or other Exchange Development
Kit (EDK) connector, such as a third-party Fax
connector.+

Why don't the "Allocated Memory Alerts" include a list of the processes that
are running at that point? Wouldn't that just be a massive help to figure
out why the stupid thing is running low?

Why is there no way to suppress or downgrade the logging of B.S. errors like:

"document failed to print" How on earth is a printer being out of paper a
freaking critical error?

Event ID 7515 where the "intellegent" message filter fails due to the email
being larger than
3MB^.

Event ID 7519 The originating IP address of message with ID x could not be
determined based on its Received
headers^.

Event ID 1 SQLVDI: Loc=CVDS::Cleanup. Desc=Release(ClientAliveMutex).
ErrorCode=(288)Attempt to release mutex not owned by
caller^. Yes, there
is a hotfix, but M$ recommends not applying it until the next rollup. If
we could suppress or downgrade the error, then our bosses wouldn't freak
and we could follow that recomendation.

WSUS server shows client
has not contacted update service in several days. Client is running AVG Firewall.
Despite the fact that all the recommended setup processes for AVG have been
run, triggering an update (by clicking Start / Run, entering CMD, enter then
typing wuauclt.exe /detectnowsetting) while watching the "Blocked Packets"
counter in AVG Firewall shows that AVG is blocking the update system. Setting
the AVG firewall to "Firewall disabled" allows the update connection to progress
and updates are detected and downloaded. Configuring AVG Firewall is confusing.
Here are step by step instructions for AVG 8.5:

In AVG, pull down the Tools menu and select Firewall settings. If you like,
you can check in "Logs" with "Show Details" to see if you can see port 8530
being blocked for ...SVCHOST.EXE.

under Profiles, select the profile AVG is current set to use. (see the main
AVG Firewall page in the lower left corner) If the client has a WSUS server,
this is most likely "Computer in domain"

In "Defined networks" click Add Network, change the name to "Server", mark
it as Safe, and enter the IP address of the WSUS server. It doesn't appear
that there is any way to use a FQDN.

In Defined services, click Add service, change the name to WSUS and click
the Add button; the Protocol is TCP, the Direction is Out, the Local ports
are "0-65535" and the Remote ports are "8530"

Under Applications / Various System Services, ensure Application action is
on Advanced settings, then click Add, Change the Detail action to Allow for
safe, uncheck Log rule occurrences. In Defined services, sroll down and check
the WSUS services. You can click the Expand / Collapse service so that only
the WSUS service is shown.

At this point, you should be able to click Apply or just Ok, and it should
update the settings. This doesn't appear to reliably happen. Try returning
to General in the upper left corner before clicking Apply. NOTE: Verify that AVG says the settings have changed and will be reloaded.
If you don't see that message, your changes didn't have effect.

Emails or NDR's
delayed until server or SMTP restart. Apparently, Exchange 2003 SP2
and later can fail to resend emails that are going to a server which tries
to "greylist" email from an unknown source. The dest server may tell Exchange
to "try again later" and Exchange fails to do so until the SMTP service is
restarted. Workarounds include using your ISP's SMTP server instead of Exchange
to send emails, restarting the SMTP service daily, and creating a
"GlitchRetrySeconds" entry as a dword in
HKLM\System\CurrentControlSet\Services\SMTPSVC\Queuing and try a value of
60 or 120, then restart the SMTP service. http://groups.google.com/group/microsoft.public.exchange.admin/browse_thread/thread/2ac7d5cfc8719427?hl=en+

Around mid April 2010, the "Server Performance Report" starts showing "The
page can not be displayed" in emails and on the management console. Update
Services in the same console gives error: "The Element Already Exists in
the Collection". Chris Puckett found that something about the WSUS entry
for update KB976703 was causing this. The solution is: Start, Administrative
Tools, Windows Server Update Services. Action, Search... Text: KB976703,
Find Now. Once the udpate has been found, right click it and select "Decline"
then confirm. If you actually have Exchange 2000 server, manually install
KB976703. Thanks to Chris and the support team.

After you find an appropriate page, you are invited to
your
to this massmind site! (posts will be visible only to you before review)
Just type in the box and press the Post button.
(HTML welcomed, but not the <A tag:
Instead, use the link box to link to another page.
A tutorial is availableMembers can
login
to post directly, become page editors, and be credited for their posts.

Link? Put it here:
if you want a response,
please enter your email address:
Attn spammers: All posts are reviewed before being made visible to anyone other than the poster.