Trouble with the SIPDEVICEGROUP Environment Variable

In a discussion about the SIPDEVICEGROUP environment variable, it was suggested that the EDXDEVICEGROUP variable may be more consistent. However, when checking the configuration data, there were still blank values. A solution was found when a user rebooted a PC that was reporting a blank value. The actual variables names are either SIPDEVICEGROUP or EDXDEVICEGROUP. Additionally, the device group can also be found in C:\ProgramData\ControlUp\EdgeDx\device_group.txt.

Read the entire ‘Trouble with the SIPDEVICEGROUP Environment Variable’ thread below:

Does anyone know how long it takes for the SIPDEVICEGROUP environment variable to update once you change a device’s device group?

I’ll verify monday. But I believe it should be relatively quick. However the variable SIPDEVICEGROUP might be old. Is there an EDXDEVICEGROUP variable instead?

There is one. I’ll check and see if this is more consistent. On one server, I had to reboot it for it to SIPDEVICEGROUP variable to update.

As far as I can tell, both SIPDEVICEGROUP and EDXDEVICEGROUP are set at the same time. It should be updated pretty quickly. As far as I’m aware the device group variable should be updated at the very least every time the agent reports data.

Which is every minute

It’s not. The reason I know this is because I have a script that checks disk space stats for each individual drive (mainly used for servers) and I include $env:EXDEVICEGROUP in the results so I can set different alerts for different system types, etc.

Looking at results in configuration>Data, I see a lot of blanks. I am going to reboot some of the systems to see if they update at all.

I assume EXDEVICEGROUP is a typo just in this message right? The actual variable names are SIPDEVICEGROUP or EDXDEVICEGROUP.

Either way. Can you also check C:\ProgramData\ControlUp\EdgeDx\device_group.txt?

That typo was my bad. When I rebooted a PC that was reporting a blank value, it updated.

Continue reading and comment on the thread ‘Trouble with the SIPDEVICEGROUP Environment Variable’.  Not a member? Join Here!