Workgroup to Domain Transition

Can anybody point me to a publication that will assist in transitioning a
workgroup based LAN to a domain using the existing servers, ie. Win 2000 and
2003. The LAN consists of 3 servers, 35 workstation, 8 printers, and uses
Symantec Enterprise VP and Backup Exec 10D. I want to know what pitfalls I
can expect and this is a 24/7 operation, so a lengthy off-hours shutdown
won't be easy.

Thanks

In news:(E-Mail Removed),
SPD <info(at)smithfieldpd.com> typed:
> Can anybody point me to a publication that will assist in
> transitioning a workgroup based LAN to a domain using the existing
> servers, ie. Win 2000 and 2003. The LAN consists of 3 servers, 35
> workstation, 8 printers, and uses Symantec Enterprise VP and Backup
> Exec 10D. I want to know what pitfalls I can expect and this is a
> 24/7 operation, so a lengthy off-hours shutdown won't be easy.
>
> Thanks

I mean no offense, but that's kind of a broad question for a newsgroup post.
We have no way of knowing what your experience and skill levels are, nor
anything very specific about your network, from this post. If you don't have
experience working with AD, etc., it might behoove your company to bring in
some outside help

I have experience with AD but I have never moved a network from a workgroup
to a domain. I am just looking for a publication or guide that may give me a
heads up to unexpected events when making the move. I'm not looking for a
specific answer to a technical question.

Thanks

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) ahoo.com> wrote in message
news:(E-Mail Removed)...
> In news:(E-Mail Removed),
> SPD <info(at)smithfieldpd.com> typed:
>> Can anybody point me to a publication that will assist in
>> transitioning a workgroup based LAN to a domain using the existing
>> servers, ie. Win 2000 and 2003. The LAN consists of 3 servers, 35
>> workstation, 8 printers, and uses Symantec Enterprise VP and Backup
>> Exec 10D. I want to know what pitfalls I can expect and this is a
>> 24/7 operation, so a lengthy off-hours shutdown won't be easy.
>>
>> Thanks
>
> I mean no offense, but that's kind of a broad question for a newsgroup
> post. We have no way of knowing what your experience and skill levels are,
> nor anything very specific about your network, from this post. If you
> don't have experience working with AD, etc., it might behoove your company
> to bring in some outside help
>
>
>

Workgroups are not a "tangeble" thing,...they are more "imaginary" and are
simply the result of having all the machines use the same workgroup
name,..."wala",...instant workgroup, you don't even have to add water.

When all machines are joined to the Domain the workgroup simply ceases to
exist. You can continue to use the Local User Accounts on the workstations
& Servers (but not DCs) as they are but it is not the recommended way.
Recreate the user accounts in the Domain that were used on the local
workstations,...you cannot access resources on the DCs until that is done
because DCs have no local accounts.

Use the File and Settings Transfer Wizard to move the contents of the user's
profiles from the local workstation to the Domian Accounts. When completed
successfully, remove the local workstation accounts and the accompanying
profiles. Only the Local Administrator account should remain on the
workstations.

That is as simple and direct as I can make it, and it is over simplified.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------


"SPD" <info(at)smithfieldpd.com> wrote in message
news:%(E-Mail Removed)...
>I have experience with AD but I have never moved a network from a workgroup
>to a domain. I am just looking for a publication or guide that may give me
>a heads up to unexpected events when making the move. I'm not looking for a
>specific answer to a technical question.
>
> Thanks
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) ahoo.com> wrote in
> message news:(E-Mail Removed)...
>> In news:(E-Mail Removed),
>> SPD <info(at)smithfieldpd.com> typed:
>>> Can anybody point me to a publication that will assist in
>>> transitioning a workgroup based LAN to a domain using the existing
>>> servers, ie. Win 2000 and 2003. The LAN consists of 3 servers, 35
>>> workstation, 8 printers, and uses Symantec Enterprise VP and Backup
>>> Exec 10D. I want to know what pitfalls I can expect and this is a
>>> 24/7 operation, so a lengthy off-hours shutdown won't be easy.
>>>
>>> Thanks
>>
>> I mean no offense, but that's kind of a broad question for a newsgroup
>> post. We have no way of knowing what your experience and skill levels
>> are, nor anything very specific about your network, from this post. If
>> you don't have experience working with AD, etc., it might behoove your
>> company to bring in some outside help
>>
>>
>>
>
>

