Need to install ENS & ENS/TP using a Powershell script

[nicksullivan]

We need to be able to install McAfee elements to bare metal server builds as part of the build process, the preferred method is using Powershell. Have used this code invoke-command -Computer $servername -ScriptBlock { Set-Location c:\source\mcafee\ENS_Install_10_6_1 -ErrorAction Stop $myargs='ADDLOCAL'+'='+'"tp"'+' /quiet' $abc=(Start-process setupEP.exe -ArgumentList $myargs -PassThru -Wait -ErrorAction Stop).ExitCode write-host $abc } this doesnt work remotely...but if you remove the invoke-command part & run the inside locally works like a charm We get an error code 16019. Anybody out there able to assist?

[AdithyanT]

Hi @nicksullivan,

Thank you for your post. I am not really a powershell expert, hence I would not really comment on that part and please correct me if I am wrong, I am afraid that would not really be a supported method of deployment as well.

Having said that, I would recommend looking at this error the same way it would be looked into when we run the deployment via ePO. I would start by looking into the installation logs for this. Do you have any installation logs created in the default folders (C:\Windows\Temp\McAfeeLogs or %temp%\McAfeeLogs\?

[cdinet]

This really belongs with the ENS folks, so I am going to move this post over to them.

[nicksullivan]

Thanks

[AdithyanT]

Hi @nicksullivan,

Any luck with the logs? Although the ,method is not officially supported, I would be glad to see if you have any logs/log findings that you need help with. Also We have our fellow community members who might help us with this.

Thank you for your kind understanding here!

[nicksullivan]

Hi Adithyan

the 'thinking' has changed now and we are considering

1. Installing the agent via the PS script, as that bit works
2. let ePO automatically install ENS or MOVE (whichever is appropriate) from the console

My question now is what do I need to do to get ePO to install on a device it finds with an agent, but no software?

[cdinet]

You can set up a new client task assignment, agent deployment type, and create a task to deploy the desired products.  If you set it to run immediately, then as soon as a new system is added to the system tree, it will get the task and invoke it.

[AdithyanT]

Hi @nicksullivan,

Thank you for your response. Apologies for the delay. As @cdinet rightly said, you can use the run immediately task to take care of the installation for all endpoints that get reported to your ePO once Agent installation is complete.

However, I would like to know if you wish to install ENS and MOVE on the same machine. I am guessing you would not want that to happen, but please correct me if I am wrong. Depending on your answer, the solution may need a bit more tweaking.

[nicksullivan]

Hi Adithyan
You are correct, the device would have EITHER MOVE or ENS, not both

[AdithyanT · Accepted solution]

Hi @nicksullivan,

Thank you for the response. Based on this, and pardon my lack of knowledge with MOVE, I would presume MOVE is going to be used for Virtual Desktops and ENS for the physical workstations. Keeping this in mind, we need to have separate "playground" for both.

We either need to put these machines separately in to 2 different groups or we need to have a "tag" in place to identify which is a Virtual machine and which is a physical machine.

Now we can have the deployment tasks in place for specific groups or apply it on the root group "My Organization" and make these 2 different deployment tasks run only for their specific tagged machines (for example: MOVE installation only on those machines tagged as Virtual ones).

I can give you a step by step answer if you prefer based on the method you will be implementing. If you wish to use tagging, I would like to know if there is any specific differentiation between the virtual machines in terms of their IP groups or sub nets or Operating system builds. Basically I am looking for a unique criteria based on which I can implement tagging automatically for the machines reporting to the Server. You can run through the available tag criteria by visiting Tag catalog section in your ePO.

Looking forward to know if this helpful to you!