You need to keep applications out of your image. If your .wim file is that big, you're doing it wrong. Use the Microsoft Deployment Toolkit 2013 to deploy a thin image and push all applications, drivers, and updates at deploy time, its actually pretty easy. MDT 2013 will even build a bootable iso file you can load to USB via Microsoft's iso to USB install tool. I suspect you're actually making this process more labor intensive than it needs to be.
Another option is to use a deployment share like I'm suggesting, but for now push these massive images across the network. Use multicast in Win2k8 if you can w/ WDS. But that's really a Band-Aid, I say you still just rebuild the image, but keep it as thin as possible and This way your image is kept lean, clean and mean. You can use always use MDT 2012 to install all apps at deploy time. If your image is way too "thick" try to keep images as lean as possible.
Always, Always, ALWAYS, build your images in VMs, to keep them hardware independent. MDT will do drivers at deploy time , so there's no need to put drivers in your image.
If you're really just trying to capture a modified OEM image, understand OEM licensing doesn't include "reimaging rights" while that's legal issue, technically, you may get away with building a capture task sequence in MDT that will do the capture for you, and you could get away with pushing that captured image with standard client deployment sequence.
First off, you need to get MDT 2012 Update1 and the Win8 ADK installed.
Create a VM. Next you need to set up a VM we can use to build the image in. I prefer HyperV, but if you’re broke and/or cheap, virtualbox will work just as well. Some of my earliest images were built using this. Regardless of how you build the VM, allocate 2 gigs if you can for the VM.
Find a copy of Windows8. You’ll obviously need a copy of Win8. As of now, you’ll need either a retail ISO or find the
wim file somehow. If you have a TechNet subscription like me, you’re in business. In your case, see if you can find one in the recovery partition or recovery media.
Build Your Share. A Standard Client Task Sequence is Fine. If you plan on putting office in the image, add Office into applications, and configure it for an unattended install if you can, if not you may get away with doing that when lite touch suspends.
Import the OS. In that share you import the
.wim file into operating systems. You don’t need
setup.exe files for Win8. DISM handles it.
Build a task sequence. Set
capture=yes in your
customsetting.ini file and customize your unattended.xml file.
Configure your share. Remember, if we’re building a reference image, we want it up to date, so turn on updates in the task sequence before and after applications.
Update the share. Right click the share in the left menu and select update. This takes some time, so go watch some lite touch unleashed in the meantime.
litetouch.iso file in the boot folder to USB using the Microsoft tool. Boot to USB, and away you go!
Check out my guide here : Build a Windows 8 Image in MDT 2012