• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Inquiries about New Plesk Windows 12.5 Installation

NOOR Hosting

New Pleskian
Hello,

Kindly we will implement Plesk 12.5 (Windows) and after installing the test control panel server plus two slave DNS servers, we faced the below points which were needed to be configured in new control panel to match our requirements.

Most of below features are exist & configured in our current Hsphere 3.4 control panel.

List of Inquiries about New Plesk Windows 12.5 Installation:-

1- Admin

- Install

It is recommended to install Plesk on C:\ partition or to install and configure it on another partition (e.g. D:\) and if there are another recommendations for Plesk installation please share it (quick installation/configuration/Policy/Security guide) .

- View

Could we customize Power User view to contain Customers,Domains,Plans, so from Admin interface we are able to manage our customers & Plans without switching back to Service Provider View.

2- DNS
- Slave DNS servers:

Is there is any way to configure cPanel DNS only DNS servers as slave DNS servers for Plesk control panel, so we can have only two DNS servers for both our cPanel & Plesk control panels.

- Prevent switch to slave zone:
We need to prevent customers from converting their DNS zone from Master to slave and they still be able to manage their DNS zone (Add / Edit and remove DNS records).

- Zone SOA Mail Address:
We need to add unique SOA mail address for all DNS zones not customer mail address.

- DNS Plan:
Create DNS Plan without enabling Mail and Web Hosting services for specific customers to manage their DNS zone only.

3- Mail

A- Domain Forwarder (Alias):

How to forward all domainA emails to another domainB (if customer has domainA and domainB and he created all his mailboxes only for domainB, so he needs to forward all sent emails to domainA to domainB with creating mailboxes for domainA)

B- Global Anti-spam Settings for customer
How to enable global anti-spam settings for every domain not for every mailbox (e.g. SCL , White-list & Black-List)

C- DKIM:
Force Enable DKIM for all customers and domains without pending on every customer to enable it from his account (Use DomainKeys spam protection system to sign outgoing email messages by default for all new customers).

Thanks,
 
Last edited:
> 1- Admin
> - Install

There is no strict requirements where to install Plesk. But it will be better if it will be installed in root folder.
Here is Deployment guide
https://docs.plesk.com/en-US/12.5/deployment-guide/get-started.70252/

> - View
No, you couldn't

> 2- DNS
> - Slave DNS servers:
You can use Plesk Slave DNS manager extension. But please be aware that it is not designed to work in multimaster scheme.

> - Prevent switch to slave zone:
You can use "DNS zone management" service plan permission. Uncheck "Home> Service Plans> Hosting Plans > Permission > DNS zone management"

> - Zone SOA Mail Address:
There is no email address in SOA for DNS zones created by Plesk. You can use some kind of custom script to add required data into DNS zone. Here you can find additional information.
https://docs.plesk.com/en-US/12.5/a...nt-parameters-passed-by-event-handlers.67897/

> - DNS Plan:
Disable hosting on "Hosting Parameters", mail

> 3- Mail
> A- Domain Forwarder (Alias):
He can create a DomainB with all mailboxes and then create DomainA as a domain alias for DomainB

> B- Global Anti-spam Settings for customer
AntiSPAM can be applied either server-wide or per mailbox

> C- DKIM:
DKIM support is planned to be implemented in Plesk Onyx.
 
Hello Bulat,

Thanks for your reply and the provided tips.

We have tested plesk features and please find below our notes regarding all of them:-


> 2- DNS
> - Slave DNS servers:
> You can use Plesk Slave DNS manager extension. But please be aware that it is not designed to work in multimaster scheme.
- We tried to configure it with cPanel DNS only using (Slave DNS Manager Extension) but not working and the same configurations were successfully running with Linux BIND9 DNS servers.

upload_2016-8-21_15-16-0.jpeg

> - Prevent switch to slave zone:
> You can use "DNS zone management" service plan permission. Uncheck "Home> Service Plans> Hosting Plans > Permission > DNS zone management"
- When we disable DNS zone management customer will not be able to manage his DNS records.
- Actually what we need to achieve is let our customer control his DNS records but unable to convert his DNS zone from master to slave or to modify zone transfer IPs.

upload_2016-8-21_14-59-51.jpeg

> - Zone SOA Mail Address:
> There is no email address in SOA for DNS zones created by Plesk. You can use some kind of custom script to add required data into DNS zone. Here you can find additional information.
> https://docs.plesk.com/en-US/12.5/a...nt-parameters-passed-by-event-handlers.67897/
- Is there any way that all DNS zone SOA address will be plesk admin contact Email address (same as cPanel).

upload_2016-8-21_15-6-3.jpeg

> - DNS Plan:
> Disable hosting on "Hosting Parameters", mail
- We have disabled hosting and Mail options but still customer see more features (e.g. we need to let customer see only DNS settings not the other options like below test.org)

upload_2016-8-21_15-12-39.jpeg
upload_2016-8-21_15-12-29.jpeg


> 3- Mail
> A- Domain Forwarder (Alias):
> He can create a DomainB with all mailboxes and then create DomainA as a domain alias for DomainB
- Thanks the domain alias feature was configured and working properly.
 
_ After enabling only FTP over SSL (security Plolicy) we are unable to upload data using FTP Clients (FileZilla , WINSCP) and we received the below error message:

"Unable to upload file with FTPS: 550 The supplied message is incomplete. The signature was not verified."

- We checked Plesk and found that this issue is related to IIS/SSL but the Microsoft Patch URL is not working.


https://kb.plesk.com/en/125368

- Could you please help me fixing this issue as we need to allow only secure FTP & most of our customers are using FileZilla as their default FTP client.
 
After moving websites to Plesk we found that some websites have the below Error message:

Is this means that we need to add .Net framework 3.5 feature to server 2012 R2 or no need to do this ?

###########

HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.


Detailed Error Information:

Detailed Error Information:
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x800700b7
Config Error There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined
Config File \\?\C:\Inetpub\vhosts\egx.com.eg\press.egx.com.eg\web.config

Config Source:
13: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
14: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
15: <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
 
You probably already have this figured out, but thought I'd document it here for future adventurers.

Some ASP.Net applications already have the System.Web.Extensions (from AJAX) added the application web.config file found in the root of the site.

In IIS, the ASP.Net 2.0 (Plesk calls it 3.5) library does not include the AJAX extensions, so they have to be manually specified in the web.config file. But in ASP.Net 4.0, AJAX extensions are included and do not need to be defined in the application web.config file.

So when you move an ASP.Net 2.0 website to a different server and do not set the application pool to be ASP.Net 2.0, IIS will complain that the sections are already defined. Because you're now running the site in ASP.Net 4.0 which already defines those sections.

The solution is either adjust the application pool back to ASP.Net 3.5 in Plesk, or simply comment out the AJAX section in the web.config file. This is what the section looks like that needs commented out. Just look for the section with the AJAX comments before and after.


<!-- AJAX -->
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" />
<sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35">
<section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="Everywhere" />
<section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" />
<section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" requirePermission="false" allowDefinition="MachineToApplication" />
</sectionGroup>
</sectionGroup>
</sectionGroup>
<!-- AJAX -->
 
Thank you very much.

We have another issue, we need to forward the main domain of the customer , we are able to forward new domain or any addon domain but we can't forward (redirect) the main domain after adding it.
 
You change the Hosting Type in the Hosting Settings page for the domain. Plesk will not let you change the Hosting Type for the main domain once a sub-domain or alias is created.

You'll have to manually do the forwarding through rewrite rules, configure forwarding in IIS itself or simply use DNS changes to point alternate domain names directly to the forwarded destination.
 
Back
Top