Anyone still having issues with UMS not showing devices as online or ready even though they are? Our issue is happening with both internal devices and ICG-connected remote devices. (UMS 6.07.100, OS-11.05.133, ICG 2.03.110).
Do you maybe disable online check?
You wrote ICG, is there a difference between internally registered and ICG ones? Can you ping the devices?
Pings working fine (to internal devices). Have both wired and wireless, internal and remote. Online check enabled. It seems random and comes and goes. Thought I had seen someone else here mention something on this topic. Not a show-stopper, but just odd.
Have you configured this? kb.igel.com/endpointmgmt-6.07/en/monitoring-device-health-and-searching-for-lost-devices-43106425.html
Hi @all, I’m facing the same issue. Enable or disable heartbeat doesn’t make any difference. Newest ICG, newest UMS, FW 11.05.100 to 133 no difference. Directly after reboot client is online. After a while client turns to red. VNC / Secure Terminal doesn’t work either. Shadowing is possible with UMS WebApp. Client behavior is random.
Interesting! But the device remains functional to that time? Could one of you both access one device physically and issue a command together with me?
Piggy backing off of Sebastian, if these are both ICG connected environments, the article I linked is UMS-_only_ I think. There’s also this heartbeat command for the ICG:
@member I am having a web session with the customer tomorrow 9am German time. Would be glad having you as the customer as various issues concerning Igel is OS 11.5 over the last weeks
Echo Michael’s comments. Configuration is good on Device Network Settings and does not matter if on internal network or ICG, still having conflicting information delivered on UMS. Device can show last contact as now. Device still receives commands from UMS. Device still can be shadowed. But, device still shows as offline by icon in UMS file tree.
@member I have seen this issue on internal device as well. Device receives config but shows offline state. I have also experienced the following: shadowed on the device over WebApp directly after green state. Whilst shadowing session device turned to red and did not receive further config updates
So, let me sum up:
1) both are on newest Systems but not on latest Private Build: .145 (worst a try, will PM the link).
2) it happens on devices on LAN and WAN (ICG), right?
3) the device remains functional but no IGEL Related actions (Shadowing, Settings sent) are possible. right?
Mostly correct Sebastien. (all except private build. haven’t seen that yet. and commands from UMS)
A YES for all
Thanks to both of you for helping out, to debug that behavior!
Continue reading and comment on the thread ‘Help with issues with UMS not showing IGEL OS devices as online or ready even though they are?’. Not a member? Join Here!
Learn more, search the IGEL Knowledge Base
Ask a question or comment on the above message thread?Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.
Submit a question, or Join Today!
Popular Message Threads
- How to Install IGEL OS via a Bootable USB Drive
- USB webcams in combination with RDP on IGEL OS?
- Receiving error: “Citrix Receiver cannot create a secure connection in this browser” when launching a secure connection from Firefox on IGEL OS
- After upgrading to IGEL OS 11.04.200.01 my Citrix Storefront configuration does not work anymore – Error adding store: AM_ERROR_AUTH_NETWORK_ERROR
- IGEL UMS Universal Update Error: “could not resolve host name”
- Any plans to support Teams Optimization Pack for VMware?
- Citrix connection via Netscaler Error: “AM_ERROR_AUTH_NETWORK_ERROR” on IGEL OS