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.

Similar Messages

Migrate SBS 2008 with exchange 2007 to office365

Hi, we have a sbs 2008 with exchange 2007 the boss got the idea to move the E-mail to office 365, i have done some research but still have some questions, now i am not an expert on exchange, could some one tell me if this is a straight operation going from
exchange 2007 to office 365, is it supported or do we have to move to exchange 2010 and then to office 365?
Thank you very much in advanced.

Yes, going from Exchange 2007 to Office 365 is supported. You want to run a Migration.
Check out this link for exact instructions on what to do for the migration:
http://help.outlook.com/en-US/140/ms.exch.ecp.emailmigrationwizardexchangelearnmore.aspx
Then, when you are ready to setup Outlook with Office 365, check out this link to make Outlook use the public Autodiscover rather than SBS Autodiscover:
http://www.mcbsys.com/techblog/2011/08/using-office-365-in-an-sbs-2008-environment-take-2/
I just did a cutover migration from SBS 2008 to Office 365 using both these websites and it went off very nicely.
Good luck on your migration.
Oh, and if you only use Office 365 for email, it is $4 a month per user.

SBS 2008 to Exchange 2013 - "Create legacy Exchange host name"... Single External IP?

Migrating a customer to Exchange 2013 from SBS 2008.
Once of the Pre-reqs is to setup an external A record for legacy.customer.com for the external IP address of the old Exchange server.
The customer only has a single external IP address...
So what do I do for this external DNS of legacy.customer.com?

Hi Allister -
You shouldn't need an EXTERNAL dns entry for legacy. Here's how it works:
Client from outside -> External IP to Exchange 2013 (now here's where the interesting thing happens)
Exchange auto-magically proxies mailboxes on the old environment. Reason being: New Exchange Servers always know how to get to old servers. You just change all the internal URLs to legacy. (or you can even do oldmail., whatever you like) and since this information
is inside AD, Ex2013 will find it.
These are the URLs you need to change in 2007/2010
ClientAccessServer
webservicesvirtualdirectory
oabvirtualdirectory
owavirtualdirectory
ecpvirtualdirectory
ActiveSyncVirtualDirectory
AutodiscoverVirtualDirectory You can read more on how to set these here:
http://social.technet.microsoft.com/wiki/contents/articles/5163.managing-exchange-2010-externalinternal-url-s-via-powershell.aspx
Here's the Million dollar question though: being SBS 2008, does this have exchange 2007 or 2010 on it? If it's 2010, you don't need the legacy namespace anymore. 2007, you do. Connect to https://ex2013server/owa and log into a mailbox on the 2010 environment.
If you can get there (you'll know cause it flipped over to a 2010 interface) then it's working.
A wise man is a fool, with a good memory.

Windows 2008 R2 - Exchange 2010 Mailbox Role Install Failed

Hi,
I have been trying to install Exchange 2010 on my Win Server 2008 R2.
I have an error when i try to install mailbox role :
The following error was generated when "$error.Clear(); $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName; $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
$dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1; if( $dismbx -ne $null) { $srvname = $dismbx.ServerName; if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" ) { Write-ExchangeSetupLog -info "Setup
DiscoverySearchMailbox Permission."; $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -eq $null ) { Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
mount-database $dismbx.Database; } $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true }; if( $mountedMdb -ne $null ) { $dmRoleGroupName = "Discovery Management"; $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupName
-DomainController $RoleDomainController -ErrorAction:SilentlyContinue; if( $dmRoleGroup -ne $null ) { Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
} } } }" was run: "Couldn't mount the database that you specified. Specified database: Mailbox Database 1527275860; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred
during discovery of the database availability group topology. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005,
ec=-1011)
[Database: Mailbox Database 1527275860, Server: serveur.domain.fr].".
Couldn't mount the database that you specified. Specified database: Mailbox Database 1527275860; Error code: An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database
availability group topology. Error: Database action failed with transient error. Error: A transient error occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
[Database: Mailbox Database 1527275860, Server: serveur.domain.fr].
An Active Manager operation failed with a transient error. Please retry the operation. Error: A transient error occurred during discovery of the database availability group topology. Error: Database action failed with transient error. Error: A transient error
occurred during a database operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
[Database: Mailbox Database 1527275860, Server: serveur.domain.fr]
An Active Manager operation failed with a transient error. Please retry the operation. Error: MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
[Server: serveur.domain.fr]
MapiExceptionJetErrorOutOfMemory: Unable to mount database. (hr=0x80004005, ec=-1011)
/prepareschema ->OK
/preparead ->OK
/preparedomain -> OK
The Account rights seems good : Domain Admins - Enterprise Admins - Schema Admins
I tried to use another installation media but no change.
I tried this : http://support.microsoft.com/kb/978776/fr
but at step 2 i have the sameerror again.
Can you help me Please :-)
tkx

