They will work with 4.6 but be advised that the 4.0 agent is not aware of multible agent handlers. It will only try and communicate with the first agent handler (spipe site) on the list in the sitelist.xml. Obviously if you only have a single ePO server with no addtional agent handlers you won't need to worry about it.
I manage a couple of legacy 2000 servers with Agent 4.0 and VSE 8.7 from within ePO 4.6 perfectly fine.
The only thing thats an issue is the install. You won't be able to deploy the 4.0 agent directly from ePO but you can do a manual install but with ePOs sitelist and keys.
Below is the instructions in the release note of the 4.0 agent (KB53808)
Installing the agent with user-selected site information and user-selected keys
Use this command to install the agent and specify a site list file and security keys (srpubkey.bin and reqseckey.bin) other than the defaults. This command is useful when upgrading an agent using framepkg_upd.exe. It specifies the server with which the agent communicates, irrespective of the site information embedded in the original installation package.
framepkg.exe /install=agent /siteinfo=<full path of sitelist.xml>
The security keys must be located in the same folder as the site list. Use ePolicy Orchestrator to export the files:
- Export the siteinfo file:
- Select Software | Master Repository.
- Click Export Sitelist.
Save the file to a new location.
- Export the security keys:
- Select Configuration | Server Settings | Security Keys, and click Edit.
- Select Master Agent-server secure communication key, and click Export.
Save the files to the same location as the siteinfo file.
- Export the siteinfo file:
Thank you very much for your replies, now I've also found this thread about the same question.
Did you enable the "Allow package check-in for any repository branch" check?
soon I´ll need to migrate some W2000 with agent 4.0 to an epo 4.6 console. Are you sure agent 4.0 can´t be installed from the epo 4.6 console. We have the 4.0 agent installer and I can create a task to install it in a client. Did you tray and it failed? Otherwise I´ll need to follow your advise to manually install the agent so the machines hungs from the new console. I´m wondering if it would work if I create a relationship trust between the two consoles. Is it possible between 4.0 console and 4.6?
agent 4.0.JPG 46.4 K
If you check the system requirements for all McAfee Agent versions you'll see that MA 4.0 Patch 4 is the last agent version to support Windows 2000.
I believe you can only have one agent checked into ePO at any one time and ePO 4.6 only has agent 4.6 then the only way to manage Win2000 in ePO 4.6 is to manaully install the 4.0 agent.
I have Agent 4.6 in the Current Branch and Agent 4.0 in the Previous Branch, but I don't deploy them through ePO.
I will try to install agent 4.0 from the evaluatión branch to a w2000 while I have 4.6 in current evaluation. At least there is the possibility to have both versions checked in at the server. Other thing is if the deploy will work.
agent.JPG 18.8 K
As far as I know it's possible to deploy McAfe Agent 4.0 patch 4 to windos 2000 computers through ePO, I did it it not so long ago and it worked for most of these servers