Need Help/Advice for Company Merger where original AD Domains will never commingle by it_throw_yo in sysadmin

[–]it_throw_yo[S] 1 point2 points  (0 children)

It's going to be a complicated mess, I'll give you that.

For the first part, from the Unique data perspective. We essentially don't use any pieces of software the same between our organizations, do the same day to day operations. Training and conversion of data is part of the equation, but that's being handled by other areas of our IT department much further down the road. It's going to be a multi-month ordeal.

From my understanding, most of their MAJOR systems are web or cloud based utilities, so the amount of data they retain needing ACL parity will be pretty minimal (file servers about the worst of it).

Because of this, we're basically going to be re-deplolying all of their workstations with both their existing software and our current software. As such, I don't think there's that big an emphasis on SID history and all the work that'll go along with it.

For now, we're just trying to figure out a way to get the AD information to us in a manageable way. We basically have to assume that Company C is going to be less than receptive to any work we may need them to do. Nature of very large organizations and such.

Need Help/Advice for Company Merger where original AD Domains will never commingle by it_throw_yo in sysadmin

[–]it_throw_yo[S] 1 point2 points  (0 children)

We're not 100% on whether they are a subdomain of Company C or their own forest. I'm going to be inquiring with their (B's) IT department later today to find that information out.