Hi,
Thanks for your sharing. It's great to hear the good news.
Best regards,
Amy
Amy Wang
TechNet Community Support

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

SBS 2008 and Exchange 2007 intermittent Email Issues

Hello
I am having an issue with my SBS 2008 Server and Exchange 2007. After setup, the mail seems to work great for about a week, then the mail just quits working. To get it working again, all I have to do is reboot the server and mail starts working
again. When looking in the event logs, all I come across is transport.exe errors. Any ideas on why it works for 5-10 days, then just quits working? Any help or insight would be much appreciated.
Thanks All

Larry
Here are some of the errors that i am getting:
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\NETWORK SERVICE; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: edgetransport.exe
Client ProcessId: 0
Client ApplicationId: Client=Transport
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account NT AUTHORITY\SYSTEM; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SERVERNAME/cn=Microsoft System
Attendant.
Error: -1069
Client Machine: SERVERNAME
Client Process: Microsoft.Exchange.ServiceHost.exe
Client ProcessId: 0
Client ApplicationId: Microsoft System Attendant Service Let
(Event ID 1022) (Source MSExchangeIS Mailbox Store)
Logon Failure on database "First Storage Group\Mailbox Database" - Windows account WIS\JLange; mailbox /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Josh.Lange.
Error: -1069
Client Machine: SERVERNAME
Client Process: w3wp.exe
Client ProcessId: 0
Client ApplicationId: Client=ActiveSync;UserAgent=Apple-iPhone5C1/1002.329;Action=User=jlange&DeviceId=ApplF18KM7FHFH1C&DeviceType=iPhone&Cmd=Sync
These are a few errors that i get when the mail isn't working. When it stops of the server, the outlook clients show the exchange server disconnected, and active sync will not work either. I can still remote to the server, so i dont think its
an internet connectivity issue. Let me know if you have any other questions. Again, the mail seems to work for about 5-7 days, then i have to reboot the server to get the mail flowing again. Any help or direction would be appreciated.
Thanks for Looking

ESE 2007 on SBS 2008 following Exchange VSS error 9782 for each storage group

I have seen the following ongoing at customer site and have not had any luck resolving as yet. I need assistance troubleshooting this. This is SBS 2008.
Log: Application
Type: Error
Event: 2007
Agent Time: 2012-03-11 00:45:24Z
Event Time: 05:43:34 AM 03-Mar-2012 UTC
Source: ESE
Category: ShadowCopy
Username: N/A
Computer: server.organization.local
Description: Information Store (2936) Shadow copy instance 23 aborted.

and...
System
Provider
[ Name]
MSExchangeIS
EventID
9782
[ Qualifiers]
49193
Level
2
Task
41
Keywords
0x80000000000000
TimeCreated
[ SystemTime]
2012-03-11T05:34:57.000Z
EventRecordID
616963
Channel
Application
Computer
Server.organization.local
Security
EventData
548103f5-8c4f-4bd8-ae6e-42dd634e4bcd:17
First Storage Group
46756C6C00
Binary data:
In Words
0000: 6C6C7546 00
In Bytes
0000: 46 75 6C 6C 00 Full.

SBS 2011 STANDARD Exchange 2010 Migration to Office 365

done

Hi
If you manually setup an outlook profile and enter in all the settings does it work?
In you local DNS you still have an autodiscover record for your local exchange server? Correct?
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Anyone done SBS 2008 to Exchange 2013 migration - disable IPv6 on SBS?

IPv6 enabled on ours without any problems. THanks for the links Anil, had not heard of those problems before

Well, considering over the scenario you have mentioned, I would like to refer you on this informative article that covers few parts of causes when disabling IPV6 on Exchange 2013 Server installation : http://mike-graham.co.uk/blog/2013/08/12/disabling-ipv6-on-exchange-2013-servers-causes-problems/Here is a well documented technet resource that also provides step-wise instructions when proceeding to migrate from Exchange 2007 to 2013 by checking all the required prerequisites : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migra...Moreover, while need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on LepideMigrator for Exchange tool that provides a hassle-free environment to get this job done without having downtime or any further interruption.

Revoked Certificate on Outlook 2010/Exchange 2007/SBS 2008

