How to create a network to use Microsoft WDS

[Dead Cell]

Hi All

I work in IT for a lawfirm and trying to get in to third line support (currently in 1st line).

My manager told me to use three machines at work to set up a network (not connected to our main network or the internet), one machine is to be installed with Windows Server 2008 and then on top of that install Microsoft WDS. The other two machines will just be dead PC's connected to this network.

The idea is this: I will upload the source files of an XP CD with service pack 3 to WDS, create a bootable image, and then create a batch file which will enable to installation to run unattended.

I will then turn on the other two machines and hit F12 and hopefully be able to install XP with Service Pack 3 to these two machines over the network from the server.

Do it all the time at work but have never been involved in putting the image together on the server, we just hit F12 on the machine that needs building, enter the credentials and then select the correct options etc and away we go.

I have a few questions for you guys.

1. MUST I have 3 machines for this or will only two machines be enough? I can't see why not as one will be the server and I will then only need one more to test to see how it builds right?
2. I have a Virgin Media Router at home which also has a built in modem. Can I disconnect the router from the Internet and just use it to connect the server and the two machines together? Or do I need a switch?

I'm a bit confused as my manager asked me to use a switch but from what I understand and correct me if I'm wrong, a router is more intelligent therefore I imagine it can do everything that a switch can do and more so it should work fine?

If my home router will work then I can just do this at home with two laptops and my desktop PC acting as the server.

Would love to hear from you guys and thanks in advance for any help you can provide.

 

[Pck21]

I have a few questions for you guys.

1. MUST I have 3 machines for this or will only two machines be enough? I can't see why not as one will be the server and I will then only need one more to test to see how it builds right?
2. I have a Virgin Media Router at home which also has a built in modem. Can I disconnect the router from the Internet and just use it to connect the server and the two machines together? Or do I need a switch?

I'm a bit confused as my manager asked me to use a switch but from what I understand and correct me if I'm wrong, a router is more intelligent therefore I imagine it can do everything that a switch can do and more so it should work fine?

If my home router will work then I can just do this at home with two laptops and my desktop PC acting as the server.

Would love to hear from you guys and thanks in advance for any help you can provide.

Hey Dead Cell!

1.) The two computers should suffice for testing, but the more tests that can be run, the better.

2.) It depends on the router you're trying to use. The home router that we all use for personal use is much different than commercial routers and switches out in the field. Most home wireless routers are a combination of a router and a switch. I kind of think of them as a layer 3 switch rather than both to be honest. If you have a wireless router with 5 fast ethernet ports (at least 3 open for your task) then it can work.

Your boss asked you to connect them via a switch because that's how end devices (desktop computers for example) connect to a network. Routers are more intelligent, sure, but that's because they perform a different function from switches in the network environment. Routers are typically used to break up domains and route packets/frames to the correct network. A switch sits on the inside of that router's network and waits for the router to send the packet to it. The switch will then make the decision to deliver the packet to the correct destination (usually by MAC address).

In your case, you don't need routing because you're creating a small LAN with 3 computers on the same network. Well, I guess you could throw a router in there, but it would be unnecessary and overkill lol! So, you will need to get a working switch somewhere, and plug all 3 computers into it. The switch should do the rest.

 

[Dead Cell]

PCK21 thanks very much for helping me out. I went out today and bought an 8 Port Netgear Switch. Now I need help with WDS!

I need to know how I can do this as I'm in a bit of panic right now.

So I have two machines for the time being, and I have already installed Windows Server 2008 R2 on my main machine and it installed fine.

But I don't think it will work. My manager said all I need is a switch and a few PC's but according to the notes below from Mircrosoft I need to install both the Deployment Server and the Transport Server. The problem there is, in order to install both I need to be a member of an AD DS domain or a domain controller for an AD DS domain (please see the notes below from Microsoft). Also I will need a working DHCP server and a DNS Server!

Does that mean I will now need:
1. A machine with Server 2008 running as an AD DS domain.
2. A machine with Server 2008 running as a DHCP Server
3. A machine with Server 2008 installed as a DNS Server
4. A machine with Server 2008 installed with WDS with Deployment and Transport server components installed
5. A client machine to actually install the image via PXE

If so then that means I will also need to throw in a router as well?

This is very interesting and I'm loving it but at the same time I'm scared of not getting it done!


These are the two options; Deployment Server and Transport Server.

The differences between the two are:

Deployment Server
• AD DS. A Windows Deployment Services server must be either a member of an AD DS domain or a domain controller for an AD DS domain. The AD DS domain and forest versions are irrelevant; all domain and forest configurations support Windows Deployment Services.
• DHCP. You must have a working DHCP server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing.
• DNS. You must have a working DNS server on the network before you can run Windows Deployment Services.
• NTFS volume. The server running Windows Deployment Services requires an NTFS file system volume for the image store.
• Credentials. To install the role, you must be a member of the Local Administrators group on the server. To initialize the server, you must be a member of the Domain Users group. For more information about this, see the Required Permissions [role] topic.

• Deployment Server. To install this option, ensure that both Deployment Server and Transport Server are selected on the second installation wizard screen. This option provides the full functionality of Windows Deployment Services, which you can use to configure and remotely install Windows operating systems. With Windows Deployment Services, you can create and customize images and then use them to reimage computers. Note that Deployment Server is dependent on the core parts of Transport Server


Transport Server
Credentials. To install the role service, you must be a member of the Local Administrators group on the server

• Transport Server. To install this option, clear the Deployment Server check box on the second installation wizard screen. This option provides a subset of the functionality of Windows Deployment Services. It contains only the core networking parts. You can use Transport Server to create multicast namespaces that transmit data (including operating system images) from a standalone server. You should use this option if you want to transmit data by using multicasting, but you do not want to incorporate all of Windows Deployment Services. For more information, see Transport Server.