Browse your product documentation including release notes and installers
Update 10/18 - Added known issue DSEN-4004
Update 11/13 - Added issues associated with the re-release of the 3.3 sensor
Update 12/6 - Added additional fixes associated with the 22.214.171.1244 sensor
Update 12/18 - Added information regarding security vulnerability resolution
Update 1/18 - Added DSEN-4520
I do not see the update on our console
was there problems with the update that merit it being pulled? I no longer see if available from the console, but I had downloaded it while it was still listed. Should I be concerned about installing version 3.3?
It was available and then was apparently causing BSODs. There's an update about it in the console on the upper right of the screen. Not sure when it will be re-released. I think they're testing with the customers who saw the BSOD before they release it to the rest of their customers.
Has anyone faced any issue with this new CB defense sensor version 126.96.36.1992 ?
Under Known issues its mentioned that with CB sensor version 3.3 "Major Windows updates occasionally fail" and if we have to avoid it we need to bypass the system and then update the windows and then disable bypass.
Although its said that occasionally fail but if it did happen then its a serious issue since its not possible to enable bypass on all systems where number of system count is huge
i encountered the issue where the CB cloud portal is not showing the updated enpoint CB version 188.8.131.522 while the endpoint has been updated to 3.3.0982. Should I be concerned about this latest version?
I installed the CB 3.3 but its showing correct version locally as well as in CB console.
1)On CB cloud portal is it showing different version or its empty?
2)Are you able to see the 3.3 version locally on the system?
3)Is this is related to any specific OS or on all OS?
4)On how many systems you are experiencing this issue?
If you think everything is alright from your end and its a generic issue on all systems then you should raise this concern to support so that if this is really a issue then it should get fixed
Is there available function "Go Live" ?
as a point of reference, I've had 184.108.40.2063 installed on my daily driver workstation since 10/5 and I haven't encountered any issues specifically, but it looks like waiting for 3.4 is the next best option.
About 05 instance (defense-prod05.conferdeploy.net), when will ver 3.3 sensor be released?
We cannot upgrade from GUI...
Has anyone installed the CB sensor 3.3 with SID option for Enabling the RepCLI Supportability Tool - User Groups.
I installed it but I am not seeing any option how to use it.
Let me know if anyone has tried this
Seeing a lot of users complaining about the freezing of applications for a window of time usually becomes unresponsive for 1 to 2 minutes and then goes back to work.
When its happening?I mean after you start the system or when you open any application?
Is it on workstation/laptop or server also?
Have you checked this with CB support
Hi, @haaris this is occurring throughout the day during normal operation. You can be in the program and a window pops up or clicking a submit or ok contextual button and the entire system seems to freeze. You can still move the mouse but cannot click or type for up to 2 minutes so far.
Can you revert 2-3 systems to old version 3.1 from 3.3 to check if its actually related to new version of CB.
Have you raised this query with CB support team
@haaris The older version of the client is working just fine at this time. Have not opened a case due to time and need to prove that this is related to the current version. Will begin working with support as soon as I can get some breathing room.
You should be able to execute commands through the command line by running a command in the command line like so -
C:\Program Files\Confer>RepCLI.exe status
The fix for the Redstone upgrade problem is currently targeting the release of the 3.4 sensor.
I do not see 3.3 in my console and it sounds like that might be a good thing. Has it been pulled and if so why does this not show up in the consoles NOTIFICATIONS section?
Can anyone tell me what is the difference between 220.127.116.112 and latest one 18.104.22.1684.
Are their any specific issues resolved in 984 which were not there in 982
Refer to the 'Update 11/26:' section on the following article:
The following post indicates that the new 22.214.171.1244 will be available for Prod05 on Dec 13th:
I think the availability issue, is just timing of release date to each servers and the date problems were found with modules.
126.96.36.1993 was available for all servers at one time, but had been pulled due the BSOD and boot hang problems.
188.8.131.523 and 184.108.40.2066 were available for test users only.
220.127.116.112 was available to Prod02 and some other users, but new BSOD problem was found before release to Prod05.
Finally 18.104.22.1684 is getting provided for all servers.
And I hope, the coming new 3.4 sensors gets released smoothly. Fingers crossed.
Thanks @haro, good info there, I appreciate the link.
Fingers crossed for a stable 3.4 sensor indeed.
I have to wonder if RepCLI only get's enabled on new installs, not upgrades. In this case it's kinda annoying to have to uninstall and then reinstall the newest version to get the enhanced ability. Sounds like fun...
The team is reviewing the functionality for enabling RepCLI access from the console. Its not in short term plans but it is on our radar.
In the meantime, you can file a feature request for enabling RepCLI in idea central.
@haaris The issue represented by DSEN-4237 & EA-13407 was the issue that initiated the maintenance release and was resolved between 22.214.171.1242 and 126.96.36.1994
@haaris In regards to your comment on OS upgrades being blocked, the 3.4 sensor has some improvements beyond the bypass scenario.
Users can workaround this issue by temporarily adding the following paths to bypass:
The user can also workaround this by ensuring the policy configuration: "When an unknown application tries to run - deny/terminate" is disabled when attempting to upgrade.
188.8.131.523 NO BSOD but conflicted with our Citrix environment.
184.108.40.2064 Deploying to our test devices to validate working with Citrix and ensure no BSOD.
3.4 Hopes it get's released soon but if 220.127.116.114 pass validation test's will be a while before rolling out 3.4 to production due to prior conflicts with version releases.
I'm in this boat as well, I pushed out a few hundred of the 3.3* sensors for testing, and now none of them seem to have the CLI_USERS option set. It would be awesome if this CLI_USERS SID string could be set within the PSC portal, so when you trigger an upgrade from the portal, it passes this parameter down for the upgrade.
EDIT: looks like there's already an Idea Central post for this here: https://community.carbonblack.com/t5/Idea-Central/Allow-RepCLI-authentication-to-be-enabled-on-exist...
Everyone go vote! :)
Major Windows updates occasionally fail. This has only been observed
during upgrades from Redstone 3 to Redstone 4. Users must place the
sensor in bypass mode to upgrade major operating systems, and then
re-enable the sensor."
I can officially state that I have "observed" this with an upgrade from Redstone 4 (1803) to Redstone 5 (1809). Two consecutive failed upgrade attempts. Then I remembered seeing this issue in the release notes, so I placed CB in bypass and surprise, the upgrade completed with no problems. This REALLY needs to be fixed. I am not going to bypass CB and manually upgrade every computer when we finally approve 1809.