In May 2020, Microsoft released an update, "Version 2004", which included several important and significant security updates, including some changes to the way an underlying set of services known as the Distributed Component Object Model (DCOM) functions. A side effect of these changes was that, at least temporarily, it introduced some disruption to how some orchestration and IT management tools function, including Block 64's agentless inventory functions.
What's the scope here?
This issue would affect any Windows 10 orWindows 2019 machines with the 2004 update (released in May, 2020 initially). They will encounter issues being remotely interacted with by tools that leverage older versions of DCOM. Some tools known to be affected by this update include Microsoft's own MAP tool, Tenable's Nessus, and of course, older versions (pre-September 2020) of the Block 64 tool. But we're happy to report - not our current version!
How do I tell if I'm affected?
Are you using our virtual appliance? If so - this issue was self-corrected, so no action required. But if you are using our Windows-based discovery application, and downloaded your Block 64 discovery software before September 16th, 2020, you might be seeing the following error message during a device inventory on any machines running the 2004 update:
SMB Error: DCOM SessionError: code: 0x80010111
OLE Received a packet with an invalid header
But not to worry, this can be easily remedied - you'll simply need to update your Block Application. Below are steps on how to do exactly that!
If you downloaded your Block 64 discovery software after September 16th, 2020 - no action required!
Help! I Need to Update my Block 64 Discovery Application
- First, let's disable discovery and the overall functioning of the Block application. Press the 'power' button at the top left to disable activity, and close the App completely by right clicking in the system tray, and selecting 'Quit'
- Open the services.msc MMC snap-in, and navigate to and stop the "Block 64" service
- Navigate to "C:\Program Files (x86)\Block 64\Block\" and delete the entire "Python" folder
- Download the patch that we've prepared for this situation
- Extract the archive you have downloaded above to "C:\Program Files (x86)\Block 64\Block\"
- After extraction is complete, navigate to "C:\Program Files (x86)\Block 64\Block\" and verify that Python folder you deleted earlier is now present again
- Go back to your services.msc window, and start the "Block 64" service you had previously stopped by pressing "Start" on the side panel
- Open your Block Application from the Start Menu
- Reset any failed statuses from within the Missing Devices window
- Press the power button at the top left corner to start Scanning