RE: Connect a NT 4.0 Server to SBS 2003

Tech-Archive recommends: Fix windows errors by optimizing your registry



Hi Bob,

Thanks for using SBS newsgroup. Lanwench thanks a lot for your valuable
suggestions.

I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
greatly appreciated!

Issue description:

I understand that you want to set up the NT 4.0 as a file server and backup
your SBS to this file server.

Analyzing:

Please understand that Windows NT is out of life cycle. We did not official
supported it any more, as your purpose, you only want to set up a file
server to backup your SBS domain. As I know any kinds of OS can be set up
as a file server, you can use windows XP as file server too. Please refer
to my suggestions below:

Suggestions:

1. Set up a file server on Windows 2003 domain, you can use either Server
based OS or client based OS on SBS 2003 domain to install as a file server,
we recommend use Windows 2000 or Windows XP or Windows 2003 OS as the files
server, as the Windows NT is not a fully supported clients on SBS domain,
there might be a lot function limitation when using this kinds of system on
SBS 2003 domain. You can enable the Windows files and sharing on the TCP/IP
protocol on the files server and created a shared folder on SBS domain on
that file server.
2. You can also set up a member server on SBS domain, then set up it as a
file server, just as Lanwench said, you might have to reinstall Windows NT
4.0, if it is a domain controller before. If you want also use it as other
role such as terminal server, you need also buy additional CAL for the
member server, you can refer to the following section for more information:

Since the TS server is a member server of the SBS network, the Windows
License should be covered by the SBS license (TS license will not be
covered by the SBS license.). You also need to configure the License mode
of the TS server to Per Seat mode, you can follow the steps below to
configure the license on terminal server: (I assume you use a Windows 2000
server on SBS 2003 domain)

1. Go to the additional Windows servers, open Services console in
''Administrative Tools''. Make sure that the ''License Logging services''
is running.

2. Go to the SBS 2003 server, open ''Active Directory Sites and Services''.
Click on Default-First-Site-Name and the double click on Licensing Site on
the right. Make sure that the SBS 2003 server is the Licensing Computer.

3. Go to the additional DC and member servers, open ''Licensing'' console
in ''Administrative Tools''. Set the licensing mode of the additional
Windows server to ''Per Device'' mode. The number of licenses should be set
to be equal to the number of SBS client access license (CAL). You can
select License->New License from the menu and then select Windows Server
from the dropdown and specify the same number of license that your SBS
server has.

327644 HOW TO: configure licensing on an additional Windows server in an
SBS network
http://support.microsoft.com/?id=327644


More info:

As you want to put the Windows NT in SBS domain, please also refer to
following article for more detailed information:


811497 Error Message When Windows 95 or Windows NT 4.0 Client Logs On to
Windows Server 2003 Domain
http://support.microsoft.com/?id=811497

555038 How to enable Windows 98/ME/NT clients to logon to Windows 2003
based Domains
http://support.microsoft.com/?id=555038

288358 How to install the Active Directory client extension
http://support.microsoft.com/?id=288358

Backup and restore SBS 2003:
http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d6
2bcc9/BKU_BkupRstr.doc

Hope the above information helpful. In the meantime, if you have any
further concerns, please feel free to let me know. I will be here waiting
for your updates.



Best regards,

Charles Yang (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • Re: How to add a user with very limited rights
    ... The Windows Server 2003 External Connector license is an optional ... An EC license is not applicable to Web Edition or Windows Small Business ... For more information about External Connector License, ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 on SBS 2003 Premium
    ... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
    (microsoft.public.windows.server.sbs)
  • RE: Service Pack 1 on SBS 2003 Premium
    ... reinstalled the SP1 from CD again, ... Restart Windows Management Instrumentation service. ... Close the registry editor and restart the server at a non-business time ... Have you applied the whole SBS SP1 successfully? ...
    (microsoft.public.windows.server.sbs)
  • Re: The list of servers for this workgroup is not currently availi
    ... Select Windows Small Business Server 2003 and then click Change/Remove. ... You may prompt to inset SBS installation CD. ... Our only problem w/ connecting to the branch office is mapping ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 Standard - Update to SP 1 fails
    ... order to prepare SBS server to deploy Windows XP SP2 to client computers ... that are running Windows XP Professional. ... The SBS SP1 launcher need copy ... please install it and then ...
    (microsoft.public.windows.server.sbs)