In our environment, we link mailboxes created within the the hosted platform to remote users in the client’s domain that has full trust with the hosted platform. Is this something that KMIT CloudPanel supports?
Yes… and no. It’s a mix actually. However the majority of our mailboxes are indeed linked. We will keep an eye on you and hope your development of CP continues.
Thank you. They are different powershell commands so that is why we don’t support them yet. I assume that each company is either linked or not? You don’t have some companies that would be mixed for some reason?
Jacob, we have instances of both. We have customers that are solely Exchange (and hence “live” in the resource farm) and others that engage us for additional services, i.e. Citrix. These latter clients have their own domains but have full forest trust with our resource farm. We currently manage all of our customers through Citrix CloudPortal Service Manager, which will be EOL this year. On the surface it’s a rather complicated set up but fundamentally fairly simple, as you point, a different set of powershell scripts are executed based on the type of customer, be it “Remote” (having their own domain) or “Hosted” (domainless – exclusively on the resource farm).
I suspect towards midsummer you will see an uptick of inquiries of your product regarding this kind of implementation.
Interesting. I am curious why they are ending that control panel? We can take a look at it but the complication lies in CloudPanel allowing you to create the users first instead of creating the user with the New-Mailbox powershell command. So CloudPanel interfaces with Active Directory directly for user updates but interfaces with Exchange for things like Enable-Mailbox.
Since there is a two-way trust it still should be able to communicate with other forests directly as long as the AD domain is specified for the customer in CloudPanel and DNS resolves (or IP)
Ah, I see. So CP creates the user first? Then enables the mailbox in the standard way? In our scenario, the user already exists, CPSM “finds” it since we’ve configured a service account in the client’s domain, stores that AD object as a variable and when CPSM creates the mailbox, it supplies that variable in the LinkedMasterAccount parameter.
CPSM definitely addressed a niche market for providers such as ourselves. Thank you for giving it some thought.
Yes, because we have users without mailboxes but with user accounts to login with Citrix. Either way I will check into it because I do know some provider setup their environments this way and even we have a few environments like that but we just create separate email accounts for them.
