...
This article describes the bulk user disable tool that is available from Logisense LogiSense upon request.
Alert: Ensure that this utility is tested in a development environment before proceeding to use it on a production system
...
Request latest utility for LogiSense Customer Care - support@logisense.com.
Extract the zip file to the EngageIP billing folder, i.e.: C\:Program Files\EngageIP\BulkUserCancelUtility. See file attached at bottom of article.
Copy all files from EngageIP/Adminportal/bin folder, paste them into / overtop of the BulkUserCancel files and folder - The dlls from your current release of EngageIP are required for the EXE itself to use. NOTE: This will need to be updated if EngageIP is upgraded.
Update the config file
with the connection string, you can find the encrypted string in the registry located here: [HKEY_LOCAL_MACHINESOFTWAREEngageIPParameters] . Double click the entry called 'BOSS', copy the encrypted string and paste into the config file overtop the existing string (between the quotes)
Update the keys (options) as required. Options defaults for 'CancelUserWithCreditBack' (Yes or No), CancelStatus (this should be the label assigned to your cancel status on the Setup tab), and 'IgnorePackages' (Yes or NO)
Enter list of users into the 'UsersToDisable.txt' file in the same directory. See txt file for the format. Its simply a list of users vertically
Backup database - BOSS
Double click BulkCancelUser.exe - the below screen will come up
...
Click Browse button, select the UsersToDelete.txt file
...
Select the cancel option 'Immediately With No Transaction' (no need to select date, that setting is for the final option)
...
Select the check box for the cancelation of packages or credit back as required
...
Click Run
...
Wait for the EXE to pop up a message that the process is complete
To Disable / Cancel Services:
...
If there are any errors, they will be displayed in a log file in a 'Log' folder in the same directory as the EXE: BulkCancelUserErrors.log . The errors may look like below, in which case you should confirm that the name is accurate.
...
Couldn't find username: user1
Couldn't find username: user2
Couldn't find username: user3
...