Last edited by ahelton; 25 Jul 2016 at 17:10.
I don't want to interrupt your conversation too much, but I will add a thought.
If you want to practise deployment, then instead of a physical machine, you could use a Virtual Machine. I use VirtualBox but Hyper-V is probably better if you have the right 'host' version of Windows. It won't activate, and is a bit slower than using physical hardware, but for test purposes it might be easier to have everything on one machine. Plus if you totally kill a virtual machine you can just delete the file and start again!
I am already over halfway through this process and thus far everything is going smoothly, fortunately. But I'd definitely like to mess around/practice with things even after I have this done, so think I will implement the virtual machine idea per your suggestion. I've never used VMs before; only have read about them, but have been wanting to give them a go for a while now. This sounds like the perfect opportunity to check VMs out. Thanks again.
You can always modify (or 'update') your image by installing new software, updates, etc... on the reference machine then capture that new image and deploy it (the new image could be deployed on select machines). You might want to re-image all the machines maybe once every 1- 3 years or so if you want to- just to give the machines a refresher, make sure everything is up to date, and possibly give all computers a change to be at the same place/ remove crap files that may have accumulated. Whether or not this is ideal is going to depend on what you want to do and your setup.
>>I don't exactly understand how my quote relates to your question so I might not have answered your question entirely...
>>I would recommend Virtualbox or VMware player (free for noncommercial- if you want to play around on your own time)- it's good for VM's and is easier for a starter to understand than Hyper-V.
I must admit I didn't read the whole thread so apologies if you said that already.
The bit that's tricky in VirtualBox is getting the VM to access a 'real' USB plugged into the host machine- Hyper-V may be better, but I usually get round it by creating virtual disks on a USB.
They have been updated in the last week, although I haven't figured out how to get the latest ADK which is required for some of it to work - may need to wait a week or two for that to be released publicly.
Basically, I was just thinking in hypothetical terms. Let's say you have 10 computers in need of imaging. 7 of those computers are going to be for mere peons and thus need to have certain settings and configuration, while the other 3 are for more advance users. The mere peons only need some basic software installation, while the more advanced users require some more robust tools. Could you therefore first create and capture a reference image for the peons, and then edit the reference computer some more and "re-capture" and image that will be used to deploy to the more advanced user computers? Could the initial "mere peon" image be given the parameter /index:1 and the "advanced user" image be given /index:2?
Does that make sense?
I have SublimeText3, so I figure I can just use that to accomplish editing the startnet.cmd file, correct?