Upgrading exchange but want to leave SBS 2008 server in place.

Hello TechNet
I would like to install an exchange 2013 server in my organization, currently i have a sbs 2008 server. I would like to keep the remote user functionality of sbs but upgrade the exchange. If that's not possible i am still upgrading exchange. Does anyone
have a best practice steps for moving from SBS 2008 to exchange 2013. Should i just fallow the upgrade path from exchange 2007 to exchange 2013? The server i'm installing exchange on is a AD server on the domain currently and is running Windows server 2012.
Thanks in advance for any advice or help.
Bri
RBIT@CA

We went that route as a stop gap when hardware constrained us: SBS 2008 successfully virtualised on a 2012 R2 Hyper-V host. It was not all plain sailing. Having shut down and disabled all the services on the physical SBS2008,
we used the Sysinternals disk2vhd tool to get two vhds (C: was system, E: was all the data including Exchange info stores), converted to vhdx using 2012.R2 Hyper-V manager and built a VM using these vhdxs. It booted at first but then
froze at restart after the Hyper-V host tools were automatically installed. We found a work round which involved running the MS System Update and recovery Tool (SURT) after the VM initial boot and before any subsequent VM restart. Once services
were put back to normal, the virtualised SBS 2008 ran fine.
There is some doubt as to whether this is a supported configuration, and it will not be easy to configure robust backups (see
this thread). However, our SBS2008 VM has been running for over a year in this configuration and am just now planning a move to Office 365 integrated Exchange with onsite Exchange 2013 plus virtualised 2012.R2 DC as per Larry's first reply.
Good luck which ever way you go, and tread carefully!

Similar Messages

Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003. I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
Please tell me that I can get it back. It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message. It's like the account doesn't exist any more.
Can it be recovered and if so, how?
thanks,
Jeff

Hi Jeff,
Would you please let us know current situation of this issue? Just check if above suggestions can help you.
If any update, please feel free to let us know.
In addition, please also refer to following article and thread, and then check if can help you.
How
to use a Recovery Storage Group in SBS 2008
How
to recover a deleted user and mailbox on SBS 2008
Hope this helps.
Best regards,
Justin Gu

Best/Safest way to P2V a SBS 2008 Server to sit on Hyper V

We have used Double Take when we did our P2V migrations to Hyper-V. We did it during office hours and didn't get any downtime.

After doing a lot of searching I managed to find that Microsoft have released an updated Version of MVMC (Microsoft Virtual Machine Converter 3.0). This new version now includes the ability to do a Live Physical to Virtual conversion.Previously they had removed this feature from SCVMM 2012 R2 and as a result I was going to do a Disk2VHD of the SBS 2008 server and then load that into Hyper V.But after doing more research I am thinking that doing a Live P2V on a SBS 2008 is risky as its got Exchange, SharePoint and other programs that change constantly.I am worried that even if I disconnect the server from the network and P2V it that something might change and I won't get a 100% carbon copy.As such I am thinking of taking an image of the Server using something like Acronis True Image Universal Restore boot CD and then restoring the image...
This topic first appeared in the Spiceworks Community

Outlook 2010 Will Not Connect to Exchange 2007 on SBS 2008 Server

Good Morning,
I have a user who cannot connect to the exchange server on SBS 2008 with outlook 2010. When they start outlook, it shows disconnected and will not connect for a minimum of 20 minutes to an hour. Any suggestions on how to fix this would be appreciated.
I have rebuilt their profile, but that does not fix the issue.
Thank you,
Lee F.
Lee Feldman SMB Consultant

Hi,
Thanks for posting in the forum.
Regarding the current issue, since you have recreated the user profile without any issue, I suspect that it’s mainly caused by the network issue. At this time, please first check the TCP/IP
configurations as Larry mentioned. Then, please also refer to the article below for details about how to troubleshoot Outlook connectivity issue.
Troubleshooting Microsoft Exchange: Outlook Connectivity Issues
http://blogs.technet.com/b/mspfe/archive/2011/04/12/troubleshooting_2d00_microsoft_2d00_exchange_2d00_outlook_2d00_connectivity_2d00_issues.aspx
Hope this helps.
Best Regards,
Andy Qi
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Andy Qi
TechNet Community Support

