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

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.

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

Migrate SBS Server 2008 with Exchange 2007 to Exchange 2013

I have looked at the documentation to co exist 2007 and 2013. However I am concerned as it talks about changing the dns name to something like legacy, as the dns name that is used for outlook to connect is the name of the server. So here
is my question. Would I have to change the name of the actual server itself? and if I choose not to, and use a new name for the 2013 server, such as mail, would the users that get migrated, would they automatically update the
name change? Also note the SBS server with exchange 2007 is also their file server at present but will be changing.

Hi ,
Thank you for posting your question 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
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

How can I edit the way autodiscover.xml behaves in SBS 2008 and 2011?

I have autodiscover working correctly on a few SBS 2008 and SBS 2011 servers. But, its doing its usual misbehaving. When setting up a new Outlook profile, the user enters their email address and password. Autodiscover is successful in creating all
the account settings, but at the end of the wizard a username and password window pops up with the users full email address incorrectly filled in as the username, which is why it didn't work.
This has always been so annoying about SBS. The user then has to be told to delete their email address in the username field, then fill in "domain\username" instead. Only then is the authentication successful.
I've read lots about people adding the external domain UPN Suffix to ADD&T, then manually changing ever users login to domain.com instead of domain.local.   Then you have to mess with the owa authentication settings in exchange to accept the
UPN.   Its all too ridiculous. There must be a simpler way.
I have read about how you can control how the autodiscover.xml behaves, and there are examples of how to do it in this document:
https://docs.google.com/viewer?a=v&q=cache:0jap1FNKgV0J:https://support.quest.com/Shared/Images/SOL51188_Outlook%2520Automatic%2520Account%2520Configuration.doc+&hl=pl&gl=pl&pid=bl&srcid=ADGEESjizUeFf-JYaM7ZdfIgUCKMMXtcCl0Y3pknFbuwd64GNHIEP1K8a_mpg2YIEisP6sz5DzbtVtdW4Pc42PE0Kjd6bz-3vXz0iaQm7FKi0AnwgvFG_41ZAkBLWynaJtf8s8xyi_d2&sig=AHIEtbSie1mEHTn8el4DPquNxrpovwknUQ
The document above shows the settings we need to change. It looks like we can add the local domain using DomainName into the autodiscover.xml and this will stop autodiscover reporting that the full email address is required.  So we
should be able to get autodiscover to populate the username pop-up with with "domain\user" automatically.
OK, so my question is, how on earth do I edit these settings in SBS 2011? I can't find any articles that talk about how to edit autodiscover.
If I could just edit this one setting (that Microsoft should have correctly configured in the first place) autodiscover will work perfectly for all existing users and all future users, without having to do anything.

Just to straighten out a few things;
1) This is NOT a bug, rather by design. Not every active directory has an exchange server in place, and MS is assuming you don't want to give your internal domain name out to people (which is why it doesn't default to domain\username)
2) Going on what I said in 1), this is NOT SBS specific this is the same way with every Active Directory/Exchange install, keep in mind Microsoft did NOT specially design the software for SBS, they just bundled it into a supported configuration in a neat
little package -since the Exchange server we run on SBS is the same Exchange server powering hundreds of hosted email providers -it makes sense why autodiscover doesn't provide the domain\username (imagine what a mess that would be!)
3) I understand it's a little bit time consuming but it can actually be done for all users in a matter of seconds, select all users, right click and go to Properties, you can then choose the UPN Suffix for all users. When a new user gets created one of the
settings in the wizard is the UPN suffix and is easily changeable as long as you notate for the person creating the user to do it. (The problem here is if you're using the SBS Console instead of AD to setup the User in which case that's just an oversight
in design not a bug in the programming)
4) You can most certainly have a powershell script that changes the UPN suffix from A to B, let me know if you're interested I'll dig one up for you. That can be run on a scheduled task and will solve the remaining issues you have :)
I do see you mentioned it in number 3, I must have missed since I didn't re-read the OP before posting the article, however I just tested on several SBS 2011 machines and OWA authentication settings don't have to be changed at all, this worked immediately
for Outlook Anywhere and Outlook Web Access in my lab and two different customer production systems.
-GreenlightTech

Windows SBS 2008 and Treo 755P

