This content has been marked as final. Show 6 replies
You can have as many ePO servers as you like - it's just that a client system can only be managed by one of them at a time - to switch between servers you can simply force a new agent out to the clients you are testing on.
Thanks Jmaxwell, for the update
we have the database on sql 2005. when installing the new server, i assume i point it to the current database, and then
I am going to install the new one on vmware for now to run along side the master repository.
We don't allow any access to the production SQL DB from the test ebvirinment <Shudders> ;)
We have a test SQL DB
Thanks and a good point, that is now sorted, got dba to restore a backup of the live one to a test environment and will get on with it.
"Playground Complete" grin
when i installed epo 3.6.1 patched it to the same as the live one and it was installed with an msde. i had a copy of the live database on a sql 2000 box.
I also made sure that i added to the repository all that was in the live one as well.
I then followed the mcafee instructions on migrating from an MSDE to a sql server completely.
i then attempted to logon to the teset epo server with a copy of the live database, and got the following messages:
reading files for alert manager 4.7.0
Error downloading policy translation file for ALERTMNG4700.Do you want to continue
cannot access server. the server maybe down or you may have spcified an incorrect port.
i have checked the ports etc, the only thing i can think of is the database contains info on the live server. my test server has a different name and ip address. Would this have anything to do with it.
i have reverted back to the original snapshot and removed and readded alert manager. but when it is pointing to the new database it does not load. but i can connect under the reporting epo databses to the test one. Anyone have any ideas please?