I have about 1000 Windows 2012 servers. However, when I ran the installer across all servers, the installer failed on about 100 servers. On the failed installation the installer does not create all the folders, like _BESData folder is missing and the BES Client service stops with error code 1602. The agent version is 9.5.2.56. I have also tried the latest agent 9.5.3.211 installer and same result. Please help.
1 Like
Did these servers have an earlier version of the agent installed previously, or did they never have the agent installed before?
You will probably need to file a PMR about this. I am definitely running the BigFix agent on some Windows 2012 servers without issue.
These are new servers that did not have an agent previously. Doing some research looks like there may be a couple reasons.
1: Port 52311 is only open for TCP and NOT for UDP.
2: Something is preventing the registry entries from beig created to start the agent.
Still looking into it. Will probably need to open a PMR if its not the port UDP issue.
Hi – a UDP port issue should not prevent client installation. You should be able to install the client even if you are offline.
If something (normally anti-virus) is preventing the creation of services/registry keys that would definitely cause an issue.
This sounds very similar to results I’ve been seeing with 9.5.2/9.5.3 where the agent can crash due to a ‘not initialized variable.’ There is suspected AV or white-listing interference as well. IBM has APAR IV90303 open for my PMR. If you open a PMR maybe cross-reference to this APAR to see if it is the same issue.
Thanks everyone. I will open a PMR with IBM. Will update status as soon as possible.
Make sure the Windows Update Service is not disabled. I found this a problem on a few Win10 machines.
What AV or security product are you running? 9.5.2 and 9.5.3 clients have a bug when interacting with AV or security/whitelisting products where the agent can crash if it is denied inspection of AV/security products. APAR IV90303 is planned to be included in 9.5.4.
FIXED! It was a mix of AV and firewall issues where port 52311 was blocked going out.
So far we are having good luck with APAR IV90303 included in 9.5.4. It helps the client to work around some common AV/security software interference with the agent.