blog.hosebei.ch

Azure AD Connect 1.1.105.0 – Missing Scheduled Task

by

martin

·

, , , ,

Hi,

today I have upgraded my Azure AD Connect to the newest Version available (Download here).
Everything seemed to be fine, except that I was missing the Scheduled Task:
azureadconnect01

And I could also determine, that the Sync wasn’t be started within the Synchronization Service Manager. I then was searching for an opportunity to manually start the Sync process. I was found a message, that the following executable will start an sync:
C:\Program Files\Microsoft Azure AD Sync\Bin\DirectorySyncClientCmd.exe
But this executable is not available with the new Version.
I then found the PowerShell Module for the Sync within this Directory:
C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync
azureadconnect02
With this, it was quite easy to start a manual sync through Powershell:

Import-Module "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\ADSync.psd1"
Start-ADSyncSyncCycle
This will run a Full Synchronization, and with
Start-ADSyncSyncCycle -PolicyType Delta
You can start a Delta Synchronization, and you can check it in the Sync Service Manager:
azureadconnect03

With this, it would be possible to create a scheduled task by myself, but I’m unsure if there was something wrong with the Installation, or why it does not sync automatically. I will update this blog, when I got more Information about this issue.

Update
The scheduled Task is gone with this new Version. The Sync process should be done within the Sync Engine. Obviously this does not work atm on my system. Will give an update if I have more Information.

Update 2
On this page, the new process is quite well explained: https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnectsync-feature-scheduler/
But on my side, I still have an issue with the sync:
azureadconnect04
I do not believe that the date of the next sync will be soon 🙂
I have to dig deeper…

Update 3 (Last)
As outlined on this page:
https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnectsync-feature-scheduler/
You can start the Sync Cycle, if it’s turned off (like you see on my PrintScreen of Get-ADSyncScheduler) by using this command:
Set-ADSyncScheduler -SyncCycleEnabled $true

Comments

