Jump to content

Recommended Posts

Posted

I have recently set up a Vista Ultimate machine on my home network and added to the domain (DC = server 2003 enterprise) This is my first expeience with Vista. I can open the Documents folder but when I try to open the folders/files in the Documents folder i get "Access Denied". File Shariing Wizard is off and I am redirecting My Documents to a network share. I have read that Vista has restructured/renamed directories and this causes issues with access to My Documents when using Vista if they are created with XP. I have not been able to find anything that is very clear on the fix (except for manual owner ship changes on each folder that i tried and didnt work). I cant believe that client/server networks that are migrating Vista in are having to correct this on a per folder basis (lots of work!). So my questions are 1. can anyone ponit me in the right direction to fix this? 2. what is the impact on users that logon to both Vista and XP machines? Thanks


Posted

I found this that I had saved on my computer. Hopefully it may give you some sort of insight.

TakeOwn_.regTakeOwn.reg adds a Take Ownership Context Menu Item to all files and folders.

It opens an Elevated Command PromptRunAsAdmin_Exe_.regRunAsAdmin_Exe_.regRunAsAdmin_Exe_.reg which recovers full access to the selected file /

directory, sub directories and their content.

You can access the Context Menu Item by holding down Shift + right-click on a file or folder.

If you want to access the Take Ownership Context Menu Item on an exe file, you must merge

"RunAsAdmin_Exe-.reg"; this reg file removes the "Run as Administrator" Context Menu Item

from all exe files (they both use the runas key).

Merge "RunAsAdmin_Exe+.reg" if you want to restore the "Run as Administrator" Context Menu Item.

Install: Merge TakeOwn+.reg

Uninstall Merge TakeOwn-.reg

RunAsAdmin_Exe_.reg

TakeOwn_.reg

Posted

Well, I managed to make a mess of that post by uploading files all over the place !!!!!

You should be able to sort it out if you are smart.

Remember to backup your registry first before making any alterations. I'll just paste in the text only again to make it a bit clearer.

A guy called "Herby" came up with this workaround. So credit goes to him.

TakeOwn.reg adds a Take Ownership Context Menu Item to all files and folders.

It opens an Elevated Command Prompt which recovers full access to the selected file /

directory, sub directories and their content.

You can access the Context Menu Item by holding down Shift + right-click on a file or folder.

If you want to access the Take Ownership Context Menu Item on an exe file, you must merge

"RunAsAdmin_Exe-.reg"; this reg file removes the "Run as Administrator" Context Menu Item

from all exe files (they both use the runas key).

Merge "RunAsAdmin_Exe+.reg" if you want to restore the "Run as Administrator" Context Menu Item.

Install: Merge TakeOwn+.reg

Uninstall Merge TakeOwn-.reg

(Use the files from the previous post)

Posted

Stik62, this is a function of the permissions structure and the default limitations imposed by Vista. As you may have surmised, you need to take ownership of the file and then you can manipulate it. I found this one of the many annoyances of Vista, but another way to address this is to login as Administrator. While you may think you have all administrative privileges if you have "Administrator" rights, the truth is you don't. Think of Administrator as having Super Administrator rights and you'll be much closer to the truth of what's happening.

By default, the built in Administrator (or root) account doesn't show on the Welcome screen and thus poses a bit of problem for normal users who want to access it. (Hint: MS doesn't want normal users to have access. In a way, I don't blame them, except if they include me!! lol) So, to access that account you need to activate it first.

This you can do in a Command Box (Run... / type "cmd" (no quotes) ). Enter this:

net user Administrator /active:yes

Now, you will see Administrator on the Welcome screen and you may login. Note there is no password, so you will have to set one once you log in. You can do this in User Accounts as well as through the Management Console.

Hope this helps.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...