Is there a fault with the Unsubscribe link in the emails? Here's one I received:

The highlighted link's URL is https://community.intersystems.com/user//subscriptions/node#edit-0-check... and when I click on it I get a new browser tab at the following URL:

https://community.intersystems.com/user/john-murray#edit-0-checkboxes-42...

The page looks like this:

Was it supposed to take me somewhere on the Subscriptions tab?

I think you meant to write that you changed the group and tag from Caché to Developer Community. I assume you did this because my original posting on the Caché group and tag was not sufficient to make it crosspost to the Google Group. I guess there is some human involvement in the crossposting, and this filtered my posting out.

Fabian, thank you for posting my original onto the group [Update: 3-Apr-2017 I can no longer find Fabian's post there sad]

Assuming you aren't using a really old version of Caché (5.0 or earlier), and that your users have their own userids in Caché (i.e. $username is different for each of them), then you can configure things so that certain users aren't able to read the database of NS2. This will stop them switching to the namespace as well. See documentation here and here.

If you find this answer useful please click the checkmark alongside it.

When Ensemble runs on Windows its background processes typically run with whatever Windows credentials the Ensemble service (see Windows Service Control Manager) is set to "Log on as". If that is LocalSystem then your background processes won't be able to access UNC paths.

For more information, see my post here

If my answer here resolves your question please click the checkmark alongside it above.

There's a flaw in your original idea of eliminating the comma from two $H-format timestamps and then comparing them with the "greater than" operation. For most of a 24 hour period the resulting $TR(dollarH,",") is 10 digits long, but from midnight until 00:00:09 it is only 6 digits long, from 00:00:10 to 00:01:39 it is 7, from 00:01:40 to 00:16:39 it is 8 and from 00:16:40 to 02:46:39 it is 9 long.

A working alternative would be to compute $P(dollarH,",")*86400+$P(dollarH,",",2) for each and compare the results, which are the number of seconds since midnight at the start of 31st December 1840.

if you need to compare a $H-format timestamp against the current time don't use $P($H,",")*86400+$P($H,",",2) as one of the expressions because there's a small possibility that your two fetches of $H will fall either side of midnight. Instead, fetch $H once, store it in a variable, then process that variable.

Laura, this probably deserves to be posted as a new question so more people will see it. But your situation isn't clear to me. If a user can't log in (why?), how are they going to be able to run something that will log out all their sessions?

I also recommend the use of the "comment" link that appears under questions, answers, or other comments. I think this helps put a response into the relevant context.