Skip to content
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

prevent detail query errors for Windows Servers #17796

Closed
roperzh opened this issue Mar 22, 2024 · 1 comment
Closed

prevent detail query errors for Windows Servers #17796

roperzh opened this issue Mar 22, 2024 · 1 comment
Assignees
Labels
~backend Backend-related issue. bug Something isn't working as documented #g-mdm MDM product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~released bug This bug was found in a stable release.
Milestone

Comments

@roperzh
Copy link
Member

roperzh commented Mar 22, 2024

Fleet version: 4.47.x

Web browser and operating system:


💥  Actual behavior

As observed in, #17476 we try to run queries for tables that might not be available on the host:

W0306 23:28:11.067581  1776 bitlocker_info.cpp:52] Error retreiving information from WMI.
E0306 23:28:11.280949  1776 distributed.cpp:187] Error executing distributed query: fleet_detail_query_mdm_config_profiles_windows: error generating table: mdm command execution: there was an error calling ApplyLocalManagementSyncML(): (0x%!X(\u003cnil\u003e))%!(EXTRA uintptr=2147947423) 

🧑‍💻  Steps to reproduce

  1. Set up a Windows server as described in 500 response for enrolled device in Fleet with no MDM status #17476
  2. Turn on Windows MDM
  3. Let the detail queries run
@roperzh roperzh added bug Something isn't working as documented ~backend Backend-related issue. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. #g-mdm MDM product group labels Mar 22, 2024
@lukeheath lukeheath added the ~released bug This bug was found in a stable release. label Mar 22, 2024
@georgekarrv georgekarrv added this to the 4.49.0-tentative milestone Apr 2, 2024
@dantecatalfamo dantecatalfamo self-assigned this Apr 5, 2024
dantecatalfamo added a commit that referenced this issue Apr 12, 2024
#17796

Fixes an issue in windows server where selecting from `bitlocker_info`
will cause the query to abort. Bitlocker is not available by default
on some version of windows server, so we first check if the optional
component is enabled before making our query
@georgekarrv georgekarrv modified the milestones: 4.49.0-tentative, 4.48.3 Apr 15, 2024
sharon-fdm pushed a commit that referenced this issue Apr 15, 2024
#17796

Fixes an issue in windows server where selecting from `bitlocker_info`
will cause the query to abort. Bitlocker is not available by default
on some version of windows server, so we first check if the optional
component is enabled before making our query
sharon-fdm pushed a commit that referenced this issue Apr 16, 2024
#17796

Fixes an issue in windows server where selecting from `bitlocker_info`
will cause the query to abort. Bitlocker is not available by default
on some version of windows server, so we first check if the optional
component is enabled before making our query
@fleet-release
Copy link
Contributor

Queries run smoothly,
Windows servers breathe at ease,
Fleet's calm, like cloud seas.

@georgekarrv georgekarrv added :demo and removed :demo labels Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~backend Backend-related issue. bug Something isn't working as documented #g-mdm MDM product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~released bug This bug was found in a stable release.
Development

No branches or pull requests

5 participants