[Exchange] RE: Kaspersky vs McAfee vs Symantec
One mild suggestion is that you split that thought process in two pieces, if not three. Treat the endpoint PC/Server protection as a separate thing than the email server parts, perhaps. Exchange malware/spam protection can be handled a billion ways, I personally have a preference for 'prefilters' (such as Symantec cloud, formerly messagelabs) where the MX records inbound (and smarthosts outbound) go through the cloud and never eat mine or my clients' bandwidth. (I carry a few thousand seats on Symantec for a large swath of corporate/business clients). The processing happens outside, I have nearly zero SPAM issues nor do I really ever see email-borne malware make it through (no cryptolocker payloads, no bad PDFs hiding in zip files, etc). There are other cloud filtering services worthy of similar praise (appriver, many others). Can't speak to the costs, but the real business costs of *not* doing something like that is always a much higher number. Appliance-based solutions also good (barracuda, sonicwall) for email. On-server stuff also good, I just prefer running it off server or pre-filter ... GFI mailessentials is good, there are a billion others that are also good. For endpoint, that's a bigger discussion, I tend to loathe McAfee, Symantec and Trend for endpoint (personal bias) and generally use a combination of two things at any given site ... typically an edge appliance that has a malware filter subscription as well as software on endpoints. For small businesses, a typical deployment for us would be a Sonicwall TZ or NSA with their gateway antimalware/filtering services, which helps block nasty stuff including oftentimes the proclivity of users to click on something stupid. Then we add on something else like NOD or Kaspersky or VIPRE, sometimes in conjunction with Malwarebytes paid products. Usually it's ThreatTrack VIPRE (ex GFI) but nothing is perfect, and again why we like to hedge with a few layers (filter email, filter at firewall, filter more on client). From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Liby Philip Mathew Sent: Monday, June 9, 2014 9:17 AM To: Admin Issues (exchange@lists.myitforum.com) Subject: [Exchange] Kaspersky vs McAfee vs Symantec Hi guys, I have been told to identify the pros cons of Kaspersky vs McAfee vs Symantec including the cost. I am looking to protect end user PC, Server, centralized management MS Exchange 2010 / 2013 AV/spam/phish/spoof etc. What are your experiences / suggestions? TIA Regards Liby Philip Mathew Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] P Protect our planet: Do not print this email unless necessary.
[Exchange] RE: Kaspersky vs McAfee vs Symantec
Second that... our mail server also sits behind a dedicated AV, spam, filtering SMTP appliance. For our end points we have several tiers. Primarily all systems protected with Malwarebytes Enterprise. Mobiles also have built-in AV turned on with our VPN endpoint client that also does web and application filtering. All systems have MS Firewall on by default/GPO as well as the built-in AV. Our file servers are covered by Malwarebytes and the McAfee AV engine and every device is WSUS updated regularly and end-users are tested and educated every quarter. Troy From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rick Berry Sent: Monday, June 9, 2014 7:37 AM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Kaspersky vs McAfee vs Symantec One mild suggestion is that you split that thought process in two pieces, if not three. Treat the endpoint PC/Server protection as a separate thing than the email server parts, perhaps. Exchange malware/spam protection can be handled a billion ways, I personally have a preference for 'prefilters' (such as Symantec cloud, formerly messagelabs) where the MX records inbound (and smarthosts outbound) go through the cloud and never eat mine or my clients' bandwidth. (I carry a few thousand seats on Symantec for a large swath of corporate/business clients). The processing happens outside, I have nearly zero SPAM issues nor do I really ever see email-borne malware make it through (no cryptolocker payloads, no bad PDFs hiding in zip files, etc). There are other cloud filtering services worthy of similar praise (appriver, many others). Can't speak to the costs, but the real business costs of *not* doing something like that is always a much higher number. Appliance-based solutions also good (barracuda, sonicwall) for email. On-server stuff also good, I just prefer running it off server or pre-filter ... GFI mailessentials is good, there are a billion others that are also good. For endpoint, that's a bigger discussion, I tend to loathe McAfee, Symantec and Trend for endpoint (personal bias) and generally use a combination of two things at any given site ... typically an edge appliance that has a malware filter subscription as well as software on endpoints. For small businesses, a typical deployment for us would be a Sonicwall TZ or NSA with their gateway antimalware/filtering services, which helps block nasty stuff including oftentimes the proclivity of users to click on something stupid. Then we add on something else like NOD or Kaspersky or VIPRE, sometimes in conjunction with Malwarebytes paid products. Usually it's ThreatTrack VIPRE (ex GFI) but nothing is perfect, and again why we like to hedge with a few layers (filter email, filter at firewall, filter more on client). From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Liby Philip Mathew Sent: Monday, June 9, 2014 9:17 AM To: Admin Issues (exchange@lists.myitforum.commailto:exchange@lists.myitforum.com) Subject: [Exchange] Kaspersky vs McAfee vs Symantec Hi guys, I have been told to identify the pros cons of Kaspersky vs McAfee vs Symantec including the cost. I am looking to protect end user PC, Server, centralized management MS Exchange 2010 / 2013 AV/spam/phish/spoof etc. What are your experiences / suggestions? TIA Regards Liby Philip Mathew Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] P Protect our planet: Do not print this email unless necessary. *** This message may contain confidential and proprietary RMH Group information and is intended only for the sole use of the recipient(s). If you are not the named recipient you should not read, distribute or copy this e-mail. Please notify the sender and destroy this e-mail and any attachments and all copies. ***
[Exchange] RE: Kaspersky vs McAfee vs Symantec
Barracuda in front of Exchange for email. Strong, well run filter for the internet. Fully patched pc's with EMET and no AV. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Liby Philip Mathew Sent: Monday, June 9, 2014 9:16 AM To: Admin Issues (exchange@lists.myitforum.com) Subject: [Exchange] Kaspersky vs McAfee vs Symantec Hi guys, I have been told to identify the pros cons of Kaspersky vs McAfee vs Symantec including the cost. I am looking to protect end user PC, Server, centralized management MS Exchange 2010 / 2013 AV/spam/phish/spoof etc. What are your experiences / suggestions? TIA Regards Liby Philip Mathew Disclaimer [The information contained in this e-mail message and any attached files are confidential information and intended solely for the use of the individual or entity to whom they are addressed. This transmission may contain information that is privileged, confidential or exempt from disclosure under applicable law. If you have received this e-mail in error, please notify the sender immediately and delete all copies. If you are not the intended recipient, any disclosure, copying, distribution, or use of the information contained herein is STRICTLY PROHIBITED. Path Solutions accepts no responsibility for any errors, omissions, computer viruses and other defects.] P Protect our planet: Do not print this email unless necessary.
[Exchange] Rejoin Exchange to New Domain?
I was instructed to build out an Exchange server on a domain provided to me. Performed the initial install (along with SCCM), but then it was discovered the internal domain and the registered web domain are different. Because of SSL certificate implications and some other non-Exchange domain impacts, they are going to build a new DC with the proper registered domain. I was told to just join the Exchange server to the new domain. Is that advisable...or even possible? I was clear I thought the best course would be to rebuild the servers (AD/Exchange/SCCM) to ensure no weirdness, but they pushed back suggesting a simple disjoin/rejoin step. With all the AD hooks (groups/containers) that are created by Exchange...will that happen during a simple joining of the domain? I was pretty confident until the other parties stated this is how we should do it. Sanity check, please? Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
[Exchange] RE: Rejoin Exchange to New Domain?
For clarity, the Exchange server is dedicated to Exchange and the SCCM server is dedicated to SCCM. Didn't mean for that to look like they were living on the same box. Thanks, Geoff From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 09, 2014 2:29 PM To: exchange@lists.myitforum.com Subject: [Exchange] Rejoin Exchange to New Domain? I was instructed to build out an Exchange server on a domain provided to me. Performed the initial install (along with SCCM), but then it was discovered the internal domain and the registered web domain are different. Because of SSL certificate implications and some other non-Exchange domain impacts, they are going to build a new DC with the proper registered domain. I was told to just join the Exchange server to the new domain. Is that advisable...or even possible? I was clear I thought the best course would be to rebuild the servers (AD/Exchange/SCCM) to ensure no weirdness, but they pushed back suggesting a simple disjoin/rejoin step. With all the AD hooks (groups/containers) that are created by Exchange...will that happen during a simple joining of the domain? I was pretty confident until the other parties stated this is how we should do it. Sanity check, please? Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
[Exchange] RE: Rejoin Exchange to New Domain?
THANK YOU! (Not yelling, just emphatic because it means I'm not crazy) From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Monday, June 09, 2014 2:42 PM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Rejoin Exchange to New Domain? Exchange will not work in that scenario. Period. Nor will SCCM. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 9, 2014 5:33 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Rejoin Exchange to New Domain? For clarity, the Exchange server is dedicated to Exchange and the SCCM server is dedicated to SCCM. Didn't mean for that to look like they were living on the same box. Thanks, Geoff From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 09, 2014 2:29 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] Rejoin Exchange to New Domain? I was instructed to build out an Exchange server on a domain provided to me. Performed the initial install (along with SCCM), but then it was discovered the internal domain and the registered web domain are different. Because of SSL certificate implications and some other non-Exchange domain impacts, they are going to build a new DC with the proper registered domain. I was told to just join the Exchange server to the new domain. Is that advisable...or even possible? I was clear I thought the best course would be to rebuild the servers (AD/Exchange/SCCM) to ensure no weirdness, but they pushed back suggesting a simple disjoin/rejoin step. With all the AD hooks (groups/containers) that are created by Exchange...will that happen during a simple joining of the domain? I was pretty confident until the other parties stated this is how we should do it. Sanity check, please? Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
[Exchange] RE: Rejoin Exchange to New Domain?
If you need documentation, search for rename exchange server. You'll find that it is only supported in Exchange 2003. And the scenarios are VERY limited. You can also search for rename configuration manager server. You'll find that it was NEVER supported. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 9, 2014 5:45 PM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Rejoin Exchange to New Domain? THANK YOU! (Not yelling, just emphatic because it means I'm not crazy) From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Monday, June 09, 2014 2:42 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Rejoin Exchange to New Domain? Exchange will not work in that scenario. Period. Nor will SCCM. From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 9, 2014 5:33 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Rejoin Exchange to New Domain? For clarity, the Exchange server is dedicated to Exchange and the SCCM server is dedicated to SCCM. Didn't mean for that to look like they were living on the same box. Thanks, Geoff From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Orlebeck, Geoffrey Sent: Monday, June 09, 2014 2:29 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] Rejoin Exchange to New Domain? I was instructed to build out an Exchange server on a domain provided to me. Performed the initial install (along with SCCM), but then it was discovered the internal domain and the registered web domain are different. Because of SSL certificate implications and some other non-Exchange domain impacts, they are going to build a new DC with the proper registered domain. I was told to just join the Exchange server to the new domain. Is that advisable...or even possible? I was clear I thought the best course would be to rebuild the servers (AD/Exchange/SCCM) to ensure no weirdness, but they pushed back suggesting a simple disjoin/rejoin step. With all the AD hooks (groups/containers) that are created by Exchange...will that happen during a simple joining of the domain? I was pretty confident until the other parties stated this is how we should do it. Sanity check, please? Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
[Exchange] RE: Public Folders in Exchange 2013?
I finally managed to decommission one of my Exchange 2007 servers: it did not go through smoothly because of the infamous Public Folders issue. I ended up using ADSIEdit to remove the PF entry for that server, and only then I was able to uninstall the product. Now, I have the last Exchange 2007 server to decommission. I can now follow the same process and use ADSIEdit to uninstall that, but I am worried about the Outlook 2010 clients that still show a connection to that Exchange 2007 server for Public Folders when I do CTRL+Click and select Connection Status. So, more specifically, I wonder what happens to Outlook 2010 clients connecting to that old server for PFs when I uninstall the server. Is there anything I need to do for preventing Outlook clients from looking up for PF server? The other day, I just shutdown Exchange 2007 server to see what would happen, and all Outlook 2010 clients got connection errors and stop working until I brought that server backup again. Basically, I do not want to keep PFs anymore on my Exchange 2013 servers. Rami From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller Bonnie L. Sent: Friday, June 06, 2014 10:24 AM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? We finally migrated the last of our PFs when going from 2007 to 2013. You don't want to just drop or block them-if they really aren't in use and you don't want to migrate, then there is a procedure for removing them you'll want to follow through with. We did have trouble with the very last step and had to open a Premier case with Microsoft to remove via adsiedit-from what I was seeing online, it's a problem quite a few people have run into. If you haven't already, give this a read: http://technet.microsoft.com/en-us/library/cc164367(v=exchg.80).aspx I don't have any experience with migrating them to 2013, so can't speak to that. -Bonnie From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Friday, June 06, 2014 9:34 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] Public Folders in Exchange 2013? Hi All, I would like to get some feedback about dropping Public Folders (PFs) as part of a migration from Exchange 2007 to 2013. Although we are not using PFs on Exchange 2007, Outlook 2010s are still pointing to 2007 server. So, there are two options: (1) migrate the PFs and let Outlook point to 2013 servers so that I can take 2007 ones offline, (2) Disable/prevent Outlook 2010 from using PFs say through GPO if this is ever possible, and then just drop 2007 servers without enabling any PFs on 2013 servers. Any idea appreciated. Rami If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
[Exchange] RE: Public Folders in Exchange 2013?
Have you removed all PF databases from all your mailbox databases? From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Monday, June 9, 2014 6:57 PM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? I finally managed to decommission one of my Exchange 2007 servers: it did not go through smoothly because of the infamous Public Folders issue. I ended up using ADSIEdit to remove the PF entry for that server, and only then I was able to uninstall the product. Now, I have the last Exchange 2007 server to decommission. I can now follow the same process and use ADSIEdit to uninstall that, but I am worried about the Outlook 2010 clients that still show a connection to that Exchange 2007 server for Public Folders when I do CTRL+Click and select Connection Status. So, more specifically, I wonder what happens to Outlook 2010 clients connecting to that old server for PFs when I uninstall the server. Is there anything I need to do for preventing Outlook clients from looking up for PF server? The other day, I just shutdown Exchange 2007 server to see what would happen, and all Outlook 2010 clients got connection errors and stop working until I brought that server backup again. Basically, I do not want to keep PFs anymore on my Exchange 2013 servers. Rami From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller Bonnie L. Sent: Friday, June 06, 2014 10:24 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? We finally migrated the last of our PFs when going from 2007 to 2013. You don't want to just drop or block them-if they really aren't in use and you don't want to migrate, then there is a procedure for removing them you'll want to follow through with. We did have trouble with the very last step and had to open a Premier case with Microsoft to remove via adsiedit-from what I was seeing online, it's a problem quite a few people have run into. If you haven't already, give this a read: http://technet.microsoft.com/en-us/library/cc164367(v=exchg.80).aspx I don't have any experience with migrating them to 2013, so can't speak to that. -Bonnie From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Friday, June 06, 2014 9:34 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] Public Folders in Exchange 2013? Hi All, I would like to get some feedback about dropping Public Folders (PFs) as part of a migration from Exchange 2007 to 2013. Although we are not using PFs on Exchange 2007, Outlook 2010s are still pointing to 2007 server. So, there are two options: (1) migrate the PFs and let Outlook point to 2013 servers so that I can take 2007 ones offline, (2) Disable/prevent Outlook 2010 from using PFs say through GPO if this is ever possible, and then just drop 2007 servers without enabling any PFs on 2013 servers. Any idea appreciated. Rami If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
[Exchange] RE: Public Folders in Exchange 2013?
Not yet since I am not sure if I should do this or do something with outlook clients first! Rami From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Monday, June 09, 2014 4:13 PM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? Have you removed all PF databases from all your mailbox databases? From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Monday, June 9, 2014 6:57 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? I finally managed to decommission one of my Exchange 2007 servers: it did not go through smoothly because of the infamous Public Folders issue. I ended up using ADSIEdit to remove the PF entry for that server, and only then I was able to uninstall the product. Now, I have the last Exchange 2007 server to decommission. I can now follow the same process and use ADSIEdit to uninstall that, but I am worried about the Outlook 2010 clients that still show a connection to that Exchange 2007 server for Public Folders when I do CTRL+Click and select Connection Status. So, more specifically, I wonder what happens to Outlook 2010 clients connecting to that old server for PFs when I uninstall the server. Is there anything I need to do for preventing Outlook clients from looking up for PF server? The other day, I just shutdown Exchange 2007 server to see what would happen, and all Outlook 2010 clients got connection errors and stop working until I brought that server backup again. Basically, I do not want to keep PFs anymore on my Exchange 2013 servers. Rami From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller Bonnie L. Sent: Friday, June 06, 2014 10:24 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? We finally migrated the last of our PFs when going from 2007 to 2013. You don't want to just drop or block them-if they really aren't in use and you don't want to migrate, then there is a procedure for removing them you'll want to follow through with. We did have trouble with the very last step and had to open a Premier case with Microsoft to remove via adsiedit-from what I was seeing online, it's a problem quite a few people have run into. If you haven't already, give this a read: http://technet.microsoft.com/en-us/library/cc164367(v=exchg.80).aspx I don't have any experience with migrating them to 2013, so can't speak to that. -Bonnie From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Friday, June 06, 2014 9:34 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] Public Folders in Exchange 2013? Hi All, I would like to get some feedback about dropping Public Folders (PFs) as part of a migration from Exchange 2007 to 2013. Although we are not using PFs on Exchange 2007, Outlook 2010s are still pointing to 2007 server. So, there are two options: (1) migrate the PFs and let Outlook point to 2013 servers so that I can take 2007 ones offline, (2) Disable/prevent Outlook 2010 from using PFs say through GPO if this is ever possible, and then just drop 2007 servers without enabling any PFs on 2013 servers. Any idea appreciated. Rami If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
[Exchange] RE: Public Folders in Exchange 2013?
As long as your mailbox database require PF databases, you will get this error. From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Monday, June 9, 2014 7:18 PM To: exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? Not yet since I am not sure if I should do this or do something with outlook clients first! Rami From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Michael B. Smith Sent: Monday, June 09, 2014 4:13 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? Have you removed all PF databases from all your mailbox databases? From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Monday, June 9, 2014 6:57 PM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? I finally managed to decommission one of my Exchange 2007 servers: it did not go through smoothly because of the infamous Public Folders issue. I ended up using ADSIEdit to remove the PF entry for that server, and only then I was able to uninstall the product. Now, I have the last Exchange 2007 server to decommission. I can now follow the same process and use ADSIEdit to uninstall that, but I am worried about the Outlook 2010 clients that still show a connection to that Exchange 2007 server for Public Folders when I do CTRL+Click and select Connection Status. So, more specifically, I wonder what happens to Outlook 2010 clients connecting to that old server for PFs when I uninstall the server. Is there anything I need to do for preventing Outlook clients from looking up for PF server? The other day, I just shutdown Exchange 2007 server to see what would happen, and all Outlook 2010 clients got connection errors and stop working until I brought that server backup again. Basically, I do not want to keep PFs anymore on my Exchange 2013 servers. Rami From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Miller Bonnie L. Sent: Friday, June 06, 2014 10:24 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] RE: Public Folders in Exchange 2013? We finally migrated the last of our PFs when going from 2007 to 2013. You don't want to just drop or block them-if they really aren't in use and you don't want to migrate, then there is a procedure for removing them you'll want to follow through with. We did have trouble with the very last step and had to open a Premier case with Microsoft to remove via adsiedit-from what I was seeing online, it's a problem quite a few people have run into. If you haven't already, give this a read: http://technet.microsoft.com/en-us/library/cc164367(v=exchg.80).aspx I don't have any experience with migrating them to 2013, so can't speak to that. -Bonnie From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On Behalf Of Rami SIK Sent: Friday, June 06, 2014 9:34 AM To: exchange@lists.myitforum.commailto:exchange@lists.myitforum.com Subject: [Exchange] Public Folders in Exchange 2013? Hi All, I would like to get some feedback about dropping Public Folders (PFs) as part of a migration from Exchange 2007 to 2013. Although we are not using PFs on Exchange 2007, Outlook 2010s are still pointing to 2007 server. So, there are two options: (1) migrate the PFs and let Outlook point to 2013 servers so that I can take 2007 ones offline, (2) Disable/prevent Outlook 2010 from using PFs say through GPO if this is ever possible, and then just drop 2007 servers without enabling any PFs on 2013 servers. Any idea appreciated. Rami If this message is not meant for you, do not use it - please let us know, and then delete it. We try hard to keep our messages and attachments free of viruses and other malicious programs, but are not liable if our precautions don't prevent their spread.
