Home

Results 1 to 7 of 7

Thread: Error provisionning mixed Exchange 2013 /2010 environment

  1. #1
    sma NNTP User

    Error provisionning mixed Exchange 2013 /2010 environment


    I have the following error when provisioning Exchange 2013 :
    DirXML: [03/11/15 10:30:46.57]: ADDriver: Exchange: begin provision
    exchange account through powershell service
    DirXML: [03/11/15 10:30:46.57]: ADDriver: Exchange: optimize
    DirXML: [03/11/15 10:30:46.57]: ADDriver: Exchange: add user mailbox to
    new mail store
    DirXML: [03/11/15 10:30:46.57]: ADDriver: Exchange: provision
    DirXML: [03/11/15 10:30:46.57]: ADDriver: Enabling mailbox...
    Enable-Mailbox -Identity
    'CN=ZFMZMM,OU=SCI,OU=DECS,OU=USERS,OU=INFRA,DC=inf ra,DC=TEST,DC=TEST'
    -Database 'CN=db01-08,CN=Databases,CN=Exchange Administrative Group
    (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MAIL-TEST,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=infra,DC= TEST,DC=TEST'
    -DomainController 'infradc-p01.infra.vs.ch'
    DirXML: [03/11/15 10:31:16.01]: ADDriver: Exchange: IDM PowerShell
    Service Response ERROR: The Mailbox database "db01-08" isn't on a server
    running Exchange 2010.
    DirXML: [03/11/15 10:31:16.01]: Loader: subscriptionShim->execute()
    returned:
    DirXML: [03/11/15 10:31:16.01]: Loader: XML Document:
    DirXML: [03/11/15 10:31:16.01]: <nds ndsversion="8.7" dtdversion="1.1">

    This is normal when you have a mixed 2013/2010 Exchange domain and this
    must be solved by setting the default Exchange server.

    But, the problem is still there even when I set the exchange server FQDN
    : mail.domain.com in the driver configuration.

    It seems this parameter is not used, as any value could be set.

    Any idea ?

    IDM is : IDM 4.0.2.7
    Remote Loader : 4.0.2.7
    ADIR driver : 4.0.0.3
    IDMPowershellservice properly installed and running.

    Thanks

    Sylvain


    --
    sma
    ------------------------------------------------------------------------
    sma's Profile: https://forums.netiq.com/member.php?userid=174
    View this thread: https://forums.netiq.com/showthread.php?t=53079


  2. #2
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: Error provisionning mixed Exchange 2013 /2010 environment

    > But, the problem is still there even when I set the exchange server FQDN
    > : mail.domain.com in the driver configuration.
    >
    > It seems this parameter is not used, as any value could be set.
    >
    > Any idea ?
    >
    > IDM is : IDM 4.0.2.7
    > Remote Loader : 4.0.2.7
    > ADIR driver : 4.0.0.3
    > IDMPowershellservice properly installed and running.


    The generated powershell command shown in the RL trace should have an
    extra option, when you set the Server DN.

    I forget the switch it adds though.


  3. #3
    sma NNTP User

    Re: Error provisionning mixed Exchange 2013 /2010 environment


    I think you are right, but the powershell command is generated by the
    driver, not by a policy.
    Where could I add this parameter ?
    thx


    --
    sma
    ------------------------------------------------------------------------
    sma's Profile: https://forums.netiq.com/member.php?userid=174
    View this thread: https://forums.netiq.com/showthread.php?t=53079


  4. #4
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: Error provisionning mixed Exchange 2013 /2010 environment

    On 3/11/2015 10:27 AM, sma wrote:
    >
    > I think you are right, but the powershell command is generated by the
    > driver, not by a policy.
    > Where could I add this parameter ?


    Driver configuration, you have to expand one of the settings about
    Exchamnge. It is only there once you enable the IDM PowerShell service,
    vs the Exchange 2010 or 2013 service.



  5. #5
    sma NNTP User

    Re: Error provisionning mixed Exchange 2013 /2010 environment


    Yes, this is done already and the problem is that the driver does not
    execute the right powershell command. It looks like the
    "exchange-server" parameter is not used.
    Thx

    <header display-name="Exchange Options"/>
    <group>
    <definition display-name="Show Exchange Management Options"
    name="xchg-options" type="enum">
    <enum-choice display-name="show">show</enum-choice>
    <enum-choice display-name="hide">hide</enum-choice>
    <value>show</value>
    </definition>
    <subordinates active-value="show">
    <group>
    <definition display-name="Enable Exchange mailbox provisioning"
    name="xchg-prov" type="enum">
    <description>Show Microsoft Exchange options. These parameters
    control what method of interface to the Microsoft Exchange Management
    system and whether to interpret changes in the homeMDB attribute as a
    move or delete of the mailbox.</description>
    <enum-choice display-name="enabled">enabled</enum-choice>
    <enum-choice display-name="disabled">disabled</enum-choice>
    <value>enabled</value>
    </definition>
    <subordinates active-value="enabled">
    <definition display-name="Allow Exchange mailbox move"
    name="exch-move" type="enum">
    <description>When enabled, the driver shim intercepts
    modifications to the Active Directory homeMDB attribute and calls into
    the Exchange Managment System to move the mailbox to the new message
    data store. This option is only supported with use-cdoexm or
    post-use-cdoexm interface types.</description>
    <enum-choice display-name="Yes">yes</enum-choice>
    <enum-choice display-name="No">no</enum-choice>
    <value>no</value>
    </definition>
    <definition display-name="Allow Exchange mailbox delete"
    name="exch-delete" type="enum">
    <description>When enabled, the driver shim intercepts removal
    for the Active Directory homeMDB attribute and calls into Exchange
    Managment System to delete the mailbox. This option is only supported
    with use-cdoexm or post-use-cdoexm interface types.</description>
    <enum-choice display-name="Yes">yes</enum-choice>
    <enum-choice display-name="No">no</enum-choice>
    <value>yes</value>
    </definition>
    </subordinates>
    </group>
    <group>
    <definition display-name="Exchange Management interface type"
    name="exch-api-type" type="enum">
    <description>Exchange mailboxes can be controlled by calls into
    the Microsoft Exchange management system instead of regular attribute
    synchronization. When enabled, the driver shim intercepts changes to the
    Active Directory homeMDB attribute and uses the selected option for
    provisioning Exchange. The RUS option relies upon the Recipient Update
    Service (RUS) to propagate account information to Exchange. The CDOEXM
    option enables the use of Collaboration Data Objects for Exchange
    Management subsystem. The EXCH 2007 and EXCH 2010 options implies use of
    Exchange 2007 and Exchange 2010 and requires installation of the IDM
    Exchange service. The EXCH 2007 and EXCH 2010 options are incompatible
    with Exchange 2000 or 2003. IDM PowerShell Service needs to be used with
    Exchange Server 2013 and Exchange Server 2010(if installed on Windows
    Server 2012). Refer to the user guide for details. The value you choose
    here is recorded in the driver shim configuration.</description>
    <enum-choice display-name="CDOEXM">use-cdoexm</enum-choice>
    <enum-choice display-name="IDM EXCH 2007
    service">use-exch-2007</enum-choice>
    <enum-choice display-name="IDM EXCH 2010
    service">use-exch-2010</enum-choice>
    <enum-choice display-name="IDM PowerShell
    service">use-exch-powershell</enum-choice>
    <value>use-exch-powershell</value>
    </definition>
    <subordinates active-value="use-exch-powershell">
    <definition display-name="Exchange Server FQDN"
    name="exchange-server" type="string">
    <description>In case of multiple Exchange Server setup, enter
    the preferred Exchange Server FQDN. This is to support mailbox creation
    on the user preferred exchange server instead of the default server
    selected by the IDM Powershell Service. If empty, IDM Powershell
    service will select the first Exchange Server it fetches from
    setup.</description>
    <value>mail-p01.infra.test.test</value>
    </definition>
    </subordinates>
    </group>
    </subordinates>
    </group>


    --
    sma
    ------------------------------------------------------------------------
    sma's Profile: https://forums.netiq.com/member.php?userid=174
    View this thread: https://forums.netiq.com/showthread.php?t=53079


  6. #6
    sma NNTP User

    Re: Error provisionning mixed Exchange 2013 /2010 environment


    It works fine by using ADDRIVER.DLL 4.0.0.4 and IDMPowershellservice.exe
    from IDM 4.5 (?).

    I have a opened incident with NetIQ support, I will check why this
    feature works only with IDM 4.5 files and update this thread.

    thanks


    --
    sma
    ------------------------------------------------------------------------
    sma's Profile: https://forums.netiq.com/member.php?userid=174
    View this thread: https://forums.netiq.com/showthread.php?t=53079


  7. #7
    Join Date
    Dec 2007
    Location
    Brooklyn, NY
    Posts
    6,213

    Re: Error provisionning mixed Exchange 2013 /2010 environment

    On 3/11/2015 12:54 PM, sma wrote:
    >
    > It works fine by using ADDRIVER.DLL 4.0.0.4 and IDMPowershellservice.exe
    > from IDM 4.5 (?).
    >
    > I have a opened incident with NetIQ support, I will check why this
    > feature works only with IDM 4.5 files and update this thread.


    That is a good point. I worked with this in IDM 4.5. I assumed they
    were keeping 4.02 and 4.5 shims in sync.

    Darn. I wish they would just release the 4.5 shim as a patch then....


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •