Exactly. My friends over in Tech Support aren't happy when I lead folks by
hand into Unsupported Territory (and you'll notice I'm not a willing guide),
but if you can find the road yourself, then you're not likely to need to call
Tech Support.
The supported mechanism is to establish a test server, load software there,
transition your install to 10, then post it back to the production server. But
some production servers are beefy enough to support a bit more, which is
how we found ourselves in this mess.
Keep in mind that nothing I've posted on this topic addresses the issues
surrounding licensing. You still need to adhere to your license agreement
with regard to number of server-CPUs, and the supported mechanism of
using a different server to run the 'sdesetup', and not installing a service
for the new instance (using only Direct Connect), is far more likely to fit in
the licensing model as-is (but you'd need to speak with your local Esri office
to clarify any of that).
- V