Has anyone had any success getting a Treo 755P (Sprint) to sync with a mailbox on a Windows SBS 2008 server ?? The device will sync with a Windows 2003 64bit and Exchange 2007 server but will not with a SBS 2008 server. I have talked to both Sprint and Palm and they weren't much help other than to tell me it was a server issue. I am getting the following errors:
AirSAMStateMachine .c1913 4628
AirSAMStateMachine .c1913 3
Sometimes I get one error and sometimes I get the other but the 4628 is the most common. I have done a hard reset on the phone as well as tried it with multiple accounts with no success. I have iPhones, Blackberries and a Treo 855W working fine with the server, I just can't get this phone to work ... I also have a purchased cert. on the server from Verisign, but tried it both with and without SSL and neither works.
Anybody with any suggestions ??
Thanks,
Post relates to: Treo 755p (Sprint)

Oh, good. You're almost there then. Does this problem affect other handhelds too? Palm/Versamail or WinMo? If you need additional testers, I can simulate one and connect with a test account.
Is the problem still occurring after a hard reset too? Is it limited to EAS when set to "as items arrive" or does it hang no matter what time increment is chosen?
Was the Sprint Treo 755p 1.07 update already applied?
Once EAS is connected to a good Exchange server, it usually works well. For kicks, did you delete and recreate the ActiveSync virtual folder on the server? Are there any hints to the hanging/freezing in the IIS logs?
Hopefully, the real prob will turn up and let him get this working 100%
Post relates to: Centro (Sprint)
Post relates to: Centro (Sprint)

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.

Exchange 2007 Room Calendar Issues

Hello, on our Exchange 2007 server, we have 6 room mailboxes, all setup exactly alike. One of the mailboxes started not responding to calendar requests. If I schedule a meeting, exchange does it's part, and sends out the invitation, but nothing shows in
the room calendar itself. Besides exporting the existing calendar entries and creating a new mailbox, is there anything I can try?
[PS] C:\Windows\System32>Get-MailboxCalendarSettings RadcliffeConf.Room | fl
AutomateProcessing : AutoAccept
AllowConflicts : False
BookingWindowInDays : 180
MaximumDurationInMinutes : 1440
AllowRecurringMeetings : True
EnforceSchedulingHorizon : True
ScheduleOnlyDuringWorkHours : False
ConflictPercentageAllowed : 0
MaximumConflictInstances : 0
ForwardRequestsToDelegates : True
DeleteAttachments : True
DeleteComments : True
RemovePrivateProperty : True
DeleteSubject : True
DisableReminders : True
AddOrganizerToSubject : True
DeleteNonCalendarItems : True
TentativePendingApproval : True
EnableResponseDetails : True
OrganizerInfo : True
ResourceDelegates : {}
RequestOutOfPolicy :
AllRequestOutOfPolicy : False
BookInPolicy :
AllBookInPolicy : True
RequestInPolicy :
AllRequestInPolicy : False
AddAdditionalResponse : False
AdditionalResponse :
RemoveOldMeetingMessages : True
AddNewRequestsTentatively : True
ProcessExternalMeetingMessages : False
DefaultReminderTime : 15
RemoveForwardedMeetingNotifications : False
Identity : xxxx.com/SDI Users Groups and Computers/
Room Mailboxes/Radcliffe Conf. Room

Hi n3lka
Thank you for your question.
Owing to not respond, you can try to check the mailbox permission.
“nothing show in the room calendar itself”, you can make outlook in cache mode, then, you can try to uncheck option “Download share folders”.
There is a similar thread you can refer to by the following link:
https://social.technet.microsoft.com/Forums/en-US/cb057c90-9eaa-4ead-8b1d-68e8ae87c0b0/exchange-2007-room-calendar-issues?forum=exchangesvrclientslega
when nothing shows in the room calendar itself, you can try to make another user schedule a meeting, if another user schedule a meeting successful, you can refer to the following link to solve it:
https://social.technet.microsoft.com/Forums/en-US/a31af989-aee1-42f0-88bd-c178c6199379/exchange-2007-room-mailbox-and-calendar-issue?forum=exchangesvradminlegacy
If there are any questions, please let me know.
Best Regard,
Jim

