Guest johan Posted November 20, 2007 Posted November 20, 2007 Does anyone know a way to get FSRM to send a pop up to a user when they violate a file screen policy, using the Command tab? when I try it i get the following error in the event log: File Server Resource Manager Service error: Unexpected error. Operation: Running command line action. Handling a file screen audit event. Processing File Server Resource Manager event Context: Action type: Command Action Action name: Command Action0 Account: NT AUTHORITY\LocalService Executable path: D:\DataRestriction.vbs Arguments: Working directory: C:\NOSW2K3\system32 Monitor command: FALSE Log result: TRUE Kill timeout: 0 File screen path: D:\Data Error-specific details: Error: CreateProcess, 0x800700c1, is not a valid Win32 application. For more information, see Help and Support Center at
Guest Jabez Gan [MVP] Posted November 20, 2007 Posted November 20, 2007 Re: File Server Resource Manager R2 Please view: http://groups.google.com/group/microsoft.public.windows.server.general/browse_thread/thread/6fc442c4029970a9/6c550422c5143bc8?lnk=st&q=fsrm+script+#6c550422c5143bc8 -- Jabez Gan Microsoft MVP: Windows Server - File Storage "johan" <johan@discussions.microsoft.com> wrote in message news:91F06F6C-3DF2-44A3-82B6-CC288F7DE6DE@microsoft.com... > Does anyone know a way to get FSRM to send a pop up to a user when they > violate a file screen policy, using the Command tab? when I try it i get > the > following error in the event log: > File Server Resource Manager Service error: Unexpected error. > > Operation: > Running command line action. > Handling a file screen audit event. > Processing File Server Resource Manager event > > Context: > Action type: Command Action > Action name: Command Action0 > Account: NT AUTHORITY\LocalService > Executable path: D:\DataRestriction.vbs > Arguments: > Working directory: C:\NOSW2K3\system32 > Monitor command: FALSE > Log result: TRUE > Kill timeout: 0 > File screen path: D:\Data > > Error-specific details: > Error: CreateProcess, 0x800700c1, is not a valid Win32 application. > > > For more information, see Help and Support Center at > >
Recommended Posts