SBS 2008 - Server Infrastructure Licensing - event id 4 and 38

Hi everybody,
I have these errors in Event Viewer
The Additional Server Count Check in the Licensing component did not pass because error 0x8007200a occurred in function f1031 [WLTT]. The specified directory service attribute or value does not exist.
Make sure that your DNS server can be contacted and the following services are running: Active Directory Domain Services (NTDS), DNS Server (DNS), Kerberos Key Distribution Center (KDC). This server will be automatically shut down if the issue is not corrected
FOLLOWED BY
The Additional Server Count Check detected a condition in your environment that is out of compliance with the licensing policy. This server will be automatically shut down if the issue is not corrected in 58 day(s) 16 hour(s) 30 minute(s). Please look for additional
events for Additional Server Count Check to troubleshoot.
BEFORE these events we have 3 informational events:
Domain Controller Check passed.
Forest Trust Check passed.
FSMO Role Check passed.
We have just ONE server (the SBS 2008, not R2); we had two but the second one (Win2008 Srv) has been dismissed. No reference to the old server is found in AD, registry or other location (DNS, DHCP...). No event about the old server is recorded at all.
This server is also a DNS server; in its network properties it has itself as the DNS server (I mean: its IP, of course)
We have no problem in FMSO roles (checked with "dcdiag /test:fsmocheck") and the server is going on regularly (no issues with services, users, ...)
Any idea? I tried to solve this all by myself but with no result at all
Thanks
Cosimo
Milan, Italy

Hi Justin,
thanks for your reply. This server was a clean install, but the domain existed before (with a SBS 2003).
I have a failed test with dcdiag /e /v
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC SERVERNAME.
The forest is not ready for RODC. Will skip checking ERODC ACEs.
* Security Permissions Check for
DC=ForestDnsZones,DC=DOMAINNAME,DC=msft
(NDNC,Version 3)
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=ForestDnsZones,DC=DOMAINNAME,DC=msft
* Security Permissions Check for
DC=DomainDnsZones,DC=DOMAINNAME,DC=msft
(NDNC,Version 3)
Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
Replicating Directory Changes In Filtered Set
access rights for the naming context:
DC=DomainDnsZones,DC=DOMAINNAME,DC=msft
* Security Permissions Check for
CN=Schema,CN=Configuration,DC=DOMAINNAME,DC=msft
(Schema,Version 3)
* Security Permissions Check for
CN=Configuration,DC=DOMAINNAME,DC=msft
(Configuration,Version 3)
* Security Permissions Check for
DC=DOMAINNAME,DC=msft
(Domain,Version 3)
......................... SERVERNAME failed test NCSecDesc
And BSA shows:
The DNS client is not configured to point only to the internal IP address of the server. For information about how to fix network settings, see "Managing Your Windows Small Business Server 2008 network" at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=115881).
+
There are no DNS name server (NS) resource records with SERVERNAME.DOMAINNAME.msft for the _msdcs delegation in the forward lookup zone astra.msft.
+
The DNS CNAME resource record for Connect in the forward lookup zone for Windows SBS 2008 does not exist.
What would you suggest to me?
thanks
Cosimo

Under contract, not upgrade-eligible, but want to switch phones. How best to do it?

I am a Verizon customer who was eligible for upgrade a month ago. So, about 3 weeks ago I upgraded from the iPhone 5 to the Galaxy Note 3. I've now decided that Android isn't for me. So, what is my least expensive option to switch back to the iPhone, specifically the 5s, considering I'm outside of my return/exchange period? I know it's going to cost me, but if I consider all options (early termination, adding additional line, etc.), what's the least expensive way to do this? Thanks in advance.

