George,  at first I agree with SASkiwi.  It would likely the best thing to have multiple metadataservers running (9.2/9.4) with the needed port isolation.  By that you are able to do a reliable conversion. I would add not to uninstall anything of 92. Just leaving all in place. While installing a windows-registry is used to determine the location of SAS shared components. As you have installed 9.3  after 9.2 It think the shared components of 9.3 could be placed within 9.2 (or vice versa). Something to look at, giving attention is (64-bit 32-bit  deployment SAS 9.4): http://www.linkedin.com/groupItem?view=&gid=3714320&item=263537284&type=member&commentID=156927560&trk=hb_ntf_COMMENTED_ON_GROUP_DISCUSSION_YOU_FOLLOWED#commentID_156927560.  With this kind of ideas and planning it is important to know well the current situation, which parts of all the possible SAS components are used and are important in a migration. We now: - 9.2 metadata-server, so expecting AMO/Eguide SMC and some other clients    Multiple Java versions can be installed parallel.    Strongly advisable to use a Private Java approach,. Using the version delivered with each SAS version. -  9.3  could be joined with SAS 9.2 and a SAS/connect or a DMS classic or a Eguide/ SAS-local approach.     The Eguide local onnection is made by a Windows-registry setting. This setting was mostly likely change when installing 9.3 aside  9.2. It will change again with 9.4. - Connection is made by Microsoft Terminal Services. You are running client processes on the server. - We did not hear SAS – Webservices (Portal dashboard) and not Eminer.   Not having this makes it a lot easier as no webserver an no webdav javacontainer is involved. The only thing on this analyze test/check thorougly your plans and the impact on another machine. Being surprised by unexpected issues and having no fall-back restore to the old running situation in a production environment is the nightmare. ... View more