With ios5 do i still need microsoft exchange

Now that i have ios5 on iphone and ipad2 do i still need microsoft exchange

Greenehouse wrote:
Now that i have ios5 on iphone and ipad2 do i still need microsoft exchange
Microsoft Exchange is an email server (and a few other things) and is run by your email hosting service (or work or where ever.)  Having access is NOT a requirement for iPhone or iPad (on any version of iOS.)  However, if your email is still being delivered to that particular email server where Exchange is running, then you still need to connect to that server with whatever device you have.  Just like if you have Yahoo mail, you would still need to connect to Yahoo from whatever device you have.
If you don't mind changing your email or moving your calendar and contact from your current Exchange account, then "you do not need Microsoft Exchange."

Similar Messages

  • With Ap3 do we still need Nik Plug-ins

    I bought the Nik plug-ins mainly for noise reduction, viveza and selective sharpening. It seems like with brushes these plug-ins are now unnecessary and still will result in large tiff files once 64-bit compatible.
    Am I missing anything here?

    I think they are "less necessary," but I don't think they are unnecessary. Certainly Silver FX and Color FX offer things you can't get directly within Aperture. The Nik sharpening is very good; probably better for output sharpening than what's built in to Aperture but it depends on what you are doing - if you're printing for sales and very critical you may still need it.
    I rarely used the Nik noise reduction plug-in because I didn't want to convert my files to TIFF early in the workflow.

  • With iCloud do I still need a backup device?

    If I use iCloud, is there still a need for a backup device such as Time Capsule?

    Absolutely. iCloud is not a general backup alternative.
    MobileMe- About moving to iCloud
    MobileMe services that no longer sync after moving to iCloud

  • With .img do you still need movie files?

    Hey All,
    I was wondering if I make a .img of my movie and dvd, can I throw away the iMovie files/project?
    This is if I am completely done with the project of course. I am trying to save space on my hard drive but I don't want to lose my movies.
    Thanks for your help.

    Hi Verbal,
    As long as you're not wanting to edit your project anymore you can delete all of the iMovie files (and the iDVD project file too). The iMovie project contains all of the raw footage and edits of course so you MUST be sure you've finished editing first.
    The disk .img file is an exact replica of the DVD contents that you would burn. You can burn as many new DVD's as you need from this file. It's the same as the disk version.
    I would advise you to create a DVD, watch it to make sure you're happy, make another copy so you have 2 DVD's then you can delete all of the files from your Mac including the .img (because you've now got one master disk and a backup disk).
    Hope this helps.
    David.

  • Do I still need Microsoft Office?

    Just wanted some feedback from the community. I have iwork 09 installed and I love it. Do I really need MS Office anymore? Just wanted to hear some thoughts.
    Thanks,
    Eddie

    There have been innumerable posts here on the issue, suggest you do some searching. If you must share lots of ms office docs (particularly word) with others, then pages has some severe limitations. If you must create complex docs with footnotes that span pages, multiple tables of contents, internal bookmark references, pages can't do that and you need a substitute. Pages is great as an everyday word processor but does have the above noted limitations. If you need something on the rare cases where translations issues arise from pages to word format, check out the free neooffice which does a great job of translating into word format. As to numbers, it is wonderful, but I suspect that given its different design (lots of small tables combined), anything other than simple spreadsheets won't translate well into xcel. But I haven't done a lot of translating back and forth on that front. Don't use Keynote/powerpoint. One last thought. If you must use word due to the need to share and translate with ease, I do not recommend the mac version of office, I think it ***** - word particularly in that the formatting toolbar cannot be resized and its preset size is too small to use. I think the only realistic solution is either boot camp or a virtual windows machine using parallels or vmware fusion and then running ms office windows version. the problem with this solution is cost, you need both office and windows.

  • Where can I download just Lion 10.7X. Computer not compatible with mountain Lion but still need to upgrade.

    Note: I'm on Snow Lepard... I Just tried upgrading to Mountain Lion but it states that it's uncompadable with my computer. So I want to upgrade to just Lion )SX 10.7 YET i can not find anywhere to buy this. It's not in the app store. I can't find any link to older versions of the OS. Can someone please help?

    UPDATE: I am going on day 3 and have yet to receive my code! Seriosuly... a NUMBER that they send via email. DAY 3??? Because it take this long to "process"??? You have got to be "F'ING" Kindding me! Customer service is key and Apple USE...USE!.. to be king. I actually waited on the phone for 25 minute just to be told I had to wait for GOD KNOWS WHEN (ie. maybe 3 days) for the order to be processed.
    As an investor ($90k deep)) i think i will be droppign about half+ my positions tomorrow. It's always good to test those you invest ;-)

  • The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete - Cant add Outlook accounts

    Hi have recently started getting the following error message when setting up new accounts with Outlook 2007:
    The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
    Outlook then prompts me to enter the username and password, i do so and get message again. This happens on Windows XP Professional and Vista, i cannot setup any accounts for new machines.
    Points to note are that OWA works fine, and previous users who are already setup work fine also. It seems to be limited to setting up new Outlook 2007 accounts.
    It can find the username fine. It comes up with green ticks underr the Online Search for your server settings:
    Establish Network connection
    Search for [email protected] server settings
    Long on to server ---------- then it fails with a big red cross at this point
    Recently i did add a second mail server to the network but it was not configured to talk to the other main mail server which was handling all the functions of mail box, CAS, hub transport. I had installed all the same roles on the second server with a view to move it across and retire the old server, the second machine is a different machine name from the main mail server. In summay my servers are:
    svr001              Server 2003 R2 Enterprise x64 domain controller
    mail                 Server 2003 R2 Enterprise x64 non-domain controller with exchange 2007 SP1
    mail001            Windows 2008 Enterprise x64 non-domain controller with exchange 2007 SP1
    The main box "mail" has been fine until i recently introduced this new server "mail001" into the network.
    I am really stuck now and would really appreciate any pointers or steps to debug the above.
    Many thanks,
    Chris

    The FIX IT here
    http://support.microsoft.com/?kbid=319206 works, but only for a user who's already logged in (if you just run the fix it program and do nothing else). To make it work for all users you'll need to manually edit the registry as it says in the article.
    To force Outlook to use a pre-defined global catalog server, use the following steps to set the following special registry parameter to point to the Fully Qualified Domain Name (FQDN). Doing this over-rides any setting in the MAPI profile.
    Click Start, and then click Run.
    In the Open box, type regedit.exe, and then click
    OK.
    Locate and then click the following key in the registry:
    HKEY_CURRENT_USER\Software\Microsoft\Exchange\Exchange Provider
    Note You may have to create the registry path.
    On the Edit menu, click Add Value, and then add the following registry value:
    Value name: DS Server
    Data type: REG_SZ (string)
    Value data: FQDN of the global catalog server
    This allowed me to roll out a bunch of laptops and not have to worry about running the Fix It for each user.
     update: Sysprep seemed to remove fix. Each time a new user logged into a newly imaged laptop (on domain) same error about Outlook 2007 cannot connect to Exchange. Have tried just about everything, but all I seem to be able to do is run this stupid
    Fix it each time. Luckily I don't have 1000 machines to setup because then I'd be screwed.

  • Exchange 2013 CU3 Fails "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception."

    I can't get Exchange 2013 to install in our Server 2008 R2 infrastructure. Setup fails with the following error when preparing AD. This is running on Server 2008 R2 SP1 VM's.
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    FAILED
         The following error was generated when "$error.Clear();
            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
    ainController $RoleDomainController
    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the

    I have set the PowerShell Execution Policy to unrestricted. After running setup /PS I get the following output
    PS C:\Windows\system32> cd c:\temp\ex2013cu3
    PS C:\temp\ex2013cu3> ./setup /ps /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Extending Active Directory schema                                                                
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation completed successfully.
    PS C:\temp\ex2013cu3>
    The installation was started at 10:13am and hung for sometime at 94% of the prereq stage. Installation finally completed at 10:47am. The errors seem to indicate that setup will continue. However upon running setup /prepareAD the installation hangs for sometime
    at 21% of Organization Preparation before finally failing with the following output....
    PS C:\temp\ex2013cu3> ./setup /prepareAD /iacceptexchangeserverlicenseterms
    Welcome to Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup
    Copying Files...
    File copy complete. Setup will now collect additional information needed for installation.
    Performing Microsoft Exchange Server Prerequisite Check
        Prerequisite Analysis                                                                            
    COMPLETED
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    Configuring Microsoft Exchange Server
        Organization Preparation                                                                         
    FAILED
         The following error was generated when "$error.Clear();
            install-DefaultAcceptedDomain -Name $RoleFullyQualifiedDomainName -DomainName $RoleFullyQualifiedDomainName -Dom
    ainController $RoleDomainController
    " was run: "The type initializer for 'Microsoft.Exchange.Flighting.RotationHash' threw an exception.".
     Task module "CmdletHealthCountersModule.Task_IterateCompleted" fails with exception "The type initializer for 'Microsof
    t.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be aff
    ected.
     Task module "CmdletIterationEventModule.LogCmdletIterationEvent" fails with exception "The type initializer for 'Micros
    oft.Exchange.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be a
    ffected.
     Task module "CmdletHealthCountersModule.Task_Release" fails with exception "The type initializer for 'Microsoft.Exchang
    e.Flighting.RotationHash' threw an exception.". This module is skipped. Task execution result should not be affected.
    The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
    <SystemDrive>:\ExchangeSetupLogs folder.
    PS C:\temp\ex2013cu3>

  • #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error.

    Hi, 
    I created a mailbox few days before, everythign was working fine and suddenly when some one tried to send email on that mailbox it bounced back with following error:
    There's a problem with the recipient's mailbox. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.
    Sent by Microsoft Exchange Server 2007 
    Diagnostic information for administrators:
    Generating server: Mail01.abc.com
    [email protected]
    #550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionNotFound:16.18969:9A000000, 17.27161:00000000CC000000000000000600000000000000,
    255.23226:00000000, 255.27962:FE000000, 255.17082:0F010480, 0.26937:94000000, 4.21921:0F010480, 255.27962:FA000000, 255.1494:00000000, 255.26426:FE000000, 4.7588:0F010480, 4.6564:0F010480, 2.17597:00000000, 2.25805:00000000, 4.8936:0F010480, 4.14312:0F010480,
    4.2199:0F010480, 2.25805:00000000, 4.8936:0F010480, 2.22957:00000000, 2.19693:00000000, 2.17917:00000000, 2.27341:00000000, 4.8936:0F010480, 4.17097:0F010480, 4.8620:0F010480, 255.1750:0F010480, 0.26849:0F010480, 255.21817:0F010480, 0.26297:0F010480, 4.16585:0F010480,
    0.32441:0F010480, 4.1706:0F010480, 0.24761:0F010480, 4.20665:0F010480, 0.25785:EC030000, 4.29881:0F010480". ##
    Original message headers:
    Received: from Mailbox.abc.com ([fe80::892d:93d6:b1ac:b70a]) by mail01
     ([10.72.0.95]) with mapi; Fri, 11 Jan 2013 14:04:55 +0500
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: Anwar Amjad <[email protected]>
    To: All-HEC <[email protected]>
    Date: Fri, 11 Jan 2013 14:04:53 +0500
    Subject: FW: Suggestions & New Arrival in HEC Library
    Thread-Topic: Suggestions & New Arrival in HEC Library
    Thread-Index: Ac3vHgwR50OLs2BnQuOzo9jWg4e1gQAvJtUw
    Message-ID: <[email protected]>
    References: <[email protected]>
    In-Reply-To: <[email protected]>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach: yes
    X-MS-TNEF-Correlator: <[email protected]>
    MIME-Version: 1.0
    X-Auto-Response-Suppress: DR, OOF, AutoReply
    After this error, i treid to send email again and there is no error and email was delivered. What was the cause of this error?
    Hasan

    Hi,
    I tried to start seeding again but it is at same status. I will try again and hopefully it will get resolved.
    But, yesterday i ran in to the most complex issue i have ever seen with Exchange.
    There was a unexpected power cut at our datacentre due to which both the nodes went down.
    After that both the nodes came up. But the all 3 databases were dismounted.
    Therefore, i ran Eseutil /mh resulting dirty shutdown.
    I was able to repair 2 databases.
    But the 3rd one was not mounting with below error.
    Microsoft Exchange Error
    Failed to mount database 'Mailbox Database'.
    Mailbox Database
    Failed
    Error:
    Exchange is unable to mount the database that you specified. Specified database: XXXXX\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216).
    I was able to mount database somehow. There are 7 User mailboxes (Tier 1) on this database.
    All emails sent to the users in this database are bouncing back with the below error.
    This storage groups holds the mailboxes of my Senior Managements. And their mailboxes are down for almost 20 Hrs. I am spinning my head since yesterday but not able to find any fix. Can you please guide me in this concern.
    Best Regards
    K2
    Kapil Kashyap

  • Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

    What am I trying to do?
    I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
    error logs at the bottom of the page but the basics are in order it will throw which loop around are:
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
    What am I running?
    2 X DC on domain and forest functional level 2008R2 both writable
    1 X fresh install of Windows 2012 R2 which is domain joined
    What have I tried?
    Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
    Rebooted every server
    Run setup as Administrator
    My account is part of the domain Enterprise Admin group
    Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
    Computer Configuration Windows Settings
    Security Settings + Local Policies
    User Rights Assignment Mange auditing and security log
    Turned off firewall on DC and Exchange Server even stopped the service
    Turned off all AV on the DC and Exchange Server
    Checked I could telnet to global catalog servers on port 3268 which I can
    Checked the global catalog records existed in DNS which they all do
    Done the obvious ping tests all round which confirms connectivity
    Schema has been prepared using appropriate commands before running the setup exe
    setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
    Making sure the following path has full permissions:
    EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    Restarted Microsoft Exchange Active Directory Topology service
    DcDiag all looks good
    What have I noticed that is suspicious?
    Microsoft Exchange Transport service will not start even though both of its dependences services have started:
    Microsoft Filtering Management Service
    Microsoft Exchange Active Directory Topology Service
    It will eventually error with
    “Windows could not start the Microsoft Exchange Transport Service on local computer
    Error 1053: This Service did not respond to the start of control request in a timely fashion”
    This error is from the GUI wizard itself:
    Error:
    The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
    " was run: "System.Exception: Unable to set shared config DC.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Exchange logs which have been written:
    **The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
    [01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
    '{ mydomain.com}'
    [01/20/2015 17:13:20.0084] [2] User specified parameters: 
    -DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
    No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
    [01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
    [01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
    Windows Event Viewer:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
    in either the local site 'Default-First-Site' or the following sites:

    Hi apl228,
    1. Please make sure the IPv6 is enabled.
    2. Please make sure the account that install Exchange server has Administrator permission.
    3. Please make sure DNS has been configured correctly.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange Server 2013 SP1 CU5 - The Microsoft Exchange Replication service VSS Writer encountered an exception

    We have 2 server DAG with a witness all servers are Server 2012 R2.  Both members of the DAG are Exchange 2013 SP1 CU5.
    We haven't seen this until recently, but during a VSS enabled storage snapshot the following errors occur.  All of which are related to MSExchangeRepl and the Exchange VSS Writer.
    Event IDs 2140, 2026, 2028, 2030.
    The errors start with the 2140 seen here:
    The Microsoft Exchange Replication service VSS Writer encountered an exception in function Microsoft::Exchange::Cluster::ReplicaVssWriter::CReplicaVssWriterInterop::PrepareSnapshot. HResult -2147467259. Exception Microsoft.Mapi.MapiExceptionDatabaseError: MapiExceptionDatabaseError:
    Unable execute Prepare on snapshot. (hr=0x80004005, ec=1108)
    Diagnostic context:
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 56264   StoreEc: 0x1388    
        Lid: 46280   StoreEc: 0x454     
        Lid: 1750    ---- Remote Context End ----
        Lid: 59216  
        Lid: 34640   StoreEc: 0x454     
        Lid: 52264  
        Lid: 46120   StoreEc: 0x454     
       at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcAdmin.ProcessSnapshotOperation(Guid mdbGuid, SnapshotOperationCode operationCode, UInt32 flags)
       at Microsoft.Exchange.Cluster.Replay.StoreRpcController.<>c__DisplayClass1c.<SnapshotPrepare>b__1b()
       at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.<>c__DisplayClass2.<ProtectedCallWithTimeout>b__0()
       at Microsoft.Exchange.Data.HA.InvokeWithTimeout.Invoke(Action invokableAction, Action foregroundAction, TimeSpan invokeTimeout, Boolean sendWatsonReportNoThrow, Object cancelEvent)
       at Microsoft.Exchange.Cluster.Replay.SafeRefCountedTimeoutWrapper.ProtectedCallWithTimeout(String operationName, TimeSpan timeout, Action operation)
       at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.SnapshotPrepare(Guid dbGuid, UInt32 flags)
       at Microsoft.Exchange.Cluster.ReplicaVssWriter.CReplicaVssWriterInterop.PrepareSnapshot().

    Hi Julez K,
    According to your description, you could try upgrading to CU6.
    In addition, you could review the Exchange Application (App) Event log and the Exchange System (Sys) Event log for errors , and some related resolutions for your reference.
    http://www.symantec.com/business/support/index?page=content&id=TECH209938
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety,
    or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Hope it can be helpful.
    Best regards,
    Eric

  • Microsoft Exchange Email not Syncing

    I have synced my Iphone with my company's server using microsoft exchange. When I did this the day I got my phone, everything worked fine. A day later, I quit receiving/sending emails. I have deleted the account and set it up again several times. My calendar and contacts sync perfectly, I just can't get my email. I've tried the trouble-shooting I could find on the website too.
    Please help!!
    Amanda

    see the bottom of this thread
    http://discussions.apple.com/thread.jspa?threadID=1747366&tstart=0

  • Need help with server for Microsoft Exchange

    Okay. My college uses Microsoft Outlook and I wanted to be able to check it from my phone.
    So I am trying to use microsoft exchange.
    but I don't know what to put in the server part.
    I don't get step three
    3.Your iPhone (or iPod touch) will now try to locate your Exchange server using Microsoft's Autodiscovery service. If the server cannot be located, the screen below is shown. Enter your front-end Exchange server's complete address in the Server field. Contact your Exchange server administrator if you are unsure of the address.
    any help or being pushed in the right direction would be greatly apperciated!!

    Your college IT people would have to have "enabled" iPhone connections to their Exchange servers, it's quite possible they have not done that. In either case, contact your college IT people to determine if they even allow this and, if they do, the Exchange server info you need to enter. They are the key.

  • DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

    Hi Board,
    i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
    we drive a 2 node DAG (Location1-Ex1-mb1 
    Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
    Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          28.09.2012 00:37:17
    Event ID:      2112
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Location1-Exc1-MB1
    Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
    Followed by
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:         
    01.10.2012 03:33:06
    Event ID:      2024
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:         
    N/A
    Computer:      Location1-Exc1-MB1
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
    The backup Application - Symantec Backup Exec 2010 R3 – states, this error
    Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
    Check the Windows Event Viewer for details.
    Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
    Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
    to restart the MS Exchange Replication Service – BUT the mentioned eventID
    8229 isn´t present on any of the both Mailboxservers.
    The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
    This confuses me, since all Backups are normally taken from the passive copy of a Database.
    So my questions to the board are:
    * Does anyone is facing similar issues?
    * Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
    -          * Does someone know the conditions, why shadows copies remain and
    aren´t removed in a proper manner?
    What can cause the circumstance, that only 1 DB is facing such issues?
    Any suggestion is welcome!
    BR
    Markus

    Hi Lenora,
    I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
    those things i´ve all tried now:
    - Backup from passive DB (forced within Symantec Backup Exec)
    - Backup from active DB (forced within Symantec Backup Exec)
    - Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
    - Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
    All those attempts failed.
    But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
    The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
    Backups are working again on all DBs!
    THX for your replys.
    Best regards
    Markus

  • Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data file (.ost)

    Fresh installation of Exchange Server 2013 on Windows Server 2012.
    Our first test account cannot access their email via Outlook but can access fine through OWA. The following message appears - "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize
    your folders with your Outlook data file (.ost)" is displayed.
    If I turn off cached Exchange mode, setting the email account to not
    cache does not resolve the issue and i get a new error message - "Cannot open your default e-mail folders. The file (path\profile name).ost is not an Outlook data file (.ost). Very odd since it creates its own .ost file when you run it for the first
    time.
    I cleared the appdata local Outlook folder and I tested on a new laptop that has never connected to Outlook, same error message on any system.
    Microsoft Exchange RPC Client Access service is running.
    No warning, error or critical messages in the eventlog, it's like the healthiest server alive.
    Any help would be greatly appreciated. I haven't encountered this issue with previous versions of Exchange.

    So it looks like a lot of people are having this issue and seeing how Exchange 2013 is still new (relatively to the world) there isn't much data around to answer this. I've spend ALOT of time trying to figure this out.
    Here is the answer. :) - No I don't know all but I'm going to try to give you the most reasonable answer to this issue, in a most logical way.
    First thing I did when I was troubleshooting this issue is that I ignored Martina Miskovic's suggestion for Step4 http://technet.microsoft.com/library/jj218640(EXCHG.150)because it didn't make sense to me because I was trying to connect
    Outlook not outside the LAN but actually inside. However, Martina's suggestion does fix the issue if it's applied in the correct context.
    This is where the plot thickens (it's stew). She failed to mention that things like SSL (which I configure practically useless - anyone who ever worked in a business environment where the owner pretty much trusts anyone in the company, otherwise they don't
    work there - very good business practice in my eyes btw, can confirm that...) are some sort of fetish with Microsoft lately. Exchange 2013 was no exception.
    In exchange 2003, exchange 2007 and exchange 2010 - you could install it and then go to outlook and set it up. And when outlook manual Microsoft Exchange profile would ask you for server name, you would give it and give the name of the person who you setting
    up - as long as machine is on the domain, not much more is needed. IT JUST WORKS! :) What a concept, if the person already on premises of the business - GIVE HIM ACCESS. I guess that was too logical for Microsoft. Now if you're off premises you can use things
    like OutlookAnywhere - which I might add had their place under that scenario.
    In Exchange 2013, the world changed. Ofcourse Microsoft doesn't feel like telling it in a plain english to people - I'm sure there is an article somewhere but I didn't find it. Exchange 2013 does not support direct configuration of Outlook like all of it's
    previous versions. Did you jaw drop? Mine did when I realized it. So now when you are asked for your server name in manual outlook set up and you give it Exchange2013.yourdomain.local - it says cannot connect to it. This happens because ALL - INTERNAL AND
    EXTERNAL connection are now handled via OutlookAnywhere. You can't even disable that feature and have it function the reasonable way.
    So now the question still remains - how do you configure outlook. Well under server properties there is this nice section called Outlook anywhere. You have a chance to configure it's External and Internal address. This is another thing that should be logical
    but it didn't work that way for me. When I configured the external address different from the internal - it didn't work. So I strongly suggest you get it working with the same internal address first and then ponder how you want to make it work for the outside
    users.
    Now that you have this set up you have to go to virtual directories and configure the external and internal address there - this is actually what the Step 4 that Martina was refering to has you do.
    Both external and internal address are now the same and you think you can configure your outlook manually - think again. One of the most lovely features of Outlook Anywhere, and the reason why I had never used it in the past is that it requires a TRUSTED
    certificate.
    See so it's not that exchange 2013 requires a trusted certificate - it's that exchange 2013 lacks the feature that was there since Windows 2000 and Exchange 5.5.
    So it's time for you to install an Active Direction Certificate Authority. Refer to this wonderful article for exact steps - http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
    Now even after you do that - it won't work because you have to add the base private key certificate, which you can download now from your internal certsrv site, to Default Domain Policy (AND yes some people claim NEVER mess with the Default Domain Policy,
    always make an addition one... it's up to you - I don't see direct harm if you know what you want to accomplish) see this: http://technet.microsoft.com/en-us/library/cc738131%28v=ws.10%29.aspx if you want to know exact steps.
    This is the moment of ZEN! :) Do you feel the excitement? After all it is your first time. Before we get too excited lets first request and then install the certificate to actual Exchange via the gui and assign it to all the services you can (IIS, SMTP and
    there is a 3rd - I forgot, but you get the idea).
    Now go to your client machine where you have the outlook open, browse to your exchange server via https://exchang2013/ in IE and if you don't get any certificate errors - it's good. If you do run on hte client and the server: gpupdate /force This will refresh
    the policy. Don't try to manually install the certificate from Exchange's website on the client. If you wanna do something manually to it to the base certificate from the private key but if you added it to the domain policy you shouldn't have to do it.
    Basically the idea is to make sure you have CA and that CA allows you to browse to exchange and you get no cert error and you can look at the cert and see that's from a domain CA.
    NOW, you can configure your outlook. EASY grasshoppa - not the manual way. WHY? Cause the automatic way will now work. :) Let it discover that exachange and populate it all - and tell you I'm happy! :)
    Open Outlook - BOOM! It works... Was it as good for you as it was for me?
    You may ask, why can't I just configure it by manual - you CAN. It's just a nightmare. Go ahead and open the settings of the account that got auto configed... How do you like that server name? It should read something like [email protected]
    and if you go to advanced and then connection tab - you'll see Outlook Anywhere is checked as well. Look at the settings - there is the name of the server, FQDN I might add. It's there in 2 places and one has that Mtdd-something:Exchange2013.yourdomain.local.
    So what is that GUID in the server name and where does it come from. It's the identity of the user's mailbox so for every user that setting will be different but you can figure it out via the console on the Exchange server itself - if you wish.
    Also a note, if your SSL certs have any trouble - it will just act like outlook can't connect to the exchange server even though it just declines the connection cause the cert/cert authority is not trusted.
    So in short Outlook Anywhere is EVERYWHERE! And it has barely any gui or config and you just supposed to magically know that kind of generic error messages mean what... Server names are now GUIDs of the [email protected] - THAT MAKES PERFECT
    SENSE MICROSOFT! ...and you have to manage certs... and the only place where you gonna find the name of the server is inside the d*** Outlook Anywhere settings in the config tab, un it's own config button - CAN WE PUT THE CONFIG ANY FURTHER!
    Frustrating beyond reason - that should be Exchange's new slogan...
    Hope this will help people in the future and won't get delete because it's bad PR for Microsoft.
    PS
    ALSO if you want to pick a fight with me about how SSL is more secure... I don't wanna hear it - go somewhere else...

Maybe you are looking for