It's not a "good" strategy, but here's what we do. We only work on a certain number of things before moving them into production. Once the project is complete, we restore the backup of production to our other servers, then start on whatever is next.
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of William Rentfrow Sent: Thursday, June 05, 2008 12:32 PM To: [email protected] Subject: Moving Task Templates, Support Groups, etc ** Just curious...this is with ITSM 7 and specifically IM 7.x We have 4 servers: Dev, QA, Training, and Prod. We frequently have to move things that are ID-dependent from server to server and I wonder how people are doing it. For example, assignment information for groups reference the group ID which can quite easily be different when you move groups from server to server - you have to take care of this when you do the move and re-map things. Task templates (IM patch 9002) reference the parent ID of the Task group template and are also prone to the same problem. Anyone come up with a good strategy for doing these moves? William Rentfrow, Principal Consultant [EMAIL PROTECTED] C 701-306-6157 O 952-432-0227 __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ Private and confidential as detailed here: http://www.sug.com/disclaimers/default.htm#Mail . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
