This post is more than 5 years old
13 Posts
0
39726
March 24th, 2015 19:00
OME 2.0.1 Installation to alternate drive letter
My customer has a requirement that all data and applications be installed on separate drives from the base OS. When I first installed OME 2.0, I was able to direct the installation to the "D" drive for most of the application installations. When I attempted to upgrade to 2.0.1, it migrated most of the application files to folders under drive "C" and I never saw an option to choose an alternate folder location. I was required to restore the server to its original configuration. Will a future version of OME allow for the installation to a different location other than "C"?
No Events found!
DELL-Vijay B
183 Posts
0
March 25th, 2015 09:00
Hi,
Thanks for the update. The issue you encountered looks like a bug in 2.0 - > 2.0.1 upgrade path.
As a workaround, you may uninstall OME retaining the old database and do fresh install of OME 2.0.1 specifying the desired location and the retained database.
Thanks,
Vijay
Dell-Ranveer
96 Posts
0
March 24th, 2015 23:00
Hi Cmangiarelli,
Thanks for your post!
While upgrading OME, by default installer will take the location where OME of (older version) is installed so you won't get an option to choose an alternate folder location while upgrading.
And as well changing folder location during upgrade is not planned for future version as of now.
Note: But OME does allow user to select an alternate folder location only during fresh install of OME which can be done by selecting 'custom' install option.
Hope this helps.
Thanks
Ranveer
cmangiarelli
13 Posts
0
March 25th, 2015 08:00
Based on what you posted, my upgrade of OME 2.0 to 2.0.1 should not have changed the installation of the basic files, but yet when I performed the upgrade, almost all of the software was relocated from the D drive to the C drive. What you posted may be the expected behavior of the ugprader, but in my case, it physically moved almost all of the files.
cmangiarelli
13 Posts
0
March 26th, 2015 10:00
Thanks, at least you know it's a bug in the installation. Unfortunately, I can't uninstall the current version right now (customer mandated) but hopefully a future patch will resolve this.