Solved

Terminal server settings won't save ?

Posted on 2006-06-19
8
313 Views
Last Modified: 2011-10-03
Using 2 server:
1 Terminal Server with Windows 2003 Standard SP1
1 Active Directory/Exchange server with Windows SBS 2003 SP1
+/- 10 Users using client Windows XP SP2

Every user want his own settings. The problem is when they change these settings like toolbar or the view of explorer. That when they log off and login again sometime's these settings going back to default.

The users have full control over there profiles. We dont use roaming profiles.
The profiles stands in the c: documents and settings map.
We have these users in a OU and use a GPO, in this GPO we only disable shutdown and some stuff in the startmenu.

When we put out these users out of the OU we still have this problem. Even when we give them admin rigths

We scanned for spyware or virus but nothing special found. Using internet under terminal server is not alowed.

Only windows settings wont save. When we change someting in word or something else there is no problem with it.

Can someone help me thanks !
0
Comment
Question by:techwaresystemen
  • 4
  • 2
8 Comments
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 16933926
With an SBS you must keep the default OU's in place.  All users must stay in \MyBusiness\Users\SBSUsers.  Instead of creating different OU's, SBS relies on Security Groups for delegation of GPO's.

However, there are a number of other important things to follow when adding a Terminal Server to an SBS network, and also for deploying roaming profiles.

Please see http://sbsurl.com/sbstss for specific instructions on adding a Terminal Server to your network.  Then please see the Roaming Profiles section of http://sbsurl.com/postinstall for the important settings necessary for roaming profiles.

But before you even start there... you need to move all users back to the default OU.

For more info on SBS overall, please see http://sbsurl.com/itpro

Jeff
TechSoEasy
0
 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 16933948
Just to clarify... since I reread your question and you say that you don't use roaming profiles... is this because the Terminal Server users only ever log onto the Terminal Server?  If that's the case, then ignore my comments about roaming profiles, but definitely you need to have those users stay in the default OU.  All users should be created with the user templates via the add user wizard.  If you want a specific one for TS users, then you should create a new template by copying an existing one and modifying.

Jeff
TechSoEasy
0
 

Author Comment

by:techwaresystemen
ID: 16935879
Since I reread your question and you say that you don't use roaming profiles... is this because the Terminal Server users only ever log onto the Terminal Server?

Yes they only log on the Terminal Server. They arent in a domain just only workgroup.


With an SBS you must keep the default OU's in place.  All users must stay in \MyBusiness\Users\SBSUsers.  Instead of creating different OU's, SBS relies on Security Groups for delegation of GPO's.

Ok, the users arent in this group. I will put them in these group. But can really cause this my problem because they are in a wrong OU ??

Thanks
0
Get up to 2TB FREE CLOUD per backup license!

An exclusive Black Friday offer just for Expert Exchange audience! Buy any of our top-rated backup solutions & get up to 2TB free cloud per system! Perform local & cloud backup in the same step, and restore instantly—anytime, anywhere. Grab this deal now before it disappears!

 
LVL 74

Expert Comment

by:Jeffrey Kane - TechSoEasy
ID: 16936415
Well, I'm not sure.

In the answer to the first question you say that they aren't in the domain... but that's not really possible unless if they are authenticating through the SBS.  But if you created users in an OU, then they are domain members... if you created them in an OU other than the default, then their settings will most likely not stick... especially if you didn't follow the Terminal Server Install guide I linked above.

And, just so you understand the licensing... you are required to have both SBS CALs AND Terminal Server CALs for these folks, as well as licenses for any software you have installed on the Terminal Server.

Jeff
TechSoEasy
0
 

Author Comment

by:techwaresystemen
ID: 16942136
In the anser to the first question you say that they aren't in the domain... but that's not really possible unless if they are authenticating through the SBS.  

I am sorry I mean that the workstations aren't in a domain. Ofcourse the terminal server is at the rigth domain.

With an SBS you must keep the default OU's in place.  All users must stay in \MyBusiness\Users\SBSUsers.  Instead of creating different OU's, SBS relies on Security Groups for delegation of GPO's.

I put the users at this OU, but I still got the same problem.  

:(


0
 
LVL 74

Accepted Solution

by:
Jeffrey Kane - TechSoEasy earned 125 total points
ID: 16945153
Did you manually put them in the OU? or did you add the users with the Add-User wizard and they were put there automatically?

With SBS you must ALWAYS use the wizards to configure things because otherwise you'll end up breaking other dependent components.

Your Terminal Server should have been added to the network by first running the Add-Server wizard on the SBS, and then running http://<sbsservername>/connectcomputer from the TS.  If it was not done this way you need to follow these steps to fix it:

The following needs to be done on the Terminal Server:
1.  Log in with THAT machine's LOCAL administrator account.
2.  Unjoin the domain into a WORKGROUP
3.  Change the name of the computer
4.  Delete or rename the following directory C:\Program Files\Microsoft Windows Small Business Server\Clients if it exists
5.  Make sure that the network settings are configured to get an IP address automatically (DHCP enabled).  If you want the server to have a specific IP, create a DHCP reservation on the SBS
6.  Reboot

Then on the server, from the Server Management Console:
1.  Remove the server if it still shows in the Servers screen on the Server Management Console's Upper tier.
2.  Add the server with it's NEW name using the Add Server wizard

Then, go back to the Terminal Server and join the domain by opening Internet Explorer and navigating to http://sbsservername/connectcomputer

Finally, run the Configure Email and Internet Connection Wizard again so that the new Terminal Server will be recognized and a menu item will be created in Remote Web Workplace... this is where remote users should log onto the Terminal Server.

Jeff
TechSoEasy

0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
Recently, I had the need to build a standalone system to run a point-of-sale system. I’m running this on a low-voltage Atom processor, so I wanted a light-weight operating system, but still needed Windows. I chose to use Microsoft Windows Server 200…
It is a freely distributed piece of software for such tasks as photo retouching, image composition and image authoring. It works on many operating systems, in many languages.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now