Requirement to use single Virtual Server
Domains can not be shared between Hosting Spaces. So in case you need to use one domain both for Exchange and Web hosting - use one Hosting Space for it.
For this mixed Hosting Space you need either create Hosting plan that contained all needed services or use Hosting plan + Hosting Add-ons.
For this mixed Hosting plan or "Hosting plan + Hosting Add-ons" combination you should use parent Virtual Server that contain all needed services.
Use OS components from Web server in this Virtual Server, not from Exchange, even your basic Hosting Plan does not contain Web services (but Web hosting Add-ons will be created).
Max mailbox size, MB - is maximum size can be set with panel. Also it defines default limits. In case you create add-on with additional Max mailbox size, MB space - it will increase default limits for new organizations, but for existing orgs default limits will not be changed - only possibility to increase them will appear.
To address this issue Enterprise Solutions Reports was implemented. With reports it is possible to bill customers by fact usage.
Also use can use "Storage Settings" menu to set default mailbox limit for Hosted Organization. Also you can reset limits for all mailboxes in Hosted Organization with "Storage Settings" menu. Limit set with "Storage Settings" menu can be less than maximum mailbox size allowed for this Hosted Organization in Hosting Space and define some "basic" limits that will be used for most existing and new mailboxes in organization, and in case some mailbox require bigger limit - it will be needed to increase it separately with DNP. Then use reports to bill this customer by fact usage.
Currently, in case you add add-on with mailbox feature (for example MAPI access) - this feature become enabled for all mailboxes. To address this issue (and to help our customers be more SPLA-compatible and HMC-competitive) To address this issue Enterprise Solutions Reports was implemented. With reports it is possible to bill customers by fact usage.
Also we are going to change this behaviour in next DNP major release.
Backup feature included in DNP works with classic webhosting only. You should backup such complex things as Exchange and AD with specialized third party backup software, such as Symantec (former VERITAS) Backup Exec or something. Also you should backup Enterprise Server database.
For more flexible backup we will create command line (shell) utility that will be able to backup and restore defined parts of Enterprise Server metabase, for example different Organizations in DNP. So you will be able to integrate this utility to third party backup software jobs. For example Symantec (former VERITAS) Backup Exec allows it.
We not plan to integrate backup of AD accounts, OUs, Exchange Databases to DNP currently and therefore we advise to backup it with special third party backup software together with upcoming DNP backup-restore utility
Ability to create Public Folders for not only post items
DNP Exchange solution supports the use of exchange public folders from the first release. However there is some issue here. Our option is to concentrate all provisioning tasks in panel. However at the moment panel can only create Public Folders for post items, but not for Calendars, Tasks, Notes, etc. It is because of EMS restrictions. Now we are researching various APIs to make possible to create different public folders type in panel. As temporary workaround we advise our customers to make some end users (who really need it) "Publishing Authors" for their organization's root public folder. Thus they can create needed subfolders with Outlook.
After new Public Folders creation method will be implemented we will create the script that will collect all folders created by Outlooks and made them visible and manageable in panel. After this it will be possible to remove "Publishing Authors" role for those users and come back to pure panel-based Public Folders creation.
As last resort (in case no one Public Folders creation method we testing now will pass internal tests) we will give up and stay only root organization Public Folders creation in panel. Also we will add possibility to make some user "Publishing Author" + possibility to count overall size of organization's Public Folders created with Outlook.
To add publishing Author permission to organization's root public folder you may run this command:
Add-PublicFolderClientPermission \org01 -User email@example.com -AccessRights "PublishingAuthor"
Note that to create organization's root public folder you need to created (and then delete if needed) at least one Public Folder with DNP