I whipped up a W2K3 SP2 box with a demo of v.7 of the server, console and agent. So this box is both the server and the client.
First, how can I know what the status of it as a client? When I look at in the console, all the fields are . I don’t know even know if the antivirus component is installed or not. When I go to Deploy Antivirus, it does show any computers that I can install to, so I am assuming it is installed and only the reporting is not yet working.
Second, I tried to updates the antivirus definitions to the client, and I made a task but I had to select “All computers with the property values selected in the tree below” since it won’t show me the client any other way.
Third, the server apparently downloaded and cached the definitions to disk and that’s it. It just stops and doesn’t go further. And it tells me there are no applicable computers just as it did when I tried to select the client. Could it be because the definitions are already up to date and I just can’t find out, but then that means I can’t reinstall them if I ever wanted to.
I just told it to set the power profile settings for this client and too seems to be stuck and not performing the task.
I just now added a Vista 64-bit client and it’s behaving the same way, no information reported back and the server can’t perform any actions on it.
All your questions seem to be related to the same issue that your agents are not properly talking to your server. I don’t have enough information to diagnose properly, but my guess is that you have a mismatch between your agent masthead and your server masthead. This causes the agent to reject the instructions from the server due to invalid signature errors.
This might happen if you tried to install the eval multiple times and got your mastheads mixed up or there could be many other reasons too. If you look in your BES Client logs and see things like “Invalidly signed directory content” or errors like that, then it would indicate this issue.
You have two basic choices for troubleshooting:
Send your BES Client logs to enterprisesupport@bigfix.com and explain this situation. Based on what they see, they can tell you why your BES Client isn’t working properly with your server.