Re: Migrating XP Pro Clients from NT4 Server to SBS2003 Server

Tech-Archive recommends: Speed Up your PC by fixing your registry



SuperGumby, Thank you so much for that detailed reply. That is very
interesting but it seems very complicated and not justifiable in terms of
time and expense for the small network that I am converting. I do
appreciate knowing these details as it helps me explain why some personal
user may be lost. It also speaks to why it is helpful to stay on the
upgrade train... when you get off (not upgrading to 2000 in this instance)
you can find yourself having to work hard to get back on. Thanks again.

"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:ueXmROvZFHA.1152@xxxxxxxxxxxxxxxxxxxxxxx
> how would you like those users to use the _same profile_ after the
> migration?
>
> Have a look at www.sbsmigration.com.
>
> The basic process is to install a temp box as NT4 BDC to your existing
> PDC, disconnect the BDC from the domain and remove the PDC from its copy
> of the domain, making the temp box PDC of the 'held' domain. The temp box
> is then upgraded to win2K or later, creating an AD based on the pre2k
> domain. SBS is then introduced as a DC in the AD, the FSMO roles are moved
> to it, as well as GC and licensing roles.
>
> Your existing domain continues to operate all this time. When you are
> ready to put SBS in place, you copy the data across to it, shutdown all
> PC's, put SBS in place, everyone signs on as if nothing has happened.
>
> "sbs2003user" <sbs2002user@xxxxxxxxxx> wrote in message
> news:hvkne.25497$Ub.2036@xxxxxxxxxxx
>> Is there a simple way to preserve local user settings on Windows XP Pro
>> client machines that are currently connected to a NT4 server before
>> having the workstation join the SBS2003 domain? I am not using roaming
>> profiles but rather just have a single user account with 'restricted'
>> local access on each of the workstations. I have been planning on just
>> copying the users local 'my documents' files along with things found on
>> their desktops and in their favorites folder. I realize that this does
>> not capture everything (such as their Outlook profile let alone any
>> Outlook rules they may have) but since I only have about 25 workstations
>> I don't want to invest more time in learning an automated way of doing
>> this than it would take for me to do it manually. Thank you for any
>> insight that you may offer.
>>
>
>


.



Relevant Pages

  • Re: Migrating XP Pro Clients from NT4 Server to SBS2003 Server
    ... > PDC, disconnect the BDC from the domain and remove the PDC from its copy ... making the temp box PDC of the 'held' domain. ... SBS is then introduced as a DC in the AD, ... >> local access on each of the workstations. ...
    (microsoft.public.windows.server.sbs)
  • Re: Migrating XP Pro Clients from NT4 Server to SBS2003 Server
    ... The basic process is to install a temp box as NT4 BDC to your existing PDC, ... to put SBS in place, you copy the data across to it, shutdown all PC's, put ... > everything (such as their Outlook profile let alone any Outlook rules they ... > may have) but since I only have about 25 workstations I don't want to ...
    (microsoft.public.windows.server.sbs)
  • Re: Logging in takes 20 minutes on SBS
    ... User profile cleanup service does not delete workstation profiles. ... ipconfig/all from server and a few workstations to ... files and delete temp IE files. ... Check your SBS with the SBS Best Practices Analyzer ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)
  • Re: status of mas90 client
    ... Gregg Hill wrote: ... The Dell PE 2800 server ... The workstations are slow to open applications, slow to save files to the ... SBS BPA gives a clean report. ...
    (microsoft.public.windows.server.sbs)