techwaresystemen
asked on
Terminal server settings won't save ?
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 !
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 !
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
Jeff
TechSoEasy
ASKER
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
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
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
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
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
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
ASKER
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
I put the users at this OU, but I still got the same problem.
:(
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
I put the users at this OU, but I still got the same problem.
:(
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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