Newbie Setup Question



We have a SBS2000 (not 2003) server running Active Directory & a
Windows 2003 Server running as a Terminal server. We added (10) new XP
client computers to the AD and (10) generically named users who are
now just members of the "Domain Users" group. This setup for the sole
purpose of the (1) clients/users running one application on the
Terminal Server. It appears that if Active Directory were running on
Windows 2003 Server we could just add the clients to the Remote
Desktop USers group to accomplish some of the things we need to
accomplish. However that group is not available in Windows 2000 AD.

So here is our goal for the (10) new clients:

1. We want every client to have the same TS desktop. It will include
the icon for starting the application and nothing else except the same
program on the Start Menu in case the icon gets deleted. No other
programs should be listed.
2. We do not want the users to have access to a local desktop.
3. We do do want any user to be able to install anything to the TS
from the USB drive or CDROM, but we do not want this hardware
disabled.
4. When the systems bootup, we do not want a CTRL+ALT+DEL prompt. We
want the system to boot and automatically display a customized TS
desktop for each of the (10) systems. If it is preferable/recommended
to have the CTRL+ALT+DEL prompt, we want each client tohave the same
login an go directly to the TS without the user manually launching RDP
connection.
5. We do not want the users to have Internet Access from the TS. We
have read about using the 127.0.0.0.
6. Possibly a mapped drive to the SBS2000 data partition to open
particular shared files in "read only" using a program installed on
the TS.

Can we accomplish all of the above?

Can anyone provide a starting point -thanks. We are currently reading
much material and have a Virtual PC setup with Windows 2003 Servers
only (no 2000 AD) but basically see we need to start with new OU.
.



Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: after installing KB011829 OWA is not working anymore
    ... Based on my research, after you install hotfix KB911829, I suggest we ... Profile WMI Provider to each client computer that is running Windows Vista ... If you are running the Premium Edition of Windows Small Business Server ...
    (microsoft.public.exchange.connectivity)
  • Re: DHCP Issues. Very strange
    ... I understand the issue to be: some client computers ... can not obtain IP from SBS server. ... it is most possible a client side issue of Windows ... since you have join it to SBS domain and the Windows XP SP2 ...
    (microsoft.public.windows.server.sbs)
  • Authentication flaw in microsoft SMB protocol
    ... Microsoft uses SMB Protocol for “File and Printer sharing service” in all ... Authentication is used to authenticate the client on the server. ... logged-in user requests for a network share on the server, Windows ...
    (Bugtraq)

Loading