Re: Question on Security Update for Exchange 2003

David A - you have your prerogative to feel my response is not well thought
out (I still think it is more than sufficient), but you certainly make a lot
of assumptions on your own about the OP's environment. Assumptions I would
not feel comfortable making. Counterpoints to your response.

1. The cost to setup a lab environment is not extremely high. It can
consist of 1 server running Microsoft Virtual Server (or VMWare Server),
both of which are free, with Exchange servers as VM's. There is nothing
that says a lab environment must duplicate hardware. The whole point of a
lab environment is to have an alternate environment in which things can be
tested before they are rolled out into production.
2. Why should there be a special push to include backups prior to applying
a security patch? Backups should be done on a nightly basis. I've never
performed a backup just for a security patch. Service packs - yes.
Security patch - no.
3. Was the link I included insufficient for this? The FAQ for the patch
clearly explains this part.
5. Can't be uninstalled, eh? Are you sure? All hotfixes and security
patches can be uninstalled via the Control Panel, Add/Remove programs.
Service Pack 2 can't be uninstalled, but everything else can be. There is
also no permanent "damage" caused by this patch.

From the deployment instructions found in the link I provided.
Removal Information
To remove this update, use the Add or Remove Programs tool in Control Panel.
System administrators can also use the Spuninst.exe utility to remove this
security update. The Spuninst.exe utility is located in the
%Windir%\$NTUninstallKB916803$\Spuninst folder.



Don't you think you are going a bit overboard for a security patch???

--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)



"David A" <DavidA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8A6620DD-4963-43FD-9D24-4ACB6AB74AB7@xxxxxxxxxxxxxxxx
I don't mean to hate but this is not a well thought out response.

So here the person posts that they have taken over Exchange duties, they
are
not an Exchange Expert and has some knowledge. This tells me this is not
a
very large shop since a larger shop will tend to put someone who has
Exchange
experience on their Exchange Management team. Given that I then can
surmise
that since this is a small/medium shop they then probably don't have a lab
environment. The cost to setup a lab environment is extremely high and
usually can only be afforded by the largest of companies.

Now given that I feel a better answer would have been.

1) Backup
2) Read about the patch and its implications
3) Understand the Send As feature and if you have already implemented it
or
if the patch will cause it to be implemented.
4) If you have third party applications that may be affected such as
Blackberry understand how to deal with this by doing research on what the
Manufacturer says on how to deal with the actions of Microsoft.
4) THE BEST: The patch is uninstalable and thus any damage caused by its
installation can be reversed. At least what Microsoft tell us!

Thanks,




"Ben Winzenz [Exchange MVP]" wrote:

Just run the .exe. Any services that need to be stopped will be stopped
automatically.

You've tested this in a lab environment first, right? This security
update
is the one that affects Blackberry, and other apps that require Send As
rights. Make sure that you've read up on the security bulletin.
http://www.microsoft.com/technet/security/bulletin/MS06-019.mspx


--
Ben Winzenz
Exchange MVP
MessageOne
Read my blog!
http://winzenz.blogspot.com
http://feeds.feedburner.com/winzenz (RSS Feed)


"sektor" <sektor@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:260B7CEA-50E8-49B3-A760-6CFE7EF52C2D@xxxxxxxxxxxxxxxx
Hello,

I have a question in regards to this specific patch:

http://www.microsoft.com/downloads/details.aspx?FamilyID=82AE4397-0982-4585-84C1-DC1AF6944A0F&displaylang=en

I have recently taken over our Exchange duties. While I am not a full
on
Exchange expert, I do have some knowledge in it.

My main question regarding this patch is the proper way to install the
patch.
Are there any recommended guidelines?
Anything I need to be aware of?
Any other caveats?

I was planning on doing it tonight, after hours when nobody was here.

Is there anything else I should know?
I like be thorough and cautions, especially on an area I am not very
strong
at.

Thanks





.

Relevant Pages

  • Re: Question on Security Update for Exchange 2003
    ... Just one other response to your question: " going overboard for a security ... patch, the amount of discussions that went on about this patch and definately ... The cost to setup a lab environment is not extremely high. ... So here the person posts that they have taken over Exchange duties, ...
    (microsoft.public.exchange.admin)
  • Re: Question on Security Update for Exchange 2003
    ... So here the person posts that they have taken over Exchange duties, ... if the patch will cause it to be implemented. ... You've tested this in a lab environment first, ... I have recently taken over our Exchange duties. ...
    (microsoft.public.exchange.admin)
  • Re: Is DST required for UK region?
    ... Yes, patch your OS and Exchange, but only rebaseline US mailboxes. ... the DST patches? ... if you haven't been keeping up with the MS Security ...
    (microsoft.public.exchange.admin)
  • RE: NOT CONNECTED - Entourage 2008 with Exchange 2003
    ... The only thing that I have been informed of that has changed is a Security ... Patch was applied during the week. ... Can you check and see if a similar thing happened with your Exchange server? ...
    (microsoft.public.mac.office.entourage)
  • VMSA-2006-0006 - VMware ESX Server 2.5.3 Upgrade Patch 4
    ... Patch URL: http://www.vmware.com/download/esx/esx-253-200610-patch.html ... Updated package addresses several security issues. ... Common Vulnerabilities and Exposures project assigned ... VMware Security Response Policy ...
    (Bugtraq)