Search the Community
Showing results for tags 'permissions'.
Found 4 results
Hello, I am making a large jump here, moving from Windows Home Server V1, to Windows Server 2016. I have been taking some time during trial periods of installing various NAS server OS's. The 2 that bring me here are Windows Server 2016 Standard (Windows Server 2016 Standard with the Essentials Roles) and WSE 2016. All of which are supported by Drivepool and in my testing I have been very impressed with Drivepool. My 1st build was without essentials and I soon realized that I didn't have the backups that Essentials provided. So I created a fresh install on another SSD, (pulling all of my drives) and after installing Windows Server 2016 standard immediately installed the Essentials as a role. I then installed Stablebit Drivepool and a second drive, and created my Storage pool using just the single drive for testing. In the Essentials Dashboard>Server Folders I used the move folders command to move the Users, Folder Redirection, etc., etc. to the storage pool I created. I then made a few test user accounts through the essentials dashboard at which time the User folders were automatically created in the Users folder (Users/Tom, Users/Test, etc.) During testing of the permissions from a client machine, I found I was able to delete the User folder (Users/Tom, Users/Test) I am not able to delete Users. And this is not what I would expect, and I am using many tools I am not familiar with, so please keep this in mind. Does the Move operation into the Drivepool, cause some permissions issues? Or is this behavior caused by the way I am using Windows Server 2016 Standard with the Essentials Role added instead of using Windows Server 2016 essentials. I have run across posts from many people coming from WHS but I have not ran across post describing the issue I am seeing. The items I value in my new home server are as follows (no particular order) Pooled drives Folder duplication to protect against drive failure (more flexible than raid solution). WHS V1 type client backups File shares for movies, music, work documents, user files, software, etc. The ability to place a HDD into any Windows PC and have immediate access to my data in the event of a server failure. The reason I am listing the criteria for my build is that perhaps Windows Server 2016 is overkill and it seems to have a steep learning curve. Perhaps it's time to bypass the Windows client backups I am used to and use alternative methods like ToDoBackup or Backupper to automate backups. This would allow me to use Windows 7 or 10 with Drivepool as a file share. I didn't expect that Windows Server 2016 would be easy, however, I have been using computers and different operating systems as well as servers for decades and it seems like it is overly complicated (multiple layers of permissions, forced folder structure for shares, automated tasks that only half-ass the basics). I digress, because obviously I must be doing something wrong as this is a new OS... Or am I? I would appreciate your input and guidance greatly, Regards, Tom
Hi, I've been beating my head on what appears to be an NTFS permissions issue. Suddenly last week my pool started showing Access Denied on any file or folder creation. I tried taking ownership and resetting permissions on the pool but kept getting Access Denied. After trying every solution out there I could think of (takeown, elevated and system cmd windows, icals, everything Access Denied), I checked on the forums here and see that several other people have had this issue, and that the Wss.Troubleshoot tool had the magic solution, so I eagerly tried it out (version .165). Unfortunately, the tool also reports Fix was not successfully applied. Access is Denied. Help would be appreciated!
Hey Guys - I've been using DrivePool for over a year now after migrating from DriveBender and really enjoy it. A few weeks ago, I had some issues with my workstation where I ended up having to perform an OS reinstall. When the issues weren't resolved, I performed yet another OS reinstall and also went from Windows 8.1 x64 Ent to Windows 10 x64 Ent. As my OS has always been on a dedicated, non-pooled SSD; I have removed the D: drive letter Windows assigns to a disk, installed DrivePool, and restored (automatically) the pool after both OS installations. This seemed to work fine and everything seemed intact. Even though it may be more of a Windows issue, I'm having an issue with permissions on many of the files on my pool, however. I've found that when trying to delete / rename / edit some files, I am unable to as old NTFS permissions are stil tied to them. When viewing NTFS permissions, there is an "Account Unknown" with a SID in one of the User spots as shown below. Mostly, they are inherited from parent folders, it seems. The Question What's the best method / command to resolve these unknown accounts and somewhat "reset" security for all of the pool's files/folders after an OS reinstall? System Specifications Drive Pool (D:\) - Total Size: 28.4tb / Free Space: 2.07tb - x8 Standard SATA Drives (3tb-4tb each) - x1 Samsung 840 Pro 256gb SSD (used with SSD Optimizer plugin) - Stablebit Drivepool 18.104.22.1681 / SSD Optimizer Plugin 22.214.171.124 Screenshot of entire pool at end of post Non Pooled Disks - (C:\) x1 Samsung 850 Pro SSD 256gb / OS & App Installs - (D:\) x1 Hybrid SSD/SATA Drive / App & Game Installs - (Y:\) x1 24gb partition dedicated to paging file (Partitioned off of non-pooled 850 Pro) Needed? Probably not Primary Specs - Intel i7-3770k CPU / 16gb RAM - Nvidia GeForce 660 - Windows 10 x64 Enterprise Bonus Questions I'm purchasing a new system soon and will be migrating the pool over. As much as I'd prefer to have all the hardware in a NAS, they are just too expensive for one with as many bays as I require to hold everything. Two questions: - Since I'm not only introducing the pool to a new OS, but also new hardware, is there anything beyond what i must do after an OS reinstall which needs to be done? - I'd like to split my pool and only have a small one in my workstation instead of it housing so many disks. Does anyone have a suggestion (other than a NAS) for the best way I can mount and access 6-7 disks other than all in my current workstation? Almost all data needs to be available 24/7 Well, I think that's it - Thanks for taking the time to read!