Forum Discussion
SCOM - Update Agent Fails
Hey there,
Recently upgraded from SCOM 2019 to SCOM 2022 and have a bunch of agents that won't upgrade. All of the agents that are failing are in a separate domain within the same forest. I have dedicated accounts for servers in each of the domains shown above and all of these agents were initially deployed using those accounts.
root.local - some agents live here, all have been upgraded successfully
- otherdomain1.root.local - SCOM server and most agents live here
- otherdomain2.root.local - some agents live here, some fail to upgrade, failure info below
- otherdomain3.root.local - some agents live here, all have upgraded properly
The error message I get is:
The Operations Manager Server could not find directory \\servername\C$\Windows\. Agent will not be installed on computer servername.otherdomain2.root.local. Please verify the required share exists.
Operation: Agent Install
Install account: otherdomain2\scomacct
Error Code: 80070035
Error Description: The network path was not found.
I have:
- Verified that the account has local admin on all affected servers.
- Logged into the same servers using the associated account. I'm able to create files locally and manage the configuration of the SCOM agent through the control panel applet.
- Remotely browsed to the share that the error says it can't access using the account.
Not sure why there are issues with the servers in otherdomain2 since they shouldn't be any different than servers in root.local or in otherdomain3. Thoughts?
TIA
~dgm~
2 Replies
- rohithmurthyCopper Contributor
I tried this even i am getting this same issue, i have upgraded dot net 4.7 version on agent but still getting this issue,DGMalcolm
DId you got any breakthrough on this
Thanks
Rohith
- DGMalcolmIron Contributor
rohithmurthy- I'm afraid that this question didn't get me very far. The agents all appeared to be properly configured, connectivity was good, .NET was up to date (4.8) and all of the other expected check boxes were checked. After some additional investigation, I ended up removing the existing agents manually then reinstalling everything, again, manually. Since all of that was completed, the agents have worked properly.