Options for deploying standardized image to desktop & laptops?
-
@MattSpeller @DustinB3403 Thanks guys. It sounds like FOG is gonna be the next route to look into. I'm already getting a VM setup for the "server" and am gonna keep digging into their wiki.
-
@DustinB3403 said in Options for deploying standardized image to desktop & laptops?:
@MattSpeller the Fog team has really gone out of their way recently to make it much easier to get setup and going.
I should probably take another look at it, as I haven't for at least a couple of years.
-
@travisdh1 said in Options for deploying standardized image to desktop & laptops?:
@DustinB3403 said in Options for deploying standardized image to desktop & laptops?:
@MattSpeller the Fog team has really gone out of their way recently to make it much easier to get setup and going.
I should probably take another look at it, as I haven't for at least a couple of years.
Ditto
-
I like this, lol: (https://wiki.fogproject.org/wiki/index.php?title=New_Home_Page#Hardware)
Requirements
Hardware
FOG is best implemented on a dedicated server, any spare machine you have. We recommend that you have sufficient hard drive space as each image you make is usually between 5 and 10 GB and it's best to have a gigabit NIC with as much processor and RAM you can throw at it.Wow, that's SO helpful of them to tell me exactly how much CPU, RAM and HD resources to throw at my server, lol!
-
@Shuey Honestly the only thing you really need for a FOG server is a gigabit nic and about 50-100GB of disk space on an array that can put out 100MB/s. RAM/CPU requirements are hilariously low.
-
@Shuey said in Options for deploying standardized image to desktop & laptops?:
I like this, lol: (https://wiki.fogproject.org/wiki/index.php?title=New_Home_Page#Hardware)
Requirements
Hardware
FOG is best implemented on a dedicated server, any spare machine you have. We recommend that you have sufficient hard drive space as each image you make is usually between 5 and 10 GB and it's best to have a gigabit NIC with as much processor and RAM you can throw at it.Wow, that's SO helpful of them to tell me exactly how much CPU, RAM and HD resources to throw at my server, lol!
You can disregard the dedicated hardware, I ran this at my last place as a VM on XenServer 6.5. I did have a dedicated NIC for a separate DHCP server that was running within the VM though.
This way I only had a single cable coming out of this NIC to my office, that had a 8 port switch so I could PXE boot, and image up to 7 computers at once.
I was getting NL-Gbe performance while deploying an image to my hardware.
-
@DustinB3403 Can confirm, my last FOG server was dedicated but with a pentium 4, 2gb ram and 8x 320gb drives in raid10
If you have a modern server, just use a VM. We have a lot of old crap laying around and electricity here is dirt cheap.
-
Uploading was approximately ~600 mbps of an image.
Which the image was hosted on the same hypervisor.
To update the golden image, I would shutdown the golden-VM, switch the NIC to "internet" NIC, update any programs or windows updates, sysprep & generalize the OS and shutdown the golden-VM.
I'd then connect to my fog instance (via XO), open the console and create an upload task for my "golden-VM".
Then go back to the golden-VM, swap the NIC, PXE boot to my fog network and the upload would proceed.
Once completed, I'd test the image process by grabbing a different laptop.
-
The whole imaging process from blank hard disk to Windows 7/10 was under 10 minutes. From there, join the system to the domain, and be on my way.
-
FOG ended up being just the ticket! It was easy to deploy, easy to configure, and I already had a base VM ready to go for image capture. Capturing and deploying the image was a breeze and took about 60 minutes total (not bad at all for the size of the base image and the speed of our infrastructure).
Thanks for taking me into giving it a try - it was well worth the time!
-
@Shuey said in Options for deploying standardized image to desktop & laptops?:
FOG ended up being just the ticket! It was easy to deploy, easy to configure, and I already had a base VM ready to go for image capture. Capturing and deploying the image was a breeze and took about 60 minutes total (not bad at all for the size of the base image and the speed of our infrastructure).
Thanks for taking me into giving it a try - it was well worth the time!
Sounds like I need to go ahead and set one up in my lab. It's been years, so probably time for a self refresher anyway.
-
@Shuey said in Options for deploying standardized image to desktop & laptops?:
FOG ended up being just the ticket! It was easy to deploy, easy to configure, and I already had a base VM ready to go for image capture. Capturing and deploying the image was a breeze and took about 60 minutes total (not bad at all for the size of the base image and the speed of our infrastructure).
Thanks for taking me into giving it a try - it was well worth the time!
Awesome, glad it works well!
-
@Shuey said in Options for deploying standardized image to desktop & laptops?:
I've currently been using a Macrium PE disc (free version)
This version is for non-commercial home use.
-
@aaronstuder said in Options for deploying standardized image to desktop & laptops?:
@Shuey said in Options for deploying standardized image to desktop & laptops?:
I've currently been using a Macrium PE disc (free version)
This version is for non-commercial home use.
He's changed to fog, so that isn't relevant any more.
Edit: Unless you're going to send the audit team. . .
-
@aaronstuder Hey Aaron - yep, I stated in my previous post that it was strictly for testing purposes (to determine if Macrium was going to work for me or not). And as Dustin stated, I ended up going with FOG anyway.
