Getting help and advice from one of the many experts here at Microsoft Community does not cost anything.
Whenever you receive a phone number as an answer and feel uncertain whether it is from someone at Microsoft, don’t take the risk,
confirm the number is for official Microsoft Support.
All of this is total BULL! There are few DOS commands to enable access. I wish I remembered them. I used it for gaining access to the sync folder... Rats I wish I took note. It has nothing to do with permissions, there is a block and there as a command
to turn it OFF, then all works just fine. Nothing to do with the typical **** answer "duh use runas"
Thanks for the response.... but you could have just said you didn't know either <lol> Hang in there. If you remember, type it in. Thanks again.
All of this is total BULL! There are few DOS commands to enable access. I wish I remembered them. I used it for gaining access to the sync folder... Rats I wish I took note. It has nothing to do with permissions, there is a block and there as a
command to turn it OFF, then all works just fine. Nothing to do with the typical **** answer "duh use runas"
It appears that these are symbolic links and that WIn7 hasn't got the wherewithal to follow the symlink to the real folder to assess the security settings. - Hence everyone's frustration.
For those of us who are extremely technical, we'd like to be able to remove and re-create a link as needed to test a scenario...
I've done it for years with Altos Xenix, SCO Xenix, SCO OS/5, AIX and Linux from Caldera 2.2 through todays versions... Windows has been moving in a direction to incorporate more *nix like concepts as they move away from their DOS orientation, but in the
process they have focused on the "general user" at the expense of the "administrative user" (i.e. "root" in *nix)
I've always wanted to try a stripped down, non-backwards compatible, Windows Server. I'm sure it could be made admin-friendly and allow push updates without spending thousands of dollars on push-update software mechanisms... But so far, they've missed
I have 1 Win7Prof PC at home, 1 Mac and 2 Debian systems. Both the Win and OS/X systems make it very hard to administer/customize/etc. the OS. The 2 Debian systems give more bang for the buck and don't inhibit the root user at all once you make 2 changes
(using "su root" as a user) in /etc/pam.d to allow logging into the desktop as root.
We can always hope MS will see those of us who recommend server platforms as a market at some point. (Wouldn't it be awesome to have basic *nix constructs available for admins? And "bash" vs. "cmd"?)
Ok...The computer is mine, the software is licensed to me...I want access to everything. If I screw it up, I can restore the entire hard drive from my Windows Home Server/ So...let me have access to MY system.