I've made similar "mistakes" in "reasoning" on wireless plans before, so I feel you.
Assuming your ill-fated "upgrade" to an Android phone was done with a promotion, leaving you in a new contract period, you have to consider several things: Is there anyone you know that might want that phone? Would they be willing to pay the monthly charges required for an additional line on your account? Do you actually trust them to pay those monthly fees every month until the end of your contract? If they were to fail to be able to complete it, or if they turn out to be a crappy human being, would you be able to comfortably afford to pay the fees for the additional line of service yourself?
If the answer to all of those questions is "yes," or even if the answer to the last question is "yes," then your best bet would be to order an iPhone 5S as an additional line of service for your account. You can then activate it in place of the phone you're currently using, so that "your" phone number will be on that iPhone 5S. (To make sure that happens correctly, you'd be best off going to a VZW Store and having a rep activate it, and put a new number on the Android for you. If you screw it up, you might not be able to fix it.) Then the Android phone can be given to your buddy, coworker, mother, sister, or whomever. Or you can use it as a backup phone in case of emergencies. Whatever.
If the answer to the very last question is "no," then make sure you can find someone to buy that Android phone from you, and that you can afford to pay ALL the cancellation fees, or the full up-front cost of an iPhone 5S to activate on VZW. You do not want to get stuck paying a monthly bill you can't afford for an additional line that you don't want or need, and you don't want a wireless bill for final service, cancellation fees, and other cruft hanging around. If it goes to collections, you're guaranteed to be taking a huge hit to the credit score. Not worth it for a more comfortable mobile phone experience.
Also keep in mind that if you buy a new iPhone 5S from Verizon, at full retail cost, and activate it with Verizon in place of your current device, you're still upholding the terms of your contract so long as you maintain all monthly services required in that contract. That means that, once you activate the iPhone 5S, you can do whatever you want with the Android phone. And since VZW is currently running a buy-back promotion to let you sell them back your used phone, you could sell it back to VZW. (I did this to upgrade from my current iPhone 4S to the iPhone 5S. I'm not eligible for a discounted upgrade OR a Verizon Edge upgrade, so I had to pay the full $899 for my iPhone 5S. They're buying back my 4S for $200, though.)
Best of luck to you!

Transfering from Gmail to TB but want to leave large attachments behind.

Before I start the transfer from Gmail to TB can I setup TB to only bring over the emails and not the attachments or those under 1mb?
I don't want to delete them from Gmail now as I have to go through them 1 by 1. I need the emails now and my Gmail account is 50GB, which I'm sure would take 10-14+ days on my meager 6mbps att residential account. (I suppose I could upgrade to the fastest account for this month).

Curt,
I am not sure what to tell you to try. The one thing that I would typically recommend, may not work with Gmail, but may be worth a try.
If you try this, I would recommend that you temporially set your Advanced Preferences to never automatically check for new messages. Then Quit Mail. Next, in the Finder, open Home/Library/Mail/the POP folder for the Gmail account. At the root level of this POP folder please you will find a file named MessageUidsAlreadyDownloaded2 -- this can be deleted. With normal POP accounts, this would cause all messages still on the server to again be downloaded, when you next launch Mail and check for new mail. However, with a Gmail account, this should not happen, because Gmail keeps track of any you have ever downloaded, and does not present them for comparison to this file. This is why with Gmail, you cannot download to more than one computer, without changing preferences using the web interface. Thus, I think only those messages not yet downloaded will be presented, and if communication with this file is involved in your issue, it might be resolved. I don't have great hope of this, however.
Check something, before trying that:
Control-click over the Inbox, and choose Get Info. In the resulting dialogue, choose the Gmail account, and tell me whether these large messages can be seen. I have just tested disabling checking for new mail, sent a message to my Gmail account, and with this feature could see the message awaiting download. With any messages actually downloaded, once, this command will not show them. Let me know what you find.
Ernie

