I’m using Bigfix version 9.5.2.56 having multiple operating system in my environment but while installing an agent on windows server 2003 by using client deploy tool, it shows, client not installed, when i begin the installation by selecting that server it gets failed in the end.
Secondly I tried it manually by placing client installation folder on the server machine 2003, it also failed by giving a prompt.
“The ibm bigfix client cannot be installed on this operating system. This version of the product requires a minimum of windows vista/server 2008 or later. Setup will now exit”
Supported operating list available on internet shows that bigfix supports windows server 2003.
Is there any work around for that ?
Operating Systems no longer supported by BigFix agents: In 9.5, agents will no longer run on these operating systems:
* Windows XP, XPe, XP/64
* **Windows Server 2003**
* HP-UX (All )
* Debian 6
* Ubuntu 10
* Mac OSX 10.6, 10.7
* ESX 4.x
The Older BES Clients will talk to a Newer BES Server.
The Newer BES Clients will talk to an Older BES Server.
Within limits. IBM seems to go to great lengths to ensure backwards and forwards compatibility of the clients.
Given that Win2003 is no longer publicly supported by Microsoft, it seems reasonable for IBM to drop support for it with their newer clients. In fact, I believe that is their policy. Once they begin to support an OS, they do so until the publisher stops supporting it.
Given that there are no new publicly available patches for Win2003 (or WinXP, Win NT, Win98, or Win95), you should be migrating OFF of Windows 2003 servers.
EDIT:That all said, I still have several hundred “unsupported” Operating systems in my environment. Linux, Windows, and Mac. Because the older clients still talk to the newer BES Server, we at least know what’s out there and can perform basic management functions on them. We can’t take advantage of all the newer features of the BigFix product, but the features that used to work, still do!
I have installed 9.2.5 version of IBM BigFix Client on Windows 2003 Service pack 2 servers but in each and every servers which belongs to 2003 series seems to be issue and BESClient is automatically getting stopped on all of those 2003 servers.
Even I have tried manually restarting the services but within 1 minute again service is getting stopped automatically.
I’d suggest opening a PMR for this issue. That said, it appears that the Client is unable to delete a file within the __BESData folder. If you stop the client, and manually try to delete the file specified in the log, are you able to? Is it possible that something is interfering with the Client’s ability to read/write/delete files within the __BESData folder? (I’m assuming the service is running as LOCAL SYSTEM?)
Service is running as local system account.
I stopped the service and deleted the BESData folder and again started the service.
After performing above steps seems like issue has been fixed.
But on few of the servers I am not able to delete the BESData folder.
Is there any permanent solution to resolve the BESClient issue on windows 2003 Servers because we are facing BESClient service getting stopped on all the windows 2003 Servers.
