by   April 10 2012   
Setting up SBS 2003 AD with 2nd SBS 2003 as Terminal Server isn't as easy as you would think. Well unless you have read all the documents about this issue. It takes time to figure out things like this Grasshopper. You will learn. I have all the links for you in this section to complete this task. And, if you need help I can fix this issue remotely. Good Luck!

SBS 2003 is shutting down every 2 hours or so.

http://www.winvistatips.com/sbs-2003-shuts-down-intermitantly-after-1-2hrs-t658886.html
http://support.microsoft.com/kb/925652
http://support.microsoft.com/kb/255504/

After you have read all the information in the above links try the SpeedGuide.Net fix for the SCore file.

UPDATE: 4-11-2012 I had to update a few things so I took down the step by step guide. If I remember this week I'll get it back up . Send a note if you needed as a reminder for me.

I had a second server on the same network and the main server would shut it down remotely.

Following the guide Microsoft published which bascially says.

We do not suggest you using the Terminal Server in a DNS server due to possible security issues.

They (Microsoft) in another article suggests that you installed another server SBS 2003 on the network to run the Terminal Server. When you do this the problems start. But the fix is to stop the shut down.

Microsoft did say you can not run 2 DNS servers on the same network which is true for the SBS2003 software. But when you demoted the AD DNS to a simple server the issue of the AD was still there. Shutting down every hour or two.

So far months have shown the fix from Speedguide.net on the in servers AD works. No mode to the second server is needed.

In fact, I bet you can run 2 full servers less the AD on the same network with this patch.

I never did post up the fix or confirm the fix.

Well I can confirm it, as long as you find the perfect Terminal Server settings this issue of running 2 SBS 2003 on the same network one as a AD and the other as a Terminal Server.

Life is good when you iron out issues like this. Look up KillProcess.vbs someplace here on this site and add your SBS 2003 terminator app to the string so you have time to do all your registry edits before the AD shuts you down.

If you need help this is a Remote Access Fix and will only take me 20 minutes on each system to setup. Then you will just have to wait to see it does work. But, it will require you on site and at the terminal during the work.

 

Setting up SBS 2003 AD with 2nd SBS 2003 as Terminal Server isn't as easy as you would think. Well unless you have read all the documents about this issue. It takes time to figure out things like this Grasshopper. You will learn. I have all the links for you in this section to complete this task. And, if you need help I can fix this issue remotely. Good Luck!