Upgraded from 7 to 8, clients not responding to actions

Usage and Config Platform
1

(imported topic written by amagewick91)

I installed the latest v7 of BES onto our test network, and made sure everything was working as it should (which it did). I then did the upgrade to 8, and everything seemed good. I did the v8 server, the console, and then the 10 clients.

Now when I open an action, the clients do not respond. Their last check-in time keeps refreshing, but the computer state is not.

Any ideas?

2

(imported comment written by SystemAdmin)

What do the client logs show?

3

(imported comment written by amagewick91)

That is it syncing with the individual sites, and that it is posting the report successfully. I am not used to looking at the log, but I don’t see much else in here.

4

(imported comment written by NoahSalzman)

You might try clearing your console cache. (That is BigFix-speak for “I have no idea… reformat/reinstall Windows.”)

5

(imported comment written by jessewk)

Sounds like your license is expired. Check the licensing dashboard.

6

(imported comment written by amagewick91)

License is fine until 11/28/2010

7

(imported comment written by SystemAdmin)

Is there a relay set up on your network? That will need to be upgraded too if it hasn’t. I had PCs doing the same thing recently due to a faulty relay server. I removed the relay and then redeployed it and the clients worked afterwards.

8

(imported comment written by amagewick91)

There are no relays. I tried restarting the bes server, sql server, and the test client and nothing has changed. It looks like the client may have initially had a DownloadPing command for the action I sent… but after that there is nothing.

The client had this in the log after the action was initiated.

DownloadPing command received (ID=98)

Is this the start of the process for fixlet ID 98? I tried to push this patch.

“00-98: MS10-054: Vulnerabilities in SMB Server Could Allow Remote Code Execution - Windows Server 2003 SP2”

9

(imported comment written by amagewick91)

We figured it out with support. I have my database on another server, and so the BES Root Server service now has to run with credentials. Once we put those in we were good!