Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SMS 2.0 - Preventing Software Distribution
- Thread starter ITT
- Start date
As Chris indicated, its a good practice to limit the ability to create advertisements to only those qualified and directed to do so. However, sometimes that's not enough. Here are some other alternatives.
The mechanisms below may not have been thoroughly tested.
--- To stop Advertised Programs Monitor ---
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. CCIM does not fix this condition since it only checks for presence of the file, not the correctness of the file. SMSMON32.EXE is called by Launch32 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.
--- To stop Advertised Programs Wizard ---
Replace %windir%\MS\SMS\clicomp\SWDist32\bin\SMSWIZ32.EXE with a 32 bit windowless application that does nothing. CCIM does not fix this condition since it only checks for presence of the file, not the correctness of the file.
--- To prevent targeting to specific clients ---
Create a collection for exclusion. This collection can be direct membership or based on a query of software inventory that checks for particular files to exist or not exist on devices. The exclusion collection can then be used as a limiter to other collections (not a "limit to collection", but WQL with WHERE NOT IN collection).
The package could have logic to detect for presence of a file or registry entry on the device, so even if a device received an advertisement the package would exit by detection of a condition.
The mechanisms below may not have been thoroughly tested.
--- To stop Advertised Programs Monitor ---
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. CCIM does not fix this condition since it only checks for presence of the file, not the correctness of the file. SMSMON32.EXE is called by Launch32 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.
--- To stop Advertised Programs Wizard ---
Replace %windir%\MS\SMS\clicomp\SWDist32\bin\SMSWIZ32.EXE with a 32 bit windowless application that does nothing. CCIM does not fix this condition since it only checks for presence of the file, not the correctness of the file.
--- To prevent targeting to specific clients ---
Create a collection for exclusion. This collection can be direct membership or based on a query of software inventory that checks for particular files to exist or not exist on devices. The exclusion collection can then be used as a limiter to other collections (not a "limit to collection", but WQL with WHERE NOT IN collection).
The package could have logic to detect for presence of a file or registry entry on the device, so even if a device received an advertisement the package would exit by detection of a condition.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question