OIM connector for AD 2008 and exchange 2008

hello,
Customer is in migration of AD 2003 to AD 2008 and exchange 2003 to Exchange 2008. I do know that OIM connects exists for AD 2003 and Exchange 2003.. but not seen any for AD 2008 or Exchange 2008.. So, does any one have idea that how to get the connectors from oracle or already exists then where are those..
Looking to here you soon.

Hi,
I don't know why your client want's to migrate to 2008, they are so new versions and there is no compatible connector at this moment for them. You could try to use the current ones, but for sure you'll find problems with them.
If they are actually migrating to 2008, you'll probably need to code your own connector from scratch, or make huge modifications on current connectors as there is no announce from Oracle for new releases.
I recommend to ask your Oracle provider or open an SR to ask about it.
Good luck!

How to set up fax solution using Windows 2008 R2 Fax server role and Exchange 2007

Hello,
I don't know if this is the right forum to post this but since it is related to Exchange I thought it might be. If this is not the right place, please direct me to the forum where my post would be more appropriate.
I'm looking to set up a Fax solution for the company that I work for as we are moving away from analog phone lines to VoIP using SIP. My original thought was to set up a Windows 2008 R2 server with Fax server role installed and have it route the fax message
to Exchange 2007 SP3 so the fax message can be delivered to each user's inbox. I was reading a little bit on the Windows Fax server role and from what I saw it looks like it can only route fax messages to one email address. This not ideal for my company. Is
there a way to have the fax server role route the email to each user's inbox? If so, how can I achieve this?
How can implement this for this sending outgoing faxes as well?
I don't know if this releveant or not but I will be using Asterisk as a media gateway between our SIP trunks and the Windows Fax server.
Any help is appreciated. Thanks!

Please find the below url for the complete Fax configuration in Exchange 2007 Unified Messaging
http://blogs.technet.com/b/exchange/archive/2007/04/18/3401950.aspx
The article is so easy to understand with detail procedure and guideliness
Exchange Queries

Snow Leopard and Exchange 2007 Configuration Issues

I know this topic may have been covered in here previously but I have yet to find a solution.
Here is the background. Our CEO has a Mac Book and two weekends ago he updated to Snow Leopard and now wants to use the Mail client on his Mac rather than OWA to get his email. We have Exchange 2007 (I am the Admin) and have all the latest patches and Roll Ups installed. We run OWA without issue and have 10 iPhones working perfectly (i realized they use different technology to sync). I enabled EWS by following this link http://technet.microsoft.com/en-us/library/bb201695.aspx and this is the actual command i used:
Set-WebServicesVirtualDirectory -identity exchaname\EWS* -externalurl https://webmail.domain.com/EWS/Exchange.asmx -BasicAuthentication:$True
Seems to have run properly and there are no errors reported.
Now when I go to connect using the Mac it does not Auto Discover and I must enter manually. I enter what i think it needed and its not working. On the Account Information Tab I have the following:
Description: generic name
Email Address: [email protected]
Full Name: The Person's Name
Internal Server: webmail.domain.com *Not sure what should be here
External Server: Webmail.domain.com *Again not sure if this is correct
Username: AD user name Also tried domain\username
Password: AD password
Ougoing Mail Server: not sure what should be here
Next is the Mailbox behavior Tab:
Did not change anything
Advanced Tab:
Internal Server Path: EWS/Exchange.asmx
Port:80 SSL unchecked
External Server: EWS/Exchange.asmx
Port: 80 SSL unchecked
I get no connections and I am sure somehting is not correct in the above but I am lost and new to Exchange as it is. Also new to Mac's
Help Please

We are already using webmail.domain.com for our OWA URL, well actually it is webmail.domain.com\OWA. Would I need one for the EWS & Autodiscover to use webmail.domian.com\ews?
We have rules in the firewall for Exchange and OWA. Would we need another for this?

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.

10.5.7 breaks RDC and Exchange 2007 connectivity?

