Fixed: We opened up the OUs we had previously blocked, unchecked them through the IIFP and now it's working as expected and automatically removed the entries we did not want to share between the orgs. Don't know if that info will help anyone else - we have unique requirements for this effort that may not exist elsewhere.
________________________________ From: Moss, Sue [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2008 10:57 AM To: Active Directory Admin Issues Subject: RE: IIFP strangeness Update: It looks like they had the denied OUs selected in IIFP before we denied them. We've corrected that and we'll see what happens with the next run. ________________________________ From: Moss, Sue [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2008 10:28 AM To: Active Directory Admin Issues Subject: IIFP strangeness Anyone out there using IIFP to syncronize GALs between two organizations? Details: Both orgs are Win2003 - up-to-date on patches. Both have E2K3sp2 - patched and up-to-date. The problem: We have explicitly denied access to the accounts that were created for the syncronization (the account on their side as well as the account on our side), yet when the sync runs they are pulling items from OUs that their account cannot even see. Likewise, the account on our side cannot see those same OUs. We're baffled! Additional info: Up until yesterday I had not explicitly denied "their" account access to our OUs we don't want them pulling from. Is it possible that they had those OUs checked previously and IIFP won't let them go until they can uncheck them? That's the only thing I can think of. Anyone else ever see anything like this ??? Thanks in advance! ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ ~ ~ ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ ~ ~ ~ NEW: CounterSpy Enterprise: Centralized Antispyware - #1 in eWEEK Test! ~ ~ <http://www.sunbelt-software.com/product.cfm?id=400> ~
