User Permissions Problem (Vista Home Basic).

[eXtremer]

I'm familiare with Xp and w2k but I'm a newbie in Vista and I have to secure the system by setting
User Permissions and Group Policy.
Got a problem with User Permissions.
I'm the current Owner of C: and replaced on subcontainers and objects.
System and Administrators have - FULL Control and Users have Read&Execute.
When I want to login under User (Users Group) I receive such a error:
The Group Policy service failed the logon.
Access Denied.

...and user cannot login.
When I login back again under Administrator I c that "The Group Policy" service is started.
What I'm doing wrong ?

I've noticed that gpedit.msc is missing though other Administrators that wrk with Vista say that
gpedit.msc is presented, maybe Home Basic version doesn't have!

After I set the permissions for Administrators, SYSTEM and Users
and I'm logged under Administrator when I want to execute a program,
for example I wanted to open Photo Gallery, this is what I receive:

Photo gallery can't start. You may not have enough space on your HD
or critical files may be missing from Windows.

What to do ?

P.S.: I didn't insert the S/N when I installed Vista and it's not activated (still have 27 days to activate).

 

[linney]

Home Basic does not have Group Policy.

Permissions are a little bit different than XP. My advice is to try not to fiddle with them too much. Administrators run with Standard Users privileges unless they are specifically elevated by right-clicking on .exe etc. The built-in Administrator is disabled by default.

You may have set up some sort of problem with the access to your paging file. Everybody needs to be able to write to that.

Here's a little story I got from Microsoft on similar permission problems.

"The junctions are there to only provide appcompat for legacy apps and aren’t meant for a user to traverse through. The junctions have been explicitly set to block read through them by setting Everyone Deny Read. The main reason here is because these are just links to the actual location, so you dont want backup tools and other tools operating on your data twice, once from the original path and once via the junctions. There are scenarios where some of these junctions actually form a loop to support the appcompat for the old namespace in comparison to the new and in those cases allowing read through them is disastrous, for e.g. setup was broken for a week when the file system wasnt honorign the deny read.

Also as far as a user goes, you will never see these as they are system hidden, and you will need to take explicit action to see them by default."