No one has responded to this discussion for at least a year, so this information may be out of date. If you're looking for information about this topic, please search for a more recent discussion or post a new question.

Set up and configure your Office desktop apps

This question is answered This question is answered

Fresh install Windows 7 Professional, Office Professional Plus and Office 365 Professional.

 

Lync installation completed and running OK.

 

Upon running "Set up and configure your Office desktop apps" only get options for "Microsoft Outlook (manual steps required)" [in other words it does nothing] and "Microsoft Lync".

 

Have installed latest sign-on wlsetup-idcrl but makes no difference.

 

Configured Outlook manually and this connects to the email OK, but won't be in sync with future password changes so not really satisfactory.

 

Suggestions?

0 out of 1 people found this post helpful.

Verified Answer
  • Hello

    what do you mean "won't be in sync with future password changes"?

    it's totally wrong; when your Office 365 password will expires, you will be notified and able to change it, then it will be kept on your client

    to have a "full password synch" - in fact not really a synchro, you have to implement ADFS which will allow you to use your AD password (as well as your own password policy) in place of Office 365

  • Hi Fundhost,

    Could you provide more information about this case, such as federation server configuration ,DNS server configuration. I’d like to explain two kind of exchange-online connection situation to you, hope it’s useful.

    Example 1, Office365 authentication
    Whether using auto-configure or manually configure, we will immediately use the new password when we change them from the office365 portal site.
    Password: password works immediately when we change it
    Outlook Auto-configure: please ensure the currently DNS server has the record same as office365 configured.

    Example 2, federation authentication
    We change our login password from our AD server, and then connect to the exchange-online service.
    Exchange online will send an authentication request to the Microsoft Federation Gateway. The MFG determines the home realm of the user to see if it is federated, if it is the client will then be redirected to the STS secure communication endpoint of the on-premise AD FS 2.0 server.
    Password: we use the login password for the entire office365 service.( Immediately work)
    Outlook Auto-configure: please ensure the currently DNS server has the record same as office365 configured

    Reference

    Plan for and deploy Active Directory Federation Services 2.0 for use with single sign-on

    http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652539.aspx
    Single sign-on: Roadmap

    http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652539.aspx

    Best Regards
    Neo Zhu

     

All Replies
  • Hello

    what do you mean "won't be in sync with future password changes"?

    it's totally wrong; when your Office 365 password will expires, you will be notified and able to change it, then it will be kept on your client

    to have a "full password synch" - in fact not really a synchro, you have to implement ADFS which will allow you to use your AD password (as well as your own password policy) in place of Office 365

  • Benoit. Presumably you are familiar with the single sign on used with BPOS. It configures the Outlook and other settings from one place. When you change the password at the requested time it changes the passwords in the associated programs such as Outlook. In this case the Office 365 equivalent is not configuring Outlook at all and requires manual configuration of the outlook client - including the password. Therefore, when the password is changed within Office 365 it is not changed in the Outlook client. AD has nothing to do this this implementation.

  • Hi Fundhost,

    Could you provide more information about this case, such as federation server configuration ,DNS server configuration. I’d like to explain two kind of exchange-online connection situation to you, hope it’s useful.

    Example 1, Office365 authentication
    Whether using auto-configure or manually configure, we will immediately use the new password when we change them from the office365 portal site.
    Password: password works immediately when we change it
    Outlook Auto-configure: please ensure the currently DNS server has the record same as office365 configured.

    Example 2, federation authentication
    We change our login password from our AD server, and then connect to the exchange-online service.
    Exchange online will send an authentication request to the Microsoft Federation Gateway. The MFG determines the home realm of the user to see if it is federated, if it is the client will then be redirected to the STS secure communication endpoint of the on-premise AD FS 2.0 server.
    Password: we use the login password for the entire office365 service.( Immediately work)
    Outlook Auto-configure: please ensure the currently DNS server has the record same as office365 configured

    Reference

    Plan for and deploy Active Directory Federation Services 2.0 for use with single sign-on

    http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652539.aspx
    Single sign-on: Roadmap

    http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652539.aspx

    Best Regards
    Neo Zhu

     

  • Hi Fundhost,

    Does the reply answer your question?

    Thanks.