After cabling, what's next?

[trymeran]

Hey guys!

First of all, thanks to those who have the answer and shared it. I'm a hardware freaking maniac inventor that loves robots and all that stuff. But, networking is something I'm starting up now. I was asking after the cabling in a office (a network like 10 users or less with 2 servers) what's next? I mean after ending all cables at the patch panel and pairing them with the switch. And the switch connected with the router also, how the IP addresses will be distributed? Is something that is automatically or do I have to set static IP's with all pc's? I think I need a network consultant for this LOL! This is what is on the rack: 2 servers with Win Servr 2012 R2, 1 patch panel EZ Plug, 1 router from Cisco.

Any answers will be appreciated!

 

[kanewolf]

For something like you describe, the PCs would typically be part of a windows domain handled by the Server 2012. That would usually be the DHCP and DNS server also -- but not required. You could allocate the DHCP/DNS duties to the router. You can accomplish the equivalent of static IP addresses, by tying MAC addresses to IP addresses (reserving IP addresses is the usual terminology) in the DHCP server. That way the clients can stay DHCP, but they will always have the same IP. There are many ways to implement.
One reason to have a Windows Domain is the ability to manage group policies across all the devices. It also provides centralized user management, the ability to throttle patch updates, etc.

 

[trymeran]

Thanks for the answer, partner!

So, the server does everything? Do I have to configure something? I don't think that is just plug all the cables to the switch and let's go or am I 1 step behind from the new products on the market? That's where I'm kinda confused...

 

[bill001g]

Sounds like you are going to need to hire some help. Since it appears someone spent quite a bit of money to get actual windows server licenses you really need to use these devices. Although the basics of running a domain server are not real tough there are so many options that there are people who make their entire career just keeping this type of server running.
You can of course just use a router to give out the IP but that really is only a small part of a business network. The hard part is controlling users access to the network. This is not something that just appears by itself you have to configure all this stuff.
Someone is going to have to take long term responsibility for this. You always have users that forget their password or employees that leave the company etc. You are going to have to either spend a number of weeks/months to learn about these servers or you are going to have to pay a outside company to do this for you.

Look at the microsoft certifications if nothing else just for a list of things you need to learn. With a small network you really could just learn the parts you really need. If you are going to hire someone I would only accept people who actually had a number of these certifications. These certifications are actually fairly easy for someone who actually specializes in microsoft server implementation so anyone who is trying to sell you their skills in this area who does not have these certifications you have to be suspect if they really know what they claim to.