I just installed 10.5.7 and now I find I cannot receive mail from our Exchange 2007 server (Entourage 2008) or connect to our file server (SBS 2008 standard).
I only found one mention of this anywhere else (http://www.macfixit.com/article.php?story=20090515093340707) but it is only stating that the problem exists, not offering a solution.
Anyone else experiencing this? I can use OWA for mail if I have to, but I admin our office and RDC is invaluable to me. I will probably have to wipe/re-install our macs if a fix is not available for this.

I had a lot of problems with this and researched it as best I could. My only solution was to format clean, upgrade to 10.5.7, manually input realms, dns servers and domain controllers in System>Core Services>Kerberos, then perform the bind in the Directory Utility. After that all domain connections work, and admin level accounts can log in directly to the Mac. Our group policy for the standard user seems to prohibit the standard user from using a Kerberos login, and I have not figured out what setting is preventing it yet. When I say all connections work I mean Entourage is able to pull email from Exchange 2007 via kerberos login or OWA and RDC reaches all Windows servers I maintain. If you check macenterprise.org you will see many people having probles with AD binding in 10.5.7 and most of them have simply reverted to a previous version. After fighting with this machine for a good long time I think I'm going to revert to 10.5.6 because of poor video performance or just wait til the real headache, 10.6 in September
Message was edited by: Witchbutter

Cfexchangeconnection on Coldfusion 9 and Exchange 2007

I am experiencing issues with Microsoft Exchange with Coldfusion 9. We recently upgraded from Exchange 2003 to Exchange 2007 and cannot now successfully connect to Exchange using the cfexchangeconnection tag.
I get the error: 'Access to the Exchange server denied.Ensure that the user name and password are correct.'
I understand there have been some issues with Exchange 2007 and Coldfusion 8 and I have followed all the instructions on Adobe's documentation. However, the username and password are correct.
1. Exchange server is running on Microsoft Server 2008 (WebDAV component has been enabled)
2. Security certificate has been downloaded to the correct location on the coldfusion server
3. Webmail has been activated on Exchange server and username/password credentials work when logging in via the webmail interface.
4. Formbasedauthentication is set to 'true'.
5. I have tried setting protocol to both http & https
6. I have tried using '[email protected]' for the username as well as just 'myusername'
7. Coldfusion can send out emails via CFMAIL using the same credentials as I entered in the cfexchangeconnection tag.
I would very much appreciate any help anyone could offer.

Hello Richard,
Do you have any URL redirecting on your environment? This can cause the error mentioned.
If you try to login via OWA to a users mailbox with the impersonation account does it succeed? If it doesn't it is likely the issue is with the permissions applied to the CUC account.
This test was for the UM service account if you run the test for the user does it display a different message? This could help to isolate.
Also make extra sure you applied the permissions to all applicable Exchanges, commonly clients only apply to one of them:
Step 4 If you set permissions on individual Exchange server in Step 2 and you have more than one Exchange 2007 server, repeat Step 1 through Step 3 on the following servers:
•All other Exchange 2007 client access servers that Connection can access.
•All Exchange 2007 mailbox servers that home mailboxes that you want Connection to be able to access.
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/unified_messaging/guide/85xcucumg020.html#wp1170148
-Regards
.D.R.P.

Mail.app and Exchange 2007 with Rollup 3 ... anyone get it to work?

Spent way too much time on this...
After finding our our Exchange 2007 server didn't have the legacy components installed to ensure WebDav would work, we can now connect to our Exchange 2007 mail server from Microsoft Entourage for all Windows Active Directory accounts.
For Apple Mail however, this is not the case. Opening mail, the account information does default in accurately (email, userID, exchange 2007 server) when I enter a users password, it says that it is unable to connect to mail server user/password failed.
If I manually create the account, the same thing occurs, a pop-up appears prompting for a password, which I enter and it comes back saying it isn't valid.
The password is valid because on the same Mac I open up Entourage and log in.
Keychain is NOT used and none of the passwords are held because of the headaches this causes.
Looking for ideas, thinking this is more of an Apple Mail.app bug not working with Exchange than a Microsoft issue.

Just want to add to this...it was resolved the Advanced tab is very important on mail.app.
The Advance tab authentication must match what the Exchange server/Active Directory is using.
For us NTLM is what we need to use.
Also we found that one exchange server had a bad installation while another had no problem connecting via mail.app.
Thus the installation is going to be looked at.

SBS 2008 and Exchange 2007 intermittent Email Issues

Similar Messages

Maybe you are looking for