KNOWN ISSUE: Unable to import computers from all security groups in Active Directory or from within a specific organizational unit
Last Updated March 09, 2012
A customer was unable to import their security groups (with computer resources) from Active Directory.
To reproduce: 1. Create a new AD import rule 2. Select 'specified resource type' and choose Computer with Source being Security Groups. Leave option to create filters. Enter domain. Hit OK. 3. Purposefully skip over "from(none)". At this point I want to import ALL security groups in AD. 4. Set specified schedule. 5. Save rule and run. Observe error in NS logs.
Expected behavior: This should import all security groups within AD, not fail
Test #2 Perform steps 1 and 2 above 3. Select "(none)" after "from". 4. Notice this is a Add Security Groups dialog. It is now forcing to tell it exactly which security groups to import. This is not desired behavior.
Expected behavior: I should be able to select 1 or more organizational units from which to import all security groups.
"System.ArgumentNullException caught in ImportSecurityGroups. Reason: Value cannot be null. Parameter name: s
( Exception Details: System.ArgumentNullException: Value cannot be null.