I use WDS on a Windows Server which is a virtual machine. Does not need to be high spec. Install 2003+ in as a VMware player virtual machine and make it a DC for a domain such as SYSTEMSETUP. It does not need any member PC's just a single server domain with DHCP and WDS on the same server and connect it to a switch.
I think you are confusing who to respond to. I would love to use WDS, but I have no Windows server to do it. So, it would have to be the USB setup. By the way, I just need to leave a "finished method", not the 100 machines imaged.
But I would have to configure a Windows server, dhcp, etc, etc, etc, etc. I never use Windows Server, I only use AIX or Linux. I have no idea. Would LOVE to, but it seems to me it is much more complicated?
I agree with you and frankly there are so many missing pieces of info here that I think he should try your WDS method
It's not more complicated. it's very easy. Take Windows 2012 R2 - even the evaluation version for 180 days will do for now. Add the ADDS role, run the promote to make it a Domain Controller (new domain in new forrest). It will install DNS in the process. Add DHCP and authorise/create scope. Install WDS, add boot image, make capture image. capture image to WIM and it will upload it to WDS for you. Deploy to 100 pc's. Profit.
Threat is giving you very good advice and even my integration methods use virtual machines so its not a simple as it was when I was doing everything in XP. Deploying 2012 is incredibly simple!!! You can honestly get this up and running in no time at all
I would try to, but don't think I have the knowledge. It looks like Windows Server 2003 R2 Standard Edition with SP2 is the smallest one? Or does it has to be enterprise? Also, I assume DC is domain controller? And DHCP can be the same virtual machine? And finally, if it does not needs any connected pc, why would I need it on a switch? I'm asking because this is a BANK setup, and I can not deploy anything without bank authorization.
Yes DC is a domain controller, And yes you install it all on one PC for this setup. The switch is so you can plug the physical PC's you want to deploy this to onto this LAN. I'm suggesting you keep this separate from you main LAN for simplicity. 1 physical PC running VMware player with this server image.
OK, so my question is. Can I usw WDS with USB drives? I can not install anything or touch the network because this is a BANK setup and they won't let me. So, if I can use WDS with USB dirves, great. If not, it is of no use for me.
What do you mean with WDS drive. You can create the virtual PC and store it on a USB drive - although the performance would not be good. I suggest a standalone PC running a VM (containing Windows Server Eval - so no licence issue) connected to a switch of it's own to plug the PC's into. That way your not connecting anything to your corporate LAN. The reason for the virtual PC to contain it instead of directly on a physical PC is just so you can prepare it now at home, and take the deployment server image in on USB and copy it to the standalone PC + switch there.
Kwanbis... not trying to be sarcastic but I am a little speechless at some of the things you are mentioning. Do you work for the bank or do you work for someone that is tech support for the bank? Again no disrespect but may I ask where your located?
What I mean is, if I can use WDS to create USB Drives that would capture and later deploy the images, I'm all for it. I can NOT use the network to send unaouthorized packages, so I can not connect WDS to the machines. It has to be a fisical thing. And I can not connect a switch there because of (stupid) bank policies. So. I can only use USBs or DVDs to do the deployment, independant of the method.
Have to say I'm a little concerned about the fact he has this 'task' to perform with a) no resources and b) no time I'm also surprised with it been a bank it would be allowed to bring in anything from home. Something very lax here and poor management by his boss by the sounds of things.
Problem happens when management have very poor understanding of IT, and they believe they are like gods.
No WDS streams over the LAN but that's why I said use a separate PC with a switch so your creating a standalone deployment LAN with no physical connection to your real LAN so no conflicts with services such as DHCP. That way your not breaking company policy. Use this standalone LAN to install the PC's then physically remove the PC's from this lan and connect them to the real LAN.
Kwanbis try to help us both understand some vital items here... are you saying that you can't take a SEPARATE switch that is NOT connected to your network in anyway and plug the laptops into it?
Besides the complications, I don't have a swtich ready to use. So, I would have to research another way.