Hi Giuseppe,

I’ve used this KB before to update the PC size and it works perfectly:
https://portal.nutanix.com/page/documents/kbs/details?targetId=kA00e000000CvAnCAK

Note: you have to stop the PC Cluster service (this won’t impact your running VMs but it will only stop PC Management). You can still manage VMs through PE.

Hi,
I have already added the resources, but I keep receiving the alert about “inadequate resources”.
I found this:

“Note: Enabling one or more Intelligent Operations features and Self-Service or DRaaS is NOT SUPPORTED on Small Prism Central. If you want to enable this combination, convert to Large Prism Central.

Please contact Nutanix support to assist with converting PC to Large instance”

I see…. it seems you will have to reach out to support then.
I’ve also found: https://portal.nutanix.com/page/documents/kbs/details?targetId=kA0VO0000005eXt0AI but the solution is to reach out to support...

Hi Giuseppe,

To convert or resize Prism Central (PC) is not officially supported through any automated or native in-place tool or button inside Prism Central itself.

Here’s a vendor-aligned solution path you should follow:

Vendor-Supported Method to Resize Prism Central (PC):

This process involves deploying a new PC of the desired size and migrating functionality to it.

Step-by-Step Process:

1. Back up the existing Prism Central
   • Use a recent snapshot or perform full VM backup (agentless or agent-based) using your enterprise backup solution.
   • Refer to your DR strategy if PC is part of one (e.g., DR plans in Leap).
2. Deploy a new Prism Central VM
   • Use the Prism Central deployment wizard (via Prism Element or Foundation Central).
   • During deployment, choose the desired size profile:
     • Small, Medium, or Large (depending on cluster scale and service requirements).
   • Ensure network settings match your environment (VLANs, IPAM, routing, etc.).
3. Unregister the old Prism Central
   • If this is a standalone or test environment and no services (e.g., Calm, Flow, DR plans, NCC) are attached, unregister the old instance cleanly.
   • Otherwise, proceed to the next step before decommissioning.
4. Re-register Clusters to the New PC
   • From each Prism Element UI, go to Settings > Prism Central Registration.
   • Unregister from the old PC, then register with the new one.
   • Confirm PC-PE sync is healthy (Services, Inventory, Alerts, etc.).
5. Migrate Services (if applicable)
   • If you were using Calm, Flow, LCM management, or Xi Leap, reconfigure or reimport configurations as needed.
   • For Flow, export policies and reapply.
   • For Calm or NCM Self-Service, export Blueprints and Projects.
6. Decommission the old PC VM
   • Once validation is complete and all dependencies are redirected to the new PC, power off and remove the old VM.
   • Clean up DNS and IP references.

Important:

• In-place resizing (increasing vCPU or RAM) of Prism Central is not officially supported and may break functionality or invalidate support unless it matches a valid PC size class (e.g., from Small to Medium profile requirements).
• Always validate with prism_central --version and ensure compatibility with managed cluster versions.
• Monitor the new PC's health using ncli, prism_central_cli, or via Alerts.

Hi Giuseppe,

If you are running CE then deleting the prism central is the only option. Reinstall it with the correct size. If this is production then involve support and they will do this for you.