Outlook 2010 appointment with exchange 2003 - organizer question

Hi Sir / Madam,
I have a exchange 2003 server and containing confernece room mailbox. The conference room mailbox is
same as a normal user mailbox since exchange 2003 don't has resource booking feature. And I have following
issue need to be fixed and don't know if this possible for my environment.
Each user can create the appointment in the conference room's calendar but when they select conference room
as resource (location), when all other users open that appointment, then will see the organizer name is conference
room, only the creator can see the appointment was created by himself/herself. I found that if the creator leave
the resource as blank, all users can see the correct organize name.
Anyone know how to fix this issue? Thx
Jeffrey

Hi Jeffrey,
According to your posting, I noticed that each user can create the appointment or meeting in the conference room’s calendar. If so, please check if the Default Calendar permission of this room Calendar is set to Author or higher permission.
Generally, if the user creates the calendar items directly from a room’s calendar instead of creating meeting request and sending it to this room, the Organizer name would not be shown as the creator.
Therefore, it is not recommended to directly create meeting request in a room’s calendar. Please create meeting requests in the organizer’s calendar and add the room as a resource, then send the meeting request to the room and attendees. Now check whether
the organizer is shown correctly.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

  • Outlook 2010/2007 with Exchange 2010 - show email address in field To: instead name

    Hi,
    I´ve SBS 2011. Some users have more email aliases. I want to see in Outlook email adress/alias in field To: <- no user Name and Surname. I know, that I can open every message and go to Options and see full header, where is email adress, but I want
    to see it on message preview in Outlook window (or Name Surname ([email protected]))
    Thank you very much for your responses.

    I think this is not what he was looking for. The link you provided is for showing the senders smtp address and not the recipients. as i understand it, hes looking for the same that i do.
    user has multiple smtp addresses and user wants to be able to see to which of his own addresses the mails has been sent.
    im looking for that solution to show recipients smtp address in the To:-Field when showing the email
    as i unterstand it, there could not be a registry-value for outlook because exchange isnt using the smtp address internaly to deliver the email.
    the only "Simple" Solution/Workaround i found is to use a distribution group with the smtp address you want to see and only add the specific user. then the user is able to see the Name of the Distribution Group instead of his own name so
    hes able to differ.
    thanks

  • Outlook 2013 won't start with Exchange 2003 on the network

    Hello All,
    I have outlined my problem below,  If someone could please help me that would be great!
    Environment
    ==========
    SBS 2003 Server Running AD and Exchange 2003
    Clients are Windows 7 with Office 2013 and Outlook 2007 (to connect to existing 2003 Server)
    Issue
    =====
    I am in the process of Migrating off of SBS 2003 to Office 365.  The situation is that my customer needs to keep the SBS 2003 server until end of life where they will at that time determine a upgrade path.  They however do not want to use Exchange
    anymore.    I have migrated their mailboxes successfully to Office 365.
    The problem that I am running into is with Outlook 2013.  Because Exchange 2003 server still exists in the network I am unable to launch Outlook 2013.  I get a Message
    "The Resource that you are trying to use is located on an unsupported version of Microsoft Exchange Contact your e-mail administrator for assistance"
    I have tried to create a new Outlook profile.  However since the exchange server exists still it auto discovers the server for the account. 
    Questions
    ========
    1.  What is the best workaround for this situation?  My customer still needs to keep their SBS sever for their domain and plans on retiring the server before Server 2003 End of Life this coming server.  (Upgrade is not an option, nor is getting
    rid of the Domain, they are a small company).
    2.  If I disabled the Exchange services on the server would this work?  Would outlook 2013 not detect Exchange
    2003 on the network?
    Basically I need to force Outlook 2013 to look at Office 365.  
    3.  Configuring Outlook 2013 to manually connect to Office 365?  The problem here is that how do I locate the server name for the manually connection?  I have found some blogs that say to use Remote Connectivity Analyzer https://testconnectivity.microsoft.com/
     but I cant seem to get that to work. 
    Any ideas?
    Thanks!

    Hi,
    Please refer to the following article to check your migration steps from Exchange 2003 to Office 365:
    http://blogs.technet.com/b/canitpro/archive/2013/05/31/step-by-step-migration-of-exchange-2003-server-to-office-365.aspx
    If all mailboxes are moved to Office 365, Outlook 2013 would use Autodiscover service to connect to your Office 365. Please make sure your Autodiscover service is configured correctly in Office 365. Also
    verify that all the DNS records and Public Folder are updated and pointed towards Office 365 services. If there is any question about migration to Office 365,
    we can ask a question in Exchange Online forum for more suggestion:
    https://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
    Regards,
    Winnie Liang
    TechNet Community Support

  • Outlook 2013 not compatible with Exchange 2003

    Hello
    Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
    clients to 2013 version.
    Microsoft, is this correct?!

    If this post is hard to read, it's because of Dragonsoft!!  (sometimes it is like auto-correct on the phone - "I said WHAT!??")
    Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
    As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
    When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
    So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
    The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
    The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
    Windows for which they are named.  So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
    made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
    package which could handle the intricacies of the licensing limitations on the SBS system.
    SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
    and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
    My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version.  You must purchase a new server, install the new SBS version, and migrate your
    entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!)  The whole process is rather daunting as not
    all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
    So off we went with our new installation of SBS 2003 R2.  Then along came SBS 2008!  I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
    When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I  fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
    nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware.  (I was not going to get stuck in a hardware box that I could not replace
    if I ever needed to restore the operating system due to a massive failure.)  So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
    Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
    on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
    that they modified, and even performed a little cleanup, after they performed their cleanup!  I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
    Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
    Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false!  I live in Texas, and the state of Texas DIR program has adopted standards which state that
    you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional!  Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
    from, anyway?)
    One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
    Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
    any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
    The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs. 
    I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
    A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
    having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
    If you allow a client to be painted in a corner, then it's not their fault, it's your fault!  Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
    expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
    If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
    they are unwilling to spend money.  You don't work for free.
    One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well.  I put it like this, "You pay me to make certain that your business operates in good times and in
    bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully.  The equipment that we have operating here is no longer
    available on the market.  If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
    I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
    can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
    where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
    It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years.  We don't want to patch this together
    and always have problems."
    And just as a note, your customer can write off $10,000+ per year for new equipment purchases.  I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
    a month later, in the next year!

  • Outlook 2010 Syncing With iPod Touch and iPad

    I have a PC with Outlook 2003 that sync’s with iPod Touch and iPad. I plan to buy a new PC with Windows 7 and Outlook 2010. Comcast tells me they don’t support Outlook (They support Outlook Express) but Outlook 2003 currently works fine on my PC with Windows XP. I have the following questions:
    - . Is there an alternative to Outlook 2010 that will sync with my iPod Touch and iPad?
    - Will Outlook Express sync with my iPod Touch and iPad and is Outlook Express still available?
    - What is Microsoft Exchange?
    Thanks for your help. LCP

    Just look at page 26 of the new US) users guide. It specifically says that the iPad syncs with Outlook 2010 (as well as 2003 and 2007). However, Comcast's mail help page only lists OL 2000, 2002, 2003 and 2007.
    http://customer.comcast.com/Pages/FAQListViewer.aspx?topic=Internet&folder=b2aa4 a3a-53eb-4730-832f-89764b6a03b9

  • Exchange 2010 deployment in Exchange 2003 Environment

    Hello,
    I have recently installed Exchange 2010 in an Exchange 2003 environment.  I need some help migrating all my settings over to Exchange 2010
    -- mailboxes, recipient policies, offline address book, free/busy, etc.
    I have looked at these following TechNet sheets for assistance, but getting a bit confused:
    http://technet.microsoft.com/en-us/library/aa996719.aspx (Exchange 2013 System
    Requirements)http://technet.microsoft.com/en-us/library/ee332348.aspx (Upgrade
    from Exchange 2003 Client Access)http://technet.microsoft.com/en-us/library/aa998186.aspx
    (Exchange 2003 - Planning Roadmap for Upgrade and Coexistence)http://technet.microsoft.com/en-us/library/ee681662.aspx (Install
    Exchange 2010 in a Mixed Exchange 2003 and Exchange 2007 Organization)
    I have two domain controllers.  Exchange 2010 is not installed on a DC, but Exchange 2003 is on one of them.  I want to eventually decommission
    the Exchange 2003 environment and implement and Edge Server in its place.  Exchange 2010 is installed on a Virtual Machine.  It's running SP3, the latest service pack.  Exchange 2003 is on a physical machine and it's running SP2.
    Please help me simplify what exactly I need to do to migrate 2003 configurations over to 2010.
    Thank you for you much appreciated assistance.

    Hi
    I would install a new DC and seize the MSO roles to the highest server. Remember you can install server 2012 but not R2 yet.
    You can setup your connectors on exchange 2010 to send/receive mail to the internet. make sure your ISP allows the new server.
    You can also setup a routing group connector so that mail flows from EX2003 to EX2010 and vice versa during your transition period.
    Remember to replicate your public folders to the new server and if you have a lot of data be patient. Once you happy with everthing then decomission the old DC.
    Hello,
    All FSMO roles are transferred (not seized) on my Windows 2008 R2 Standard Domain Controller.  I transferred all the roles off my Windows 2003 Domain Controller.  The W2K3 DC is also my Exchange Server 2003 SP2.  I specifically did not want to
    install Exchange 2010 on a DC.  It's on its own member server.
    Should I make the Exchange 2003 Server a Front-End Server when I create a routing group for mail flow to Exchange 2010?  I want to eventually implement an Edge.  Also, can I have mail flow from the Internet directly to the Hub and bypass the Exchange
    2003 mail flow?

  • Can i change my Exchange 2003 organization to NATIVE MODE if my Front-End Exchange server is Windows 2000 Server

    I am planing to upgrade from exchange server 2003 to exchange server 2010. I understand 2010 can co-exisist with 2003, but my 2003 organization must be in NATIVE MODE, not a problem because i don't have anymore MS Server 2000 domain controllers, they
    were decommisioned a few moths after we moved to AD. However my Front-End exchange server that sits on my DMZ is running Exchange server 2003 on Windows 2000 Server.
    Can i change my Exchange 2003 organization to NATIVE MODE if my Front-End Exchange server is on the Windows 2000 Server OS? If not, will i have to setup a new Front-End Exchange server on at least Windows Server 2003 to replace the 2000 server setup?
    It's been a very long time since these servers were configured so i may need help setting up a new Front-End server if it will be required.
    thanks
    B
    Bobby

    My apologies for the very, very late reply, is have made the change to native mode for my
    Exchange environment, email is working fine, no problems. Thanks Cheng.<o:p></o:p>
    I ran the Exchange 2010 Pre-Deployment Analyzer tool yesterday, and it showed that the
    Active Directoy Forest is not Windows Server 2003 native. The domain forest
    functional level showed the level to be "Windows Server 2003", is
    just wanted to verify this.<o:p></o:p>
    Our corporate AD has one Root domain, (I’ll call it, Corp.com) and one child
    domain, (I’ll call it, na.corp.com). na.corp.com is functioning at Server 2003,
    the Forest of Corp.com, as the analyzer found, shows a functional level of
    Windows 2000. All Windows 2000 PDC have been off the network for almost 9
    years, and were properly demoted and removed. I guess the one place is didn't
    look was at the Forest level.<o:p></o:p>
    I opened the AD Sites and Service mmc plugin on the corp.com server and did find the old
    Windows 2000 PDC listed with the Servers. I drilled down into the containers
    for the old server, deleted everything, and was able to delete the W2K PDC. I
    still cannot raise the Forest level however.<o:p></o:p>
    I also noticed that domain replication has errors, (8614, 1908, 1256, and 8606), so i
    have a bit of a mess, and i am not sure how to fix it. I will post this on the
    Exchange 2010 upgrade, and AD forums for assistance, but i wonder if i need
    paid assistance.<o:p></o:p>
    Thanks again Cheng
    B<o:p></o:p>
    Bobby

  • Require Passcode Immediately with Exchange 2003 and iPhone 3.0?

    Before I upgraded to iPhone 3.0 I was syncing with Exchange 2003 SP2 and I had set my passcode to be required after 1 hour, which was changed from the default of 4 hours. On the Exchange server we have a policy in place to have a max of 12 hours before a passcode is required which works on my WM phones.
    After upgrading to 3.0, the phone now immediately requires a passcode every time I turn it on. I went into the settings to change it to be a little longer, but the only option is to have it Immediately and I have lost all of the other options. Is there a way to get back at least 1 hour or something that reflects the 12 hour setting on my Exchange server?

    I can confirm that you just need to turn OFF Mail, Contacts and Calendar sync within the Exchange account, set the timeout 4 hours (or whatever - it will automatically shrink down if your Exchaange administrator's policy is more restrictive), and then turn back ON Mail, Contacts and Calendar sync.
    Note you'll get a scary warning that says all your Contacts and Calendar data will be deleted from the phone - Outlook users can ignore if you're syncing with Outlook, since it will re-sync when done.

  • Uninstall/Reinstall Exchange 2010 in coexisting Exchange 2003

    Hi,
    Can we uninstall Exchange 2010 without any affect to Exchange 2003 in the co-existing environment?  I installed Exchange 2010 in existing Exchange 2003 and tried to configure for both Exchange exist in our domain.   Somehow the Exchange 2010 crashed
    and now it cannot start, only stuck in Initializing process.  I want to uninstall and then reinstall but I don't know if doing this will cause any problem to the Existing Exchange 2003.  Could someone tell me?
    Thanks,
    Jim

    You don't have to uninstall and reinstall server, just rebuild base server with OS with what it had earlier and recover Exchange 2010 with /m:recoverserver switch.
    Recover an Exchange Server
    I assume you still have Exchange 2010 database backup or original files for restore if needed and this is just OS crash and can not be repaired scenario
    Blog:
    http://exchangeshare.wordpress.com/

  • Is it possible to sync with both my win 7 computer (Outlook 2010), and with iCloud, without duplicating contacts and appointments? thanks.

    Is it possible to sync with both my win 7 computer (Outlook 2010), and with iCloud, without duplicating contacts and appointments? thanks.

    Hey keiichi-san,
    Yes, It is possible. You can merge contacts, calendars, and bookmarks between multiple computers.
    When you sync the contacts and calendars to your iPhone from the new computer you'll see the option to Merge or Replace, just choose Merge.
    These articles provide more information on syncing options:
    http://docs.info.apple.com/article.html?artnum=306071
    http://docs.info.apple.com/article.html?artnum=305741
    Jason

  • I have three iphones that synchronize with outlook 2010,each with a different profile.Two of them, running ios4.3 succesfully update contacts with the apropriate profile of windows/outlook (which is open at the time). The third iphone using ios 5.1 will a

    I have three iphones that synchronize with outlook 2010,each with a different profile.Two of them, running ios4.3 succesfully update contacts with the apropriate profile of windows/outlook (which is open at the time). The third iphone using ios 5.1 will always sync contacts with the admin account, regardless of the win/outlook account being open.

    I have three iphones that synchronize with outlook 2010,each with a different profile.Two of them, running ios4.3 succesfully update contacts with the apropriate profile of windows/outlook (which is open at the time). The third iphone using ios 5.1 will always sync contacts with the admin account, regardless of the win/outlook account being open.

  • Will Microsoft Exchange2000 Portlet work with Exchange 2003

    Hi All,
    Has anyone tried using Microsoft Exchange2000 Portlet with Exchange 2003 ? Or is there any Portlet available for Exchange 2003 ?
    Thanks in Advance.
    Dipak

    I'm facing problem with Exchange 2003 portlet which is not working with all users. it's working good only with the one user. I mean it doesn't allow the other users to put there user name & Password .
    Please help me with this portlet or is there other portlet for exchange 2003
    Thanks
    Waleed

  • Setting Out Of Office from Outlook not working with exchange 2010

    Hi 
    We have an exchange 2010  server with 2 load balanced CAS server and Mailbox servers in a DAG.  We have a few domain
    names accepted (will call it firstdomain.com and seconddomain.com)  but only one is in certificate (firstdomain.com).
    The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service
    packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later”  where
    setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.
    we have both internal and external urls for all virtual directories set to external
    host address (https://mail.firstdomain.com
      etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.
    Autodiscover works fine (tested in outlook ) and giving correct address for OOF link
    ( https://mail.firstdomain.com/ews/exchange.asmx)
    wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .
    I enabled  logging in outlook and thats what I am getting in there:
    We have an exchange 2010  server with 2 load balanced CAS server and Mailbox servers in a DAG.  We have a few domain
    name accepted (will call it firstdomain.com and seconddomain.com)  but only one is in certificate (firstdomain.com).
    The issue is - when user with default email @seconddomain.com try to set “Out Of Office” from outlook (2010 with all service
    packs and updates) he is getting “ Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later”  where
    setting it from webmail works fine and setting it from outlook for users with @firstdomain.com reply address works fine.
    we have both internal and external urls for all virtual directories set to external
    host address (https://mail.firstdomain.com
      etc). All the users are on intranet with local ip subnets (sites connected via vpns ), all the routing is in place and DNS points to correct ip addresses.
    Autodiscover works fine (tested in outlook ) and giving correct address for OOF link
    ( https://mail.firstdomain.com/ews/exchange.asmx)
    wich opens fine if entered into address bar in IE so its NOT AN AUTODISCOVER issue .
    I enabled  logging in outlook and thats what I am getting in there:
    1600       0x49763D20        02/02/15 16:50:44           
    +++++++++++++++++++++++++++++++
    1600       0x49763D20        02/02/15 16:50:44           
    OWINHTTP SEND HTTP REQUEST BEGIN
    1600       0x49763D20        02/02/15 16:50:44           
      Profile=Outlook
    1600       0x49763D20        02/02/15 16:50:44           
      [email protected]
    1600       0x49763D20        02/02/15 16:50:44           
      URL=https://mail.firstdomain.com/ews/exchange.asmx
    1600       0x49763D5F        02/02/15 16:50:45           
    GetLastError=0; httpStatus=401.
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHtpp disabled auth schemes:
    1600       0x49763D5F        02/02/15 16:50:45           
    <NONE>
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHtpp supported auth schemes:
    1600       0x49763D5F        02/02/15 16:50:45           
    Negotiate
    1600       0x49763D5F        02/02/15 16:50:45           
    NTLM
    1600       0x49763D5F        02/02/15 16:50:45           
    Basic
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHttp attempting Auto-Negotiate with Desktop Credentials.
    1600       0x49763D5F        02/02/15 16:50:45           
    OWinHttp USING pcreds->dwAuthScheme:
    1600       0x49763D5F        02/02/15 16:50:45           
    Negotiate
    1600       0x49763D9D       02/02/15 16:50:45           
    GetLastError=0; httpStatus=500.
    1600       0x49763DAD       02/02/15 16:50:45           
    OWINHTTP SEND HTTP REQUEST END
    1600       0x49763DAD       02/02/15 16:50:45           
    Last thing - we are using proxy server and with proxy off it works fine although all
    possible exchange server hosts/domains/ip addresses excluded from proxy.  
    Aside from obvious question - what can be wrong and what to test next, another question
    is - how can I check/monitor setting OOF on server side (log files etc)?
    Last thing - we are using proxy server and with proxy off it works fine although all
    possible exchange server hosts/domains/ip addresses excluded from proxy.  
    Aside from obvious question - what can be wrong and what to test next, another question
    is - how can I check/monitor setting OOF on server side (log files etc)?
    Thanks

    Hi,
    According to your description, I understand that Outlook client with second domain name cannot use OOF setting and get an error “Your Out of Office settings cannot be displayed, because the server is currently unavailable.”  However OWA works fine.
    If I misunderstand your concern, please do not hesitate to let me know.
    I want to double confirm whether all account or some special user experience this question.
    Would you please try to reconfigure Outlook profile in other Computer, Outlook version and return the results?
    If this issue only appeared on Outlook 2010, please refer to below link to troubleshooting:
    https://support.microsoft.com/kb/2596516?wa=wsignin1.0
    Please try to run ExBPA to test OOF to get more details about this question. Additional, I find a similar thread about your question, for your reference:
    https://social.technet.microsoft.com/Forums/exchange/en-US/81ebc1de-c899-4097-b224-a0e4b33e4162/users-cant-open-out-of-office-assistant
    Best Regards,
    Allen Wang

  • Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

    Dear All,
    I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
    The 2013 environment are:-
    2 X CAS server with MS NLB configured
    2X MBX server with DA
    Internal NLB/licent access: excas2013.int.my.domain
    External access (current set on 2010 as well): webmail.my.domain
    Certificate with valid subject name has been import to 2013 and 2010:
    CN: webmail.mydomain
    SAN: excas2013.int.my.domain
    SAN: excas.int.my.domain (for 2010)
    I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
    the process looks good:-
    Establish network connection (checked)
    Searching for [email protected] server settings (checked)
    Log on to server
    The process stop at "Log on to server" and a windows prompt, saying:
    The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
    Clicked OK, I can see:-
    MS Exchange Server:
    [email protected]
    Mailbox:
    =SMPT:[email protected]
    WHen I click "Check Name", it said The name cannot be resolved.
    I have no idea of what is going on. Just want some help~

    I have checked the iis log:-
    2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
    2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
    15
    2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
    2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
    2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
    2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
    80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 64 78
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 109
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 64 15
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 31
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    15
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 0 15
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 46
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
    0
    2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
    MSRPC 404 0 0 31
    2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
    MSRPC 200 0 64 46

  • Configure new exchange 2010 while old exchange 2003 running ?

    Hello,
    I'm in the process of deploying a new fresh installation of SBS 2011/Exchange 2010 server. Currently
    I have SBS2003/Exchange 2003 running. I want to retired the server and replace with the new server. No migration. By doing that, I am setting up the new server SBS2011 name/domain/ip everything the same as the old server and will replace once all the configuration
    is completed.
    1. Since they both using the same domainname/ip, can I setup the new server Exchange 2011 while the old
    server is alive? If yes, how's the process?
    2. If I export and import users email in .pst (on user outlook client) and when the new server is put in place alive does it will regenerate the database
    in new Exchange 2011? 
    Thanks in advance =)

    For the 1st question, both servers are in different/isolated network. So you were saying yes i can do that correct? will not going to have any issue running both servers having all the same configuration while configuring the new server up? 
    the 2nd. since i am not migrating, i am planing to export/import user email from outlook client and when i replace the old server with the new server, i setup the user email client and import the .pst back.  

Maybe you are looking for