This then means the file is no longer protected by WIP as it is now considered a personal file. While cipher.exe cannot be used to mark files as corporate (at least as far as I can tell), when ask cipher to decrypt a WIP protected file it will also strip all the ownership information from the file. Personal files just don’t have any ownership information defined, which will come in handy shortly. WIP uses EFS to mark the ownership of the files as corporate or personal. This application has several different functionalities, but the important one for us is that it can decrypt files encrypted with EFS (Encrypting File System). The solution was a Microsoft application that comes with every single Windows install called cipher.exe. He ended up further down the path as me and then came across the solution. Unbeknownst to me at the time one of the in-house developers was actually doing the exact same thing and came to the same conclusion of writing an application for this. I had commitments that I needed to get to, so I had to stop and pick this up the next day. The problem is that almost no information seems to be available on how to change the WIP ownership of a file through the command-line or from within a script.Īfter quite a few hours of fruitless searching for a solution, I decided the look into what would be required to write a little application to be able to achieve this. This had to be done in a script as the application was being rolled out to a significant number of users. The solution to this problem seems simple, just change the WIP ownership to be personal and the problem goes away. After a lot of investigation by some of the development team and myself we concluded that Windows Information Protection (WIP) was sometimes preventing SQL Express from accessing the files, even when SQL Express was marked as a corporate or an exempt app. This is where we started running into issues with SQL Express not being able to access some of the files. With everything tested and working, I started deploying it to general users. This all went fine and testing on my device as well as some test users all came back working. I started writing a script to do the migration of the databases from where LocalDB stored the database files (in the user’s appdata) to a defined location (let’s say c:\Database). The application was previously using SQL LocalDB, but for reasons I will not go into here it needed to be moved over to SQL Express. A little while ago I had to deploy SQL Express to a number of devices that needed it for an in-house developed application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |