Forum

Ok, hmm that makes it more tricky, i assume this is fine for you but just to double check: You got a primary hierarchy listed in ECP --> Public ...

Alright so it's just about local accounts? In that case it generally is about permissions to the directory/accounts/user group it self

For the set-pf permissions: you should see something in the exchange logs where it attempts to execute the shell command and ending up with info/ warn...

Yes, i will add it to the fix list. As it shouldn't be mail enabled or anything (it is an unusable pf root basically just there to segregate people...

It appears to be an issue with your setup I tried it on both my live aswell as development setup both without issues as serveradmin or reseller ...

How about the exchange management log? does it hold any further information or warnings as to what fails to execute?

Glad it worked out 🙂 It's still odd that it acts out this way on Domain controllers and i will update the documentation with this note shortly.

Hello, Is this with active directory accounts/ environment? if so you will need to make sure that you have the features: Group Policy Management,...

Yes, as we where occupied with more urgent matters we did not yet have time to make a fix on the date time issue as for now.

Hmm, that error is very generic do you have any further warnings or errors in your event viewer on the Exchange server ? as it should have a bit mo...

Hello, It seems to get stuck on Mailbox setup instructions from the error. Is this user on a special reseller or something different then the ot...

Hello, I would highly recommend not to ever use AD DNS for Public domains. As you will need to remove all root zones and disable recursion (forw...

That's very odd behavior. Do all of your users have the public folder fix? so 1 main public folder per organization, and each user has their org...

Anonymous with create items is indeed required for mail enabled pf normally. however that shouldn't be set on the first pf or the root PF of each o...

We have added this to our feature requests. It most likely will not be part of the next version (as there's simply too much to do, and to little ti...