Learn when you want, where you want with convenient online training courses. Sign up now!
[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
...you must be logged on as a member of the Domain Admins security group.
Start the Remote Access Wizard.
Follow the instructions to complete the wizard.
Once you finish the wizard, you can configure client computers to remotely connect to the local network by doing one of the following:
To configure mobile client computers, such as laptops, that are currently connected to the local network, run the Set Up Computer Wizard, and then select the option to install Connection Manager.
To configure remote client computers not currently connected to the local network, you can create a remote connection disk. You can then use the disk to configure the remote client computer to connect to the local network. Alternatively, users can download Connection Manager from the Remote Web Workplace.
For more information about configuring client computers, see Connect remotely to the server. For more information about using the Remote Web Workplace, see Understanding Remote Web Workplace.
You must also assign users to the Mobile Users security group so they have the necessary permissions for remotely accessing the local network. To do so, assign the Mobile User template, Administrator template, or Power User template to the user account by doing one of the following:
To make existing users a member of this group, run the Change User Permissions Wizard.
If the user does not currently exist, run the Add User Wizard.
"Allow log on through Terminal Services" security policy setting, and by default it's only set to allow administrators. Clicking the "Explain" tab says this:
Allow log on through Terminal Services
This security setting determines which users or groups have permission to log on as a Terminal Services client.
On workstation and servers: Administrators, Remote Desktop Users.
On domain controllers: Administrators.
The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.
The simplest way to resolve this issue is to add your thin client users into the Remote Desktop Users Group (or any other group for that matter) then grant that OU the "Allow log on through Remote Desktop Services" ("Terminal Services" in pre 2008 R2 releases) via:
Start > Run > gpedit.msc
Expand: Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Management
Select: Allow log on through Remote Desktop Services
Add Remote Desktop Users to the Policy.
To apply the changes: Start > Run > gpupdate /force
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
From novice to tech pro — start learning today.
Premium members can enroll in this course at no extra cost.