That is not a good idea at all. We found a number of issues with 7.0.0 patch
2 of the client on a patch 3 system, I am not sure what you would get with a
version that old.
If its an issue getting v.7 of the tool to your users, maybe move them to
the Web.
Howard
On 7/31/08, Shellman, David
I have to agree on this - don't do it.
A while back we had a customer with AR 4.x clients connecting to a 6.x
server - a few workstations got missed in an upgrade. One API call had
changed on the backend. Whenever a user did a certain specific search
the entire server went down immediately.
Thank you Susan, Shawn and Carey for your input, I went ahead and
upgraded the user tool to 7.1 :-).
Thanks!
Manjari R. Shrestha
Junior Programmer Analyst
SAIC
12530 Parklawn Drive, Suite 350
Rockville, MD 20852
Office: (301) 998-7364
[EMAIL PROTECTED]
Hello,
I have upgraded ARS server from 5.1.2 to 7.1. Can we use client 5.1.2
with the upgraded server? I am planning to upgrade the client as well
but wanted to wait for few weeks just to be on the safe side. Please
advise.
Thanks!
Manjari R. Shrestha
Manjari,
In general I have found that upgrading the client first is a
better strategy. The newer clients can _generally_ down grade their
behavior to be like the older client better than the older client can
talk to the newer servers. This is especially true if your talking
about security
Not to mention that even if it does appear to work, BMC support will not help
you with issues if you encounter them with this configuration because it is not
supported. I agree with the client upgrade being done first in this case.
-Original Message-
From: Action Request System
Manjari,
That was our strategy when we upgraded from 5.1.2 to 7.0.1P3 and it caused
us a tremendous amount of grief. It worked in the past to keep an older
version of the user tool but with this combination it was terrible.
Something in the login process would cause issues and threads would
7 matches
Mail list logo
