Discussion Locked

Win2K Terminal Services on a NT 4.0 LAN

0 helpful
93 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am setting up a Windows 2000 Server running Terminal Services in an existing LAN with a NT 4.0 PDC domain controller. I am having issues with User Sessions logging in correctly, profiles, and policies in this type of setup. I know this is a generic question, but what I'm looking for is a good reference that I can use to configure TS in this type of setup. TechNet is not very helpful when it comes to detail oriented steps and clarification. Any other information at all regarding this type of setup would be greatly apprcieated. I have lots of points that will generously distributed, thanks. JEFF
jeff@intellicominc.com

93 replies

by patrick.bisaillon

Hi Jeff

Could you please give us more details about what you are looking for exactly. I have a lot of experience with WTS and could give you some hint.

Regards
Patrick

by sdraney

I just got through upgrading an NT4.0 Terminal Server to 2000 Advanced Server with Terminal Services. It was an interesting experience.
The biggest things I had to watch out for were:
1. Type of profile and any shares that need to be mapped.
2. Active directory replication.
3. WINS and Userdata replication.
4. Terminal services permissions levels and the way each user will log into the new Termial Services Server.
If you watch how those are moved/mapped then the process should be a bit easier.

by william shipway

Hi Jeff

Without much detail about your problems I can only offer these two good reference points:

1) "Windows NT/2000 Thin Client Solutions" by Todd W. Mathers, Macmillan Technial Publishing. This is a great book to take you from the beginnings into the detail needed to solve problems with profiles and policies.

2) The thin client mailing list and its archive at http://thethin.net/ are extremely useful for problem-solving.

HTH
William

by peter ritchie

