PowerShell
retention policy on Enabling Transcription Logging by using Group Policy
Summary of the new feature / enhancement
currently, there is no retention policy on Enabling Transcription Logging by using Group Policy, so they might be a capacity issue over time
Proposed technical implementation details (optional)
No response
What kind of retention policy would you want? Total number of transcripts? Transcript size? Date? I always assumed it was the IT pro's responsibility to manage transcript files.
What kind of retention policy would you want? Total number of transcripts? Transcript size? Date? I always assumed it was the IT pro's responsibility to manage transcript files.
I think this is for when transcription is on via GPO so the IT Pro (or other user) doesn't necessarily know there are files to manage. If there is a location set it wouldn't be hard for whatever turns logging on to check that location for files over a certain age, or more than some size in aggregate. If the suggestion is for a GPO to hunt down the transcripts I've left here there and everywhere - that would be a tougher job entirely.
Hi Jeff,
Apology for the late response. Retention policy on each text file size I meant.
Regards, Mohammad
On Tue, 8 Aug 2023 at 06:34, jhoneill @.***> wrote:
What kind of retention policy would you want? Total number of transcripts? Transcript size? Date? I always assumed it was the IT pro's responsibility to manage transcript files.
I think this is for when transcription is on via GPO so the IT Pro (or other user) doesn't necessarily know there are files to manage. If there is a location set it wouldn't be hard for whatever turns logging on to check that location for files over a certain age, or more than some size in aggregate. If the suggestion is for a GPO to hunt down the transcripts I've left here there and everywhere - that would be a tougher job entirely.
— Reply to this email directly, view it on GitHub https://github.com/PowerShell/PowerShell/issues/20070#issuecomment-1668396109, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXBPD5KK2KMQ5S73N53V4Z3XUEYMHANCNFSM6AAAAAA3B7ZVAU . You are receiving this because you authored the thread.Message ID: @.***>
--
-- Best Regards, Mohammad Torabi.
+1
We've seen this filling up drives on DCs. We use a number of monitoring technologies that use PowerShell to perform monitoring functions (i.e. System Venter Operations Manager) and it can generate quite a number of transcripts, and the setting is required by DISA STIG:
https://www.stigviewer.com/stig/microsoft_windows_server_2022/2023-05-03/finding/V-254384
(meaning we can't turn it off)
If you don't own this .admx send me that direction please.
STIG Viewer | Unified Compliance Framework®
Security Technical Implementation Guides (STIGs) that provides a methodology for standardized secure installation and maintenance of DOD IA and IA-enabled devices and systems.
