Re: Swing migration tool question



Gee,

You'd think I would have thought of that, but NOOOOO!!! I will email him with the question...thanks for the suggestion!

Gregg Hill



"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:OH2HWgVoGHA.4404@xxxxxxxxxxxxxxxxxxxxxxx
just curious
Have you contacted Jeff?

--
Cris Hanna [SBS-MVP]
--------------------------------------
Please do not respond directly to me, but only post in the newsgroup so all can take advantage
"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message news:ubcn2TMoGHA.4192@xxxxxxxxxxxxxxxxxxxxxxx
I posted a related question in the microsoft.public.windows.server.general
newsgroup, but since this group is more familiar with Jeff's swing tools, I
thought I would ask the next question here.

*****Question to microsoft.public.windows.server.general newsgroup*****
Background:
I inherited a single-server Windows 2000 domain that has two workstations on
the domain and three that are in a workgroup with the same name as the
domain. The DC has a bizarre long name, and I would like to rename it, but
since it is the only DC and the only server, the only way to do so would be
to dcpromo it to a stand-alone server. My question is: what happens to the
domain accounts (about ten accounts for the five workstations) if I do a
dcpromo out of the domain? Do they get converted to local accounts on the
server, or do they just get deleted?

If the domain accounts become regular local accounts on the server after
dcpromo down to a stand-alone, I assume I could then rename the server to
something logical, then dcpromo back to a domain, add the three workstations
that were in a workgroup, take the two previous domain members and change to
workgroup then place them into the new domain.

Am I any where near correct on what happens to the accounts after dcpromo?

*****Answer in that newsgroup*****
1. Do the DCPROMO, change the server name, recreate the "new" domain and the
user accounts/groups. Specific group/user file permissions will also have
to be recreated.

2. Build a temporary server, run dcpromo to make it another DC in the
domain, move the fsmo roles over, and he will retain your AD environment
while you DCPROMO the original DC back to member server
status to be renamed. You can then DCPROMO it back to domain controller
status, and DCPROMO the temp server back out of the domain after moving the
fsmo roles back.

*******************************

Now for the swing tool question. If I do method two and add a temp DC, then
rename the current DC, and dcpromo it back into the domain, can I use the
ShareMig tool to re-create the shares and permissions on the DC?

Gregg Hill



Relevant Pages

  • Swing migration tool question
    ... newsgroup, but since this group is more familiar with Jeff's swing tools, I ... to dcpromo it to a stand-alone server. ... domain accounts if I do a ...
    (microsoft.public.windows.server.sbs)
  • Re: Hello all...
    ... - demote the DC that you want/need to rename ... - remove the server from the domain ... >dominion and want to do it without despromover the dominion and returning it ... >>>like changing the name of a domain controller in windows2003 without dcpromo ...
    (microsoft.public.windows.server.scripting)
  • Wht happens to domain accounts after dcpromo to stand-alone server?
    ... to dcpromo it to a stand-alone server. ... domain accounts if I do a ... that were in a workgroup, take the two previous domain members and change to ...
    (microsoft.public.windows.server.general)
  • Re: Wht happens to domain accounts after dcpromo to stand-alone server?
    ... I was afraid of the accounts going away. ... Probably a lot easier than recreating ... Build a temporary server, run dcpromo to make it another DC in the ...
    (microsoft.public.windows.server.general)
  • Re: W2k < W2k3 replacement
    ... I hadn't seen these documents or the rename tool. ... replace a server in a SINGLE AD server environment. ... Install Windows 2003 with a temporary name ... Does dcpromo do these things for me? ...
    (microsoft.public.windows.server.migration)

Loading