Hi there,

We've recently set up SolidCP Version 1.5.1, and are moving to it from an old WebSitePanel instance. We've run into a few issues, but there's a few that I think have the same root cause, and I'm hoping someone has seen this before.

Essentially, we're importing organizations in from AD so they show up in SolidCP, we're creating the Customer and Hosting Spaces manually, then running the Enterprise Import Tool which imports/creates the Hosted Organization, Domains, and Users removed link The import runs fine, and everything looks correct in SolidCP. However, there are a few issues we experience with these imported organizations.

Important to note, that these issues do not occur if we create brand new Hosted Organizations - just for imported ones.

• Distribution lists can not be created (a constraint violation occurred error)
• Distribution lists can not have members added (a constraint violation occurred error, however it still makes the change)
• When creating users under the organization, it does not set the PrimarySMTPAddress or ProxyAddresses attributes correctly (they show correctly in SolidCP, but in the back end, they are incorrect. Adjusting the aliases after creation fixes this issue)
• Some extentionAttribute values are not set against users in AD on creation, namely extensionAttribute1 which should contain the name of the OU the user is in

These lead to a variety of issues, but these are all isolated to just Hosted Organizations that are created with the Enterprise Import Tool. None of the above issues occur under newly created Hosted Organizations.

I've been browsing the SolidCP interface and back end database to see if I can find a value differentiating imported vs non-imported hosted organizations, or just any differences between the two, but so far I have not been able to find anything set differently.

I thought it may be an AD issue, as imported organizations use existing OUs, and created organizations are having SolidCP create the OU, but I did some fiddling to create a new HostedOrgnization, then adjusted the OU it was pointing to in the back end database to point to an existing OU instead, and then just imported the users only. And this Hosted Organization does not have the issue - so this should rule out anything on the AD side, it must be something in SolidCP that's treating imported Hosted Organizations and newly created ones differently. I just really can not find any settings or flags that are different between the two.

If anyone has seen anything similar, or has any ideas of what else I can check or test, any and all help would be greatly appreciated!

Thanks,

-SP