Hi All,
I have an issue that has been frustrating me for quite some time now.
Our setup is SBS 2008 with Exchange 2007. 2 Weeks ago we had to renew our certificate for remote.xxxxxxx.com. This was done through the SBS consoles > Network > Fix my Network and followed the wizard. and this worked fine.
I have however got one user who has a problem and he informs me that this is been an issue since before the cert was renewed.
He is a remote laptop user who visits the office maybe 5 times a month. When launching Outlook 2010 on his machine (Win 7 x64) it comes up with the error: Security Alert, Information you exchange with this site cannot be viewed or changed by others. However,
there is a problem with the Site's security certificate. (Red X) The security certificate for this site has been revoked. This site should not be trusted. Then OK and View Certificate buttons.
I have tried to use the View Certificate to install the certificate to the correct store but no luck. Also tried exporting the cert from the server and installing manually into Trusted Root CA, via MMC Certificates Snap-In and no luck.
I'd like to mention that If i log into a different user, on the same domain, on the same laptop, the issue is gone. So it's local to his profile on the laptop.
Plus, he cannot access the OWA on his laptop either, but again a different user - same laptop can. I have verified that the OWA is still working from another machine in the business, that is using the same certificate. I cannot understand why the
subject machine thinks the certificate has been revoked when I don't believe it has.
Can anybody please shed some light on this situation for me - any avenues to explore would be hugely appreciated.
Many thanks
Nicky

I hope this helps
http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/managing-exchange-certificates-part2.html
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

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

Forefront for exchange 2010 - how long?

Hi there.
Read this article: http://blogs.technet.com/b/server-cloud/archive/2012/09/12/important-changes-to-forefront-product-roadmaps.aspx
I would have additional question.
Our company is MS Gold Partner and we need to renew our yearly license every year around AUGUST.
We are thinking about changing our SPAM filter external gateway with exchange edge, but as we can see from that article, you Will be unable to renew it license after December 2015.
I know that Microsoft offers online Forefront protection but that is not option in our case because of data sensitivity.We need an answer how long we Will be able to get updates regarding forefront for exchange 2010 and be licensed ok?
I guess after 2015 december Forefront Exchange 2010 Will no longer recieve spam updates thru Windows update, right?
And also engines Will not be updated after that date?
Is this the correct view and understanding?
with best regards
bostjanc

Hi Bostjanc,
>>how long we Will be able to get updates regarding forefront for exchange 2010 and be licensed ok?
I think you must have seen the information below in that blog.
For current customers, Microsoft will continue to support the subscription through Dec.31, 2015. If customer subcriptions expire before Dec.31, 2015, and annot be renewed because the product is no longer offered, these products will continue to be supported
through that date in order to provided with customers sufficient time to move to alternative solutions.
You could also check the following blog.
License extension for End-of-Life Antigen/Forefront products
Note: Microsoft provides third-party contact information
to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
If the information above still cannot resolve your questions, please contact Microsoft to get definitive answers.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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!

Install problem Exchange SP3 on SBS 2008

I'm unable to install Exchange SP3 on SBS 2008 running Exchange 2007 SP2. I get the following error message:
Failed to initialize the logfile: Access to the path C:\ExchangeSetupLogs\ExchangeSetup.log is denied.
Setup will not continue.
Can anybody tell me how to solve this issue?
Tom.

Hi Tom,
From your error description, I recommend you do the following steps for troubleshooting:
1. Please ensure you run the setup as a local admin at first.
2. Please disable UAC and then install Exchange 2007 SP3. We cannot install Exchange 2007 while UAC is enabled.
Hope it helps.
If you need further assistance, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Outlook 2010 using Exchange 2010 - cannot send this item after updating draft email

I have a client who has the following setup.
SBS 2011 server (Exchange 2010) and a Windows 2008 R2 Terminal Server (with Office 2010 SP1 installed).
This particular user has a Windows XP PC with Office 2010 SP1 installed (joined to SBS 2011 domain).
This user creates a email at their office on their PC and saves it in draft to continue working on it when they get home.
At home they RDP into the terminal server and load outlook and start updating their saved (Draft) email. They then try to send it and the following error pops up. "Cannot send this item".
If they try to save the changes they have made it pops up with "The operation failed".
I have tried various settings all with the same results.
Office 2010, Office 2010 SP1, Online mode and Cache mode (on the Windows XP PC).
Any ideas?

Hi Rajkumar,
OK. After further testing I have narrowed it down to the email signature?
If I save a draft email in Outlook on the Fat client (Windows XP + Office 2010), then go straight into Drafts folder and open the email and add one line of text and try to send or save again it fails.
If I don't have a signature, it works fine.
I currently trying to determine what part of the signature it doesn't like (it is quite a large signature, multiple images and a disclaimer etc). I'm having mixed results - I can remove the signature totally from the draft email and then it will save
or send fine.
Strange that it can save the email to Draft in the 1st place but doesn't like updating it a 2nd time???
I have also created a new outlook profile (online mode) with the same results.

SBS 2008 & Forefront Exchange 2010

Similar Messages

Maybe you are looking for