Trying to improve perfomance of a SBS 2008 Server

My customer has a 2008 Small Biz Server running on an HP Proliant ML 310. This system is somewhere between 4 and 5 years old. The problem is that we have maxed out the physical RAM at 8 GB. When I originally specced out this system, I though that would be
plenty, but time has proved me wrong.
The amount of free memory on the server is often at very close to 0. The MS Exchange store takes a huge amount of RAM. I know that it is designed to do that, but it would be nice if it would leave a little more for other processes.
When I am sitting at the server console doing any kind of work, the performance is very slow. This afternoon, I was trying to install a 2nd backup drive and test it and next thing I know the server console had completely locked down. I could not log off or
even access the task manager to kill whatever offending task was causing the problem. Client PCs could not access shared files or email. Finally, after waiting about 30 minutes, I reluctantly powered the system down. Fortunately, it came back OK.
A couple of weeks ago, I had to do a normal re-boot and it took close to an hour. About 20 minutes to shut down and 30 to come back up.
I have tried to convince the owners of this firm that a new server would be a great thing, but they simply refuse to spend the money. Is there anything I can do to improve this server's performance with its existing hardware? Maybe some services that don't
need to be running that are? I don't have that much running at startup - just McAfee antivirus and an on-line backup program.
Thanks,
Mike

It is normal for exchange to grab RAM and free RAM on a server is wasted RAM but I understand your issue, especially when you are trying to do some tasks on the server. Any chance a BIOS upgrade or something will let the server support more than 8GB
of RAM?
If not, try throttling exchange a bit (not too much):
http://www.bursky.net/index.php/2012/05/limit-exchange-2010-memory-use/ (this works for exchange 2007 but note that page size difference in the calculations)
You can also throttle the SQL databases used for Wsus, Monitoring/Health and Companyweb in the SQL manager. Best to experiment a bit depending upon how much they are used by your users and how much RAM they use (check task manager).
-- Al

Moving from Exchange 2007 to 2013 (leaving the DNS Server for it's own dedicated server)

Hello! I am quite new to Exchange and Server management in general. I will do my best to explain my situation.
I am looking to move my Exchange server off of our DNS server. When we installed them on the same server, we did not have the funds to buy 2 separate servers. I am told that it is best to separate the two. I have followed the Microsoft instructions for installing
the prerequisites for Exchange 2013 on a 2012 R2 server, and i am at the point where it wants me to configure AD LDS. As I have active directory running on the current server, I was a little hesitant to just install it without understanding what i am doing.
After the AD LDS is configured, I believe i can move forward with installing Exchange 2013 (all 3 roles will be hosted on the new server), export the mailboxes from 2007 server and import them into the new Exchange 2013 server. After 2013 is up and stable,
I plan on removing 2007 from the old server (DNS server).
What are my next steps after importing the mailboxes? Am i missing important details that I need to change or migrate?
My biggest fear is that nothing works after the installation and moving the mailboxes over. For that case, it makes sense to keep 2007 installed as a fallback for when my installation fails and all i have lost is just my time :)
Current Server:
Windows Server 2008 Standard (64 bit)
1. Roles: Active Directory, DNS, IIS
2. Software: Exchange 2007
New Server:
Windows 2012 R2 Server
1. Roles: ???
1. Software to install: Exchange 2013
Thank you for any help you can provide!

These are good resources, but i am still caught up with the active directory issue. Am I able to keep the old Domain/DNS/Active directory on it's current server and move Exchange 2007 off onto a new server (with Exchange 2013)?
In the first example, he is moving everything (domain controller, exchange, users, etc) onto a different server and decommissioning it.I've been told that it would be better practice to keep the domain and exchange on 2 different servers. Is this true?
I go to run commands like:
.\setup /PrepareAD /OrganizationName: orgname /IAcceptExchangeServerLicenseTerms
on the new exchange server, as a prerequisite and it doesnt recognize the command - even after following the steps before. Is this because the new server is not a domain controller? does it have to be? What are the best practices for setting up a server(s)
with exchange + domain controller?
Thanks for responding.

