Re: Log in locally to client computer through RWW
- From: v-yanniw@xxxxxxxxxxxxxxxxxxxx ("Jenny wu [MSFT]")
- Date: Fri, 21 Oct 2005 06:14:23 GMT
Hi Bryce,
I wanted to inform you that I have replied to your thread in:
Newsgroup: microsoft.public.windows.server.sbs
Titled: Log in locally to client computer through RWW
Please reply directly to the thread if you have any other question or
concern. You may receive this email notification before you are able to
view my reply in the newsgroup. I also copy the content as following for
your convenience:
******************
Hi Bryce,
Thanks for posting here! Many thanks for Susan and Lanwench's input.
Yes, as Susan and Lanwench said, you can logon locally through RWW if you
have the local admin user account and the password is not blank.
Additionally, you need ensure the local group policy that doesn?t prevent
RDP connection. I list the following group policy settings related remote
access for your reference:
1. Click Start->Run, type "gpedit.msc" (without the quotes) and click OK.
2. Go to Computer Configuration\Windows Settings\Security Settings\Local
Policies\User Rights Assignment.
3. Double click the "Access this computer from the network" policy and make
sure the following groups are listed:
Administrators
Everyone
Power Users
Users
4. Double click the "Allow logon through Terminal Services" policy and make
sure the following groups are listed:
Administrators
Remote Desktop Users
5. Check the "Deny access to this computer from the network" policy and
make sure the groups mentioned above are NOT listed.
6. Check the "Deny logon locally" policy and make sure the groups mentioned
above are NOT listed.
7. Check the "Deny logon through Terminal Services" policy and make sure
the groups mentioned above are NOT listed.
8. Check the "Log on locally" policy and make sure the following groups are
listed:
Administrators
Guest
Power Users
Users
9. Close the "Gourp Policy" window.
If you change any settings, you can run command to refresh group policy and
force to client computers:
10. Click Start->Run, type "gpupdate /force" (without the quotes) and click
OK.
If you have any further concern or question on the issue please let me
know. We are glad to help!
******************
If you are unable to view the reply to your thread, please send me an email
with a description of the problem and what newsreader you are using.
Have a nice day.
Sincerely,
Jenny Wu
Microsoft Online Partner Support
MCSE 2000/2003
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.
More Information
===========
Please be informed that we have released The Microsoft? Baseline Security
Analyzer (MBSA) 1.2 to the public; the download link is
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/
tools/mbsahome.asp.
The Microsoft? Baseline Security Analyzer (MBSA) is a tool that allows
users to scan one or more Windows?-based computers for common security
misconfigurations.
Microsoft has published information, that details the tool and instructs
customers how to use the tool:
- Microsoft? Baseline Security Analyzer (MBSA) Home Page
- Microsoft Baseline Security Analyzer (MBSA) Version 1.2 Is Available
(320454)
- Microsoft Baseline Security Analyzer (MBSA) Version 1.2 Q&A
MBSA 1.2 now includes new support for the following Products:
- Exchange Server 2003
- Microsoft Office (Note: MBSA can only be used for to perform a local
scans for Microsoft Office. Please see the above referenced documents for
more information).
- Microsoft Data Access Components (MDAC) 2.5, 2.6, 2.7, and 2.8
- Microsoft Java Virtual Machine
- MSXML 2.5, 2.6, 3.0, and 4.0
- BizTalk Server 2000, 2002, and 2004
- Commerce Server 2000 and 2002
- Content Management Server (CMS) 2001 and 2002
- SNA Server 4.0, Host Integration Server (HIS) 2000 and 2004
If you have any questions regarding the tool or its implementation after
reading the above resources, you should contact Product Support Services in
the United States at 1-866-PCSafety (1-866-727-2338). International
customers should contact their local subsidiary.
.
- References:
- Log in locally to client computer through RWW
- From: Bryce
- Re: Log in locally to client computer through RWW
- From: "Jenny wu [MSFT]"
- Log in locally to client computer through RWW
- Prev by Date: Re: Log in locally to client computer through RWW
- Next by Date: Re: Full name changes to Username and some open files lose connection
- Previous by thread: Re: Log in locally to client computer through RWW
- Next by thread: Re: Log in locally to client computer through RWW
- Index(es):
Relevant Pages
|