Must be a Windows thing. It is not installed with AR System or Email on Linux RHEL. That's using the 7.1.0 patch 2 installs.
Rick On Wed, Mar 12, 2008 at 11:38 AM, Joe D'Souza <[EMAIL PROTECTED]> wrote: > ** Rick, > > It is released to the best of my knowledge.. It usually gets installed > with the Email installation of 7.1? > > These are the initial results I get if I run it which sounds like it is > the new version.. > > E:\Program Files\AR System\AREmail\KCH1D001>archgid > Action Request System Change ID Utility Version 7.1.00 Build > 200707311333 > (c) Copyright 2002-2007 BMC Software, Inc. > > > Enter user name: > > I haven't used this version of it to say if it works or not but I would > assume it should.. > > Cheers > > Joe > > -----Original Message----- > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] Behalf Of *Rick Cook > *Sent:* Wednesday, March 12, 2008 2:11 PM > *To:* [email protected] > *Subject:* Re: What specifically breaks upgrades? > > ** Good advice, Joe, except that AFAIK, archgid isn't available for v7.1yet - > if it ever will be. I don't think the > 7.0 one will work against 7.1. > > Rick > > 2008/3/12 Joe D'Souza <[EMAIL PROTECTED]>: > > > ** Allen, > > > > I would put using reserved field ranges to create your custom fields to > > be a number 1.. By reserved I do not mean AR System reserved but the ones > > that Remedy Developers use for their application.. If in case you have > > created custom fields and using their range that they usually create fields > > from, then in the event that they use the same ID, it could break your > > upgrade.. > > > > I would say the same thing for using the immediately available user > > range.. Avoid those too.. I have seen Remedy engineering using some of those > > fields for trim fields etc. too in the past, as they do not bother to give > > those trim fields a specific ID.. stay clear of those.. use ranges above the > > 6, 7 or 8 million range.. That way you could be sure that they would not > > invade that range.. > > > > In case you have already done the above, I would use the archgid to > > correct the problem and give your fields an ID on or above the 6 million > > range.. > > > > Cheers > > > > Joe > > > > -----Original Message----- > > *From:* Action Request System discussion list(ARSList) [mailto: > > [EMAIL PROTECTED] Behalf Of *Moore, Christopher Allen > > *Sent:* Wednesday, March 12, 2008 12:56 PM > > *To:* [email protected] > > *Subject:* What specifically breaks upgrades? > > > > ** > > > > Hey everyone- > > > > > > > > I'm putting together a plan to upgrade from 7.0 to 7.1. We have done > > some modifications to the system, but nothing too drastic. Form changes, > > additional workflow, but (as far as I know) no changes to the BMC OOTB > > workflow. > > > > > > > > What sorts of changes specifically are problematic when upgrading? > > > > > > > > Windows Server > > > > SQL DB > > > > > > > > Thanks! > > > > Chris > > > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
