Maybe if you first can catch the @SID of the user(s) that is (are) logged on...