Change policy, let nonadministrator use BurnAtOnce

[Dubious Dude]

I am trying the make the CD burning freeware BurnAtOnce usable by my
nonadministrator account. I am using a procedure outlined for
a different burning program (idea seems to be the same):
http://www.anandtech.com/guides/viewfaq.html?i=117

When I try to enable the local policy setting for "Restrict CD-ROM
Access to locally logged-on user only", I see that the effective
policy setting is "Disabled". I also noted the warning "If
domain-level policy settings are defined, they override local policy
settings" snap-in". BurnAtOnce still works only for the
administrator. I googled for this problem and found the following.

1. http://tinyurl.com/7oom6

I made sure that I was not part of the domain under My
Computer/Properties i.e. I ensured that I was part of
"workgroup".

2. http://tinyurl.com/9xmqq

This says I need to have the administrator (also me, different
account) add the rights to my GPO. After much googling, I
assume that this means Group Policy Object. More googling to
figure out how.

3. http://tinyurl.com/965bk

This describes some steps to be performed for the "Win2K Server",
and I'm not sure if it applies to my laptop. It is sometimes on
dialup, sometimes on a DHCP ethernet LAN on-campus, sometimes on
a friend's home router.

4. http://support.microsoft.com/default.aspx?scid=kb;en-us;268473

This refers to a snap-in to fix the problem.

After more googling and perusing Windows 2000 help, I ended up using
run-as to run mmc as administrator. The Console Root folder is shown,
and it is empty. When I open the "Add/Remove Snap-in" dialogue, the
Standalone tab shows an empty list. The Extensions tab also shows an
empty list.

I also looked at
http://www.brienposey.com/kb/understanding_group_policies.asp to see
how to respond to the above situation. It is good background, but I'm
not sure whether it is relevant to my specific situation (how to get
the domain level policy to allow nonadministrators to use the burner).
Could someone suggest a simple procedure to do this?

Thank you.

 

[Steven L Umbach]

If you were able to configure the user right in Local Security Policy and
your computer is not a member of an Active Directory domain then a reboot of
the computer should show that effective setting to be the same as the local
settings unless you have a startup/shutdown script, etc that uses secedit
and a security template to enforce your security settings. --- Steve

 

[Dubious Dude]

If you were able to configure the user right in Local Security
Policy and your computer is not a member of an Active Directory
domain then a reboot of the computer should show that effective
setting to be the same as the local settings unless you have a
startup/shutdown script, etc that uses secedit and a security
template to enforce your security settings. --- Steve

Steve, it works. I logged in as administrator. Thank you!


<<...snipped various attempts at a solution...>>