We recently upgraded our server and followed the steps in KB71078 even though we were going 64BIT OS to 64BIT OS. It seemed to work well for us, however our DB is on a differnet server and that did not change.
- The Agent uses either the last known IP address, DNS name, or NetBIOS name of the ePO server. If you change any one of these, ensure that the Agents have a way to locate the server. The easiest way to do this would be to retain the existing DNS record and change it to point to the new IP address of the ePO server. After the Agent is able to successfully connect to the ePO server, it downloads an updated SiteList.xml with the current information.
Once the clients get the new sitelist.xml they start talking.
Thanks for the details about the agent.
What about the databases, is there anything I need to do to redirect them to the new software installation?
Before anything else, a very important question is - how many machines will be managed by this ePO server? It may be that moving ePO onto the same machine as SQL will adversely affect the performance of the machine, especially if there are other applications using the same SQL server.
As said Joe, it's was important to know how many systems are connected inyour ePO server and it also facing performance issue.
First you have to upgrade 4.5 to 4.6 than you can go for migration of ePO toDB server. There is less chances to all systems automatically connected withePO. If have domain environment than there will be possible as sailed by cpromen.
As you askabout database redirection whenever you run new setup than ePO create newdatabase there is no option you can use same DATA files in ePO setup. You haveto take backup and restore into the same but we are not recommended that thingsthere is some prerequisites before you want to use old database like sameinstallation path, extension, packages etc…it was risk.
You haveto take final decision but we strongly recommend take help of McAfee SupportTeam
There is only about 80 machines connected to the ePO server.
1 of 1 people found this helpful
That should probably be fine then, assuming a halfway-decent spec on the machine and that it's not overloaded at the moment. My recommendation would be to back up *everything* first, as described in KB66616, and then use the process in that document to move the ePO server to the new machine.
Thanks for the advice.
Will do a bit more research on the KB and then give it a crack.