(imported topic written by sinucus)
I recently upgraded from 9.0.586 to 9.1.1088 and I still have the red warning splash on the left domain panel in my console. If I run the relevance for it through the QnA it reports as false and if you look at the applicable computers tab it reports as 0. How do I get this warning to go away? I have closed the console, I have cleared the cache, I have restarted the server. What else do I need to do?
(imported comment written by sinucus)
I think I might have nailed down why I’m getting this error. The question is, how do I upgrade it?
q: version of file (value “base” of key “HKLM\SOFTWARE\BigFix\BESAPI\Paths” of registry as string & “BESAPI.dll”)
A: 9.0.586.0
T: 0.608 ms
I: singular version
(imported comment written by sinucus)
Sure enough, that was it. I ran the following fixlet and it took care of it.
1766 Updated Windows Platform API - IBM Endpoint Manager version 9.1.1088.0 Now Available! Critical BES Support 0 / 42 0 Upgrade 25.88 MB IBM 5/1/2014
(imported comment written by vorosp)
Hello,
I’ve got the same message, but the server version is 9.0.853.0 in our environment, and the following registry key is not available: HKLM\SOFTWARE\BigFix\BESAPI\Paths and BESAPI.dll file is not found.
Do you have any idea why I’ve got this “security exposure detected” message?
Thanks.
(imported comment written by Tim.Rice)
You should be able to click the “
Security Exposure Detected!
” line and be taken to a Fixlet where the Description will list the reason for the Warning.
By way of example, I’m also running a 9.0.853.0 server, but two of my Console Operators have not recently turned on their Virtual Machines (Mac Admins with Windows VM’s) and their Windows VM’s are still reporting the older version of the Console. I have an Open Action for the Upgrade fixlet that will catch their machines the next time they boot their Windows VM’s.
Now it’s just a waiting game. (I’ve actually emailed them asking them to boot their VM’s as soon as possible).
(imported comment written by sinucus)
Well, not exactly. When I clicked the “Security Exposure Detected!” line it took me to the Server fixlet which is what I talked about in the first post. It wasn’t until I reviewed ALL fixlets in the BES Support site that I noticed that Fixlet 1766 was relevant. The security exposure warning never linked me to that specific fixlet, even though it somehow knew about it, which is why it was still displaying despite me updating the server. I would suggest that vorosp review all of the fixlets in the BES Support site to see what else is relevant.
(imported comment written by vorosp)
Thank you the answers!
Some hours later a message was disapperared…I don’t know why or how. The only thing what I’ve done to updated the installed client version to 9.0.835.0.
But when I clicked on “Security Explosure Detected” line I’ve got an empty fixlet…