locked
AADSync Beta 2 RRS feed

  • Question

  • Is there an upgrade procedure for getting from Beta 1 to Beta 2?
    Wednesday, July 16, 2014 12:43 PM

Answers

  • It is supported to upgrade from Beta 1 to Beta 2. As documented in the Beta 1 docs, you must use a service account in Active Directory for this to be supported. It is not supported if you use a service account on the local machine.

    To upgrade, cancel out of wizard (just as in beta1) and specify the parameters for the service account on the cmdline:

    DirectorySyncTool.exe /serviceaccountname <acctname> /serviceaccountpassword <acctpassword> /serviceaccountdomain <acctdomain>

    To clarify the statement regarding how and when to use in production. All our pre-release products always come with the statement that those should not be used in production unless approved by Microsoft. For AADSync we are making this approval process as easy as we can where you will test AADSync in a pre-production environment and when you are ready to go to production, you will let us know.

    /Andreas

    Thursday, July 17, 2014 1:11 AM

All replies

  • I would like this also.  MS sends this email out stating it is OK to use in production but don't provide the download link.  We're getting ready to embark on our Office 365 project (multi account forest and exchange resource forest) and I would really like to use AADSync.  
    Wednesday, July 16, 2014 1:41 PM
  • Darryl, 

    I found the download - https://connect.microsoft.com/site433/Downloads/DownloadDetails.aspx?DownloadID=53831 or https://connect.microsoft.com/site433/Downloads

    Wednesday, July 16, 2014 1:45 PM
  • Here is my issue - on the description of the download it states that we should NOT use this in beta.  

    Welcome to Azure AD Sync Services Beta

    WARNING: You may not use this release in a production environment unless agreed to by Microsoft.

    But in the Beta 2 available email it states the following.  

    We are looking for customers who are interested in using Beta2 in production. If you are interested, then do the following:

    - Download the updated build from Connect and read the documentation on http://go.microsoft.com/fwlink/?LinkID=393942 for the latest information.

    - Install and verify the scenarios you plan for production use. You do not need permissions from Microsoft to start evaluating AADSync.

    - If you find any issues or need help, submit feedback through Connect. This is also the fastest way to get access to our beta support team.

    - When you have completed the verification and all issues have been resolved, send an email to “Azure AD Sync Service Feedback”AADSyncFB@microsoft.com [mailto:AADSyncFB@microsoft.com] with information which scenarios you plan to use and have verified are working. Also provide contact information. We will respond back with information on how to get call-in support during the preview phase.


    Wednesday, July 16, 2014 1:48 PM
  • It is supported to upgrade from Beta 1 to Beta 2. As documented in the Beta 1 docs, you must use a service account in Active Directory for this to be supported. It is not supported if you use a service account on the local machine.

    To upgrade, cancel out of wizard (just as in beta1) and specify the parameters for the service account on the cmdline:

    DirectorySyncTool.exe /serviceaccountname <acctname> /serviceaccountpassword <acctpassword> /serviceaccountdomain <acctdomain>

    To clarify the statement regarding how and when to use in production. All our pre-release products always come with the statement that those should not be used in production unless approved by Microsoft. For AADSync we are making this approval process as easy as we can where you will test AADSync in a pre-production environment and when you are ready to go to production, you will let us know.

    /Andreas

    Thursday, July 17, 2014 1:11 AM