So this may seem weird, but here is my situation. I have a job that runs daily from our partner from their system. The job comes into a directory on a server, scans for all the files, copies them off, and deletes everything in the directory as it leaves, including any folders. The files are generated on medical devices that are sent via ftp into a specific folder inside of the directory that the other system is scanning. Unfortunately the method of the ftp is hard coded into the medical devices and cannot be changed. If the directory is missing, the transfers fail, and the device will not create the directory either. Our partner that is coming in and pulling the files out is also unable to change the scanning process to not delete the folder, or to scan that specific directory as it would mess up everything on their end of their systems.
Here is an example of what is happening. \\server\share\dir1\subdir1\anon is the folder that the medical devices are hard coded to send the files into. Our partners system comes into \\server\dir1\subdir1 and initiates the scan from there. When it is done scanning and copying all files from the directory and any sub directors, it deletes everything, including the anon folder inside of the subdir1 directory. So the next day when the medical devices start trying to ftp the data over, the folder is missing, and the transfers fail.
So here is what I need to have happen in the long run. The system does its scan and copies the files off and deletes the folders and files inside of the directory. FIM will monitor the \drive\dir1\subdir1 directory. Then I want to create a rule that says if \drive\dir1\subdir1\anon is deleted, create a new directory called anon inside of \drive\dir1\subdir1. Unfortunately I do not see a way to do that. Is this possible with LEM or no? Unfortunately doing a restore of the deleted directory is not an option as it will result in duplication of files on the other end every day, the directory has to be recreated clean and empty daily after it is deleted.