The batch files are created to detect the architecture of the Operating system and address the following :

1.createproviderstore : For Example SelfService.exe –init –createprovider Go https://go.citrite.net/Citrix/Store/discovery
Where "Go" is the store name and "https://go.citrite.net/Citrix/Store/discovery" is store account 

2.deletepasswords : Deletes all stored passwords
 
3.deleteproviderstore : For example selfservice.exe -init -deleteproviderbyname Go 
where "Go" is the store name

4.disconnectapps : Disconnect any current HDX sessions 

5.reconnectapps : Reconnect to any existing sessions the user has. 

6.fastterminate : Log off the current user and leaves their applications connected ( Functionality available only in Receiver 4.2 and above )

7.terminate : Disconnect applications for all users on endpoint ( Functionality available only in Receiver 4.2 and above )

8.qlogon : Reconnect any existing apps for current user ( Functionality available only in Receiver 4.2 and above )

9.rmPrograms : Clean up shortcuts and stub programs for current user.

10.poll : Contact the server to refresh application details.Mostly used where passthrough authentication is configured. For example selfservice.exe -init -poll -exit

11.ipoll : Contact the server to refresh application details as in –poll, but if no authentication context is available, prompt the user for credentials. For example selfservice.exe -init -ipoll -exit

12.cleanup : Reset the receiver to factory defaults removing the following :
 a)All accounts and stores.
 b)All apps delivered by the Self-Service Plug-in, along with their icons and registry keys.
 c)All file type associations created by the Self-Service Plug-in.
 d)Cached files and saved passwords.
 e)Per-user registry settings that are user preferences and, for per-machine installations, all user-specific registry settings.
 f)NetScaler Gateway registry settings for Receiver.

This software application is provided to you as is with no representations, warranties or conditions of any kind. You may use and distribute it at your own risk. CITRIX DISCLAIMS ALL WARRANTIES WHATSOEVER, EXPRESS, IMPLIED, WRITTEN, ORAL OR STATUTORY, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT. Without limiting the generality of the foregoing, you acknowledge and agree that: (a) the software application may exhibit errors, design flaws or other problems, possibly resulting in loss of data or damage to property; (b) it may not be possible to make the software application fully functional; and (c) Citrix may, without notice or liability to you, cease to make available the current version and/or any future versions of the software application. In no event should the software application be used to support ultra-hazardous activities, including but not limited to life support or blasting activities. NEITHER CITRIX NOR ITS AFFILIATES OR AGENTS WILL BE LIABLE, UNDER BREACH OF CONTRACT OR ANY OTHER THEORY OF LIABILITY, FOR ANY DAMAGES WHATSOEVER ARISING FROM USE OF THE SOFTWARE APPLICATION, INCLUDING WITHOUT LIMITATION DIRECT, SPECIAL, INCIDENTAL, PUNITIVE, CONSEQUENTIAL OR OTHER DAMAGES, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. You agree to indemnify and defend Citrix against any and all claims arising from your use, modification or distribution of the software application.

Self Service Plugin activities are driven by user interaction. However, Self Service Plugin exposes sufficient information for its activities to be scripted. The advantage of this approach is that it allows Self Service Plugin to do most of the difficult operations and in particular handle authentication. This provides support for all the authentication methods without having to interact programmatically with the aggregation tier. Self Service Plugin also coordinates the session launch process. This article outlines some of the batch files that can be used as a ready reckoner or template for modifying it as per requirement to use the parameters as described in CTX200337

These batch files can be deployed as the following : 

1. Startup program ( Add the batch file to the following location : C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp )
2. Via startup script 
3. Via task scheduler