You feel this will not be able to accomplish it? The Microsoft article talks about using Set-Acl to accomplish all this.
I think you'll need to have rights management in there. >I don't believe you'll be able to achieve this with just windows permissions.
#Blind write just write Pc#
From what I can tell, this ends up preventing this PC from writing to this subfolder at that point (thus transcription logs will fail from this PC, although not others).ĭid Microsoft document this page wrong? Any thoughts on the proper permissions to set so that all users can only write (subfolders and files) to the folder, and not read/delete/etc? Windows automatically creates the subfolder for the day of transcription logs, but the CREATOR OWNER has been marked as PCNAME1$ which is the PC. Powershell outright crashes when this happens.Įxample: First Powershell activity across the network comes from workstation PCNAME1. Is this correct? If UserA executes Powershell for the first time on WorkstationA, the subfolder gets automatically created by Windows with UserA marked as the CREATOR OWNER correct? So then if UserA again executes Powershell, Windows will attempt to record the transcription under the same user and I believe get denied due to permissions. Advanced permissions indicates all checkboxes are checked. txt files as expected.īut I've run into issues where Powershell cannot write transcription logs and I'm unsure what the proper permissions should be.Īs the first permission rule, Microsoft seems to be recommend a DENY of CREATOR OWNER for all Subfolders and files only. The Powershell transcription logging works and creates folders (per day) and. I am attempting to create a read-only Windows folder/share where all devices can write to it, but not read.