How to backup a SBS 2008 Server

This should be a simple question.
My concern the entire server including the exchange store.
There is a lot of conflicting information.
SO, if I used the backup wizard to backup the entire server, will I be able to restore the entire server including exchange.
Charles Frost

Absolutely, positively, affirmative. Assuming the external drive is compatible and there is a link here:
http://social.technet.microsoft.com/wiki/contents/articles/1780.windows-small-business-server-external-backup-drives-compatibility-list.aspx
And, for your reading pleasure, please review this link and the links contained therein:
http://social.technet.microsoft.com/wiki/contents/articles/1919.sbs-2011-v-backup-restore-and-disaster-recovery.aspx
You should have at least 2 targets and preferably 3. With 3, one is always out of the building. But regardless of how many, you should do a regular test restore of different items to a test folder on the server.
I have found the WD Passport Ultra to be very cost effective, comes with a three year warranty. Note that 2 TB is the largest supported target. And I have not had any issues with the ones labeled nesn.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Using Mac Mail with SBS 2008 + Exchange 2007

Hi,
I'm having a nightmare trying to connect my Mac Mail to our mail server. We just got a brand new SBS 2008 server put in our office, but my Mac Mail doesn't want to connect.
Every time I try, it does show the Certificate, and when I click accept it trys to connect and gives this eror:
"The Exchange Server "myserver.local" doesn't have the minimum required version installed. To use Mail with Exchange, the server must be running Update Rollup 4 for Exchange Server 2007 Service Pack 1 or later. Contact your server administrator."
Obviously the myserver bit isn't the actual server, I just don't want to tell the world our server name.
The server has the required update, it actually has Update Rollup 10 installed as of today.
Any ideas?

I think any poster who replys to their own post with something like, "Actually nevermind, I got it working." and leaves it at that despite requests for help, should be banned from ever posting on or visiting any forum on the internet for the rest of their life.
NoahG - you came here looking for answers, hoping and expecting the community to aid you, but can't be arsed to help out others once you found your own solution. You sir are a leach.

Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

I'm trying to remove Exchange 2007 from an SBS 2008 server
(Server 2008 Standard FE). My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers. We have two full blown DC's in the environment.
I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server. I can NOT seem to find a TechNet article that shows me how
to proceed in this kind of scenario. I am trying to use the TechNet article:
http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard.
When I go to Disable Mailboxes I get the following error:
Microsoft Exchange Error
Action 'Disable' could not be performed on object 'Username (edited)'.
Username (edited)
Failed
Error:
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
OK
I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010. I just want
to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
Can someone point me in the right direction?
Thanks!

Hi,
Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
On current situation, please refer to following articles and check if can help you.
Transition
from Small Business Server to Standard Windows Server
Removing SBS 2008 –
Step 1: Exchange 2007
Removing SBS 2008 – Step 2:
ADCS
Removing
SBS 2008 – Step 3: remove from domain / DCPROMO
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
does not guarantee the accuracy of this information.
Hope this helps.
Best regards,
Justin Gu

Onsite Scanner Unable To Send Documents Through Exchange 2007 Server (SBS 2008)

I have an SBS 2008 server complete with Exchange 2007 in house and have configured Exchange 2007 to use the Exchange Online Protection (EOP) to process mail for malware, etc. This setup has worked great for the last year or so with no issues.
However, all of a sudden in the last couple of weeks our onsite copier can no longer send documents through email to anyone within the organization. The copier is a Kyocera TaskAlfa 3050CI and exists with the same network. The copier can scan
to a network folder without issue.
If I change the SMTP settings to use a gmail account instead of a local account I can send mail to outside email address. Even with this changed though I still can't send to our domain addresses.
I tried running a message trace from the Exchange Management Console but it doesn't find anything for hte given subject or date/time when I scanned the document.
I am not exactly sure what I should be checking or what piece of the puzzle is causing the problem here. Any ideas on what might be happening or how to correct it?
Thanks so much!

