Exchange 2013 Configuration for PST & OST

Greetings,
currently we are using pst file to store the mails but now we wanted to store emails on server of few accounts for 10 days & simulteniously mails need to be download on pst as well. When user is online user can see the exchange mails & when user
is offline he can see the mails from pst. Please suggest what settings needs to be done in exchange server 2013?  I know it is possible with OST but i am having already pst files with emails...
Regards,
Damodar Mahajan

On Sat, 9 Mar 2013 06:27:09 +0000, Damodar Mahajan wrote:
>currently we are using pst file to store the mails but now we wanted to store emails on server of few accounts for 10 days & simulteniously mails need to be download on pst as well.
The management of PSTs is strictly a client-side thing. Exchange can't
help you with that.
>When user is online user can see the exchange mails & when user is offline he can see the mails from pst.
Okay. That sounds exactly right.
>Please suggest what settings needs to be done in exchange server 2013?
What are you asking for? If the user is "offline" they certainly won't
be able to see anything on the Exchange server, and if they're
"offline" they can't move messages to the PST.
>I know it is possible with OST but i am having already pst files with emails...
What I think you're asking is, I think, illogical. You can't see the
messages on the server unless you connect to the server, and you can't
move the messages to a PST unless ou connect to the server which means
you're "online".
Give up the PST files and keep the mail on the server. Use OST files
-- but they won't be updated unless you're "online" either.
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