Thanks for your over simplification but I would have appreciated it more if
you had just answered my original question. You may want to consider that
when communicating with future posters...but thanks again anway.


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> Workgroups are not a "tangeble" thing,...they are more "imaginary" and are
> simply the result of having all the machines use the same workgroup
> name,..."wala",...instant workgroup, you don't even have to add water.
>
> When all machines are joined to the Domain the workgroup simply ceases to
> exist. You can continue to use the Local User Accounts on the
> workstations & Servers (but not DCs) as they are but it is not the
> recommended way. Recreate the user accounts in the Domain that were used
> on the local workstations,...you cannot access resources on the DCs until
> that is done because DCs have no local accounts.
>
> Use the File and Settings Transfer Wizard to move the contents of the
> user's profiles from the local workstation to the Domian Accounts. When
> completed successfully, remove the local workstation accounts and the
> accompanying profiles. Only the Local Administrator account should remain
> on the workstations.
>
> That is as simple and direct as I can make it, and it is over simplified.
>
> --
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
> The views expressed are my own (as annoying as they are), and not those of
> my employer or anyone else associated with me.
> -----------------------------------------------------
>
>
> "SPD" <info(at)smithfieldpd.com> wrote in message
> news:%(E-Mail Removed)...
>>I have experience with AD but I have never moved a network from a
>>workgroup to a domain. I am just looking for a publication or guide that
>>may give me a heads up to unexpected events when making the move. I'm not
>>looking for a specific answer to a technical question.
>>
>> Thanks
>>
>> "Lanwench [MVP - Exchange]"
>> <(E-Mail Removed) ahoo.com> wrote in
>> message news:(E-Mail Removed)...
>>> In news:(E-Mail Removed),
>>> SPD <info(at)smithfieldpd.com> typed:
>>>> Can anybody point me to a publication that will assist in
>>>> transitioning a workgroup based LAN to a domain using the existing
>>>> servers, ie. Win 2000 and 2003. The LAN consists of 3 servers, 35
>>>> workstation, 8 printers, and uses Symantec Enterprise VP and Backup
>>>> Exec 10D. I want to know what pitfalls I can expect and this is a
>>>> 24/7 operation, so a lengthy off-hours shutdown won't be easy.
>>>>
>>>> Thanks
>>>
>>> I mean no offense, but that's kind of a broad question for a newsgroup
>>> post. We have no way of knowing what your experience and skill levels
>>> are, nor anything very specific about your network, from this post. If
>>> you don't have experience working with AD, etc., it might behoove your
>>> company to bring in some outside help
>>>
>>>
>>>
>>
>>
>
>

In news:%(E-Mail Removed),
SPD <info(at)smithfieldpd.com> typed:
> Thanks for your over simplification but I would have appreciated it
> more if you had just answered my original question. You may want to
> consider that when communicating with future posters...but thanks
> again anway.

There is no link or document that I can think of that would address your
question; as I said, it's quite broad. I think Phil's reply is well written.
There is really no such thing as a workgroup in the real sense. Just think
of it as a lot of standalone machines; that's what they are. Move all data
to your server(s), join the workstations to the domain, and migrate profiles
if you wish. I think that's pretty much all anyone in here will be able to
tell you.

These newsgroups are for specific technical questions & issues, and you
haven't really asked one. If you do have experience with AD, as you've said,
I'm not sure why you're asking this.




