On 14/09/2013 19:09, Ruslan Zakirov wrote:
And as far as I am aware RT4.2 is still Beta, well - release candidate, but still Beta. Therefore you shouldn't really be upgrading to it as moving from release candidate to a higher version is not guaranteed possible.On Sat, Sep 14, 2013 at 5:28 PM, Xin, Qiao <q...@cio.sc.gov <mailto:q...@cio.sc.gov>> wrote:Thank both of you very much for the reply. According to the reply from Kevin: "I'm confused how you're running 4.0.5 with RTIR 2.6.1, since that version isn't compatible with RT 4 (RTIR 3.0.0 is the compatible version)." After I upgrade RT to 4.0.x but before I upgrade RTIR, I will end up with RT 4.0.x with RTIR 2.6.1. Will the system still be able to run? How can tell theRT part should be able to do basic things, RTIR has some hooks inserted into RT, but not so many to prevent everything from working. However, you should not use such setup in production.RT upgrade works fine? You can bring up RT web interface and play around with read only parts.Anyway, upgrades across major versions should be performed with test runs, do test run, document every step, play with every aspect important to you, repeat all steps during cut over.
-- Regards, Giles Coochey, CCNP, CCNA, CCNAS NetSecSpec Ltd +44 (0) 8444 780677 +44 (0) 7983 877438 http://www.coochey.net http://www.netsecspec.co.uk gi...@coochey.net
smime.p7s
Description: S/MIME Cryptographic Signature
-- RT Training in New York, October 8th and 9th: http://bestpractical.com/training