Similar Messages

  • Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

    Objective:
    We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
    to download and upload mail from the old tennant to the new tennant.
    Background: 
    We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
    the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan.  As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
    vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
    After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
    migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
    Environment:
    1 MS AD domain:
    - Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
    - UPN has been changed to [email protected] to allow for ADFS
    - ADFS has been deployed and SSO works for all users with UPN [email protected]
    - An "On-Prem exchange server" does not yet exist
    1 O365 Account where main tennant FQDN is @corp.com
    - There are 5 registered domains
    -contoso.ca
    -corp.com
    - contoso.legacy.ca
    -deprecated/will be deleted
    -deprecated/will be deleted
    - There are 40 E3 licenses, all using a @corp.com UPN
    - There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
    - No accounts currently use contoso.ca for email
    - O365 was upgraded to 'the latest version' sometime in summer 2013.
    Migration Plan (High Level):
    Setup a local windows server (trial license)  
      Deploy an exchange 2013 server (trial license) on the aforementioned windows server  http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
      Prepare and deploy Dirsync Deployment
    of Dirsync
      Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
    More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
    http://help.outlook.com/en-us/140/ff633682.aspx
      Evaluate total time it took to sync data. 
    Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
      Open a new office365 account under the M plan.
      Plan a 1 hour mail & contoso.ca domain login outage
      temporarily change all user UPN's to match the new tennant
      perform a dirsync to the new tennant
      disable dirsync after all accounts have been auto-created/provisioned
      re-establish UPN + mail access.
      Plan a date and time for the cut over.
      remove the exchange hybrid server from the old tennant. 
      Point MX records directly to the exchange server.
      Cut office 365 service.
      After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
    the new tennant
      fix all user UPN's in the cloud to match their real UPN's.
    This can be done with powershell.
      attach exchange hybrid server to new tennant
      Point MX records to the new tennant 
      Migrate all data from the local exchange server to the cloud under the new plan.
    Current progress (Lab):
    I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
    1x Domain Controller (DC) running windows server 2012 (named DC02)
    1x DC running windows server 2008 R2 (named DC01)
    1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
    Where I am stuck / Problem:
    I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected]. 
    After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
    the problem. 
    In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
    1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
    2) If I must add them to exchange, I am provided with three choices: 
    - Authoritative Domain
    - Internal Relay Domain
    - External Relay Domain
    Given that the domain is currently in office365 and is authoritative there, which of these applies?
    3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
    process? Would love it if it took into consideration multiple UPN/email addresses.

    Hi,
    Here are my answers you can refer to:
    1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
    http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
    2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
    To determine it, you can firstly check the function of the three types in the following article:
    http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
    3. Here are some reference about the migration from on-premise Exchange server to Office 365:
    http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
    Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
    http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
    If you have any question, please feel free to let me know.
    thanks,
    Angela Shi
    TechNet Community Support

  • Outlook 2013 - Exchange 2013 - Prompts for username and password when EWS basic authentication is enabled

    So we have an Exchange 2013 environment, and a CRM solution that requires basic authentication to EWS internally.  Problem is, after a reboot of our Exchange server, all of our Outlook clients begin prompting for username and password (which nothing
    works) which also starts locking users AD accounts out due to failed login attempts (somehow).  If I disabled basic authentication on EWS, Outlook authenticates as normal using NTLM and there are no issues.  Once Outlook has authenticated, I can
    turn back on basic authentication, and Outlook will be fine until the next time the Exchange server is rebooted.
    Any ideas?

    Hi,
    According to your description, I understand that Outlook client prompted for username and password when Exchange server restart and basic authentication is enabled for EWS.
    If I misunderstand your concern, please do not hesitate to let me know.
    It’s normal. This caused by the difference between basic authentication and NTML authentication:
    Basic, with any version of Outlook prior to 2010, results in a pop up dialog asking for creds. Outlook 2010 makes the 'save this password' actually work, so in an Outlook 2010 or later world, Basic can mean no need to authenticate every time you open/reconnect,
    but in all earlier versions, you will have to enter creds every time.
    NTLM, when used by a client that is domain joined and logged in with cached creds, results in the client simply sending the cached in creds to the server, resulting in what looks like a pretty seamless single sign on experience. However, if you want to do pre-authentication
    at something like TMG, and not let the traffic go all the way to CAS, you need to configure TMG for this.
    Thanks
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Allen Wang
    TechNet Community Support

  • Exchange 2013 DNS for internal and external domain

    Hi All,
    I have been assigned a task to implement Microsoft Exchange Server 2013. I need some help in setting up DNS namespaces and design a strategy to have same internal and external names. Let me share some details here.
    We have an Active Directory domain myinternaldomain.net, and we have a public domain
    mypublicdomain.com and we have setup email policy to have
    mypublicdomain.com as the SMTP domain for all the users. We have created another DNS zone in Active directory integrated DNS and created a records for
    mail.mypublicdomain.com and autodiscover.mypublicdomain.com which will point to CAS NLB IP. We have 2 CAS servers and 2 MBX servers, we have configured DAG for MBX High availability and planning to implement WNLB for CAS as
    hardware LB is out of scope due to budget constrains.
    We want to have same URLs for OWA, Autodiscover, ECP and other services from internal network as well as from public network. Users should not be bothered to remember two URLs, using one from internal and other from public networks. I also want to confirm
    that with this setup in place do i need to have myinternaldomain.net and server names in SAN certificate?
    Thanks

    Hi Sccmnb,
    You can easily achieve this using split DNS.
    Internal DNS hostname "mail.mypublicdomain.com" will be pointing to your internal CAS NLB IP and the external public DNS hostname"mail.mypublicdomain.com" will be pointing to the Network device or
    Reverse proxy server IP.
    Depending upon users access location(internal\external) the IPs would vary and they should be able to access the website with same name.
    The names that you would require on the certificate(Use EAC or powershell to raise the request) for client connectivity would be
    SN= mail.mypublicdomain.com
    SAN= autodiscover.mypublicdomain.com
    You don't need to have the active directory domain name present in the certificate.
    Additional  to this you need to update the AutodiscoverURI for all servers and OWA,ECP,Autodiscover Virtual Directories InternalURL and ExternalURL fields with appropiate public names.
    Some additional Info:
    *Internal vs. External Namespaces
    Since the release of Exchange 2007, the recommendation is to deploy a split-brain DNS infrastructure for the Internet-based client namespaces. A split-brain DNS infrastructure enables different IP addresses to be returned for a given namespace
    based on where the client resides – if the client is within the internal network, the IP address of the internal load balancer is returned; if the client is external, the IP address of the external gateway/firewall is returned.
    This approach simplifies the end-user experience – users only have to know a single namespace (e.g., mail.contoso.com) to access their data, regardless of where they are connecting. A split-brain DNS infrastructure, also simplifies the configuration of Client
    Access server virtual directories, as the InternalURL and ExternalURL values within the environment can be the same value.
    *Managing Certificates in Exchange Server 2013 (Part 2)
    *Nice step by step article
    Designing a simple namespace for Exchange 2013
    Regards,
    Satyajit
    Please“Vote As Helpful”
    if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Unity Connection 9.1.2 - MS Exchange 2013 support for Single Mailbox?

    Hello,
    we are currently running a unity connection system in version 9.1.2TT1.11900 together with single mailbox enabled with our Exchange server in version 2007.
    We are now planning to upgrade the exchange server to version 2013. From my understanding Exchange 2013 is supported with CUCN 9.1.2 (see http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/design/guide/9xcucdgx/9xcucdg020.html).
    When i go to the configuration screens I cannot choose Exchange 2013 ... Is there a special way to configure this or is 2013 not supported with Unity connection 9.1.2 ?
    any hints ?
    Michael

    Exchange 2013 is supported.
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/connection/9x/unified_messaging/guide/9xcucumgx/9xcucumg020.html#17832
    If you choose to allow Unity Connection to search for Exchange servers, then you need to select from the following two options:
    – Exchange 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2007, Exchange 2010, and Exchange 2013.
    – Exchange 2003, 2007 and/or 2010: Unity Connection can access every mailbox in the Exchange organization consisting of Exchange 2003, Exchange 2007, and Exchange 2010. When the Exchange organization includes Exchange 2003 servers, Unity Connection always communicates directly with the Exchange back-end servers, it never communicates with Exchange front-end servers.
    The drop down does not state 2013 but it will work fine for 2013..

  • Exchange 2013 Certificates for Hybrid Deployment Clarification

     I have an Exchange 2013 servers (CAS and Mailbox on separate server) which I wanted to setup for Hybrid deployment. I already have a certificate acquired from 3rd party with 3 names (mail, autodiscover and owa). the certificate was installed in the
    CAS server. As per the hybrid deployment documentation I need also to install a certificate in the mailbox server, questions:
    1. Can I use the same certificate for installation in the mailbox server?
    2. Can I also use the same certificate in the Hybrid Configuration wizard for the "certificate to use with securing the hybrid mail transport"?
    3. Do I need to include the primary smtp domain (xxxxx.com) in the certificate since current configuration points to the mail.xxx.com as the certificate common name?

    Hi,
    Here are my answers you can refer to:
    1. It depends.
    The certificate used for hybrid secure mail transport must be installed on all on-premises Exchange 2013 Mailbox and Client Access servers.
    If you're configuring a hybrid deployment in an organization that has Exchange servers deployed in multiple Active Directory forests, you must use a separate third-party CA certificate for each Active Directory forest.
    2. Yes. But we recommend that you use a dedicated third-party certificate for any optional AD FS server, another certificate for the Exchange services for your hybrid deployment, and if needed, another certificate on your Exchange servers for other needed
    services or features.
    3. Yes. Here are the minimum suggested FQDNs that should be included on certificates: domain.com, autodiscover.domain.com, edge.domain.com
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/hh563848(v=exchg.150).aspx
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2013 Support for OIM11g

    Guru's,
                    I want to know the OIM11g Support for Exchange 2013 Connector, is any one configured the exchange 2013 with OIM?
    Thanks,
    Caddick.

    Oracle Identity Manager
    You can use one of the following releases of Oracle Identity Manager:
    Oracle Identity Manager 11g Release 1 (11.1.1.5.6) or later
    Oracle Identity Manager 11g Release 2 (11.1.2.0.6) or later
    Target systems
    The target system can be any one or a combination of the following:
    Microsoft Exchange 2007 SP1, SP2, SP3 (64-bit)
    Microsoft Exchange 2010 RTM, SP1, SP2, SP3 (64-bit)
    Microsoft Exchange 2013 RTM (64-bit) For the Exchange 2013 support, Patch 17239236 must be applied on Release 11.1.1.6.0 of the Exchange connector. This Patch can be obtained from My Oracle Support under Patches and Updates.
    Download Exchange-11.1.1.6.0 connector and then Apply patch 17239236 for Exchange 2013

  • Need help regarding the location of Exchange 2013 Logs for parsing

    Hi, I am trying to create reports based on the logs that are created on my exchange server. I am using
    exchange 2013. My problem is that I cannot handle every log, and instead want specific types of logs.
    I need help finding the specific locations of the following types of logs (If they even exist), so that I can parse them and use them effectively:
    Audit Logs (Mailbox logons, Mailbox permission changes, Mailbox property changes,
    Exchange store changes)
    Mail Report Logs (Mailbox size and growth, Mailbox storage growth, Enabled users, Expired and Soon-to-Expire Mailboxes)
    Exchange Traffic Reports (Details on size and amount of messages sent and recieved, Internet traffic [to and from], Traffic between exchange users)
    I understand this might sound like a huge undertaking, but any help that can be provided would be appreciated.
    Again, I need information on the locations of these types of logs on the exchange server, so that I can parse them. Collecting them all and searching through them is not practical for my available resources.
    Thanks,
    Matt

    Audit Logs (Mailbox logons, Mailbox permission
    changes, Mailbox property changes, Exchange
    store changes) ---- these are two type of logs, 1. mailbox audit logs and that is stored in each mailbox under dumpster
    http://technet.microsoft.com/en-us/library/ff461930(v=exchg.150).aspx however you need to
    enable
    it for individual mailboxes... 2. admin audit log, this is stored into a system mailbox dumpster.... http://technet.microsoft.com/en-us/library/dd335052(v=exchg.141).aspx
    Mail Report Logs (Mailbox size and growth, Mailbox
    storage growth, Enabled users, Expired and Soon-to-Expire Mailboxes) ---- there isn't any specific log for this, you would need to create some time of script to collect this every day for you and store it somewhere... This is a good start... http://www.stevieg.org/2011/06/exchange-environment-report/
    Exchange Traffic Reports (Details on size and
    amount of messages sent and recieved, Internet traffic [to and from], Traffic between exchange users) ----- This you can get from message tracking log... http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx

  • Outlook Clients for Exchange 2013 Prompt for Password

    I have a co-existence of versions 2007 and Exchange Server 2013 CU2 and currently have the following problem: 
    - Customers now where I performed the migration to the 2013 version, when starting Outlook is always asking for password. The settings for Outlook Anywhere are as follows: 
    RunspaceId                         : b43cd829-a81f-4b00-bb4d-73389c9df50d
    ServerName                         : EXCH-HTCA13
    SSLOffloading                      : False
    ExternalHostname                   : webmail.first.pt
    InternalHostname                   : exch-htca13.first.pt
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    XropUrl                            :
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : True
    Can anyone help me identify the problem?

    Hi,
    Agree with Andy,you can change the ExternalClientAuthenticationMethod to NTLM,
    In addition, I recommend you refer to the following article:
    Users Constantly Prompted for Credentials after Being Migrated to Exchange 2013
    Thanks.
    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.
    Niko Cheng
    TechNet Community Support

  • Where is exchange 2013 SDK for transport agent?

    I am upgrading my transport agent to exchange 2013.  
    I remember when I build the agent for 2010, it requires exchange 2010 SDK.
    I search around But I can not find exchange 2013, neither from download.microsoft.com nor msdn.microsoft.com
    Would anyone provide a link?

    There you go..
    http://blogs.technet.com/b/omers/archive/2013/01/22/how-to-write-an-exchange-2013-transport-agent.aspx
    http://blogs.technet.com/b/exchange/archive/2013/01/21/how-to-write-an-exchange-2013-transport-agent.aspx
    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.

  • Best Mac Pro (2013) configuration for photo editing/processing?

    Hi all,
    I couldn't find a reliable answer to this in my searching here or on google, hence I'm posting it here.
    I'm going to buy and upgrade to the new mac pro when it's announced this month (Dec 2013).  My primary use will be photo processing in photoshop.
    Configuring it with 64gb RAM is the no-brainer part. And probably a 512gb or 1TB flash drive too.
    The bit I'm unsure about is whether to opt for the 6 core processor option over the quad core?  For photo editing (adding layers, filters, brushing in, multiple files open at times, running batch edits etc), does anyone have an opinion on whether the performance increase (if there is in fact any increase for photo work?) of the 6 core 3.5ghz would justify paying the extra AU$1300 difference over the quad core 3.7ghz option?
    And from my earlier research paying the huge prices for 8 or 12 cores would simply be a waste for photo processing.
    Thanks for the advice...

    Mozzzaaa
    I have the exact same requirements, here are my findings based on some observations from Activity Monitor and research based on how the hardware works.
    Photoshop does not utilize multiple cores well for many standard editing ativities - therefore one core will be busy while the rest remain idle, however I have noticed over time that upgrades to Photoshop seem to take more advantage of multiple cores as Adobe updates the code. For example, appling filters utilize all of the cores while the filters are computing changes (smart sharpen for example).  Try running CPU monitoring in Activity Monitor (double click the CPU graph to display all cores).
    Lightroom utilizes all of the cores for Import, export and other activities that process multiple files.  Being more modern code, it beter utilizes muti cores.
    Keep in mind that each core handles two code threads, therefore a four core system is capable of processing 8 "streams" of code, the 6 core can manage 12 threads, etc.  
    Here is a screen shot of Mac Book Pro running PS CC Smart Sharpen:
    All the new Mac Pro run at 3.9Hz Turbo Boost - they are all the same in that respect.  This means that when the processers are not hot, at least one core will run at 3.9Hz - therefore on a relativly idle machine (just editing in PS for example) you would likley be running at 3.9Hz on all the Mac Pro 2013.
    There are also the GPUs to consider.  Apple as usual has not made enough information available to easly determine the cost benefits of the more powerful GPUs and I don't know if PS would utiliize the AMD GPUs well now,  or perhaps better utilize them for the future.  Perhaps someone could comment on that.  Here is an interesting article: http://architosh.com/2013/10/the-mac-pro-so-whats-a-d300-d500-and-d700-anyway-we -have-answers/
    Clearly the D500 that is standard with the 6 core seems a major bump over the 4 core D300 (therefore the costs of the 6 core reflect that).  I don't know how much the D700 would cost - it would be helpful if this were published so I could consider my order.
    There are two GPU in the new Mac Pros - but the purpose of the second one is not toally clear (thanks again to Apples's communication).  It likley will be utilized for all sorts of things that don't really exist now and FCP X is scheduled for a new release better utilize the GPU for video (as nwaphoto mentioned video processing will be a major use of this equipment).
    I was interested in your comment regarding 64 Meg ram.  Yes that would be a hudge boost to PS performance, but would it be better to purchase from Apple or wait for OWC who offer RAM at major discounts over Apple.  Once again, no info yet that I am aware of.
    I believe the flash drive is upgradable but rumor has it that it uses a proprietary connecter. Makes me want to go with the largest size but once again OWC might be the way to go for an upgrade in a year or two.
    In the past, the 6 core 2012 Mac Pro's were somewhat of a sweat spot in terms of horsepower vs cost.  I will be considering that in my decession to upgrade. So I am considering a 6 core,  will check out the Ram and Flash diIsk based on price - which is the infor I don't have.  If you have anything please post
    Thanks

  • Exchange 2013 - Location for SMTP Receive Connector verbose logs

    So I'm trying to troubleshoot a relay failure:
    + 1415809433 51000008 Wed Nov 12 11:23:53 2014
    F:[email protected]
    T:[email protected]
    A:c:\v1\temp\200046.pdf
    S:Sales Order Number  200046
    ! Error in SMTP conversation:
      550 5.7.1 Unable to relay
      dbmailsend error 8 (Error in SMTP conversation).
    ! Command-line dump follows (delimited by colons):
      [0]:c:\v1\dbmail\bin\dbmailsend:
      [1]:-vv:
      [2]:-a:
      [3]:c:\v1\temp\200046.pdf:
      [4]:-s:
      [5]:Sales Order Number  200046:
      [6]:-t:
      [7]:[email protected]
      [8]:-r:
      [9]:[email protected]
      [10]:-h:
      [11]:C:\Users\sagert\AppData\Local\Temp\dbf72A3.tmp:
    ! Error in SMTP conversation:
      451 4.7.0 Temporary server error. Please try again later. PRX5
      dbmailsend error 8 (Error in SMTP conversation).
    ! Unable to send report to administrator.
    Note the SMTP Converstion error, I've done the steps in this forum article:
    https://social.technet.microsoft.com/Forums/fr-FR/fc26dac5-d4e2-49da-903d-361ea8b85388/451-470-temporary-server-error-please-try-again-later-prx5?forum=exchangesvrgeneral
    but the issue still exists... so I need to review my Exchange logs for this relay (I've enabled verbose logging on the specific receive connector this should be using)

    Fromhttp://technet.microsoft.com/en-us/library/bb125140(v=exchg.150).aspx
    Set-ReceiveConnector
    The location of the Receive connector protocol logs for all Receive connectors configured in the Transport service on a Mailbox server or an Edge server is specified by using the Set-TransportService cmdlet with the ReceiveProtocolLogPath parameter.
    Run a get-transportservice|fl *logpath* and that should get you what you need.

  • Exchange 2013 / 2013 Coexistence - OWA rendering on 2010 CAS for 2013 Mailbox

    So I'm running Exchange 2013 CU2v2 alongside Exchange 2010 SP3 (both on top of 2008 R2 SP1) and I'm having a bit of a weird thing happen when migrating test users from Exchange 2010 to 2013. 
    After migrating a user from a database on the 2010 server to a database on the 2013 server, when you access OWA (through a url pointing at the 2013 server), it still appears to render on the 2010 CAS (and functions normally). If you click ? > About it
    shows properly that the mailbox server is the 2013 server, but the host address and client access server are still the old 2010 server. It seems that after a few hours it fixes itself. ECP, however, renders properly on the 2013 server immediately after migration.
    The migration completes successfully with no errors, and outlook connects fine after migration, hitting the 2013 CAS.
    I thought maybe this had to do with the Exchange Information Systems Cache, as in 2010 this was occasionally an issue:
    http://www.terminal.com/blog/bid/70313/Moving-Mailboxes-During-an-Exchange-Migration
    but the mailbox will still render on the 2010 CAS even after restarting the ExchangeIS service.
    I should also note that this behavior DID NOT occur with Exchange 2013 CU1 alongside 2010, and only started happening after upgrading to CU2v2.
    Does anyone have any thoughts as to why this is happening and what I can do to make it transition quickly to render OWA against the new mailbox? Thanks!

    Exact same symptoms here;
    Single site, 1 Exchange 2013 CU3 on 2012 Server, 1 Exchange 2010 SP3 as source for migration;
    Exchange 2013 configured as external access 'cas' owa etc. and proxy to 2010.
    Accessing an 2010 mailbox thu 2013 works correctly (OWA, ECP, ActiveSync, Outlook Anywhere etc.)
    Created new mailbox on 2010, migrated to 2013 and this mailbox is accessed/proxied thru OWA 2010. Strangely this mailbox is hosted on the proxying 2013 server now but still gets proxied. ECP for this user does instantly connect to the correct 2013 server.
    The 2010 OWA connecting to 2013 mailbox server: help | about:
    Host address: https://ex2010.corp.local/owa
    Version: 14.3.174.1
    Proxy host address: https://ex2013/owa
    Proxy version: 15.0.775.0
    Proxy server name: ex2013
    S/MIME control: not installed
    Exchange Client Access server name: ex2010.corp.local
    Exchange Client Access server .NET Framework version: 2.0.50727.5472
    Client Access server version: 14.3.123.0
    Client Access server platform: 64bit
    Mailbox server name: ex2013.corp.local
    Mailbox server Microsoft Exchange version: 15.0.775.0
    Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
    Authentication type associated with this Outlook Web App session: Basic
    Authentication type for Exchange Client Access server to Client Access server proxy session: Negotiate
    Public logon: Yes
    So to me is that the 2013 server is still proxying to 2010 and the 2010 CAS is accessing the mailbox on 2013 ;).
    This even when the mailbox is moved on the 2013 server itself!!
    How strange is this?!
    Regards,
    Arian van der Pijl
    Hello!

  • Creating a New Email address policy for users in another Domain with Exchange 2013 powershell?

    Hi
    Everyone
    Is it possible to create a new-emailaddress policy with Exchange
    2013 Powershell, for users within OU´s located on another different
    domain/forest than where Exchange 2013 is installed?
    There
    is a Transitive, two way trust between the domain/forest where the users are
    located - and the Exchange 2013, multi tenant domain.
    Further
    more, and if possible, I need to create linked mailboxes to all these users as
    well.
    Í have been struckling with this issue for weeks, so please anyone -
    advice - and comment.
    Best
    Regards
    Peter
    A-ONE Solutions

    Hi Siddharth
    I want to create a new e-mailaaddress policy - and after that create linked mailboxes/users in my account domain with powershell.
    Can you help me achieve that ?
    I have a powershell CMDlet, but i doesn´t work. (Cannot fint user OU in my account domain)
    CMDlet is as follows:
    New-EmailAddressPolicy -Name $CustomerName   -RecipientContainer "OU=$CustomerName, OU=kunder, DC=Domain, DC=local" -IncludedRecipients 'AllRecipients' -ConditionalCustomAttribute1 $CustomerName -Priority '1' -EnabledEmailAddressTemplates SMTP:%2g%1s@$AcceptedEmailDomain
    Where $Customername = test.dk
    and Account domain is = OU=kunder, DC=Domain, DC=local
    But the command fails with:
    New-EmailAddressPolicy : Couldn't find organizational unit "OU=Test.dk, OU=kunder, DC=Domain, DC=local". Make sure you have typed the name correctly.
    At line:52 char:1
    + New-EmailAddressPolicy -Name $CustomerName   -RecipientContainer "OU=$CustomerNa
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [New-EmailAddressPolicy], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : [Server=HE-MBX03,RequestId=2cbe1b51-4af2-4c04-9f7e-e440000975e6,TimeStamp=24-03-2014 12:58:19] 2D00FD2A,Mi 
       crosoft.Exchange.Management.SystemConfigurationTasks.NewEmailAddressPolicy
    So, I cannot find the OU on the Account forest/Domain, even though the OU do exists in the Account domain. 
    Verifying with this: 
    Get-ADOrganizationalUnit -Identity "OU=$CustomerName,OU=kunder,DC=Domain,DC=local" –Server ‘DC01.domain.local’| FL
    This works fine, Can you please help/assist?
    Peter

  • Exchange 2013 Site Resilience - Basic questions for setup in two seperate AD Sites, same domain

    I am just getting ramped up with Exchange 2013 and have a friend that I am assisting with planning an exchange 2013 deployment for.  I am not asking for step by step directions for setup, just asking for a basic overview so I can dig in to this and
    assist.
    Goal is to have an exchange server, one in NC and one in Switzerland in an active/passive mode for site resilience.  Both servers will be multi role servers. 
    This is a small organization, less than 50 users and on a budget for equipment.  HQ is in NC and the server will have all roles installed on a single server. Switzerland will have only one Exchange server for fail over.  There is only
    one domain total with two AD Sites. 
    My questions for clarity -
    1. Can I create a Site resilient deployment with two Exchange Multi Role servers in these locations?
    2. Currently, the organization does not have a Load Balancer.  Will this be required? 
    3. They do not have a third location for a Witness Server, what issues could potentially happen if the witness sits in one of the two sites?
    4. Any other basics for this design are much appreciated.  I am reading a lot, however a little confused as I read through the requirements.
    Thanks for your input and direction!
    Wall

    Hi
    Please find below answers to your questions.
    1. Can I create a Site resilient deployment with two Exchange Multi Role servers in these locations?
    Yes
    2. Currently, the organization does not have a Load Balancer.  Will this be required? 
    No you don't need to have a load balancer. As you are setting up the infrastructure in Active / Passive mode you don't need a dedicated LB for this.
    3. They do not have a third location for a Witness Server, what issues could potentially happen if the witness sits in one of the two sites?
    The issue with the witness server in primary or DR site is if your witness server is not responding your DAG won't work properly (failover). If you don't have a 3rd site then you can setup a witness server in your primary site and Alternate witness server
    to your DR site.
    4. Any other basics for this design are much appreciated.  I am reading a lot, however a little confused as I read through the requirements.
    I would recommend to use Exchange sizing calculator and technet is the best resource for you :)
    Kindly mark this as answer if it fulfill your requirements. :)
    Regards, Riaz Javed Butt Consultant Microsoft Professional Services MCITP, MCITP (Exchange), MCSE: Messaging, MCITP Office 365

Maybe you are looking for