NT domain, windows server 2003 client

We have a windows NT domain here that we haven't upgraded to windows
2000/2003 b'coz there is no bandwidth/need for it. We sporadically use
this domain and last week I tried to add a client that is running
windows 2003 server to this domain. I could successfully add, but I
couldn't reboot at that time since my user wanted to me to wait till
the weekend to reboot.

I had to add this system to the domain to test some netbackup
processes. However, I am not sure if the system would've issues going
forward if it's on NT domain. So, I want to take the system out of the
domain. I have to reboot the windows 2003 client this week for another
reason and I don't want it to think that it's going to be in the domain
going forward.

My question is, should removing this computer's name from the domain's
server manager enough or do I have to do anything more? I just don't
want this client to be part of the domain. I need to know if I need
to do anything specific on the client side. Looks like there is no way
to tell the client u don't want to be part of the domain. Meaning,
there is no way to remove it from the domain, from the client side.

Any ideas/thoughts?

Thanks a lot!
A

.

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: Fax service on W2003Sbs - client dont send fax
    ... follow the steps to Update the Windows Small Business Server ClientApps ... Please paste the full content of the file to the Newsgroup. ... Microsoft CSS Online Newsgroup Support ... >the same day I do a system restore to monday;-) and client can send fax. ...
    (microsoft.public.windows.server.sbs)
  • Re: Changes in 2005.
    ... The client base I currently have makes transitioning to new technologies ... out over the UK which is Windows 2000 with SP4. ... > VS.NET 2003 does not compile to unmanaged code. ... > the JIT compiler handles the compilation to unmanaged code from IL. ...
    (microsoft.public.dotnet.languages.csharp)
  • 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: [opensuse] best file distribution technology for my case?
    ... It must be accessible from Windows linearly, ... It must be accessible from Linux randomly, with no client side ... in HTTP header and charset conversion is done automatically; ... users may not be to happy if it the server collapses under the load. ...
    (SuSE)