locked
SMTP Error email to Public Folder RRS feed

  • Question

  • We completed a 2003/2010 transition and the 2003 server has been decommissioned and shutdown.  I am getting this error when I send an email to a mail-enabled Public folder.    

    Message delivery to 'domain.org' failed on server MAILSERVER Server: MAILSERVER
     A message tracking log entry was generated on server MAILSERVER at 02/01/2010 14:21:09 indicating that a message sent by USER@domain.org could not be delivered to 'domain.org'. Check the status to determine the reason for the failure. Recipients: address@domain.org Status: 554 5.6.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn't found.

    Exchange 2010 ENT on Server 2008 R2. 

    Wednesday, February 3, 2010 5:05 PM

Answers

  • Called PSS on Saturday. 

    6 hours of troubleshooting and I had to put a workaround in place.  I exported the data from the public folder, created a new 2010 PF and imported the data from a PST.  Microsoft has escalated the problem and is supposed to find a fix for the problem.
    • Marked as answer by Alan.Gim Friday, February 12, 2010 1:59 AM
    Monday, February 8, 2010 6:36 PM

All replies

  • I have several Mail Enabled Public folders that were migrated frmo Exchange 2003 to Exchange 2010.  Users are now receiving an NDR bounce with this error

    #554 5.6.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn't found. ##

    Messages are being sent from both internal users and external customers.  I applied 4 updates over the weekend
    KB 978506; KB978207; KB977074: KB972270

    As of yesterday users started to receive these NDR's.  What I find odd is that none of these updates have anything to do with Exchange 2010--they are all Windows and IE updates.  I can send a message as the Public Folder.  Do mail-enabled public folders now need a corresponding AD user account?

    • Merged by Alan.Gim Friday, February 5, 2010 2:37 AM same topic
    Tuesday, February 2, 2010 3:08 PM
  • Does the issue happen to newly mail-enabled public folder?

    Please mail-disable the problematic public folder and re-enable it, see if the issue still persists


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    Wednesday, February 3, 2010 4:06 AM
  • James

    Thanks for your response.  I have mail-disabled and reenabled the folder.  The problem still persists.  In researching this problem I see that this error can occur when trying to replicate PF's from Exchange 2003 to Exchange 2007/2010.  Our EX2003 server has been decommisioned and shutdown. 
    Wednesday, February 3, 2010 5:45 PM
  • Does the issue happen to newly created public folder on the exchange 2010? If not, please compare the attributes between the problematic public folder and the fine, see if there’s any difference


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    Thursday, February 4, 2010 1:05 AM
  • Is there any error event in the application log on the exchange servers?

    Does the issue only happens to migrated public folders (2003), or newly created public folders (2010), or both?

    Please verify if public folder store points to the right public folder hierarchy

    1.      Start->Run->ADSIEdit.msc

    2.      Expand “Configuration”->”CN= Configuration,DC=DomainName,DC=Com”->”CN=Services”->”CN=Microsoft Exchange”->”CN=OrganizationName”->”CN= Administrative Groups”->”CN=Exchange Administrative Group (xxx)”->”CN=Databases”

    3.      In the right pane, go to the “Properties” of the “CN=PublicFolderDatabaseName” folder, check “msExchOwningPFTreeBL” attribute in the “Attribute Editor” tab, copy the value of the attribute into a notepad

    4.      Now, expand “Configuration”->”CN= Configuration,DC=DomainName,DC=Com”->”CN=Services”->”CN=Microsoft Exchange”->”CN=OrganizationName”->”CN= Administrative Groups”->”CN=Exchange Administrative Group (xxx)”->”CN=Folder Hierarchies”

    5.      In the right pane, we can find “CN=Public Folders” entry, double-click it, copy the value of “distinguishedName” attribute in the “Attribute Editor” tab to the same notepad. Two values shall be matched

    Notes: Please also verify if the “msExchOwningPFTreeBL” attribute of the “CN=Public Folders” entry contain the path of the public database on the exchange 2010 server, and make sure that path of public databases of exchange 2003 server doesn’t exist

    If there are working e-mail public folders, please compare the following attributes between the problematic public folders and the working ones

    1.      Start->Run->ADSIEdit.msc

    2.      Expand “Default naming context”->”CN=Microsoft Exchange System Objects”

    3.      In the right-pane, double-click the mail-enabled public folders, and then check the attributes

    Ø  Legacyexchangedn

    Ø  Homemdb 

    Ø  mailNickname

    Ø  proxyAddresses

    Ø  msExchHomeServerName

    Please update the GAL (Reference)

    Please run ExBPA against the exchange server for the health check


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    Thursday, February 4, 2010 3:55 AM
  • It appears to be a new issue after creating a new PF.  here are the results. 

    Delivery has failed to these recipients or groups:

    Testing <mailto:IMCEAEX-_O%3DKMSF_OU%3DEXCHANGE%2B20ADMINISTRATIVE%2B20GROUP%2B20%2B28FYDIBOHF23SPDLT%2B29_CN%3DRECIPIENTS_CN%3DTesting701f799640d1db698ccf679f687d7be40fa795@domain.org>
    The e-mail address you entered couldn't be found. Check the address and try resending the message. If the problem continues, please contact your helpdesk.

    Diagnostic information for administrators:

    Generating server: SERVER.domain.org

    IMCEAEX-_O=KMSF_OU=EXCHANGE+20ADMINISTRATIVE+20GROUP+20+28FYDIBOHF23SPDLT+29_CN=RECIPIENTS_CN=Testing701f799640d1db698ccf679f687d7be40fa795@domain.org
    #550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

    Original message headers:

    Received: from server.domain.org ([fe80::109f:5098:1dce:aa82]) by
     server.domain.org ([fe80::109f:5098:1dce:aa82%19]) with mapi; Thu, 4 Feb 2010
     10:14:36 -0500
    Content-Type: application/ms-tnef; name="winmail.dat"
    Content-Transfer-Encoding: binary
    From: USER <user@domain.org>
    To: Testing <Testing@domain.org>
    Subject: Testing new folder
    Thread-Topic: Testing new folder
    Thread-Index: AcqlrMN0NHjWdPpyTN+4Hh3bDiQqaQ==
    Date: Thu, 4 Feb 2010 10:14:35 -0500
    Message-ID: <DEE4468DB74F9B4AB88FA92BE2E706710EC7C6@server.domain.org>
    Accept-Language: en-US
    Content-Language: en-US
    X-MS-Has-Attach:
    X-MS-TNEF-Correlator: <DEE4468DB74F9B4AB88FA92BE2E706710EC7C6@server.domain.org>
    MIME-Version: 1.0

     

    Thursday, February 4, 2010 3:19 PM
  • 1.       There aren’t any entries in the application log for the failed messages.

     

    2.       The issue happens on both the 2003 migrated folders and newly created 2010 folders.

     

    3.       The value of the msExchOwningPFTreeBL is

     

    CN=Public Folders,CN=Folder Hierarchies,CN=First Administrative Group,CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=org

     

    4.       When I expand the CN=Folder Hierarchy there are no entries in ADSIEdit.

    5.       No entry in ADSIEdit

    There are no working Mail Enabled Public Folders.

     I have posted the attributes for a mail-enabled public folder.

     

    Microsoft Exchange System Objects

    Legacy Exchnage dn

      /o=DOMAIN/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Incident Reporting701f799640d1db698ccf679f687d7be41

    Home MBD

    CN=Public Folders,CN=Folder Hierarchies,CN=First Administrative Group,CN=Administrative Groups,CN=KMSF,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=org

    Mail NickName

    IncidentReporting

    Proxy Addresses

    SMTP:IncidentReporting

    X400:C=us;A= ;P=KMSF;O=Exchange;S=IncidentReporting

     

    mxExchHomeServerNAme

    /o=kmsf/ou=exchangeadministrative group (fydibohf23spdlt)/cn=configuration/cn=servers/cn=server

     

     

    Thursday, February 4, 2010 4:19 PM
  • The results of the ExBPA are too large to paste.  It exceedes 60000 characters...I have posted the trouble items

     

    First Administrative Group

     

     

    This administrative group is in native Exchange 200x mode.

     

     

    This is the default administrative group.

     

     

    Routing Group

     

     

    First Routing Group

     

     

    The nominated routing group master for routing group 'First Routing Group' has been deleted. This may cause mail flow problems. Server name: CN=KMSFMAIL\0ADEL:8ecb55f9-03b2-4a16-9aa0-76bb6c75bcbf,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=KMSF,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=kmsf,DC=org.

     

     

    Server KMSFMAIL\0ADEL:8ecb55f9-03b2-4a16-9aa0-76bb6c75bcbf is a routing group master but a connection to port 25 cannot be established from the workstation where this tool is running.

     

     

    Server KMSFMAIL\0ADEL:8ecb55f9-03b2-4a16-9aa0-76bb6c75bcbf is a routing group master but a connection to port 691 cannot be established from the workstation where this tool is running.

     

    Thursday, February 4, 2010 4:22 PM
  • One other question--You asked me to update the GAL.  I see the command reference in hte link you sent but what happens when you run the command?  How will this affect the end users?
    Thursday, February 4, 2010 8:28 PM
  • Proxy Addresses

    SMTP:IncidentReporting

    The value shall be “SMTP:IncidentReporting@DOMAIN.com”

    Quote: “When I expand the CN=Folder Hierarchy there are no entries in ADSIEdit”

    Where did you look under?

    CN=First Administrative Group,CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=org

    Or

    CN=Exchange Administrative Group (xxx),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=org

    Please look around in the “Configuration” partition, and find the “CN=Public Folders” entry back. If can’t, please refer the methods in the threads below to create a new one

    There is currently no route to the mailbox database

    Need to recreate public folders due to broken permissions


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    Friday, February 5, 2010 3:09 AM
  • Hi Dave,

    On the PF permissions does Anonymous have Contributor rights?
    Exchange won't accept any incoming mail for the folder unless it does.

    Neill
    Friday, February 5, 2010 12:51 PM
  • Hi Neil

    Anonymous has Create Items permission.  Is this different from Contributor?  My PF's were accepting mail up until a reboot this past Sunday.  It may have someting to do with the GAL still having a Legacy RecipentFilter.  I have updated the other Address Lists to the 2010 filters. 

    Thanks!
    Friday, February 5, 2010 1:04 PM
  • I tried to update the GAL with the rerference you sent me.  Here are the results. 

    Log Name:      Application
    Source:        MSExchange Configuration Cmdlet - Remote Management
    Date:          2/5/2010 8:55:34 AM
    Event ID:      4
    Task Category: General
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SERVER.DOMAIN.org
    Description:
    (PID 5340, Thread 77) Task Update-GlobalAddressList writing error when processing record of index 0. Error: Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Global Address List' couldn't be found on 'DOMAINCONTROLLER.DOMAIN.org'.
       at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError)
       at Microsoft.Exchange.Configuration.Tasks.ObjectActionTask`2.ResolveDataObject()
       at Microsoft.Exchange.Configuration.Tasks.SystemConfigurationObjectActionTask`2.ResolveDataObject()
       at Microsoft.Exchange.Configuration.Tasks.ObjectActionTask`2.PrepareDataObject()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateAddressBookBase`1.PrepareDataObject()
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.ObjectActionTask`2.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange Configuration Cmdlet - Remote Management" />
        <EventID Qualifiers="49152">4</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2010-02-05T13:55:34.000000000Z" />
        <EventRecordID>52805</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SERVER.DOMAIN.org</Computer>
        <Security />
      </System>
      <EventData>
        <Data>5340</Data>
        <Data>77</Data>
        <Data>Update-GlobalAddressList</Data>
        <Data>0</Data>
        <Data>Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Global Address List' couldn't be found on 'DOMAINCONTROLLER.DOMAIN.org'.
       at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.GetDataObject[TObject](IIdentityParameter id, IConfigDataProvider session, ObjectId rootID, OptionalIdentityData optionalData, Nullable`1 notFoundError, Nullable`1 multipleFoundError)
       at Microsoft.Exchange.Configuration.Tasks.ObjectActionTask`2.ResolveDataObject()
       at Microsoft.Exchange.Configuration.Tasks.SystemConfigurationObjectActionTask`2.ResolveDataObject()
       at Microsoft.Exchange.Configuration.Tasks.ObjectActionTask`2.PrepareDataObject()
       at Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateAddressBookBase`1.PrepareDataObject()
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.ObjectActionTask`2.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()</Data>
        <Data>{7a8feb8c-5621-4275-85f6-2838fdbd6330}</Data>
      </EventData>
    </Event>
    Friday, February 5, 2010 2:18 PM
  • I finally managed to start the GAL Update.  I had an orphaned AD object that was causing the update to fail. 

    I have a single server with the HT, CAS and MB role.  About 600 recipient objects.  How long can I expect the GAL update to run? 

    Thanks
    Friday, February 5, 2010 5:16 PM
  • Called PSS on Saturday. 

    6 hours of troubleshooting and I had to put a workaround in place.  I exported the data from the public folder, created a new 2010 PF and imported the data from a PST.  Microsoft has escalated the problem and is supposed to find a fix for the problem.
    • Marked as answer by Alan.Gim Friday, February 12, 2010 1:59 AM
    Monday, February 8, 2010 6:36 PM
  • I've had the same issue and found a related issues here:

    Public Folder Mayhem on Exchange 2010

    Public folders not replicating betwen exchange 2007 and 2010

    Removing the empty server container via ADSIedit resolved my issue immediatly:

    CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local

    Be sure to have a backup and do it at your own risk!

    I have blogged about my specific issue here .
    • Proposed as answer by SumYunGuy Thursday, May 6, 2010 6:06 PM
    Tuesday, March 16, 2010 9:11 AM
  • Dave's response solved the issue for me.  I went into ADSIEdit and remove the empty Servers container from the original (2003) admin group and emails started immediately flowing to our mail-enabled public folders.  Note: if the Servers container is not empty, do NOT delete it.
    Thursday, May 6, 2010 6:09 PM
  • Thanks, it worked for me
    Monday, May 31, 2010 9:19 AM
  • The Exchange team blogged about a related issue here:

    Public Folder Replication Fails Due To Empty Legacy Administrative Group

    This will be fixed in a upcoming roll-up.
    • Proposed as answer by MartinPlo84 Wednesday, July 3, 2013 8:17 PM
    Monday, May 31, 2010 9:48 AM
  • Worked for me as well.  Thanks!!!
    Tuesday, March 15, 2011 5:40 PM
  • I've had the same issue and found a related issues here:

    Public Folder Mayhem on Exchange 2010

    Public folders not replicating betwen exchange 2007 and 2010

    Removing the empty server container via ADSIedit resolved my issue immediatly:

    CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local

    Be sure to have a backup and do it at your own risk!

    I have blogged about my specific issue here .


    Thanks! This helps!

     

    Greetings

     

    Björn Reichard


    Mfg Björn Reichard
    Tuesday, May 3, 2011 11:22 AM
  • Hi Dave,

     

    We need remove the "Server" container itself  inside the "First Administrative Group" ?

     

    Thank you.

    Friday, May 20, 2011 3:20 PM
  • Hi BReichard,

     

    We need remove the "Server" container itself  inside the "First Administrative Group" ?

     

    Thank you.

    Friday, May 20, 2011 3:21 PM
  • Hi BReichard,

     

    We need remove the "Server" container itself  inside the "First Administrative Group" ?

     

    Thank you.


    Hi,

    The Server folder was empty. In my case it helps.

     


    Mfg Björn Reichard
    Monday, May 23, 2011 8:02 AM
  • If that container is emtpy and hosted your last Exchange 2003 server AND you have the issue, than deleting this container could resolve Public Folder SMTP issues. But be sure to have a backup and recovery setup, just in case. I never had any issues deleting this, but better safe than sorry.
    Technical Specialist / Infrastructure Architect @ www.OGD.nl - MCSE 2003 Messaging - MCITP Enterprise Messaging Administrator 2007 & 2010
    Friday, May 27, 2011 8:46 AM
  • sure enough, I had the same problem.  New 2010 exchange server added to 2007 org that had originally been created as 2003 exchange org.  public folders never did replicate correctly from 2007 to 2010.  Eventually backed up the whole PF tree (small organization) to pst and completely deleted and recreated the PF tree on the 2010 server.  Still could not get email to mail-enalbed public fodlers, got an SMTP error about an AD user object not found, then i found this post.  used ADSIedit to delete the empty "servers" container under the old 2003 "first admin group" and my problem is fixed.  thanks!
    MCITP:Enterprise Admin (Vista/2008), MCSA/MCSE (2003/XP), MCDBA (2000)
    Thursday, June 23, 2011 8:38 PM
  • I've had the same issue and found a related issues here:

    Public Folder Mayhem on Exchange 2010

    Public folders not replicating betwen exchange 2007 and 2010

    Removing the empty server container via ADSIedit resolved my issue immediatly:

    CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local

    OK, I'm lost... Where do I find this in ADSIEdit?!?!? I just retired the old exchange 2003 server and my 'time tracking' public folder doesn't work anymore... I've tabbed thtough everyting in ADSI Edit and con't find it uinder any of the headers (configuraiotn, schema etc...) Help??

     

    Thanks

    Mick

    Wednesday, December 28, 2011 9:16 AM
  • I've had the same issue and found a related issues here:

    Public Folder Mayhem on Exchange 2010

    Public folders not replicating betwen exchange 2007 and 2010

    Removing the empty server container via ADSIedit resolved my issue immediatly:

    CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local

    Be sure to have a backup and do it at your own risk!

    I have blogged about my specific issue here .
    Worked for us too! And saved us tons of time troubleshooting. Thanks for great find!
    Monday, April 30, 2012 1:39 PM
  • It more or less worked for me.  Messages now post to the Public Folder, but I get a NDR every time even though message actually posts.  The NDR is related to an account that doesn't even exist anymore. Of course I've changed the domain to domain.com or domain.local but you get the idea.  Any help would be greatly appreciated.

    Diagnostic information for administrators:

    Generating server: domain.com

    IMCEAEX-_O=CANET_OU=First+20administrative+20group_cn=Recipients_cn=khunt@domain.com #< #5.1.1 smtp;550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found> #SMTP#

    Original message headers:

    Received: from exchange.domain.local ([fe80::f19e:8d51:ec64:32c9]) by   exchange.domain.local ([fe80::f19e:8d51:ec64:32c9%11]) with mapi id  14.01.0355.002; Tue, 5 Jun 2012 01:56:36 -0700 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 From: Josiah Munson <josiah@mywork.com> To: "Katherine A. Hunt" <khunt@domain.com> Subject: FW: testing in @ 1:54AM Thread-Topic: testing in @ 1:54AM Thread-Index: Ac1C+ND7r5ONdm56QhW9T1rNR9dUqA== Date: Tue, 5 Jun 2012 08:56:34 +0000 Message-ID: <1E50E7C25EB92242A9BA8D470240DB7504A573@CAEX.domain.local> Accept-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: <1E50E7C25EB92242A9BA8D470240DB7504A573@CAEX.domain.local> MIME-Version: 1.0

    Tuesday, June 5, 2012 9:32 AM
  • Thanks,

    removing the empty Servers container work for me

    Greg

    Friday, November 30, 2012 10:48 AM
  • I had exactly same issue after sbs2003 to sbs2011 migration.

    This worked for me too.

    Friday, March 15, 2013 2:26 PM
  • Thank you, this works for me and save me a lot of hours (after a lot of hours search ;) )

    Regards from Austria ;)

    Wednesday, July 3, 2013 8:18 PM
  • Thanks very much Dave Stork.  Your solution fixed it for me too after we migrated a client from SBS 2003 (Exchange 2003) to SBS 2011 (Exchange 2010) using Microsoft's recommended migration procedures.

    All migrated mail-enabled public folders had stopped receiving mail (and sent back NDRs) after decommissioning the source SBS 2003 server.  New mail-enabled public folders also had the same problem.  After working out how to use ADSI Edit properly, your fix was easy - restarted a few Exchange services and all sorted!

    Thursday, January 23, 2014 12:39 AM
  • Works for me too !!! Thanks !

    ( pf email issue after migration exch 2003 to 2010 )

    Saturday, February 14, 2015 4:08 PM
  • Removing the empty server container via ADSIedit resolved my issue immediatly:

    CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local

    Thanks Dave.

    I've tried all the other much more complicated solutions without success. Your tip finally solved our problem (we migrated from SBS 2003).

    Friday, April 24, 2015 9:28 AM
  • Worked a treat for me over here too!!  As soon as I removed the whole 'first administration group' from ADSIEdit, bam, worked immediately.  I would always advise exporting the key first before removing however.
    Friday, September 11, 2015 11:27 AM