Solution Manager Upgrade

The upgrade finished but you skipped running SGEN — what symptom will users hit, and why is the timing a planning problem?

A customer on Solution Manager 7.0 asks you to scope the move to 7.2 — what's the costly misconception to correct up front?

For a standard 7.2 migration, what single property decides between in-place and parallel export/import — and when does it rule one out?

Upgrade vs fresh implementation of Solution Manager — what's the discriminating question that actually settles it?

The 7.2 upgrade imposes a JVM and kernel prerequisite — what's the precondition, and what's the consequence of leaving the kernel for later?

The 7.2 upgrade labels a functional area 'High' vs 'Medium' impact — what does High actually obligate you to do, and which areas are High?

You're freezing the SLD before a Solution Manager upgrade — what's the real reason, and which step is easy to omit?

After upgrading to 7.2, Diagnostics Agents (DAA) drop their connections — what changed, and why is fixing it after the fact painful?

What are the four phases of a Solution Manager 7.2 upgrade, and which one do teams most often under-plan?

You're upgrading to 7.2 with SUM then SWPM — under what condition are those two steps enough on their own, and when do they stop being enough?

Around a Solution Manager upgrade you suspend background jobs with BTCTRNS1 — what's the failure if that's the only transaction you run?

Before disabling SLD-to-LMDB synchronization for an upgrade, what must you verify, and what's lost if you don't?

SUM and SWPM ship together in the SL Toolset — which tool owns SID changes and system copies, and what's the easy mix-up?

What specific condition flips the recommendation from upgrade to a fresh Solution Manager implementation?

After the dual-stack split, when do you actually need an SAP Web Dispatcher — and what's the trade-off of adding one you don't need?

Why upgrade Solution Manager on the development system before production — what does sequencing it the other way cost you?

When the goal is the fewest possible downtime windows on a move to 7.2 plus HANA/ASE, what does DMO inside SUM give you that the separate path doesn't?

DMO has the lowest downtime — what's the misconception that makes 'lowest downtime' the wrong reason to default to it?

You have 20+ managed systems connected to Solution Manager — how should that tilt the upgrade-vs-fresh-install call, and why?