Need to upgrade ePO 4.6.7 to 5.3.2
ePo 4.6.7 is running on Win 2008 32 bit server .New server win 2012 64bit prepared for 5.3.2
and DB SQL 2008 32bit sp1 is running on different server
Could you kindly keep to one thread in your attempt to obtain assistance? This is the (3rd) thread you have created referring to the same Topic. Please know that someone will eventually add to the discussion.
I might ask if I may, do you have a 'Grant Number' which you or your IT Department could seek assistance through the Portal?
upgrading the EPO Server in your way is to complex and there will not be any step-by-step document available. Enclosed some options which can highly impact your EPO upgrade.
For the first step to clarify the infos above you can use the UpgradeCompatibility Tool which is included in the EPO Setup zip. It shows which extension are not compatible with EPO 5.x version.
Just a question: Do you need the existing Events? If no, i would suggest a new EPO server. Transfering the existing policies and so on and afterwards registering each EPO Server to the other. So you can "transfer" the endpoints to the new EPO environment without any installation on the endpoint.
As you can see, there are so many different options which can impact a EPO Server upgrade and therefore it is not possible to provide a step-by-step guide. To generate such a document you have to know the exactly status of the existing EPO server and have a goal about the new EPO server. Then it is possible to design a suitable upgrade szenario for your environment.
Another question: Do you habe a solution partner which assists you when doing configuration changes with EPO??
Hope this helps,
it depends.... when starting the EPO setup the actual installed extensions are checked if there is an old unsupported extension installiert.
Yes, if there is nor error message you should be able to upgrade....
Please remember, do a safety check with your extension or install the latest available extension before upgrading. Also make a backup of you EPO Server and the Database, so can have a Fallback Strategy if there is an error.
Absolutely important, check the database maintenance and the access rights to the SQL Server.