Posts

Showing posts from June, 2020

Windows Deployment Methods

Computers in the enterprise world require being up-to-date. This means IT teams need to be able to have a solid OS deployment plan for all the employees. With so many scenarios, it’s important that the plan be flexible as well as functional. Luckily, Microsoft offers many options of deployment to help cater for the wide range of scenarios. This post will briefly discuss the comparison between some of traditional deployment methods: WDS, MDT, SCCM. WDS Windows Deployment Services is a feature installed on Windows Server OS that gives the capability to push a Windows OS image to a computer. It’s a good foundation to have set up to start your deployment methods. This option has the quickest initial setup to get up and running but does require more manual configuration when it comes to building the OS image to your liking. MDT Microsoft Deployment Toolkit takes WDS take it to one big step further from WDS. It actually requires WDS to work but implements Lite Touch Installation. This would

What are the importance of Layer 3 and Layer 2 networks

For network engineers and architects, understanding the difference between a Layer 3 and Layer 2 network can greatly enhance the overall security and speed of your network infrastructure. Generally speaking, Layer 2 is a broadcast Media Access Control (MAC) MAC level network, while Layer 3 is a segmented routing over internet protocol (IP) network. To better understand both layers, let’s dig a little deeper into the OSI model. Understanding the OSI 7 layer model OSI stands for Open Systems Interconnection. It is a model used to standardise the functions of telecommunication and computing systems around the world. OSI 7 is conceptual, as the layers are abstractions that don’t define the actual technology used; however, the network topology and interoperability can be designed. But what does that actually mean? In Information Technology, standardisation is abstract so that providers, manufacturers, programmers and everyone involved has a model to work with that provides a uniform level

Bridging Network Connections

There are several ways to hook up individual computers into a network. One is to use hardware routers to link up the network segments. If you buy hardware bridges, those will also connect the computers with each other. In Windows XP, simply clicking the "Bridge Connections" icon joins parts of a network together, even if the parts use different media to link their segments. Advantages Using a router or a hardware bridge requires buying more equipment to connect your computers. With a wireless router, each computer and network segment needs its own Internet Protocol (IP) address in order to direct data to the right computer. Both methods may require an IT professional or experienced amateur to connect everything properly. With Windows XP, building a bridging connection requires just a few clicks of your mouse in the right places. Bridging To make a bridge, you must log in as an administrator on your network or your computer. Click the computer's "Control Panel,"

Windows Deployment Methods

Computers in the enterprise world require being up-to-date. This means IT teams need to be able to have a solid OS deployment plan for all the employees. With so many scenarios, it’s important that the plan be flexible as well as functional. Luckily, Microsoft offers many options of deployment to help cater for the wide range of scenarios. This post will briefly discuss the comparison between some of traditional deployment methods: WDS, MDT, SCCM. WDS Windows Deployment Services is a feature installed on Windows Server OS that gives the capability to push a Windows OS image to a computer. It’s a good foundation to have set up to start your deployment methods. This option has the quickest initial setup to get up and running but does require more manual configuration when it comes to building the OS image to your liking. MDT Microsoft Deployment Toolkit takes WDS take it to one big step further from WDS. It actually requires WDS to work but implements Lite Touch Installation. This would

Windows Deployment Methods ?

Computers in the enterprise world require being up-to-date. This means IT teams need to be able to have a solid OS deployment plan for all the employees. With so many scenarios, it’s important that the plan be flexible as well as functional. Luckily, Microsoft offers many options of deployment to help cater for the wide range of scenarios. This post will briefly discuss the comparison between some of traditional deployment methods: WDS, MDT, SCCM. WDS Windows Deployment Services is a feature installed on Windows Server OS that gives the capability to push a Windows OS image to a computer. It’s a good foundation to have set up to start your deployment methods. This option has the quickest initial setup to get up and running but does require more manual configuration when it comes to building the OS image to your liking. MDT Microsoft Deployment Toolkit takes WDS take it to one big step further from WDS. It actually requires WDS to work but implements Lite Touch Installation. This would

Why to Wake on LAN With Ping

To remotely boot a computer on a network, you'll need a "Wake-On-LAN" supported network adapter. Once the adapter is installed, the computer can be "pinged" from another computer on the network to initiate the boot sequence. A ping is a signal sent from one computer to another and can be sent directly from the Command Prompt in Windows. Step 1 Open the "Start" menu on the computer that will be pinged, then type "CMD" into the Search box and press "Enter." Step 2 Type "ipconfig/all" then press "Enter." Make note of the following items: Physical address, IP address and subnet mask. Step 3 Open the Command Prompt on the computer from which you will be sending the wake-on-LAN command. Type "ping" followed by the computer that you will be sending the wake-on-LAN command's IP address. For example, if the IP address is "192.168.1.1," type "ping 192.168.1.1" and press the "Enter&qu