Yep, you're totally confused.
We are using the same domain name. We used to share the same domain
with our parent, we had DC's and they had DC's in the "blah.corp"
domain, all of our users, servers, workstations were in the
"blah.corp" domain. For whatever reason, all of the FSMO role
holding DC's were at on our parent's DC's. They also had some other
domains that we were not part of that had trusts to our "shared"
domain, other children if you will.
So when we were kind of abruptly sold, we disconnected the WAN and
seized the roles onto our DC's since we still had to function in the
"blah.corp" domain. As mentioned before, I cannot find the "orpaned"
domains that appear in our Log On To box in WINS or AD Domains &
Trusts.
On Jul 12, 11:26 am, "SBS Rocker" <nore...@NoDomain.com> wrote:
> Well I'm totally confused. If you're not going to use the same domain then
> what was the purpose of seizing the FSMO roles from that domain and what
> good is it going to do you? Also you do realize now that the domain that the
> DC you removed no longer has a DC that has the FSMO roles.
>
> <doug.mast...@gmail.com> wrote in message
>
> news:1184190756.355438.285630@o61g2000hsh.googlegroups.com...
>
> > No, since our former owners will be still be using that domain and
> > it's trusts.
>
> > On Jul 11, 2:52 pm, "SBS Rocker" <nore...@NoDomain.com> wrote:
> >> Well given the fact that you did seize the FSMO roles then I assume you
> >> plan
> >> on keeping the same domain and forest. You still should of broken the
> >> trust
> >> relationships from the other domains while still connected.
>
> >> <doug.mast...@gmail.com> wrote in message
>
> >>news:1184181870.359697.246160@r34g2000hsd.googlegroups.com...
>
> >> >I had to seize the roles since the DC's holding the roles were not
> >> > mine. None of the servers in the "orphaned" domains have ever
> >> > existed on my LAN. What I did fail to mention is that I have
> >> > "cleaned" the parent company's DC's from AD via the method described
> >> > in KB 216498 since I no longer have connectivity to them. In
> >> > ADSIEdit under Domain NC - DC=xxx - CN=System the domains in question
> >> > are NOT listed as "trustedDomain" nor do they exist in ADD&T
>
> >> > On Jul 11, 11:32 am, "SBS Rocker" <nore...@NoDomain.com> wrote:
> >> >> Well according to what you just posted all you did wa "disconnected"
> >> >> your
> >> >> self from the WAN. you never removed the servers from the domain so
> >> >> that
> >> >> domain as well as all the other trusted domains will still be an
> >> >> option
> >> >> in
> >> >> the login domain drop down window. I'm curious if you disconnected
> >> >> from
> >> >> the
> >> >> WAN why did you need to seize the FSMO roles?
>
> >> >> <doug.mast...@gmail.com> wrote in message
>
> >> >>news:1184169162.189290.73260@d55g2000hsg.googlegroups.com...
>
> >> >> > Last Friday, my company disconnected our WAN from our former owner.
> >> >> > We both shared the same domain, we seized all FSMO roles to your
> >> >> > DC's
> >> >> > after being disconnected. That seemed to go well, the event logs on
> >> >> > my DC's are pretty clean and no users are reporting any problems.
>
> >> >> > The former owner had several other domains that would show up in the
> >> >> > Log On To drop down box. We never logged into those, but since
> >> >> > we're
> >> >> > disconnected I would like to remove those and only offer the valid
> >> >> > domains. My only thought on what to check was the Domains &
> >> >> > Trusts,
> >> >> > those domains do not exist there.
>
> >> >> > Thanks in advance for pointing me in the direction I need to go.-
> >> >> > Hide quoted text -
>
> >> - Show quoted text -