>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
>> Workgroups are not a "tangeble" thing,...they are more "imaginary"
>> and are simply the result of having all the machines use the same
>> workgroup name,..."wala",...instant workgroup, you don't even have
>> to add water. When all machines are joined to the Domain the workgroup
>> simply
>> ceases to exist. You can continue to use the Local User Accounts on
>> the workstations & Servers (but not DCs) as they are but it is not
>> the recommended way. Recreate the user accounts in the Domain that
>> were used on the local workstations,...you cannot access resources
>> on the DCs until that is done because DCs have no local accounts.
>>
>> Use the File and Settings Transfer Wizard to move the contents of the
>> user's profiles from the local workstation to the Domian Accounts. When
>> completed successfully, remove the local workstation accounts
>> and the accompanying profiles. Only the Local Administrator account
>> should remain on the workstations.
>>
>> That is as simple and direct as I can make it, and it is over
>> simplified. --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>>
>> The views expressed are my own (as annoying as they are), and not
>> those of my employer or anyone else associated with me.
>> -----------------------------------------------------
>>
>>
>> "SPD" <info(at)smithfieldpd.com> wrote in message
>> news:%(E-Mail Removed)...
>>> I have experience with AD but I have never moved a network from a
>>> workgroup to a domain. I am just looking for a publication or guide
>>> that may give me a heads up to unexpected events when making the
>>> move. I'm not looking for a specific answer to a technical question.
>>>
>>> Thanks
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <(E-Mail Removed) ahoo.com> wrote in
>>> message news:(E-Mail Removed)...
>>>> In news:(E-Mail Removed),
>>>> SPD <info(at)smithfieldpd.com> typed:
>>>>> Can anybody point me to a publication that will assist in
>>>>> transitioning a workgroup based LAN to a domain using the existing
>>>>> servers, ie. Win 2000 and 2003. The LAN consists of 3 servers, 35
>>>>> workstation, 8 printers, and uses Symantec Enterprise VP and
>>>>> Backup Exec 10D. I want to know what pitfalls I can expect and
>>>>> this is a 24/7 operation, so a lengthy off-hours shutdown won't
>>>>> be easy. Thanks
>>>>
>>>> I mean no offense, but that's kind of a broad question for a
>>>> newsgroup post. We have no way of knowing what your experience and
>>>> skill levels are, nor anything very specific about your network,
>>>> from this post. If you don't have experience working with AD,
>>>> etc., it might behoove your company to bring in some outside help

There is no simple document for that. So it is not possible for me to give
one.
Had there been one, she probably would have gave you the link and that would
have been it. Her and I have both been doing this for a long time and we
answer the post the way that we answer them for a reason.

Active Directory, in a large enough environemt, is a "career" all by itself.

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

The views expressed are my own (as annoying as they are), and not those of
my employer or anyone else associated with me.
-----------------------------------------------------


"SPD" <info(at)smithfieldpd.com> wrote in message
news:%(E-Mail Removed)...
> Thanks for your over simplification but I would have appreciated it more
> if you had just answered my original question. You may want to consider
> that when communicating with future posters...but thanks again anway.
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
>> Workgroups are not a "tangeble" thing,...they are more "imaginary" and
>> are simply the result of having all the machines use the same workgroup
>> name,..."wala",...instant workgroup, you don't even have to add water.
>>
>> When all machines are joined to the Domain the workgroup simply ceases to
>> exist. You can continue to use the Local User Accounts on the
>> workstations & Servers (but not DCs) as they are but it is not the
>> recommended way. Recreate the user accounts in the Domain that were used
>> on the local workstations,...you cannot access resources on the DCs until
>> that is done because DCs have no local accounts.
>>
>> Use the File and Settings Transfer Wizard to move the contents of the
>> user's profiles from the local workstation to the Domian Accounts. When
>> completed successfully, remove the local workstation accounts and the
>> accompanying profiles. Only the Local Administrator account should
>> remain on the workstations.
>>
>> That is as simple and direct as I can make it, and it is over simplified.
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>>
>> The views expressed are my own (as annoying as they are), and not those
>> of my employer or anyone else associated with me.
>> -----------------------------------------------------
>>
>>
>> "SPD" <info(at)smithfieldpd.com> wrote in message
>> news:%(E-Mail Removed)...
>>>I have experience with AD but I have never moved a network from a
>>>workgroup to a domain. I am just looking for a publication or guide that
>>>may give me a heads up to unexpected events when making the move. I'm not
>>>looking for a specific answer to a technical question.
>>>
>>> Thanks
>>>
>>> "Lanwench [MVP - Exchange]"
>>> <(E-Mail Removed) ahoo.com> wrote in
>>> message news:(E-Mail Removed)...
>>>> In news:(E-Mail Removed),
>>>> SPD <info(at)smithfieldpd.com> typed:
>>>>> Can anybody point me to a publication that will assist in
>>>>> transitioning a workgroup based LAN to a domain using the existing
>>>>> servers, ie. Win 2000 and 2003. The LAN consists of 3 servers, 35
>>>>> workstation, 8 printers, and uses Symantec Enterprise VP and Backup
>>>>> Exec 10D. I want to know what pitfalls I can expect and this is a
>>>>> 24/7 operation, so a lengthy off-hours shutdown won't be easy.
>>>>>
>>>>> Thanks
>>>>
>>>> I mean no offense, but that's kind of a broad question for a newsgroup
>>>> post. We have no way of knowing what your experience and skill levels
>>>> are, nor anything very specific about your network, from this post. If
>>>> you don't have experience working with AD, etc., it might behoove your
>>>> company to bring in some outside help
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>