If you want to be a bit nasty but not alter their machine you can have a Filter that looks for $CLIENT-TYPE$ = 3 that has Run Process: Application-Invalidate-User.
Then they can't get back in until somebody resets/clears the password in the User form. And it is a filter so there is no playing goofy games to get around it. Jason On Thu, Sep 24, 2015 at 5:36 AM Pierson, Shawn < [email protected]> wrote: > ** > > For that matter, why not do an Active Link with a Run Process that calls > the wmic command to uninstall it. I forget the exact syntax but I’m sure > it is easily found on Google. Something like: > > > > C:\> wmic product where “description=’BMC Remedy Action Request System > 7.6.4’ “ uninstall > > > > I don’t know if it can uninstall the client if it’s actually running, so > maybe the idea would be to have one action kick off the uninstaller and > immediately after it exit the app you suggested. > > > > That being said, I find the User Tool to be completely essential to > working with Remedy as an administrator. Without it, RBE would be > unsupportable, for example since it doesn’t work right in the Mid Tier. > > > > Thanks, > > > > *Shawn Pierson * > > Remedy Developer | Energy Transfer > > > > *From:* Action Request System discussion list(ARSList) [mailto: > [email protected]] *On Behalf Of *LJ LongWing > *Sent:* Wednesday, September 23, 2015 3:59 PM > *To:* [email protected] > *Subject:* Re: Prevent User from using Client Tool > > > > ** > > Keith, > > Create a shared workflow that fires on window open of your main forms. > Check the $CLIENT_TYPE$ keyword and any time the client type = 3, display a > message saying that they aren't authorized to use that tool anymore, and > then do an 'Exit App' run-process, which will shut down the client... > > > > On Wed, Sep 23, 2015 at 2:43 PM, Sinclair, Keith < > [email protected]> wrote: > > ** > > Is there a really good way to prevent users from using the User Tool? > > > > We have removed the tool from new laptop builds, images, etc. However, > there are some people who refuse to give up the tool unless we pry it from > their cold dead hands. These people are also downloading and reinstalling > the client when we do remove it. > > > > So, what is a great way of preventing them from using it in the first > place? I know I am not alone in the forcing of users away from the tool. > > > > Thanks, > > > > *Keith Sinclair* > > Remedy Development > > ShopperTrak Chicago, USA > > *O* 312.676.8289 > > [email protected] | shoppertrak.com > > *Retail Profitability, Improved.* > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > > > > _ARSlist: "Where the Answers Are" and have been for 20 years_ > Private and confidential as detailed here > <http://www.energytransfer.com/mail_disclaimer.aspx>. If you cannot > access hyperlink, please e-mail sender. > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