7 responses to “Azure AD Connect 1.1.105.0 – Missing Scheduled Task”

  1. Andres Bohren Avatar
    Andres Bohren

    Seit ich Set-ADSyncScheduler -SyncCycleEnabled $true gesetzt habe, erhalte ich bei Get-ADSyncScheduler eine wüste Fehlermeldung:

    Get-ADSyncScheduler : System.Runtime.Serialization.SerializationException:
    DateTime values that are greater than DateTime.MaxValue or smaller than
    DateTime.MinValue when converted to UTC cannot be serialized to JSON. —>
    System.ArgumentOutOfRangeException: Specified argument was out of the range of
    valid values.
    Parameter name: value
    — End of inner exception stack trace —
    at System.Runtime.Serialization.Json.JsonWriterDelegator.WriteDateTimeInDefa
    ultFormat(DateTime value)
    at
    System.Runtime.Serialization.Json.JsonWriterDelegator.WriteDateTime(DateTime
    value)
    at System.Runtime.Serialization.XmlWriterDelegator.WriteDateTime(DateTime
    value, XmlDictionaryString name, XmlDictionaryString ns)
    at WriteSchedulerSettingsToJson(XmlWriterDelegator , Object ,
    XmlObjectSerializerWriteContextComplexJson , ClassDataContract ,
    XmlDictionaryString[] )
    at System.Runtime.Serialization.Json.JsonClassDataContract.WriteJsonValueCor
    e(XmlWriterDelegator jsonWriter, Object obj,
    XmlObjectSerializerWriteContextComplexJson context, RuntimeTypeHandle
    declaredTypeHandle)
    at System.Runtime.Serialization.Json.JsonDataContract.WriteJsonValue(XmlWrit
    erDelegator jsonWriter, Object obj, XmlObjectSerializerWriteContextComplexJson
    context, RuntimeTypeHandle declaredTypeHandle)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalWrit
    eObjectContent(XmlWriterDelegator writer, Object graph)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.InternalWrit
    eObject(XmlWriterDelegator writer, Object graph)
    at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleExcepti
    ons(XmlWriterDelegator writer, Object graph, DataContractResolver
    dataContractResolver)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.WriteObject(
    XmlDictionaryWriter writer, Object graph)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.WriteObject(
    Stream stream, Object graph)
    at Microsoft.IdentityManagement.PowerShell.ObjectModel.SchedulerSettings.Ser
    ialize()
    at SchedulerUtils.GetCurrentSchedulerSettings(_ConfigAttrNode* pcanList,
    UInt32 ccanItems, Char** syncSettingsSerialized, Char** errorString)
    At line:1 char:1
    + Get-ADSyncScheduler
    + ~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : WriteError: (Microsoft.Ident…ADSyncScheduler:G
    etADSyncScheduler) [Get-ADSyncScheduler], PSInvalidOperationException
    + FullyQualifiedErrorId : System.Runtime.Serialization.SerializationExcept
    ion: DateTime values that are greater than DateTime.MaxValue or smaller th
    an DateTime.MinValue when converted to UTC cannot be serialized to JSON. –
    –> System.ArgumentOutOfRangeException: Specified argument was out of the
    range of valid values.
    Parameter name: value
    — End of inner exception stack trace —
    at System.Runtime.Serialization.Json.JsonWriterDelegator.WriteDateTimeI
    nDefaultFormat(DateTime value)
    at System.Runtime.Serialization.Json.JsonWriterDelegator.WriteDateTime(
    DateTime value)
    at System.Runtime.Serialization.XmlWriterDelegator.WriteDateTime(DateTi
    me value, XmlDictionaryString name, XmlDictionaryString ns)
    at WriteSchedulerSettingsToJson(XmlWriterDelegator , Object , XmlObject
    SerializerWriteContextComplexJson , ClassDataContract , XmlDictionaryStrin
    g[] )
    at System.Runtime.Serialization.Json.JsonClassDataContract.WriteJsonVal
    ueCore(XmlWriterDelegator jsonWriter, Object obj, XmlObjectSerializerWrite
    ContextComplexJson context, RuntimeTypeHandle declaredTypeHandle)
    at System.Runtime.Serialization.Json.JsonDataContract.WriteJsonValue(Xm
    lWriterDelegator jsonWriter, Object obj, XmlObjectSerializerWriteContextCo
    mplexJson context, RuntimeTypeHandle declaredTypeHandle)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.Interna
    lWriteObjectContent(XmlWriterDelegator writer, Object graph)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.Interna
    lWriteObject(XmlWriterDelegator writer, Object graph)
    at System.Runtime.Serialization.XmlObjectSerializer.WriteObjectHandleEx
    ceptions(XmlWriterDelegator writer, Object graph, DataContractResolver dat
    aContractResolver)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.WriteOb
    ject(XmlDictionaryWriter writer, Object graph)
    at System.Runtime.Serialization.Json.DataContractJsonSerializer.WriteOb
    ject(Stream stream, Object graph)
    at Microsoft.IdentityManagement.PowerShell.ObjectModel.SchedulerSetting
    s.Serialize()
    at SchedulerUtils.GetCurrentSchedulerSettings(_ConfigAttrNode* pcanList
    , UInt32 ccanItems, Char** syncSettingsSerialized, Char** errorString),Mic
    rosoft.IdentityManagement.PowerShell.Cmdlet.GetADSyncScheduler

    Ist das bei dir auch so?

    Reply
  2. Maarten Peeters Avatar
    Maarten Peeters

    Hello Martin,

    I also see 1-1-001 as date. Were you able to found the solution for this?

    Kind regards,
    Maarten

    Reply
    1. Martin Wüthrich Avatar
      Martin Wüthrich

      No, I had to reinstall the software to get it run. Sorry for the late answer, I was on vacation

      Reply
  3. Andres Bohren Avatar
    Andres Bohren

    The Problem is now posted in the TechNet Forums:
    https://social.technet.microsoft.com/Forums/msonline/en-US/c344ddff-3f87-42f9-a0a8-f8f71d301a45/azure-ad-connect-11-getadsyncscheduler-systemruntimeserializationserializationexception?forum=onlineservicesmigrationandcoexistence

    Reply
  4. Andres Bohren Avatar
    Andres Bohren

    Problem is solved with Azure AD Connect 1.1.110

    Reply
    1. Martin Wüthrich Avatar
      Martin Wüthrich

      thanks for posting this comment

      Reply
  5. Unhealthy Identity synchronization Notification: a trivial solution (and Microsoft’s useless troubleshooter) | Tim Anderson's IT Writing

    […] I found this post. Somehow, AD Connect had configured itself not to sync. You can get the current setting in […]

    Reply

Leave a Reply to Maarten Peeters Cancel reply

Your email address will not be published. Required fields are marked *