|
|
|
date: Thu, 1 May 2008 00:52:29 -0700,
group: microsoft.public.exchange.misc
back
Documentation JV.
This is the firs time I use this particular forum to ask a question.
In fact, I think I have several questions.
Let me explain the situation:
As we move in our company from Exchange 2003 ï E2007 (SP1, Enterprise) I do
prepare two test servers: one with the âEdgeâ role and one with the âotherâ
roles.
In addition, we bought Forefront Security for Exchange (SP1).
I installed that product on both servers.
It is maybe good to mention that we also use Forefront Client Security to
protect our servers and workstations. Note that we use WSUS 3.0 SP1 to update
the clients.
My problem is about updating of the various components of E2007 (SP1,
Enterprise) and Forefront Security for Exchange.
The matter is that I cannot find a proper set of documentation explaining
how updates can be performed.
1) Most comprehensive part of the story is the updating of Forefront
Security for Exchange.
The (default) primary update path for it is
http://forefrontdl.microsoft.com/server/scanengineupdate
It works, no problem, but please note that I would prefer to receive the
updates via WSUS (for a future version).
2) Now the problems start.
Main reason for us to switch to E2007 (SP1, Enterprise) is the well known
spam problem we hope to fight with the âPremium spam protectionâ provided by
E2007 (SP1, Enterprise) (and that is NOT part of Forefront Security for
Exchange as far as I can see).
I the Edge Server âExchange management Consoleâ, I have one âbuttonâ that
can either âenableâ or âdisableâ âAnti-Spam Updates.
Is that âall there isâ?
Is that all that enables or disables AND updates what I see passing by in my
WSUS server like:
- Microsoft Exchange Server 2007 Enterprise Anti-spam Signatures
- Microsoft Exchange Server 2007 Enterprise Block List Updates?
How is it configurable?
Is it possible / advisable to manually add additional âblocksâ.
(Note I understand that it would be good to add an âallow listâ.
3) I understand that the spam should preferably be eliminated at the Edge
Server.
However, the Edge server is not in the domain and dies not âseeâ my WSUS
server.
How should this be configured?
Alternatively, will the Edge Server communicate after having made the âEdge
Subscriptionâ (I did not yet make the Subscription)?
As you see, main problem I face is that I cannot find a comprehensive set of
documentation bringing all points together.
Please assist,
Thanks,
--
Jan
date: Thu, 1 May 2008 00:52:29 -0700
author: Jan
Re: Documentation JV.
Responses inline.
--
Bharat Suneja
Microsoft Corporation
------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
"Jan" wrote in message
news:866B81D9-785A-4244-87D9-00B26306ABC5@microsoft.com...
> This is the firs time I use this particular forum to ask a question.
>
> In fact, I think I have several questions.
>
> Let me explain the situation:
>
> As we move in our company from Exchange 2003 ï E2007 (SP1, Enterprise) I
> do
> prepare two test servers: one with the âEdgeâ role and one with the
> âotherâ
> roles.
> In addition, we bought Forefront Security for Exchange (SP1).
> I installed that product on both servers.
> It is maybe good to mention that we also use Forefront Client Security to
> protect our servers and workstations. Note that we use WSUS 3.0 SP1 to
> update
> the clients.
>
> My problem is about updating of the various components of E2007 (SP1,
> Enterprise) and Forefront Security for Exchange.
> The matter is that I cannot find a proper set of documentation explaining
> how updates can be performed.
>
> 1) Most comprehensive part of the story is the updating of Forefront
> Security for Exchange.
> The (default) primary update path for it is
> http://forefrontdl.microsoft.com/server/scanengineupdate
> It works, no problem, but please note that I would prefer to receive the
> updates via WSUS (for a future version).
>
> 2) Now the problems start.
> Main reason for us to switch to E2007 (SP1, Enterprise) is the well known
> spam problem we hope to fight with the âPremium spam protectionâ provided
> by
> E2007 (SP1, Enterprise) (and that is NOT part of Forefront Security for
> Exchange as far as I can see).
> I the Edge Server âExchange management Consoleâ, I have one âbuttonâ that
> can either âenableâ or âdisableâ âAnti-Spam Updates.
> Is that âall there isâ?
> Is that all that enables or disables AND updates what I see passing by in
> my
> WSUS server like:
> - Microsoft Exchange Server 2007 Enterprise Anti-spam Signatures
> - Microsoft Exchange Server 2007 Enterprise Block List Updates?
> How is it configurable?
> Is it possible / advisable to manually add additional âblocksâ.
The anti-spam documentation is at:
Managing Anti-Spam and Antivirus Features
http://technet.microsoft.com/en-us/library/bb124375(EXCHG.80).aspx
Anti-Spam Updates
http://technet.microsoft.com/en-us/library/bb124241(EXCHG.80).aspx
How to Manually Update Content Filter Data by Using Microsoft Update
http://technet.microsoft.com/en-us/library/aa996810(EXCHG.80).aspx
> (Note I understand that it would be good to add an âallow listâ.
An allow list for the Content Filter?
Exchange 2007 Content FIlter: The Whitelist Is Here!
http://exchangepedia.com/blog/2007/01/exchange-2007-content-filter-whitelist.html
>
> 3) I understand that the spam should preferably be eliminated at the Edge
> Server.
> However, the Edge server is not in the domain and dies not âseeâ my WSUS
> server.
> How should this be configured?
> Alternatively, will the Edge Server communicate after having made the
> âEdge
> Subscriptionâ (I did not yet make the Subscription)?
Refer to the anti-spam update documentation above. The Edge Transport server
can get updates from Microsoft Update web site (if it has outbound
http/internet access).
>
> As you see, main problem I face is that I cannot find a comprehensive set
> of
> documentation bringing all points together.
Refer to the doc links in above repsonses.
>
> Please assist,
>
> Thanks,
> --
> Jan
date: Thu, 1 May 2008 07:26:20 -0700
author: Bharat Suneja [MSFT]
Re: Documentation JV.
Dear Bharat Suneja,
Thanks for your swift reply.
I will study the various hints you marked.
However, the simple fact that I have to search for the answer(s) on various
locations does indicate that I am correct with my statement that (regarding
malware) Exchange lacks a "comprehensive set of documentation bringing all
points together".
That is a pity because it is so important.
Jan
"Bharat Suneja [MSFT]" wrote:
> Responses inline.
>
> --
> Bharat Suneja
> Microsoft Corporation
> ------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "Jan" wrote in message
> news:866B81D9-785A-4244-87D9-00B26306ABC5@microsoft.com...
> > This is the firs time I use this particular forum to ask a question.
> >
> > In fact, I think I have several questions.
> >
> > Let me explain the situation:
> >
> > As we move in our company from Exchange 2003 ï E2007 (SP1, Enterprise) I
> > do
> > prepare two test servers: one with the âEdgeâ role and one with the
> > âotherâ
> > roles.
> > In addition, we bought Forefront Security for Exchange (SP1).
> > I installed that product on both servers.
> > It is maybe good to mention that we also use Forefront Client Security to
> > protect our servers and workstations. Note that we use WSUS 3.0 SP1 to
> > update
> > the clients.
> >
> > My problem is about updating of the various components of E2007 (SP1,
> > Enterprise) and Forefront Security for Exchange.
> > The matter is that I cannot find a proper set of documentation explaining
> > how updates can be performed.
> >
> > 1) Most comprehensive part of the story is the updating of Forefront
> > Security for Exchange.
> > The (default) primary update path for it is
> > http://forefrontdl.microsoft.com/server/scanengineupdate
> > It works, no problem, but please note that I would prefer to receive the
> > updates via WSUS (for a future version).
> >
> > 2) Now the problems start.
> > Main reason for us to switch to E2007 (SP1, Enterprise) is the well known
> > spam problem we hope to fight with the âPremium spam protectionâ provided
> > by
> > E2007 (SP1, Enterprise) (and that is NOT part of Forefront Security for
> > Exchange as far as I can see).
> > I the Edge Server âExchange management Consoleâ, I have one âbuttonâ that
> > can either âenableâ or âdisableâ âAnti-Spam Updates.
> > Is that âall there isâ?
> > Is that all that enables or disables AND updates what I see passing by in
> > my
> > WSUS server like:
> > - Microsoft Exchange Server 2007 Enterprise Anti-spam Signatures
> > - Microsoft Exchange Server 2007 Enterprise Block List Updates?
> > How is it configurable?
> > Is it possible / advisable to manually add additional âblocksâ.
>
> The anti-spam documentation is at:
> Managing Anti-Spam and Antivirus Features
> http://technet.microsoft.com/en-us/library/bb124375(EXCHG.80).aspx
>
> Anti-Spam Updates
> http://technet.microsoft.com/en-us/library/bb124241(EXCHG.80).aspx
>
> How to Manually Update Content Filter Data by Using Microsoft Update
> http://technet.microsoft.com/en-us/library/aa996810(EXCHG.80).aspx
>
> > (Note I understand that it would be good to add an âallow listâ.
>
> An allow list for the Content Filter?
> Exchange 2007 Content FIlter: The Whitelist Is Here!
> http://exchangepedia.com/blog/2007/01/exchange-2007-content-filter-whitelist.html
>
> >
> > 3) I understand that the spam should preferably be eliminated at the Edge
> > Server.
> > However, the Edge server is not in the domain and dies not âseeâ my WSUS
> > server.
> > How should this be configured?
> > Alternatively, will the Edge Server communicate after having made the
> > âEdge
> > Subscriptionâ (I did not yet make the Subscription)?
>
> Refer to the anti-spam update documentation above. The Edge Transport server
> can get updates from Microsoft Update web site (if it has outbound
> http/internet access).
>
> >
> > As you see, main problem I face is that I cannot find a comprehensive set
> > of
> > documentation bringing all points together.
>
> Refer to the doc links in above repsonses.
>
> >
> > Please assist,
> >
> > Thanks,
> > --
> > Jan
>
>
date: Sun, 4 May 2008 09:46:00 -0700
author: Jan
|
|