-
1
- #1
There may be cases where a device should not receive the SMS client, or cases where a device can have the client for inventory purposes but should never receive mandatory advertisements. While these cases can be handled procedurally from the server side, sometimes settings on the device itself are most proper.
Here are some inoculations and their antidotes from the device perspective:
Running SMSLS.BAT[ul][li]Inoculation: On device set environment variable SESSIONNAME = "this variable prevents SMS 2 from installing" (Note: the text of the variable is not important) This works if running SMSLS.BAT out of the box. You can edit SMSLS.BAT to perform environment variable or other checks as needed.[/li]
[li]Antidote: Detect and remove or disable variable during logon.[/li][/ul]Client install[ul][li]Inoculation: To prevent SMS from installing, even if SMSLS.BAT is successfully run, place a file named MS (no extension) in the %windir% folder. MS folder cannot already exist for this to work. This prevents the MS folder from being created and the SMS installation process stops.[/li]
[li]Antidote: Detect and delete or rename file during logon.[/li][/ul]Advertised Programs Monitor[ul][li]Inoculation: Replace %windir%\MS\SMS\clicomp\SWDist32\bin\SMSMON32.EXE with a 32 bit windowless application that does nothing. This allows SMS to function normally, but ensures that no advertisement is detected and automatically displayed. This does allow the user to run Advertized Programs Wizard through the control panel to receive active advertisements. (SMSMON32.EXE is called by CCIM32 process through the registry and through the control panel Advertised Programs Monitor. When APM detects an advertisement it pops up a dialog asking whether to open the Advertised Programs Wizard. This inoculation prevents APM from detecting an advertisement, thus not calling APW which actually runs the advertisement.)[/li]
[li]Antidote: Detect file version and replace file.[/li][/ul]Note: You can run SWDstUns.exe to remove APM and APW functionality, but this does not remove Control Panel icons until reboot. If device is still assigned to CAP, and CAP remains configured to require APM and APW, then they will be reinstalled automatically.
Possible topics for a later posting:
- How to prevent certain components (e.g. remote control) from installing and/or working.
- How to prevent APW from running
- How to hide APM and APW icons in control panel
Here are some inoculations and their antidotes from the device perspective:
Running SMSLS.BAT[ul][li]Inoculation: On device set environment variable SESSIONNAME = "this variable prevents SMS 2 from installing" (Note: the text of the variable is not important) This works if running SMSLS.BAT out of the box. You can edit SMSLS.BAT to perform environment variable or other checks as needed.[/li]
[li]Antidote: Detect and remove or disable variable during logon.[/li][/ul]Client install[ul][li]Inoculation: To prevent SMS from installing, even if SMSLS.BAT is successfully run, place a file named MS (no extension) in the %windir% folder. MS folder cannot already exist for this to work. This prevents the MS folder from being created and the SMS installation process stops.[/li]
[li]Antidote: Detect and delete or rename file during logon.[/li][/ul]Advertised Programs Monitor[ul][li]Inoculation: Replace %windir%\MS\SMS\clicomp\SWDist32\bin\SMSMON32.EXE with a 32 bit windowless application that does nothing. This allows SMS to function normally, but ensures that no advertisement is detected and automatically displayed. This does allow the user to run Advertized Programs Wizard through the control panel to receive active advertisements. (SMSMON32.EXE is called by CCIM32 process through the registry and through the control panel Advertised Programs Monitor. When APM detects an advertisement it pops up a dialog asking whether to open the Advertised Programs Wizard. This inoculation prevents APM from detecting an advertisement, thus not calling APW which actually runs the advertisement.)[/li]
[li]Antidote: Detect file version and replace file.[/li][/ul]Note: You can run SWDstUns.exe to remove APM and APW functionality, but this does not remove Control Panel icons until reboot. If device is still assigned to CAP, and CAP remains configured to require APM and APW, then they will be reinstalled automatically.
Possible topics for a later posting:
- How to prevent certain components (e.g. remote control) from installing and/or working.
- How to prevent APW from running
- How to hide APM and APW icons in control panel