If your Win2k TS server has access to your NT domain (ie it's trusted) then you should simply be able to add users from the NT domain to your Win2k server. These users should then be able login remotely through the TS Client. Profile/polices from the NT domain would still come into play. Once the users are added to the Win2k server then you can deal with profiles/policies local to that server as well.

Other than that, maybe you could provide more detail to the specific problem you have encountered.

by pan 13 x

by ithink2020

We really do need more detail to help, but I would deffenetly go to the links that Pan 13 X listed in his post. There are some good sites listed.

by eyounes

hello Jeff,
I have faced the same problem when I was working for a Company in California. I went and bough the Resource Kit for windows 2000. They have a whole book about how to install configure and implement your TS. Beside, the book will help you in determining which kind of digital signature u need to use to get your clients or user in the TS server. It was really difficult but It took like 4 week to work and now they have more than 35 simultanious connections using the TS Server to access different workstation.
I hope that this will help u. I know you did not put much details in. But This book will help you really plus u will get ~ 300 programs that will help u in the security of the TS server.
Truly
ELie

by sprocket

We currently run a NT Terminal Server Farm with Citrix. Like you we wish to upgrade to Win2000 TS. We use NT 4 for other servers including our PDC and have looked into this issue and other companies that have tried it.
We have come to the conclusion that even through Microsoft say it can be done, in reality it can't. Its a all or nothing affair.
Using NT with 2000 will cause many problems esspecially with profiling.

by jodyc

This setup shouldn't really be much different than if it was Win2k Pro. I have many Win2k Pro machines running in 4.0 domains. There aren't any issues with them. Keep you policies local to the Win2k machine and stay away from roaming profiles on your 2KTS. Also, watch out the licensing. Don't activate it until you are ready to turn in on for real.

Good Luck

Jody

by tex

Okay, so you're running a mixed-mode domain. That isn't a Bad Thing(TM). However, whenever running in mixed mode Microsoft suggests that you upgrade your PDC to Win2k before any other machine. Otherwise you begin to have problems with roaming profiles and user-login parameters. Given your current dilema it sounds like your pain level is quite high. You can do one of two things:

1. Hire a Citrix consultant who may require that you take the Citrix machine offline and then require you immediately upgrade your PDC to Win2k. Then they will most likely want to rebuild that server and create new profiles based on the ones converted by the upgrade of the PDC.

2. Do-it-yourself: you will need to design an active directory, then upgrade your PDC, then build the active directory according to your design, then rebuild your Win2k-TS box. Once you have rebuilt your TS-box you will then have to reinstall all apps with the compatibility scripts that then can reference the new login profiles onyour Win2k DC (old PDC).

My suggestion: depending on your pain level I would hire a consultant and get a book at the same time. Burn through the book and stand over the consultant's shoulder while he is doing the work. If your pain level isn't high then get a book, read, then get together a good game-plan for the over-all upgrade.

Have fun,

Jim Cabe - CCA, CCNP
Consultant Network Engineer
IPM Inc.

by shmaltz

I have it set up the exact same way. The problem is because NT profiles and Win2k Profiles are not interchangeable. Here is how it worked for me.
On the server where the Profile share is located, create a subdirecotry in the profile directory called TS (you dont have to share it since the parent directory is shared).
On the terminal server computer go to start run and type in: "Usrmgr"
Select the users that are going to use terminal services.
Click on profiles in the terminal server profilepath type in the profile path (without the username) plus "\ts\%username%"
Remove any Default Profiles you have on your network (I know this is one of the problems using a mixed windows environment), You have to make sure that the default profile is going to be created from the local machine, since windows NT default profile is not going to work on a windows 2000 machine.
Now the next time a user logs on to windows 2000 terminal server the new (if that user dosnt have a profile in the ts subfolder) profile should be created from the local Default Profile and be saved in the profile_path\ts\%username% folder.

by mhi tech

Win2K SP2 addresses several issues concerning terminal server and user profiles. Go to tech net and check article # Q282522 for the entire list of bug fixes for w2k. Although this service pack is not manditory for proper operation of W2k it may address some if not all of your issues.

by jeffhasenauer

I already tried this, it did not resolve the problems I was having. Most of my problems are resulting from having an NT PDC with a Win2K Terminal Server.

by jdfcomputer

Before we go too far into figuring this out I would like to verify a few things.

1. The win2k terminal server is logged in as admin

2. The users have an account on the terminal server (these are separate accounts from the PDC login)

3. All programs and permissions required for the users are installed on the server under the admin login for testing.

4. The server is a part of the NT4 domain, preferrablu a BDC.

please respond and I will help you fix this problem.

by pcman223

We have faced just that issue in our organization. I myself do not have the answer but my buddy on the NT Admin side of the house should and probably will have the answer. I will get with him tomorrow and let you know what he comes up with.

DanJohnson

by pcman223

We have faced just that issue in our organization. I myself do not have the answer but my buddy on the NT Admin side of the house should and probably will have the answer. I will get with him tomorrow and let you know what he comes up with.

DanJohnson

by Former member

Get a book...since i know you won't rate this answer and time will expire it, I thougt I'd just grab some points....Heh.

by jeffhasenauer

I appreciate all of your feed back on this question. I am getting closer to the conclusion of this project and will shortly be spending many hours finishing my documentation from which I will post an article summarizing the methods I chose and somework-arounds that I had to impliment. Be looking for it at the end of August. Thanks again for all of your input and comments. Jeff Hasenauer, MCP MCSE A+

by chad

im with this guy above me. you should get that book. im snagging some points too.

by estebandelatorre

Hi Jeff,
I have faced a simmilar problem when I was working for a Company at Argentina. I went and bough the Resource Kit for windows 2000. They have a whole book about how to install configure and implement your TS. Beside, the book will help youin determining which kind of digital signature you will need to use to get your clients or user in the TS server. It was really difficult but It took like 4 week to work and now they have more than 35 simultanious connections using the TS Server to access different workstation.
I hope that this will help u. I know you did not put much details in. But This book will help you really plus u will get ~ 300 programs that will help u in the security of the TS server.
There?s a good article about TS on www.mcpmag.com The new issue is online up to 10 aug.

by razzadaz

Don't pay for a license. These packs cost about $135 for each user in a five-user concurrent license.

The trick is that TS is free in Windows 2000.
Don't install TS after the fact. Yes, you can install TS on Windows 2000 Server by running theAdd/Remove Programs control panel. But this has the nasty habit of forcing you to reinstall many applications.

A better way to install TS is to select it in the middle of installing Windows 2000 Server in the first place. Any applications you install after this will likely be fine.

Don't install TS on a domain controller. The rule about not installing TS after the fact is easy to follow because you shouldn't install it on a Windows 2000 domain controller anyway. Allowing TS users to log in to such a server poses an unacceptable security risk. And, because TS in application-sharing mode gets high priority, it sucks up performance from other server tasks.

It's best to set up a new server (or a lightly used server) to handle TS users.

Don't let codes drive you nuts. If you support Windows 9x and Windows NT users of TS, you must buy a CAL pack within 90 days of first use. But the 25-digit code in the license pack doesn't work. You need to call Microsoft to get the real 35-digit number. It doesn't say this in the license pack.

(www.certcities.com/editorial/tips/story.asp?EditorialsID=5).
(www.microsoft.com/windows2000/guide/server/features/ terminalsvcs.asp)

by james_randy

Jeff,

Follow this link:

http://lcis.booksonline.com/cgi-bin/ndCGI.exe/Develop/pagClubHome.hrfTIOLI_onWebEvent(hrfTIOLI)?selGetClubOffer.TB_OFFER_ID_OFFER=330118%2e0&selGetClubOffer.TB_OFFER_ID_ITEM=33011%2e0&selGetClubOffer.TB_OFFER_ID_OFFER=330118%2e0&^CSpCommand.currRowNumber=0&hrfTIOLI=Mark+Minasi%27s+Windows+2000+Resource+Kit&SPIDERSESSION=%3f%3f%3f%3f%3f%5f%3f%3f%3f%40%5b%3f%3f%3f%3fBOs%5cH%3f%3f%3f%3f%3f%3f%3f%3f%3fM%60FoJLbFZJPro%3f%3f%3fE%40xTP%5cvDsgV%5cslFSrxQEPhvP%40lWNddJSaPCE%40%5cvEqWV%5csTJ%5b%40OdJvWX%5eqCeVaxxHsDyQqXXHvgeUQDr%5bbLpIaXXGuTdDeKa%5doHbEs%5cXS%60%60%7d%3fv%5fd%5b%60OVQuSQWQGV%5cskVDv%5b&%5euniqueValue=997636225328

(I know it's long, but you can cut & paste into a browser.)

This is really one of those Computer "Book Clubs", but they have some of the better resource information. I purchased this Windows 2000 Resource Kit - which included 4 excellent books and CDs - for $9.99. You will be obligated to buy another book in the next year, but that'sreally no big deal.

No, I'm not associated with that company and/or book club. I just found this to be a great resource to learn about the different facets of Win2000. And at a cheap price.

If, by chance, that long link won't work, follow thisone:

http://lcis.booksonline.com/cgi-bin/ndCGI.exe/Develop/pagHome?clubId=LCI&promo=4028

and select "Mark Minasi's Windows 2000 Resource Kit"

Good Luck,

jr

by jeffhasenauer

Actually, we have already done this. It's a decent book program, I'd would recommend it. Good books, cheap pricing.

by claymuir

First of all the best reference I know of is the resource kit. The thinnet and thinclient websites are fine but the Resource kit gives you programs and indepth information at your finger tips.

Now, I think the things to remember are:
Make sure all users have accounts through Usrmgr, that there are not any Default profiles and the user references list a correct path for the profiles used.

by bill.beckett

Jeff, not an answer but I would be interested in knowing what you did for an outcome. We also have an NT PDC with a 2K terminal server but it is not in production use yet.

by jeffhasenauer

Thanks again for all of your input on this post. I am running about 10 days behind schedule for posting my summary of findings and implimented solutions. I am dedicated to having it posted by Sept. 12th. Sorry again for the delay. If anyone has specific questions that they would like input on within a more timely manner, feel free to send me an e-mail or call me at 1-308-237-0684 Ext. 225, thanks.

by bwood

You can also simply install Win2k in a seperate Domain. A single server running AD and all related services (DNS, TS Lic, Etc), and then have your Terminal Server box hit be a part of that domain using a trust. We are using this for some older apps that run via terminal services without having to upgrade the current domain to Windows 2000 and Active Directory. This way all profiles are handled correctly and AD authentication works properly, and your TS sessions are licensed. The DC box doesn't have to be big. We use a Dell 2200 (233 PII) with 128 MB of ram and have no problems.

Thanks,

Brad Wood MCSE, CCNA

by mpdcsup

If you don't need to roam the profiles between the Terminal Server and NT4 domain, I would put the Terminal Server in it's own Active Directory Domain (in Compatibility Mode) and establish a one-way trust (Active Directory Domain trusts NT4 domain).

by jasonschambers

As you've probably heard, Windows 2000 will depend heavily on the DNS service. With the scheduled Windows 2000 October release date just around the corner, it makes sense to ensure you have a DNS server and it's set up correctly. In this article, we'll explain why you should be running DNS. We'll begin by exploring the various components and functions of a DNS server.
Check out TechRepublic's TechProGuild!
This article appears courtesy of TechRepublic's TechProGuild, the subscription Web resource for IT administration and support professionals.

by tordster

If the problems you are experiencing is related to "access denied" etc regarding your profiles you probably need a fix from Microsoft. The fix must be ordered per phone - you can find more details on MS Web:
Q257848

If you can't get the fix fromMS send me a mail at tordster@hotmail.com

by istal

Just make user access to the individual applications, instead server desktop!

All best.

by stoker

How did it turn out?
I have found W2K Terminal services to be very randomly be successful in loading a users main profile, so I had to juts make a distinguished difference of user type; Either he has to be a normal user with no access to the profile under terminal server (Set normal profile only), or he had to be primarely a terminal server user, with a terminal server profile only, so a domain logon anywhere else would bring up almost nothing from the profile. The second way, with TS-User-only has been the most successful way, requires a somewhat more beefy server, but no matter where the user is, he can always log in to any computer on the domain with his username and access his profile with the Terminal services client from there (Mostusers seem to like working in TS better than on their own WS, speed is better etc).
When/If you do migrate all your NT4's to 5's, and are going to install Active Directory, I would recommend Oreilly's book "Windows 2000 Active Directory", ISBN 1-56592, it explains how the master roles are distributed and can be shifted a lot better than any MS book or the res-kit.

by geek2d

The book you need is Windows NT/2000 Thin Client Solutions By Todd W. Mathers ISBN 1-57870-239-9 Look in www.bookpool.com for your best price. I have heard from other admins that agree, this is a really good book. There is a chapter just for you. You can also check www.newriders.com for more info.

by jfrink

Jeff, I don't know the answer, but I could use 6000 points.

Give them to me
Give them to me
Give them to me
Give them to me
Give them to me
Give them to me
Give them to me
Give them to me
Give them to me
You should be under my trance now thanks for the points.
Jeremy Frink
City of Kearney

by jeffhasenauer

WOW! Is it October already! I apologize for not getting this question closed. I still appreciate all of the responces that this question has generated. My Terminal Server Team have a scheduled meeting this month to conclude this project and archieve all of our information. I will still post a brief summary of our findings but will avoid very much detail due to the amount of material that was needed to complete this project. Last promise : Look for it before NOV. 1st. I will close the question at that time, thanks again. Jeff Hasenauer, MCP MCSE A+

by maximk

Since almost everybody has had a go on this one, I might as well give it a try also ;-)

Depending on the number of users on the terminal server, the amount of file servers you use for profiles, and the type of applications you are running, it is possible that you are running into a limitation described in Q190162 (http://support.microsoft.com/support/kb/articles/q190/1/62.asp).

Good luck!

HTH

Maxim

by pablob

Citrix has many benefits over native terminal services from bandwidth economy of the ICA protocol to true colour display, session shadowing, server farms etc. etc. - see the Citrix website for all the marketing stuff.

The terminal servers should be treated as multi-user workstations and only "client" software loaded onto them e.g. no database, mail server software or the like.

Use a token based VPN remote authentication, don't rely on fixed passwords.

Locate your server farm in its ownDMZ and use the firewall to control access to your LAN and your terminal servers. This means remote users can ONLY attach to the terminal servers e.g. port 1494 for Citrix. Only allow access from the terminal servers to your LAN via the firewall.Viruses will only come from remote users if they are allowed to upload local files to the terminal servers. If they need to do this then make sure each terminal server has client virus checking software installed and that the definition files are up-to-date.

To determine server and bandwidth requirements you need to do some benchmarking. For terminal servers the main areas are going to be RAM, then CPU, then Disk. RAM is important because you don't want excessive paging as this will impact user performance. Start with Task Manager and check the memory footprint for a user. For bandwidth don't assume anything - benchmark using a Packetshaper or Sitara or similar device.

by sativocomputerservices

Make sure your DNS box 47 is unchecked, otherwise you client laptops will use cached authentication and will not get policies!!! Just a friendly suggestion.

by rkelly

I've got one of these working pretty well at the moment.

The major issues concerned are with profiles and user data.

To resolve these it's important that EVERYTHING is installed on an NTFS volume. It's also usual to install on a Windows 2000 Member Server - if you have issues with profiles then you can either use local profiles on the terminal server, or use roaming profiles.

To install apps you either use Add/Remove programs of use Change user /insall to open the system registry for updates. (remember to close it again change user /execute).

Use NTFS permissions to stop users executing apps.

I'm interested in seeing your findings as the one I installed and tested installed with very few issues indeed, but obviously any future ones could have all sorts of problems.

by mystie75

The solution my company went with was having users login via a web version of citrix. We still had to install the citrix program on their machines, a program to allow users to print locally, IE5.5 and Adobe5. The users user IE to get to login to citrix, this allows for the possibility of using wireless internet to keep in contact also.

by tony

Hi Jeff

I have finally found out the answer to this question after spending about two months on it !
MS didnt even think of this issue when designing there setup ! (what a great shock !! :-)

The root of all my problems was that my users wereusing Roaming profiles, which meant that when they attempted to logon, it converted their account to NT 5 (2k). Even when I tried the answer from Newyork?? (Answer 13) it still didnt solve my problems !!

I then had a brain wave... (and it hurt)I disabled my roaming profile (and hey presto)
Good luck, hope this helps you..
and saves many, many long, hair pulling nights

TonyMCSE MCP CCNA

by tommylee10039

Hi,

I have win2k server as well as win2k professional on a single 20GB hard drive, now i would like to use all 20GB for win2k professional, and get rid of win2k server. how would you suggest that i proceed.
Thanks Tommylee

by avswamy

i make it with in four days likely by 8th of this month if u open it upto then.

by jeffhasenauer

Thanks again for everyone's comments. Obviously it is difficult to post all of my findings on this question in this small comment area, so I will e-mail to those who are interested in Word 2000 format. I will eventually post it on our web site fordownload, but until then, please send your requests to my e-mail address above and I'll forward you a copy of my brief summary of findings. Thanks again for all you input, sorry this took so long to close. Jeff Hasenauer, MCSE A+

This discussion is closed to new replies.