• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

converting standalone to AD member server issues?

R

rspurlock

Guest
Will there be any issues if converting a server, already set up as standalone, to be a member server of an AD? The server already has Plesk installed and some sites.

Here's the deal...I just came back from a swsoft sponsored Microsoft seminar and it covered some of the benefits of running Plesk over an AD setup versus standalone, especially when it comes to expandability.

So we're looking at if we need to add our Plesk windows server to an AD which will also hold the MS SQL server clusters and any Exchange clusters for hosted exchange services.

Any thoughts on how you guys have gotten this set up? We want maximum expandability without having lots of standalone servers, mainly for adding space as we grow.

TIA

Rob
 
Back
Top