• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Older .net Versions

RodStr

Basic Pleskian
ASP.net 2.0 and 4.0 were installed, and Plesk picked them up just fine and displays them as options under the Service Plan configuration tool.

Discovered that many customers we are migrating to the Plesk box utilize ASP.net 1.1.

So I installed .Net 1.1 (and SP1) on the Plesk box, went through the processes to enable it.

However, Plesk is NOT picking up that it is available.

Is there something I need to configure within Plesk to detect the new (well old ) version of .Net that is now
available on the Box ?

Thank you!

Rod
 
I think I answered my own question... sort of...

1.1 is NOT necessary to be installed since 2.0 will automatically handle 1.1 sites just fine.

Rod
 
Back
Top