With Unix it is easy, you can just do a find command on IP or hostname in remedy folders to find all the references and make changes accordingly. But with windows not sure if the same approach will work with registries etc.. In either case I would suggest once your admins copy the VMs just remove/uninstall all remedy components/folders and just reinstall those again as a server group option. That way you would not miss any conf file or registry server name references. Since you are not really doing any upgrade install, just reinstalling same version the installer should not take much time. May be couple of hrs for the entire ITSM suite.
Not sure how much it would help you the following. We had to rollout new ITSM env few years ago and we had to copy the db from preprod to prod during the cutover. So I went through several postings in arslist,bmc support site, bmc communities and made a list of items to do before and after. Some of the steps might be outdated or may not valid depending on the specific version so take it with grain of salt. Restore db from Development to Production: Pre db copy: 1. In production servers disable email engine,escalations in ar.conf 2. In dev server disable email mail boxes 3. Delete all pending or unwanted email entries Post db copy: 1. Update the default web path 2. Update Servername, Servergroupname, servergroup ranking entries 3. Form data changes: --> Report form entries with new Server Name -- change server name to <development>.fqdn or <development> --> SHARE:Application_Properties, HelpFile URL pointers --> SYS:Application form -- Survey URL --> CAI Application Registry -- In Connection tab, change all Server names from <production>.fqdn to <development>.fqdn --> SHR:Association -- The server name is stored in two fields on the form - Server 1 and Server 2 --> Configure Custom Form Info --> SYS:Attachments form --> CMS Configuration Management --> AP:Notifications - Check any custom notifications with Server links --> AP:Rule Definition (Server = "@") --> AR System Server Group Operation Ranking --> AR System User Preferences -- Change Report Server values from <production> to <development> for any user account you are going to log in with on development --> AR System Administrator Preferences -- Partial List Settings - Partial List Details:Other - Pack List Settings --> AR System Searches Preference -- Delete records from original server --> AR System User Central File -- Delete records for user --> KMS:Administration_Integration-- Change Server Name and Short Description --> SRD:STAGE:MasterDataMappingList --> SRM:ApplicationSettings, if SRM installed, to point to correct web path --> AST:ARServerConnection -- AR Login Info --> AST:ComplianceARBased_Advanced--AR System License Type Compliance --> SYS:Escalations --> SYS:Attachments --> SLM:ConfigPreferences -- Update Dashboard MidTier URL --> SLM:RuleActionSetValue_base -- Found four records to change with SLA_destination Server Name = <production>.fqdn,Changed all of them to "@" --> SLA data sources, service agreements, and service targets with milestones, after the db had been restored --> CHG:CCMCalendar:PrintActionWUT -- Active Links that contain server references --> AREmail Configuration -- update with production email accounts --> Table fields -- check with sql select distinct tfserver from field_table --> AIS:GlobalPreferences form (Atrium Impact Simulator) --> AIE > EIE:ApplicationSettings form (field name: Help File Path) --> AIE > EIE:BackUpLoadFlag form entries (field names: Host, Internal Instance Name,InstanceName) --> AIE > EIE:DataExchange form entries (field names: Instance Name, zTmpInstanceAlias) --> BMC.CORE.CONFIG:BMC_FederatedInterface records (Field name: ARServerName) --> IEORA:RuleHelper (field name: Path) --> EIE:CommonDialog (Help File Path) --> Reinstall and Reconfigure AIE and all Data Exchanges --> Check in remedy metadata(AL,FL tables) to see any hard code server references. 4.The mid-tier configuration, where you specify the Data Visualization server 5.If you have customised any of the OOB notification messages to include a hardcoded a url then you need to change the server name reference. 6. Make sure all the integrations (webservices,scripts,apis,dblinks) pointing to correct environments. 7.Enable email engine,escalations. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
