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

What is your and the business' time worth?

In my case, if I take more than a couple of hours additional time, compared
to that of a Swing It! process to complete a similar migration _my charges_
to the client are greater than the cost of the kit.

But say I'm doing it for my own company, and that company has 25
workstations I need to touch (which Swing It! mostly avoids). The lost
productivity of the company due to the additional time taken far outweighs
the cost of the kit.

I performed a similar style migration moving from SBS2000 to SBS2003 on my
LoungeAN (did it 'off the top of m'head' in fact, or maybe 'by the seat of
m'pants' would be a more accurate term :-). Though I obviously have most of
the knowledge to perform such a thing I spent many hours finding the
relevent KB articles (documented in the kit) to address items I either
missed or was not prepared for/aware of.

It's probable that I will move my LoungeAN SBS from the current box into
Virtual Server by year's end. Though I can use a process similar to 'moving
the server to new hardware' to do so there are differences in how I will
want data distributed. I believe I'll use the Swing It! kit to accomplish
the task.

What you wish to do is complex. The Swing It! kit documents the process in
logical manner and also contains time saving tools, and Jeff's support. It
reduces the need to understand the complexity of the situation and therefore
_will save you time_.

There is no reason for any user data or setup to be lost.

Skipping versions has not increased the complexity much. NT4 to SBS 4.5, I
never tried it but I don't think a similar procedure is possible. NT4 to
SBS2000, same complexity level, maybe a little harder.

"sbs2003user" <sbs2002user@xxxxxxxxxx> wrote in message
news:wOFne.18067$Ib.1876@xxxxxxxxxxx
> 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
    ... > _my charges_ to the client are greater than the cost of the kit. ... > workstations I need to touch (which Swing It! ... > Skipping versions has not increased the complexity much. ... NT4 to SBS 4.5, I ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrade from NT4
    ... Frank McCallister SBS MVP ... I'm pretty sure Jeff would also promote the NT4 tempDC 'offline', ... Does Exchange server exist in the NT domain? ...
    (microsoft.public.windows.server.sbs)
  • Re: Impact upon adding SBS 2000 to existing network to access internet
    ... existing NT4 domain is ACS connected to the DSL Modem ... I will download and burn to a CD SBS SP1a. ... accessing the internet ... >> configuration and testing. ...
    (microsoft.public.backoffice.smallbiz)
  • RE: 2003 SBS sevrer cannot trust another domain !!!!
    ... You can not bring the old NT4 server from the old domain into the new SBS ... Windows NT4 into SBS 2003 as a member server. ...
    (microsoft.public.windows.server.migration)
  • RE: Migrating NT4 Exchange 5.5 to SBS 2003
    ... Welcome to SBS newsgroup. ... I understand that you want to migrate from NT4 to SBS 2003, ... For migration the PST files, it is your best interest to exmerge, to do it, ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
Loading