Hello Dan,
Thank you for using newsgroup!
First, thanks Nass for his kindly notifications.
From your post, we cannot reproduce the issue. Could you confirm the
information that Nass mentioned first?
If the issue still occurs, I am not sure if the following steps can help:
Reset the security settings to the defaults
---------------------------------------------
1. Log on the computer as a Local Administrators group member.
2. Click Start, click Run, type cmd, and then press ENTER.
3. Type "secedit /configure /cfg %windir%\repair\secsetup.inf /db
secsetup.sdb /verbose" (without quotation marks), and then press ENTER.
You receive a "Task is completed" message, and a warning message that
something could not be done. You can safely ignore this message. For more
information about this message, view the %windir%\Security\Logs\Scesrv.log
file.
4. Restart the computer, and then try to open the folder.
5. If the folder cannot be opened, please try to take the ownership and
configure the permissions.
NOTE: After security settings are applied, you cannot undo the changes
without restoring from a backup. If you are uncertain about resetting your
security settings back to the default security settings, you must make a
complete backup that includes the "System State" (the registry files).
Items that are reset include NTFS file system files and folders, the
registry, policies, services, privilege rights, and group membership.
For detailed information, please refer to the following KB article:
313222: How To Reset Security Settings Back to the Defaults
http://support.microsoft.com/?id=313222
Hope that helps!
Thanks & Regards,
Ken Zhao
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Anyone can unlock workstations.
| thread-index: AcZ/OIli3JrPO1xyQLy+mXvcjUoBLw==
| X-WBNR-Posting-Host: 163.153.164.1
| From: =?Utf-8?B?RGFuaWVsIFAuIENheWVh?= <
[email protected]>
| Subject: Anyone can unlock workstations.
| Date: Wed, 24 May 2006 06:47:02 -0700
| Lines: 17
| Message-ID: <
[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
| Newsgroups: microsoft.public.windowsxp.general
| Path: TK2MSFTNGXA01.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windowsxp.general:1512085
| NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
| X-Tomcat-NG: microsoft.public.windowsxp.general
|
| This is one of the oddest things I have ever seen and I can't detect any
| change to my systems that would cause this.
|
| When a user locks a workstation, it was designed so that only that user
or
| an administrator could unlock it. I thought that was the design out of
the
| box. Now anyone can come in and boot that user (who had locked the
| workstation) off and log on themselves. What should I check for to see
why
| this is happening and how to reverse it? I know that the people who are
| "unlocking" the workstations are not administrators or are in that group.
|
| TIA
|
| Dan
| --
| Daniel P. Cayea
| Capital Region BOCES NERIC
| Peru Central School District
|
