This article contains two tables. The first lists customer-related problems that were addressed in the 8.4 release of Security Manager. The second lists known problems in the release. For more information, talk with your Support representative.
Problems Addressed
No problems have been repaired in Security Manager release 8.4 since the 8.2 release.
Known Problems
| Problem | Description |
| Application Blocking | |
| 56687 | Application blocking does not work on Vista |
| Configuration UI | |
| 41010 | Need to be able to suppress all reboots when applying security settings |
| Packaging and receiving | |
| 46911 | Patches with long names may not be added to policy after mgspatchreceive |
| Patch management | |
| 43767 | Intermittent file in use error for mssecure*.cab during errata refresh |
| 44334 | SUSE patches do not get added to policy from admin server |
| 57635 | Superseded patches are hard to identify and manage in console |
| 75481 | Bulletins that supersede themselves will be put into hidden list |
| Reporting | |
| 45332 | Scan status drill down does not list "Unknown" machines |
| 45333 | Different Security Manager reports report on different sets of devices |
| Security analysis | |
| 46066 | MBSA preferences are inconsistently located and missing from CSPs |
| 47568 | Bad status reported for patches superseded by patches not in mssecure |
| 54938 | MBSA output fails to be found if %USERPROFILE% different from %APPDATA% |
Comments
0 comments
Article is closed for comments.