Migrating ePO 4.6.6 to 5.0.0 using upgradecompatibility tool.

[Former Member]

The new db.properties has the old db name which is how it is attached.  The instance name is the same so it is unchanged in the new db.properties and the server name is the name of the new server.  Application Server remains running for only a few seconds.

[Former Member]

#Thu May 30 08:41:53 PDT 2013

db.database.name=ePO4_(look in sql under data base and place name here.)

db.jdbc.driver=jtds

db.param.ssl=request

db.param.USENTLMV2=true

db.instance.name=(EPOSERVER or MSSQLSERVER)

db.user.domain=(domain name if using windows authentication)

db.user.name=(user name)

db.port=(like 1433 or that you use)

db.pool.exhausted.action=grow

db.user.passwd.encrypted.ex=fsJJ1eqSbeXg8zSNJrSM+w\=\=

db.server.name=(Server name like serverabcd)

Before editing this file take a backup of this file)

Edit with identical names and then first start application server service, let me know  if it works.

[Former Member]

Went through and confirmed all.  I also checked to make sure the account that I am using has the proper sql roles.  Still no go.

[Former Member]

Infect  I missed a pointe that you should attach DB first and then install EPo over it direction it to SQL DB. Well. Could you detach this DB and attch its own and let the services start?

Also let me know do you have your old ePO up and running?

We will go with another way now..

[Former Member]

give it a try :

Change the DB user passwords

• db.user.name  is the name of the account ePO will use to connect to SQL.
• db.user.domain indicates if ePO is using Windows or SQL authentication: if blank, it's using SQL: otherwise this is the name of the domain that will be used for Windows authentication.
• db.user.passwd.encrypted.ex is the password hash for the account.

Change db.user.passwd.encrypted.ex to db.user.passwd and enter the password in plain text. So for example if the password was "foobar", the entry might look like this:

db.user.passwd.encrypted.ex=WiZy6IX3X4iLqq6AljJWHA\=\=

You would change it to:

db.user.passwd=foobar

start all three services and post logs event parser log and orion.log)

[Former Member]

Tried that.  I found an article that discribed changing the password to plain text.  I did this just to make sure the password was correct.

I also uninstalled ePO and then attached the DB.  I then tried reinstalling ePO and selecting the DB but it wanted to delete the DB and create a new one.  I then using "Restore ePO from an existing database snapshot" but it told the DB version was wrong.  4.6.6 and not 5.0.

[Former Member]

Okay.

Do you have your old epo up and running?

Do you have your ePO 5.0 with its own DB up and running?

Now I will register your old ePO with new one and then we will transfer your clients to this ePO and Agent to server com keys Plus policies? I think DB is 32 bit and 64 bit machine is not accepting it. Well please reply the above and lets continue with second plan.,

[Former Member]

They are both up now.

[Former Member]

great.

Is this new epo part of your domain?

Now go to register servers and register a LDAP server. Once you do post back.

[Former Member]

All done.