This content has been marked as final. Show 3 replies
I'm new to EPO too, but as I understand it the clients look for the server IP, DNS name then Netbios. If you unplug the old server, then give the new one the same IP and/or hostname won't they just connect to that one?
I'll eventually have to migrate my EPO 4 server to a new box so I'm interested to know how this works.
I'm impressed! Let me know how this idea works.
Here's the Loop logic which utilizes an input file named Hosts.txt,
Formatted as such:
And produces a single listing of all your hosts showing their SiteList "ServerName":
< Not Needed >
You can run this before and after your script to confirm the change.
Of course, the easy modification to copy the file is left as a drill for you! Good luck!
Thanks for your reply. Today I found an solution, we have an script for pushing Microsoft patches to servers in our DMZ, with a little modification I can use that scripts to execute this migration.
It's a quite complex scripting with use of psexec and so on, and everything can than be done remotely from our managementservers. Unfortantely I'am not allowed to share it on the internet.
Anywany, everyone who has taken the effort to reply, thanks very much.
In ePO 4.0.2 it is much easier to migrate this clients, as soon as you have an list op ip-adresses of hostnames. You can import them into an Directory/Site,and the run an deployment task on that site to deploy the McAfee Agent, and systems are migrated. Of course not forget to delete them from the old ePO server.
Quote from the ePO 4.0.2 product guide:
Creating a text file of groups and systems
Define the groups and their systems by typing the group and system names in a text file. Then
import that information into ePolicy Orchestrator. You must have network utilities, such as the
NETDOM.EXE utility available with the Microsoft Windows Resource Kit, to generate complete
text files containing complete lists of the systems on your network. Once you have the text file,
edit it manually to create groups of systems, and import the entire structure into the System
Tree.Regardless of how you generate the text file, you must use the correct syntax before importing
1 List each system separately on its own line. To organize systems into groups, type the
group name followed by a backslash (\), then list the systems belonging to that group
beneath it, each on a separate line.
2 Verify the names of groups and systems, and the syntax of the text file, then save the text
file to a temporary folder on your server.
Importing systems and groups from a text file
1 Go to Systems | System Tree, then click New Systems. The New Systems page
2 Select Import systems from a text file into the selected group, but do not deploy
3 Click Browse, then select the text file.
4 Select what to do with systems that already exist elsewhere in the System tree.
5 Click OK.
The systems are imported to the selected group in the System Tree. If your text file organized
the systems into groups, the server creates the groups and imports the systems.