by   March 21 2011   
Adding a second SBS2003 Server running Terminal Services on a SBS2003 Domain network Attempting to run terminal services might be more than you expected in regards to setup and keeping things running smoothly. Our first attempt worked perfectly until a security update. Now we are going to document the process for others to follow.

Setting up a SBS 2003 Terminal Server on a SBS 2003 Domain controller network.

Tech to Tech: This is Golden and worth every hour of testing. Now that I've setup the path for your success just make sure you share some good information with the next technician you work with. If it's All about You, one day a tech like me will make it Pay if it's You. Mentor others! Do it Right the First Time.

This technical article has not been completed as of this date.

Below are only notes from the technician without order.

1-31-2011

Reg Edits:

HKLM/SYSTEM/CurrentControlSet/Services/

TermDD Start set from 1 to 2

TermService Start set from 4 to 2

HKLM/SYSTEM/CurrentControlSet/Control

Terminal Server

TSAdvertise 0

TSAppCompat 0

TSEnabled 1

TSUserEnabled 0

HKLM/SYSTEM/CurrentControlSet/Services/

SBCore Start set from 2 to 4

 

File mod:

C:\WINDOWS\system32

sbscrexe.exe (Permissions) Read & Execute and Read Deny Write. (Looking to disable the network server shut down and preventing security updates to this file. First test was to place account everyone with deny on all settings. That seemed to work and the terminal server worked for a few days until an update replaced our settings.

Ok, now that this system has been running smoothing for a couple of months with only one issue which I will post the work around later after more testings.

The SBSCREXE modification (hack) that is posted in speedguide.net should be run only on the AD domain controller. The Terminal server once dc was demoted seemed to work just fine.

The issue you might have is if the system rebooted without a controlled reboot like having a power outage. Restarting or normal start up all settings seem to work just fine but on a power failure test the system returned to rebooting. Using the Last Good configuration boot things returned to normal but terminal services had to be updated again.

Not sure why this happens but it is Windows small business 2003.

If you search KillProcess.vbs use that script to kill the SBSCrexe while you are editing the registry. It will self start which makes it a pest. When I dig up my old script I'll load it here.

 

By the way, there is a challenge or should I say was and this was resolved 100% with more than 1 year of trouble free service.

But the challenge is today, How do you update a system like this without completely changing this configuration? Updates are needed but what changes would take place if you did upgrade this system? Remember this is not totally a "Free Admin Guide" and for those that are thinking it's going to be easy. I leave you one last message.

Education is not a substitute for knowledge. Let’s chalk up one more for the Microsoft and Motorola field techs!

You should have a few hours on a good working 2003 before you start changing the way it was designed to run. Troubleshooting isn't in the books once you edit that registry. Ask any IT Admin that works the industry not the computer labs.

 

 

Adding a second SBS2003 Server running Terminal Services on a SBS2003 Domain network Attempting to run terminal services might be more than you expected in regards to setup and keeping things running smoothly. Our first attempt worked perfectly until a security update. Now we are going to document the process for others to follow.