Removing CREATOR OWNER permissions from Drivepool root drive locks out Admin users when creating folders for shares

[Sonicmojo]

Long story short. New Windows 2022 Server. Latest Drivepool. New pool created moments ago (2 8TB EXOS drives). Pool created perfectly.

Used this Covecube Knowledge Base Article to preset the pool NTFS defaults BEFORE creating any shares:

StableBit DrivePool Q5510455 - Covecube - Wiki

1. Owner - check

2. Permissions - check (removed CREATOR OWNER)

3. Enable inheritance - check 

Click OK - applied successfully (minus a couple of benign errors about Recycle Bin etc)

Whether I restart the server after this - OR just go right in the now empty pool drive and attempt to create a folder - I get this:

For the record - I AM signed in with a Admin Account. This account is part of the Administrators group. AND only that group. Account is not even in the Users group.

I have read other users out on the net have had this issue - specifically with DrivePool - in other similar situations. 

I should also mention that I have another older Windows 2019 Server running here and this was never an issue.

If CREATOR OWNER is left in the permissions - any folders that I create on the fly on the server - immediately get owned by the account that created them - I do not want that. And the article above specifically says to clean everything out but what I have left in as above.

Should also mention that I create a share using the Server Manager->Add Share Wizard - the share is created correctly WITH the right defaults as above.

However - if I am on the server logged in as WSA (windows server admin) - I still get nailed with the message above.

Conversely - if I move over to a VM that I have, log into it with the same WSA account - I am able to browse to this new share, create, rename and delete a folder with no issues whatsoever.

What is going on? 

Sonic.

 

[Sonicmojo]

20 minutes ago, Christopher (Drashna) said:

That is just so bizarre.  And it sounds like permissions/trusts in the OS are messed up, somehow? 

There is always the nuclear option to fix it... 

But aside from that, are you using the system as a domain controller, by chance? 

Found out the cause. On Windows Server 2022 (and presumably 2019) - if you are logged in with ANY account that is NOT the actual "Administrator" - even if that account is a member of the Administrators group and has admin rights -it appears that File Explorer de-escalates itself  - and requires "approval" for simple stuff like my screencap above.

I was chatting with a user on Reddit who asked me - if you click Continue on my screencap - does the folder get renamed? And yes it does. So this is simply a User Account Control thing. Which BTW - I never saw on my other 2019 server - because you guessed it - I am running using the real Administrator account on that box.

So now I just did the same on this new server. This is a home network so I am not worried about the "enterprise best practices" of never using the Admin account.

One less box to click though a few hundred times is good enough for me.

Solved.

S

[Christopher (Drashna)]

If the configuration works for you, then use that. 

However, the settings for that guide were based on a freshly formatted drive. I've I have a Server 2022 system, and have helped set up a friends, and have used this config. 

So, it's very odd that it's not working for you properly.  But may be a Windows specific thing. 

[Sonicmojo]

1 minute ago, Christopher (Drashna) said:

If the configuration works for you, then use that. 

However, the settings for that guide were based on a freshly formatted drive. I've I have a Server 2022 system, and have helped set up a friends, and have used this config. 

So, it's very odd that it's not working for you properly.  But may be a Windows specific thing. 

Chris

And that is what I do have - a very freshly formatted drive. And it is very odd.

But I need to be able to ctrust this build for the long term and be able to create folders both on the fly or using Server tools on this pool whenever the mood strikes

So I need to figure out exactly what Windows specific thing this is. Will keep testing this.

Sonic.

[Sonicmojo]

Another update here. So I added another drive to the server via the hotdock slot - and the same weird thing is occurring on the this stand alone drive as well. 

So it appears not to be Drive pool related after all.

Now I need to figure out where this is coming from and how to fix it. Seems something is sorely messed up here.

S

[Christopher (Drashna)]

That is just so bizarre.  And it sounds like permissions/trusts in the OS are messed up, somehow? 

There is always the nuclear option to fix it... 

But aside from that, are you using the system as a domain controller, by chance?