Marco Tiggelaar
@m-tiggelaar
Admin
Noble Member
Joined: Jan 7, 2016
Last seen: Mar 25, 2026
Topics: 2 / Replies: 2007
Reply
Comment: CREATE_MAILBOX error – WinRM client received an bad request status (400)

That one actually sounds familiar to a old WSP bug: is your user mail settings set to Plain text? (found if you edit user) If so set it to html (i...

10 years ago
Reply
Answer: DNS Issue after migration

From the error: You are using DNS 2012+ provider? If so: This issue is generally if you use a DNS Record template or setting that the panel can't h...

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

hmm, i think i have missed a part of your issue: you only have issues specifically with a Reseller hosting space? So a normal user space works fine?...

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

yup, you can then check in ECP --> it should state "Primary hierarchie" (might take a few minutes). Once you got that you are good to go on the P...

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

Expand Configuration –Services – Microsoft Exchange – “Your Exchange Org Name” (Properties) --> find AND clear: “MsExchDefaultPublicFolderMailbox”

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

Well it more or less depends if you still got a primary. Create one manually in ECP (i would generally always create the first PF outside of the panel...

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

Well the primary public folder is always the first PF ever created. it is however deleteable (especially during testing) so always make sure in ECP ...

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

It works with CU12 (there's not many changes) Actually most of the codes even work with Exchange 2016 (just testing the 2016 module now). You verifie...

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

The 1 of unlimited is because i deploy my organization automatically with the hosting plan setup. Issues can in rare cases also be environmental as i...

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

Just to be sure i double checked it on my live environment aswell as test lab, but their all working as expected. There was one minor change for Exc...

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

I'm assuming the Reseller plan is a old plan in this case? it most likely has incorrect values saved to it's space. you generally can only fix that b...

10 years ago
Reply
Comment: Exchange 2016 Support

Alrighty, and yes ofcourse. we welcome any form of contributors (just lack the pages at the moment to show it.. another thing that still needs to be ...

10 years ago
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
Page 131 / 134