Preventing and not allowing are different indeed. And I'll bet that your site doesn't disable local virus scanning just because you block the POP ports.
-----Original Message----- From: Lefkovics, William [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 6:12 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch >>"Not allowing" POP access doesn't prevent the user from configuring it anyway If it doesn't, then you're preventing it wrong ;) William Lefkovics, MCSE, A+ ----------------------------------------------------------- Why just ride, when you can fly? http://www.airborne.net ----------------------------------------------------------- Rent this space: [EMAIL PROTECTED] -----Original Message----- From: Dillon, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 3:13 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch I believe we're all free to counter bad advice. And I gave several suggestions, here and offline. I seriously doubt that there is a single AV vendor who makes client- and server-end AV products who says they shouldn't be used simultaneously. "Not allowing" POP access doesn't prevent the user from configuring it anyway--it's quite easy. Please don't get upset when you make a questionable blanket statement based upon reasons you can't recall, and someone objects. -----Original Message----- From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 4:56 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch I'm not going to sit here and argue with you. I will admit that I don't always present things in a matter which explains every nit-picking detail. I do know that it was explained to me some time ago exactly why we do not enable client-based Exchange AV here and while I can't remember every single detail, I do know there were valid reasons presented that stated why we would not employ this feature. I still pose the question to you of have you spoken to your Exchange AV vendor and asked them about having both server and client side scanning simultaneously? You never answered me. I don't know why you feel a burning desire to prove your overwhelming knowledge about this subject, and try and prove that I don't know what I am talking about - don't know if you noticed, but I'm not the only one that suggested disabling antivirus on the client. Or were you too busy thinking of a retort to my comments? I did notice that disabling it had no effect. I also made some other suggestions, or didn't you notice those either? I haven't seen any suggestions come out of your mouth (or keyboard, as it were). Your comment about a need for client-based Exchange AV is relevant when dealing with non-Exchange POP3 access. I agree with that. We don't allow POP access because of this, and other security reasons. The MAPI scenario, while acknowledged to by MS, I have never seen happen in a real-life scenario. Have you? We still use MAPI-based scanning, and process a LOT of mail, and this scenario has never happened to us. Then again, if you buy cheap AV software, you may be more at risk. None of us here are too worried about it. Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems, Inc. -----Original Message----- From: Dillon, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 4:13 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch The server and client don't "fight" for the messages--the client tells the server to send a message, the server sends it (whether the server first scans it or not is irrelevant) and the client then scans it. The more CPU cycles spent scanning by the client, the less cycles are available to request the next message, reducing the server load. As you've seen from the follow-ups, disabling the local scanning has NO effect on the pegged client CPU--there is something else afoot. Your suggestion that scanning is unwanted at both the client and server level is unwise on several counts, starting with the scenario where the client has configured access to a non-Exchange POP server. And in the MAPI-scanning scenario, MS acknowledges that a server under extreme load puts higher priority on delivery than scanning, so unscanned messages can reach the client. If there's nothing scanning at the client level, you're in trouble, needlessly. -----Original Message----- From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:26 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch It doesn't reduce the overhead because the Exchange-based is trying to scan every piece of mail before it gets to the client. In the case of a synch, you are dumping massive amounts of e-mail to a local .ost file. If you have both Exchange and client AV software fighting to get to the same e-mails, guaranteed the Exchange side is going to win, at the expense of the client. It could also depend on the type of AV that is on the server, i.e. is it MAPI-based scanning, or AVAPI. I still don't think I would recommend running Exchange AV on both the server and client, if nothing else, than for the potential to cause problems. Call your Exchange AV vendor and see what they say. You may just be getting lucky. Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems, Inc. -----Original Message----- From: Dillon, Jeff [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:18 PM To: MS-Exchange Admin Issues Cc: '[EMAIL PROTECTED]' Subject: FW: 100% CPU when Synch I'm not sure I buy this analysis...if a LOCAL virus-scanning utility is scanning email hosted on an Exchange system that also has virus software active, the ability of the client machine to request the next item for synchronization is REDUCED by the local overhead of scanning the item. If anything, the local scanning REDUCES the load on the Exchange server by limiting the rate at which the clients can task the server. We run local and server-based Exchange anti-virus software simultaneously, and have seen none of the problems mentioned. I suggest the problem lies elsewhere, and the original comment that "...a FEW of these (clients) are pegging the CPU" is your clue. -----Original Message----- From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 1:03 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch If you have AV on your Exchange server as well, turn that option off on the clients. Think of it this way. Your Exchange AV program and your desktop AV (NAV-CE) are basically fighting to see who gets to scan the e-mail. Whoever gets to it first locks it and the other one can't get to it. Normally, the Exchange AV program will win. Hence, you have problems on your desktops. Turn it off on the client side, and I bet your problems will go away. It's understandable to want to have it running - heck, our Security team wanted us to turn it on, until we explained to them the hurt it could cause. Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems, Inc. -----Original Message----- From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 12:55 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch Yes, with the Outloook\exchange option... -----Original Message----- From: Benjamin Winzenz [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 11:55 AM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch With the Exchange/Outlook add-on or no? Ben Winzenz, MCSE Network/Systems Administrator Peregrine Systems, Inc. -----Original Message----- From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 12:50 PM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch could be.. we are using NAV CE on all the clients... -----Original Message----- X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Lefkovics, William [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 11:48 AM To: MS-Exchange Admin Issues Subject: RE: 100% CPU when Synch Aunty Virus? William Lefkovics, MCSE, A+ ----------------------------------------------------------- Why just ride, when you can fly? http://www.airborne.net ----------------------------------------------------------- Rent this space: [EMAIL PROTECTED] -----Original Message----- From: MHR(Michael Ross) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 19, 2001 9:46 AM To: MS-Exchange Admin Issues Subject: 100% CPU when Synch I have alot Outlook 2000 SP2 clients connecting to an Exchange 5.5 server. A few of these pc's are pegging the CPU at 100% when you force a synchronization with the ost file. This also happens whenever the client itself syncs up with the OST file.. anyone have any ideas? Michael Ross Network Analyst 2 Panduit Corp. [EMAIL PROTECTED] If at first you don't succeed, Skydiving isn't for you. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm