RE: NT4 Print server on BDC

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

Hi Vincent,

Thanks for prompt reply. The only concern was will the renaming of existing
NT4 BDC to new printserver cause any concern in Active Directory. Can I just
rename it or are there any special steps to be performed. Please advise.

Thanks
TG


"Vincent Xu [MSFT]" wrote:

> Hi TG,
>
> From your description, you choose to a clean installation migration. In a
> clean installation, you must create all new printers or migrate existing
> printers. I think yor migration path is correct. However, I still suggest
> you refer to following link before you perform migration.
>
> <http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepK
> it/7f43ef1b-4f33-447b-b1b5-cbb159c30ddd.mspx>
>
> Best regards,
>
> Vincent Xu
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
>
> --------------------
> >>Thread-Topic: NT4 Print server on BDC
> >>thread-index: AcWfUqsM49S4DYXYShSGujKjZz5WCQ==
> >>X-WBNR-Posting-Host: 64.72.236.184
> >>From: "=?Utf-8?B?VEc=?=" <TG@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>Subject: NT4 Print server on BDC
> >>Date: Fri, 12 Aug 2005 08:29:45 -0700
> >>Lines: 23
> >>Message-ID: <E7D300F3-2E00-4091-808D-91CDA7B13D76@xxxxxxxxxxxxx>
> >>MIME-Version: 1.0
> >>Content-Type: text/plain;
> >> charset="Utf-8"
> >>Content-Transfer-Encoding: 7bit
> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>Content-Class: urn:content-classes:message
> >>Importance: normal
> >>Priority: normal
> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>Newsgroups: microsoft.public.windows.server.migration
> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windows.server.migration:11637
> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>
> >>Hi Experts
> >>
> >>I have a Windows 2003 Domain with one NT4 BDC. This domain has trust
> >>relationship with two other NT4 domains. The NT4 BDC is also print
> server
> >>called PRINTSRV. Now I am going to move NT4 print server to Windows 2003
> >>based print server while keeping the NT4 BDC running (Since BDC is
> talking to
> >>two NT4 domains and some 9x clients). Also I do not want to go to all
> clients
> >>to recreate printers.
> >>
> >>I plan to do following:
> >>1) Create a new server as print server on windows 2003 call it TEMP.
> Create
> >>all new queues on the new server.
> >>2) rename NT4 BDC to something else e.g. NT4BDC
> >>3)rename windows 2003 based print server to the name of existing
> >>prinserver/BDC (so that clients do not have to recreate queues on their
> >>machines.)
> >>
> >>I would like to know if this strategy will work or if there are other
> things
> >>I should be aware of.
> >>
> >>Thanks
> >>TG
> >>
> >>
>
>
.

Relevant Pages

  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: Error DHCP Windows 2008 R2, DHCP client is not a reserved clie
    ... This results in windows 2008 R2 in the error message: The specified DHCP client is not a reserved client. ... Migration with netsh has worked. ... Migrating DHCP using the Windows Server 2008 R2 Migration Tools ...
    (microsoft.public.win2000.networking)
  • Re: SwingIt Pain and Suffering
    ... BTW - I did purchase the Advanced Windows Small Business Server 2003 Best Practices book and consumed large parts of it before starting this project. ... That being said, I do feel like his documentation could greatly benefit by having some more detailed check points for verifying the health of AD at various steps along the way, and what steps to take or resources to consult if the replication doesn't seem to be going according to plan. ... BTW, even after discovering this constraint and disabling the firewalls on my destination server as part of the base OS install, replication still initially failed and I was dumb founded to find the firewall reenabled. ... I did complete the AD replication from the migration computer to the destination computer as planned. ...
    (microsoft.public.windows.server.sbs)
  • Re: Network printing - HowTo?
    ... Microsoft Windows Debugger Version 5.2.3790.3959 ... Please check your debugger configuration and/or network access. ... Guess I'm wondering if sharing my network printers off of a server is ...
    (microsoft.public.windowsxp.print_fax)
  • Re: NT4 to 2003 with Dell2650
    ... PDC for good; ie Will the accounts stay on the PDC to allow me a testing ... The Recommended Migration Order is listed below for your reference: ... Yes, after completion of ADMT, you may logon to the new Windows Server 2003 ...
    (microsoft.public.windows.server.migration)