Discussion on installing ControlUp agents through the console. Initially, there was an issue with failed attempts due to ports being blocked and files not being able to be replaced. A support ticket was recommended for further assistance. Later, it was discovered that a permission issue was causing trouble and a specific fix was needed. It was suggested to get on a call for further troubleshooting.
Read the entire ‘Troubleshooting ControlUp Agent Installations Through the Console’ thread below:
Hey, New ControlUp user here so forgive my ignorance. My company did a POC on control up before we purchased it, and in the POC we had to manually install some agents using the MSI so we didn’t have to setup firewall rules. Anyways, I went through and un-installed the agent using the MSI so we could set it up using the real-time console so going forward updates would be easier and such. However, we keep running into this issue, where the re-install with the RC fails, and we get this error. Just wondering if anyone else might have experienced this and has an idea on how to get it resolved?
So were you able to push the agent from the console? Because that message just means that the console tried to connect to the remote machine on 40705 and nothing was listening.
You can right click the machine > agent control > upgrade/install agent.
might be the port was not opened on the windows firewall? try run a test net comect from console to the machine over the port
That is what I tried to do, but it kept failing with that error. I am able to install the agent on other machines using this method, its just the machines that previously had the manually installed agent on them that I can’t get to install.
I will check the port and find out.
@member whats the files and reh keys again. the agent might not have fully uninstalled
Added a firewall rule for both in and out bound for port 40705, and re-tried the install. Got a the same error. It did flash something about it couldn’t replace files but I couldn’t catch that.
@member I think you are on the right track, it’s almost like it still sees the agent there but can’t replace the files.
not sure it chnged in v9 but look for a smartx folder /files and in registry. software smartx
not seen issue with agent not uninstalling for a good view versions
its an old school issue
We are special, if it can go wrong, it will go wrong with us. I will try to see what I can find in the file and reg. Thanks
haha CU support love me for if it can go wrong i will find it
So I deleted the Reg file and the 2 folders in programdata and program files. Got a different error:
Here is a full screenshot of the error:
Suggest log ticket with support
Something not right
dose u account tha u have the console open writes on the target machine to install?
also are they open to the target server
I am having our Network Engineers look at the firewall to make sure it’s not getting blocked, but I wouldn’t assume that they are getting blocked because it was able to install on other machines in the same subnet. As for the permissions, the account it is using is a domain admin level account. So it should have more than enough permissions. I think I might have to submit a ticket with support at this point, but I will wait to hear back from my networking team first.
Hey Zach,
Apologies for the late reply.
The last screenshot you sent is a permission issue, not a networking issue. The way that remote agent push works is:
- The console tries to determine if the agent is installed on the remote machine by trying to query the remote machine using WMI. This step is failing. The remote machine reports access denied. Implying that the user you run the console as isn’t allowed to perform the WMI query in the error message.
- IF the service exists, stop the service using WMI again
- Send files via Windows file sharing (SMB) to the remote machines admin shares (\machine\c$\program files….)
- Modify the remote registry using WMI again to register the service
- Start the service using remote WMI again
You’re getting stuck on step 1 with a permission issue. MOST likely the user you ran the console as isn’t an administrator on the remote machine. There are 2 things you can do about that:
- Run ControlUpConsole.exe as a user who is administrator on that remote machine
- In settings > ad connections create a new set of credentials for the domain in which the remote machine is located. The console will use these credentials for machines in the domain specified under domain.
Do note for option 2:
This configuration is stored in your roaming profile. If you don’t have a Windows profile set or aren’t using some profile solution (which many organization do not for admin users), you’ll lose this configuration when you log on to a different machine.
Last but not least, if the above is too much for a Slack message (I tend to ramble), feel free to send me a direct message. We can get on a call and troubleshoot live or discuss in person.
@member Sorry I am juggling a few different fires right now. I will try to do this on my own and if I keep running into a wall, I will reach back out and set something up with you. Thank you for the guidance!
@member I tried running the .exe as our enterprise admin account and I changed the AD creds to our enterprise admin account and got the same error. So I think it is failing on step 3? It connects, then it verifies .Net 4.8, then it is when it tries to copy the files, that is when the error is thrown. I am happy to hop on a call with you and show you what is happening.
any event logs on the target machine or Console machine?
oh sorry my bad, misread the image. The image says RPC server unavailable. Is the remote machine running the windows firewall? If so, either disable it (for testing) or allow WMI through it. I think the Windows firewall groups all of them as remote administration.
If there’s a firewall between the console and the machine running the agent, same thing, allow WMI and SMB
That did the trick, I was able to temporarily disable the local firewall and it worked. Just need to build a GPO to push out to the others. Thanks for your help on this.
Continue reading and comment on the thread ‘Troubleshooting ControlUp Agent Installations Through the Console’. Not a member? Join Here!
Categories: All Archives