locked
Create Client Access Array change outlook userprofile servername RRS feed

  • Question

  • exchange 2010 sp2 ru3

    outlook2010

    outlook userprofile servername:mail1.domain.com

    becouse Create Client Access Array FQDN mail.domain.com

    so  userprofile servername need change to mail.domain.com

    Excuse me 

    are there any ways to change without affecting the user 

    thnaks

    Excuse me
    Excuse me
    Are there any ways to change without affecting the user under
    Are there any ways to change without affecting the user under
    Wednesday, August 3, 2016 9:58 AM

Answers

  • CAS array should have been created prior to moving users to Exchange 2010 to stop this from happening.

    You can change it now, but the Outlook profiles may or may not update.  See point #1 above.

    Newer builds of Outlook do update better, but you see notes in the forums that it is not 100%


    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    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.

    • Proposed as answer by Niko.Cheng Thursday, August 4, 2016 8:29 AM
    • Marked as answer by Niko.Cheng Friday, September 9, 2016 8:48 AM
    Wednesday, August 3, 2016 12:48 PM
  • Hi Majigougou,

    Agree with Rhoderick.

    In general, a CAS array object is recommended to create before creating Exchange 2010 database. The reason is that the RpcClientAccessServer attribute is used to tell Outlook clients during the profile creation process what server name should be in the profile, and a CAS array object exists is to automatically populate the RpcClientAccessServer attribute of any new Exchange 2010 mailbox database created in the same Active Directory site (as the CAS array object).

    If you create CAS array before creating databases, the RpcClientAccessServer property of all the mailbox databases are populated with the CAS array object’s FQDN, and that will eliminate the impact on users.

    Best regards,


    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 tnmff@microsoft.com.

    Niko Cheng
    TechNet Community Support

    • Marked as answer by Niko.Cheng Friday, September 9, 2016 8:48 AM
    Thursday, August 4, 2016 8:47 AM

All replies

  • CAS array should have been created prior to moving users to Exchange 2010 to stop this from happening.

    You can change it now, but the Outlook profiles may or may not update.  See point #1 above.

    Newer builds of Outlook do update better, but you see notes in the forums that it is not 100%


    Cheers,

    Rhoderick

    Microsoft Senior Exchange PFE

    Blog: http://blogs.technet.com/rmilne  Twitter:   LinkedIn:   Facebook:   XING:

    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.

    • Proposed as answer by Niko.Cheng Thursday, August 4, 2016 8:29 AM
    • Marked as answer by Niko.Cheng Friday, September 9, 2016 8:48 AM
    Wednesday, August 3, 2016 12:48 PM
  • Hi Majigougou,

    Agree with Rhoderick.

    In general, a CAS array object is recommended to create before creating Exchange 2010 database. The reason is that the RpcClientAccessServer attribute is used to tell Outlook clients during the profile creation process what server name should be in the profile, and a CAS array object exists is to automatically populate the RpcClientAccessServer attribute of any new Exchange 2010 mailbox database created in the same Active Directory site (as the CAS array object).

    If you create CAS array before creating databases, the RpcClientAccessServer property of all the mailbox databases are populated with the CAS array object’s FQDN, and that will eliminate the impact on users.

    Best regards,


    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 tnmff@microsoft.com.

    Niko Cheng
    TechNet Community Support

    • Marked as answer by Niko.Cheng Friday, September 9, 2016 8:48 AM
    Thursday, August 4, 2016 8:47 AM