Sbs 2011 install client access role

Because each user will be executing his or her programs on the server itself, you need to determine exactly how your users work and what their real requirements are.

And rightly so—capacity planning is subject to an enormous number of variables. So take the following as merely basic guidelines, and carefully consider how your environment affects these numbers.

If the available memory per user drops below this point, excessive paging can occur, causing an unacceptable user experience.

Predicting exactly how much CPU power will be required per user is difficult because each user has a different mix of applications and expectations. A physical server with a single quad-core processor Windows Server R2 with sufficient RAM present to avoid swapping can realistically host somewhere between and users—in other words, more than an SBS network has to worry about. Without SLAT, the maximum number of users drops to roughly 50—70 users for a four-processor virtual machine—still enough to handle the vast majority of SBS environments.

Limiting the maximum color depth to bits per pixel bpp significantly improves the capacity of the RD Session Host server. However, if your RD Session Host is supporting no more than 50 users, enabling Desktop Composition Aero and bit color should not be an issue. A typical SBS network with 1 Gbps networking has more than sufficient network bandwidth to support as many Remote Desktop clients as necessary. If your network is limited to older Mbps networking, you might end up with network bandwidth issues if your RDS users run graphics-intensive applications, even on an SBS-sized network.

Remote users can tailor their RDP settings to limit bandwidth use over slow connections. The maximum number of RemoteApp users that a given server can support is actually slightly fewer than if the users were running full sessions with the same application mix. Remote Desktop Services use requires special licensing considerations.

It should not be enabled on the main SBS server. Windows XP. Windows Vista. Windows 7. Windows Azure. Windows Server. Windows Phone. RDS is licensed separately from SBS, and one of two licensing modes can be selected: per device or per user. Regardless where you are installing the RDS licensing server, choose per device or per user.

By default, only the local Administrators group has access to connect to the RDS server. Click add to add a group of users to have rights to the server. Type in domain users to allow all, or whatever specific security group you have set up.

Confirm that domain users are added. Click next. The client experience can be tailored for your specific environment based on the level of functionality desired and the hardware available. Confirm the choices and click on install. The role will then install. You have to restart the server.

Click yes to restart. Click Start, and in the box type in Regedit and hit enter. Then to Software. Then to Microsoft. Then to Small Business server. After navigating to the SmallBusinessServer key, create a new registry key.

Right mouse click , then on new, then on new key. Name the new key RemoteUserPortal. Now inside this key, create a new multi-string value. Call the multistring value name TsServerNames and enter the name of the member server.

While in a SBS network one does not need Windows Server cals in order to access the r2 member server role, one does need RDS cals in order to properly license the ability to access the member server as a remote web access box. Go to the member server, click on start, run and then the RD licensing console. Approve the User Account Control prompt. Ensure that the server is activated via WGA before the next step. After it has gone through WGPA the error message you get indicates that it is looking for a license server.

Your other options here are web browser and telephone. I was following a guideline that I found which gave particular instructions on how to configure the default web site authentication. To cut to the chase, I disabled Anonymous Authentication.

This was causing the problem. As soon as I enabled Anonymous Authentication, everything went smoothly. See my snap shots below. I hope this helps. I had Microsoft dialed in for approx 15 hours over the past week trying to figure out what was going but to no avail. This morning I tested changing some of the authentication settings in IIS, and when it looked liked I might be on the right track, I googled to double-check I wasn't messing around with any security settings that I shouldn't be messing with.

The search led me to your response above to my original question. I tested enabling Anonymous Authentication on the "Default Web Site" as per your screenshot above but it didn't fix the problem. However, enabling Anonymous Authentication on the "Connect" subgroup just below the "Default Web Site" did fix it - finally!!

Only 2 months later!! Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads.

Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. This happens on all the PC's and Laptops. Checked that all PC's meet the required prerequisites 2. Installed and then updated. Net 4 5. Disabled IPV6 6. Checked that time and date on server and clients are the same 8. LAN connections are wired 9. No luck. I have scoured lots of forums and tried other bits and pieces but can't work this one out. Getting somewhat desperate - Any help would be greatly appreciated.

David from Downunder. Monday, September 24, PM. Sunday, September 23, AM. There is a different forum for SBS Essentials so you may get better response asking in it. Sunday, September 23, PM. Still having this issue? Are you wired or wireless Hi Steve I spent some time searching for the best forum to seek assistance and felt this was the best one.

Cheers David. Hi Larry Thanks for the hints. Connections are wired 2. Hi Jim Thank you for your help.