• 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.

Resolved Plesk migrator error: RPC agent not started by built-in administrator

Hostinet SLU

New Pleskian
Hi,

We are using "Plesk Migrator" tool to make a migration between a Plesk 12.5 and an Onyx 17, both are Windows servers. We downloaded the RPC Agent application, but when executing it on the source server (Plesk 12.5), we received the following alert message, even the script is executed under a user belonging to the "Administrators" group:

"RPC agent was started by not built-in administrator ..."

Due to this, we are not able to carry out the migration.

Any help is welcome.

Thanks in advance,
 
Migration is started not under the built-in Administrator account. In this case, Plesk Migrator is unable to perform the different operation in the source server because of lack of permissions.

Start migration under Administrator account.
 
Back
Top