9.2 Patch 5 for IBM BigFix Platform (Updated)

Release Announcements Platform (Release Announcements)
7

NB: Take heed of the retroactively added (updated) “Important Notes” section re the extra length of time required and no feedback - even on a small instance. Ugh. Please fix the feedback part going forward. Here’s some strong text:

strong text
strong text
strong text

1 Like
8

Just before the end of the upgrade a Window popped up asking for the proxy password. I entered a password. It appeared to be wrong and then the Window closed. I do not need to set proxy settings and I do no have proxy settings set. Does anyone know why the proxy Window appeared? According to support it should not have.

9

IEM console 9.2 patch 5 is not backward compatible. I am not able to connect to old versions of IEM servers.

10

This is normal behaviour. The consoles and servers need to remain able to talk the same language and when a schema or interface changes they need to be the same.

For the releases we currently have, the server and console should always be the same version

1 Like
11

Have requirements for the IEM Console changed somehow in patch 3?
All the previous version worked before but its not possible to install latest version on Win 7 Enterprise 32-bit anymore.

12

Console is a 64-bit application. Have you previously installed the 9.2.* Console on 32bit ?
The requirements report for console only shows supported on 64-bit.
See https://support.bigfix.com/bes/changes/fullchangelist-92.txt and the sections :

= Changes between 9.2.2.21 and 9.2.3.68 =

Features Added or Changed

  • Windows Server Components (Server, Console, Web Reports, FillDB, and BESAdmin) are now 64-bit Windows applications.

…

=====================================
= Changes between 9.1 and 9.2.0.363 =

…

  • OS Support

    • Linux Server, Relay and Agent components can now be installed on RHEL 7
    • MS Windows 2003 R2 is no longer supported for the IEM Server, Web Reports and Console
    • Windows Server and WebReports components can now be installed on 64-bit platforms only (MS Windows Server 2008 and higher)
      The IEM Server installer prevents deployment on 32-bit operating systems.
      The IEM Console installer will allow a manual installation on 32-bit platforms. Future Console installer releases will not support this mode of installation.
1 Like
13

Yes, we used the version 9.2.2.21 of a Console without a problem. Now I see in the release notes that since 9.2.3 it is a 64-bit application. It was just confusing as in IEM Console requirements, it is listed as 64-Tolerate app for x86-64 hardware.

Does it mean there are no plans to support it on 32-bit systems in the future? Unfortunately, all the workstations used in our company are 32-bits, even in year 2015. In that case we might need to downgrade IEM or find some “workaround”.

14

Correct there are no plans to continue supporting the server components on 32 bit OS’s

The amount of data in use requires the 64 bit address space for many customers.

2 Likes
15

I upgraded the server/relay/clients this week and noticed that the start type of service “X” is no longer working. I am guessing it is something with the new client but I opened up a ticket for support as we were using this for a few different tasks. the result was usually manual/demand/disabled based on the start type of the service

example:
q: exists service "SepMasterService"
A: True
T: 0.019 ms

q: start type of service “SepMasterService” | "Not Installed"
A: Not Installed
T: 0.025 ms

1 Like
16

Yeah, it looks like this is a bug in the 9.2.5 agent. :disappointed: You’ll likely have to downgrade these agents until we can release a fix, or use a workaround like:

value "Start" of key "HKLM\SYSTEM\CurrentControlSet\Services\BESClient" of native registry
17

Understood, PMR was already submitted for it too.

Can you easily downgrade the clients by taking the 9.2.1 job and removing the relevance for version of client < “9.2.1.48” and version of client >= “7.2”? Just wondering the effort for 20000+ endpoints versus just recreating the properties using the relevance you provided (which results in 2/3/4 which correlates to Automatic/Manual/Disabled in Services).

18

No, the installer only works if the existing client is at an older version, so you’d have to do a custom action to remove and then reinstall. Or do an uninstall action, and then use the client deploy tool or AD login script to re-install the older version.

19

I would definitely recommend the option of uninstalling and then reinstalling with a BAT file deployed through BigFix if you need to downgrade.

I wouldn’t recommend just uninstalling and then trying to get another mechanism to work to get it back… I would only recommend that if there are failures.

20

See this related post:

21

Here is some more information that I got from support a couple days ago

I was informed that the fix for the reported issue is going to be on Patch 9.2.6, and it will cover the client and QNA.

I just got the information that the ETA for patch 9.2.6 will be on November 2015.

1 Like
22

That is quite a ways off.

24

It (November) is here.

When will the patch be here?

25

I was told November 6th would be the release date by one of the reps. It is now the 11th and I still see nothing?

26

Look for patch 6 next Monday.

For future reference, we don’t generally release at the beginning of the month, so if you hear a target month from someone, always assume middle or end of the month (read 15th or 30th).

4 Likes