Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Using Thinclient with Win SBS 2003
01-07-2014, 08:33 PM,
#26
RE: Using Thinclient with Win SBS 2003
(01-07-2014, 07:37 PM)greavette Wrote: Hi Dennis,

I'm confused...I think this has gotten more complicated than it needs to be. Let's back up here...

You originally had a Dell Workstation. I'm assuming you used that Dell Workstation to connect through remote Desktop to your Windows Server 2003. If this is true then there is no need to find out what userid or domain to use...you already know this. Use the same credentials you previously used when you used remote desktop from the Dell Workstation.

If you didn't use remote desktop from the Dell workstation then maybe you used the desktop from the Dell workstation. That's dead...now you are using the desktop from the Windows 2003 Server. It will look different than the Dell workstation. Makes sense?

Ok..now on to remote desktop...I'm unclear what you are expecting here? For remote desktop use the IP of the Windows 2003 Server and login with a userid and password that has the correct access to login with Remote Desktop. You'll see a Windows 2003 Desktop. Server Manager will open if it's set to open when logging in. Close it if it's opened. Customize this desktop anyway you like. When you logout and log back in with the same user you should see this same customized desktop for that userid.

If this is all unclear to you then I would suggest you do one of two things:

1. Reach out to someone in your area to assist you with your connection issues. If possible have them look over your shoulder as you show them what you are doing. If you have a deadline looming and your job is on the line, you shouldn't be messing around with what userid to use and what domain to use. These should already be established and known. Don't let this get down to the last day where you are still scrambling.
2. Have a backup plan or escape plan that will solve your problem by the deadline with whatever you need to get the job done. Using the Pi for Remote Desktop should be easy...if it's not then don't use it. Use something you are familiar with and comfortable with. On the side play with the Pi and remote desktop (when you don't have a deadline hanging over you).

It's up to you if you want to continue...I'll keep an eye on this thread if you have more questions...the above is just what I would do if I were in your situation.

I'm sorry I was confused (I think) - Here is what I thought/expected

1- When an employee logs in after ctl+alt+delete their personalized desktop loads (seemingly) from the server. I know now that much of the information on their computers (including files and documents) are in fact not on the server but stored locally on their C: drives.

2- I have tried several different users...they all seem to have access to the server management when i log them in through rdesktop (window to manage server pops up) and they have access through start menu. When they log in through a working Dell PC in the office, they do not have those rights...i am guessing I will have to change some settings in the server to manage policies for users doing it this way.

3- I am successful in logging in through rdesktop with several users in the office. They all seem to have a standard setting of 3-4 applications on the server desktop. Their files and other custom icons/apps seem to be on their local Dell workstation. I do not have enough free space on the server to install everyone's personalized applications and documents, so that poses another issue I guess.

4- I may be wrong, but I am guess that for this to work, I would need a LOT of free drive space on the server...there is a large office management application that I now understand is installed through an installer on the server onto each workstation locally. If I were to install this and all other apps (card readers, scanners, documents folders, files, etc.) on each desktop in the server,it would be impossible.

5- Additionally, the stupid monitors in the office are all VGA, and after buying a VGA to HDMI converter realize that it won't work. So all monitors will have to be switched over or I will have to buy a powered converter at about $50.00 USD each.

6- I guess my lack of knowledge in how the server played a role in the workstations was the issue. I thought it was set up where each personalized desktop (including files, folders, and applications) were not stored on workstations, but instead on the server. I see now I was so wrong!

I really want to thank you. It looks like the end of the road for me on this one. I guess I could clone the current 60GB hard drive Server 2003 is installed on in the server and install a 4+ terabyte drive, copy the cloned image, and then copy all files and folders from each workstation to the server desktop associated with each user login.

You are a very intelligent and very helpful person. I am sorry I have nothing at the moment to offer you in return, but I do sincerely appreciate everything and all the help you have offered. I know your time in responding has created a nice little tutorial for other readers...thank you a million times over.
Reply


Messages In This Thread
Using Thinclient with Win SBS 2003 - by dbirk007 - 22-05-2014, 10:35 PM
RE: Using Thinclient with Win SBS 2003 - by dbirk007 - 01-07-2014, 08:33 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)