-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solved: Error In Query #121
Comments
What version of windows are you seeing this on? |
I’m seeing on Windows 10, 64-bit, build 19042
But we have more than a dozen identical systems that installed without any errors
|
Later, I will have some commands for you to try, so we can figure out what is going on with those machines |
Thank you, much appreciated!
Also, I don’t know if it matters, but we had meshagent previously installed on these systems, but removed it since we set up a new custom name and directory for the agent to live at. Most systems haven’t had an issue with this.
|
Try running this command, it will output more info, and should help pinpoint where it's failing: |
Thanks, I just ran it on a few systems on different networks, received the same results:
|
If you do |
Ok, try running this command (kinda long so may want to cut/paste): |
Just tried it, it outputs the same as before
|
Does this command work on your machine? |
Running from powershell, I get the following:
---- edit---- I ran the same command above on another system that the agent installed on, LOTS of output |
I got it!!! your command above got me looking into fixing the wmic repository. After stopping WMIC, reseting the repository, then letting it rebuild, the above command ran correctly and the meshagent installed without an issue. Guess I'm gonna have to write this into my onboarding script. Thank you! This was a big help!!! U guys are the best! |
Interesting! I'm going to modify the code to catch this exception. I never expected this particular query to fail. I may make it save a log entry mentioning the wmi repository, so others with the same issue can resolve it |
For anyone interested, below is a code snippet for fixing the WMI issue from the powershell script I wrote for deploying meshagent. If anyone is interested in the full deployment script, let me know and I can make a new thread with a skeleton script for users to follow.
|
Afternoon guys,
We've been slowly but surely streamlining how to deploy software to our endpoints and figure out some great scripting for installing MeshAgent on Windows endpoints. But I came across a really odd issue on random systems.
We have a group of systems where the agent just won't install, we get the below error
The above is the result of running the exe with -install or -fullinstall . The oddest thing is if I run it with just the run flag, the agent connects without an issue.
Any ideas?
The text was updated successfully, but these errors were encountered: