The manual says that you must upgrade the CM first, I believe. Of course, if 
it's a designated CM, the size of the db may make it a good candidate to go 
first anyway...


On 8 jun. 2012, at 14:49, Skylar Thompson wrote:

> Sorry for the late response to this, my email client helpfully ignored
> ADSM-L messages for a while.
> 
> If it helps others, we've been running a v5.5 config manager and v6
> servers for a while, with no issues so far. When I get time (ha!) I'll
> update the config manager to v6.3.
> 
> On 02/28/12 13:10, Rick Adamson wrote:
>> I have five version 5.5 TSM Servers that I am preparing to upgrade to
>> 6.3.
>> 
>> One server is designated as the configuration manager and the other 4
>> are managed servers for admin schedules, policy domains, etc.
>> 
>> While I might have missed it I don't recall the documentation discussing
>> how to handle them.
>> 
>> 
>> 
>> Do I start with the cfg-mgr, the managed servers, does it matter ?
>> 
>> When upgraded are the configuration manager and managed server roles
>> retained?
>> 
>> 
>> 
>> I will be using the new system network method and before I get started
>> would like to know how more about how to handle, and feedback or links
>> would be appreciated.
>> 
>> 
>> 
>> 
>> 
>> TIA
>> 
>> ~Rick
>> 
>> Jacksonville. FL.
>> 
>> 
>> 
> 
> --
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Systems Administrator, Genome Sciences Department
> -- University of Washington, School of Medicine

-- 
Met vriendelijke groeten/Kind Regards,

Remco Post
r.post AT plcs DOT nl
+31 6 248 21 622