IIS Modules locked in read only windows server 2012 r2

Have  Server 2012 R2 with IIS Role. Running a RMM (Kaseya v7.0) application that basically took over the default web site folder and reassigned it to their folder C:\Kaseya\WebApps. Several of the features they use utilize the IIS Modules feature . One of the Applications is a virtual folder named "Download". If I select it from the list below the Default Web Site and then select (double click) Modules in the IIS section, the Alerts section in the upper right corner indicates "This feature has been locked and is read only" (See attached clip).

Kaseya is stumped on this and states this Locked & Read-Only state must be removed but cannot find a way to do this. I have tried to use the attrib command to in various ways to assure the virtual folder is not locked to read-only. However this does not seem to make any effect.


Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MedInfoTechAuthor Commented:
Nevermind. I resolved this myself just now. Had joined this to an AD domain and had logged in as a Domain Admin whose group was clearly contained in local administrators group. However full rights were apparently not being extended to that Domain Admin as I had decided to log out and back in under the true server's local administrator account and then reinstall the Kaseya VSA. Same uneventful/no error install but this time the module was not locked and set to read only.

Not clear why this happened as the Domain Controller was a virtualized SBS 2011 server and seemed to and seemed to add this server without issues.

Perhaps I could convert this original ticket issue to this more global file/folder/permissions issue since I recall at least once before a similar issue happened and the resolution was to be sure to log in a local administrator rather than a domain admin. I suspect I am not doing something right when I join a member server to AD and that is what is causing this issue. I have no clue what that might be however.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.