Need an Opinion!

  • Thread starter Thread starter Paul
  • Start date Start date
P

Paul

Hey all,

I have a question that requires an opinion.

I am working on designing a new strategy for my company's
windows network.

Currently we have one domain (abc.company.com) and no
child.

I am toying with the idea of pitching that we create a new
root level domain and a child domain. The root domain
would be called company.com and the child would be
corp.company.com

Now my question is, can I create a brand new domain called
company.com even though there is a abc.company.com
(company.com would be the same for both) without causing
any conflicts?

Next.. the company runs 192.168.xxx private IP address for
all offices.. I am thinking of perhaps changing the
corporate office to a 10.x.x.x network and leave the
remote offices as 192.168.xxx networks? Does anyone think
this is a wise idea, or should I just leave it as it is?

Lastly.. If I were to change domain names to company.com
would it also be wise to use Windows 2003? Has anyone had
any problems that they regret as a result of it?

Thanks!

Paul
 
You can have abc.company.com and corp.company.com and company.com as domains. The problem came if company.com is
registered in Internet by others or you may want for security to go to company.internal inside.

Domain splitting may create additional hassle for object moving, delegation and administration; think twice and do your
own research before and put all advantages and disadvantages. You may choose to create OUs.

Chris



Hey all,

I have a question that requires an opinion.

I am working on designing a new strategy for my company's
windows network.

Currently we have one domain (abc.company.com) and no
child.

I am toying with the idea of pitching that we create a new
root level domain and a child domain. The root domain
would be called company.com and the child would be
corp.company.com



Now my question is, can I create a brand new domain called
company.com even though there is a abc.company.com
(company.com would be the same for both) without causing
any conflicts?

Next.. the company runs 192.168.xxx private IP address for
all offices.. I am thinking of perhaps changing the
corporate office to a 10.x.x.x network and leave the
remote offices as 192.168.xxx networks? Does anyone think
this is a wise idea, or should I just leave it as it is?

Lastly.. If I were to change domain names to company.com
would it also be wise to use Windows 2003? Has anyone had
any problems that they regret as a result of it?

Thanks!

Paul
 
Back
Top