Actually it should be the other way around.. It’s a good thing you pointed it 
out.. But thanks for pointing that out.. Its something I missed..

If installing on a new environment and migrating is your preferred upgrade 
option, then before you import any customization to a new server, if there were 
permission groups that you have created (groups with Group Type View or 
Change), or Roles that you have created that your forms have been added to, 
those need to be imported or created on the new AR System with the same Group 
and Role ID before you import your customizations.. Failing which you will have 
issues with permissions..

Joe

From: Drew Shuller 
Sent: Tuesday, April 10, 2012 2:40 PM
Newsgroups: public.remedy.arsystem.general
To: arslist@ARSLIST.ORG 
Subject: Re: Transferring in-house 6.3 code to a 7.6.04 server

** To add what JMD says, after making sure that you've transferred any 
customizations of the core forms, import your Groups, Roles, and users. Make 
sure your permissions are EXACTLY the same and you'll be ready to import your 
objects and data.  

Drew
Comayagua


On Tue, Apr 10, 2012 at 11:59 AM, Dee <ddus...@aim.com> wrote:

  David,

  I understand you going to 7.6x on solaris, but maybe you will see issue
  like, what we when thru.

  We when from 6.3p20 to 7.5.p4 on UNIX with 10g - custom service and change
  environment. As Joe pointed, if you have not  customized core forms:
  user:group, etc.. you  should be good but then you may get minor errors
  example the user form gave us a box 4 error, which made the installer fail.
  Basically delete the view (not the table) that is given the issue.

  We did this, copy your production to test, and run the upgrade work thru the
  kinks. Blow the test away again, do it again, to smooth out the process and
  steps. This way you can work with BMC on the issues.

  We found the installer failed many times,..

  we did a gradual, installing each component at a time, and work thru the
  errors.
  - ar servers
  - ardbc
  - area
  - fb
  - email engine
  (our MT is on a separate server).



  --
  View this message in context: 
http://ars-action-request-system.1093659.n2.nabble.com/Transferring-in-house-6-3-code-to-a-7-6-04-server-tp7453426p7453807.html
  Sent from the ARS (Action Request System) mailing list archive at Nabble.com.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to