Just a double check: You do have the SolidCP Server installed on the CAS server of Exchange 2013 right?

Other then that this is really all there’s to it:
1) in Exchange ECP –> Servers –> Virtual Directories –> Powershell –> URL with https –> Security tab integrated auth

2) Application pool user being an Active Directory account with Administrators / Enterprise admins / Organization Management added

3) in Portal set the Powershell url to https with local fqdn ( it won’t work if it’s not the local fqdn –> as external access requires different permissions.)

4) In the Portal --> Server Active Directory setting having auth none –> and domain.local filled in.

If you can’t work it out my company also provides services to provide support through teamviewer/ rdp. This issue won’t take too long to solve for us.

I followed all of those steps and it appears I have managed to fix the WinRM connection issues, I am getting a different error message this time.. Are they still related?

Error creating mailbox. See audit log for more details.

System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'CREATE_MAILBOX' task on 'testing123' EXCHANGE ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Specified method is not supported. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SolidCP.Providers.Exchange.ExchangeServer.CreateMailEnableUser(String upn, String organizationId, String organizationDistinguishedName, String securityGroup, String organizationDomain, ExchangeAccountType accountType, String mailboxDatabase, String offlineAddressBook, String addressBookPolicy, String accountName, Boolean enablePOP, Boolean enableIMAP, Boolean enableOWA, Boolean enableMAPI, Boolean enableActiveSync, Int64 issueWarningKB, Int64 prohibitSendKB, Int64 prohibitSendReceiveKB, Int32 keepDeletedItemsDays, Int32 maxRecipients, Int32 maxSendMessageSizeKB, Int32 maxReceiveMessageSizeKB, Boolean hideFromAddressBook, Boolean isConsumer, Boolean enabledLitigationHold, Int64 recoverabelItemsSpace, Int64 recoverabelItemsWarning) at SolidCP.EnterpriseServer.ExchangeServerController.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress, Int32 mailboxPlanId, Int32 archivedPlanId, String subscriberNumber, Boolean EnableArchiving) --- End of inner exception stack trace --- at SolidCP.EnterpriseServer.ExchangeServerController.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress, Int32 mailboxPlanId, Int32 archivedPlanId, String subscriberNumber, Boolean EnableArchiving) at SolidCP.EnterpriseServer.esExchangeServer.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress, Int32 mailboxPlanId, Int32 archivedPlanId, String subscriberNumber, Boolean EnableArchiving) --- End of inner exception stack trace ---

"Specified method is not supported"

I almost never seen this error. Only time when i saw it the Integrated auth wasn't enabled in the virtual Powershell dir (so using a different auth).

Can you make sure only integrated auth is enabled in the virtual powershell settings? (not directly from IIS but through ECP).

If you want i can take a quick peek tomorrow (for free, as a party gift for the SolidCP launch).

I can confirm code wise it's working (we have about 20 deployments running on the same SolidCP codes), configuration wise i can only think of the ones i listed in the previous post.

I have checked the setting again, it is enabled please see below screen shot:

If I'm unable to fix it by then, you will be more than welcome to take a peek, thank you.. In the mean time I will double check everything again... It's odd as I'm able to create public folders and add domains..

Thanks!

Hi,

You will be relieved to hear I managed to solve the issue, under "Hosted Organizations" The domain controller had a slight spelling mistake in the FQDN.. Once this was corrected, I was able to create a mailbox.

Again thank you for your help.