Marco Tiggelaar
@m-tiggelaar
Admin
Noble Member
Joined: Jan 7, 2016
Last seen: Jun 17, 2026
Topics: 2 / Replies: 2010
Reply
Answer: Exchange 2016 Support

Well i mainly did research for the differences between 2013 and 2016. I do believe most of it should be compatible with the existing 2013 module to w...

10 years ago
Reply
Answer: SolidCP hmail server support

Hello, SolidCP supports hmail server, aswell as mailenable, smartermail, exchange, etc. I am hoping to have a complete list available of what SolidC...

10 years ago
Reply
Answer: MySQL / Connector Support

Hello, Mysql up to v5.7, and MariaDB i believe all versions but not 100% sure. The mysql connector should be all versions (or so i was told) i have ...

10 years ago
Reply
Comment: Plans for Clean Install with import users from WSP?

Thank you for sharing. One small tip tho: The password issue at step 13 you can resolve by backing up and re-using the WebsitePanel Enterprise cipher...

10 years ago
Reply
Comment: Migrate from MSPControl to SolidCP

I have added your SQL script to the documentation: Please let me know if you have any additional tips or advice.

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

No problem. I think most easy is to check out the video, once seen check out the writing. The Writing is a little less detailed on some aspects but mo...

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

A little side note: I think the path variable comes from the Hosted Org settings, you can leave it empty aslong as the box is unchecked (like in my ho...

10 years ago
Reply
Answer: CREATE_MAILBOX error – WinRM client received an bad request status (400)

Ok, I have finished the video. You can view the video howto here: The written manual will be available there later tonight as well.

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

It's not a bug in SolidCP (i just finished the video, no such bug present, completed successfully) I will post a link once the mp4 has been generated...

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

-1 generally always means username / email already exist in AD (this error is still scheduled to be made much more clear in actual words in the next v...

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

that one should be the fqdn yes. i will make a video in a minute (probably ready within 2 hours) on how to configure the Exchange 2013 with SolidCP (...

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

hmm thats an odd one i don't think i seen many times before did you fill in the root OU? for example: CustomersExch1 ?

10 years ago
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

Alright, i did forget to mention that on any permission or auth related setting change you most likely have to do an iisreset on the exchange cas (you...

10 years ago
Reply
Answer: CREATE_MAILBOX error – WinRM client received an bad request status (400)

Hello, The first things to check are: Powershell url in the Portal configuration: make sure that you use a https url with the local fqdn (not a rem...

10 years ago
Reply
Comment: Error executing scheduled task

Glad i could help, and apologies for the inconvenience.:)

10 years ago
Page 132 / 135