Hi,
Any update? Would you please let us confirm some questions as Howtodo mentioned. Please feel free to let us
know.
Based on your description, it seems that only the copier can’t send documents via emails. On your SBS 2008
environment, please check if some user accounts encounter the similar issue. In other words, did users also can’t send emails attached with documents? If the email was attached with a small size document, will the same result?
In addition, can find any relevant error or events?
Hope this helps.
Best regards,
Justin Gu

Removing Exchange 2007 from SBS 2008 after Migrating to Office 365 Mid Sized with DirSync and SSO

We have recently completed off a Migration of Exchange 2007 to Office 365 Mid Sized platform.
I now need to decomission the old SBS 2008 server as they have moved to a Windows Server 2012 R2 server setup for DC, File and print and application servers.
I need to know what are the ramifications of removing the Exchange 2007 server from the SBS 2008 server and will this remove the LegacyDN details from AD and cause any issues with internal emails between users using Outlook linked through to Office365.
I understand that after removing Exchange 2007 there will be no friendly GUI to update and maintain proxyAddress, targetAddress and LegacyDN addresses, I am comfortable doing this in ADSI edit or with a script.
Will this remove the x500 addresses relating to the on premise Exchange Orgainisation and just leave behind the x500 addresses for Exchange Labs which I assume is the x500 addresses for the Azure AD intergration for Office365.

Hi ,
Thank you for posting your issue in the forum.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

SBS 2008 & Forefront Exchange 2010

Uninstalled the Forefront for Exchange that ships with SBS 2008 and installed the new Forefront 2010 for Exchange. Everything works great but I have a problem with the SBS Console alert. In Forefront Exchange 2010, the Forefront engine takes over the anti-SPAM function from Exchange and that is a good thing, but now the inherent SBS 2008 console has an error message under SECURITY for "Spam protection for E-Mail" as CRITICAL. I know what the problem is but I do not know how to disable the alert. Now that Excahnge is no longer handling anti-SPAM, the SBS server sees the function inactive and issues an alert sice it is unaware that that role is now filled by the Forefront 2010 anti-spam engine. Is there a method do disable the SBS Consoel alert on the SECURITY tab? Everything is working great with Forefront Exchange 2010 on SBS 2008 other than this little alert that is bugging me.
Thanks to anyone out there that has any insight on this...

GaryD9, on this thread:
http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/67eea70a-5ed8-49ae-ba06-6abb2673f38e
posted a detailed answer which worked for me, as far as the Console alert goes. It doesn't fix the emailed reports. I'll copy it here incase that thread becomes unavailable:
the CAUSE of the error is that the MS Exchange "content filter" is turned off in favor of the forefront content filter when forefront is installed. The SBS console is still looking at the Exchange filter status (which is now off) and is generating an
error. On my SBS 2011 server, the cause of this is a file named "E12AntiSpam.xml" in the "C:\Program Files\Windows Small Business Server\Data\SHExtensions" directory. Within that file, there is probably a line such as
$(Get-TransportAgent "Content Filter Agent").Enabled
The fix can be as simple as changing the line to:
$(Get-TransportAgent "FSE Content Filter Agent").Enabled
(just inserting "FSE " in the front of the agent name)
It should be noted that you can't edit this file unless you open it from Notepad after right clicking
on the shortcut for Notepad and selecting "Run as Administrator". Also, you won't see any changes until you close and re-open the Windows SBS Console.
I'm a little concerned that removing the FSE.XML file (as proposed on the SBS forum) may stop ALL error
reporting rather than just changing the source from the regular content filter to the Forefront version. This solution of editing the E12AntiSpam.XML file seems a safer bet.

Upgrading exchange but want to leave SBS 2008 server in place.

Similar Messages

Maybe you are looking for