Changing Out of Deployment Server

These are the general reasons I have seen in the past for changing out of Deployment Server.

• The machine is far too old and ready for retirement.
• Hardware problem with can’t be solve without changing to new one.
• Inaccurate sizing at the beginning and having disk space issue.
• JDE upgrade, different sizing, and hence changing to new machine.
• IT Outsourcing.

Therefore, as a CNC administrator, you can’t get away from doing this. I have done this few time in the past, these are the cutover steps I used as a guide. It might not cover all the scenarios but at least it is workable.

1. One the new machine, install all the require software stated in MTR, e.g. Visual Studio.
2. On the new machine, configure the Windows Environment Variables.
3. On the new machine, install the Deployment Server CD, choose to install System only.
4. Copy JDEdwardsOneWorld or PeopleSoft folder from old machine and overwrite the new machine.
5. Export JDEdwards and ODBC.INI registry from old machine. Make changes to the drive path and deployment server name, imports them into the new machine’s registry.
6. Share JDE folder with appropriate Windows security.
7. Update the Planner database.
   Update f9650 set MMMKEY='new machine' where MMMKEY='old machine';
   Update f9651 set MDMKEY='new machine', MDSERSHP='[new drive]:\jdedwardsoneworld\b7334' where MDMKEY='old machine';
   Update f00942 set EMMKEY ='new machine' where EMMKEY ='old machine';
   Update f00945 set RMMKEY ='new machine' where RMMKEY ='old machine';
8. Update JDE tables
   Update jde7334.sys7334.f00942 set EMMKEY ='new machine' where EMMKEY ='old machine';Update jde7334.sys7334.f00945 set RMMKEY ='new machine' where RMMKEY ='old machine';
   Update jde7334.obj7334.f9861 set SIMKEY ='new machine' where SIMKEY ='old machine';
   Update jde7334.sys7334.f9650 set MMMKEY='new machine' where MMMKEY='old machine';
   Update jde7334.sys7334.f9650 set MMDEPSRVNM='new machine' where MMDEPSRVNM ='old machine';
   Update jde7334.sys7334.f9651 set MDMKEY='new machine', MDSERSHP='[new drive]:\jdedwardsoneworld\b7334' where MDMKEY='old machine';
   Update jde_pd7334.pd7334.f983051 set VRMKEY ='new machine' where VRMKEY ='old machine';
   Update jde_py7334.py7334.f983051 set VRMKEY ='new machine' where VRMKEY ='old machine';
   Update jde_dv7334.dv7334.f983051 set VRMKEY ='new machine' where VRMKEY ='old machine';
9. Update the various INF files.
10. Test the package assembly, package build and package deploy functions.
11. For workstations and terminal servers, update the JDE.INI. (includes all the user profile's JDE.INI)
    [EVEREST]ServerHelpPath=\\\B7334\Helps
12. For workstations and terminal servers, update the Registry by changing the old machine name to new machine name.
13. Remove the JDE folder share for old machine.

For steps 11 and 12, you can make use of scripting tool to automate the update.
Anything I have left out? Please let me know if you find one