Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Brady

  • Rank
  1. Thanks very much for the tip!! I'll definitely look into this as a possible solution. Is it possible for multiple end points to be able to do this to a single server? I'll lay out our scenario and maybe there's another way I'm just not seeing.. 3 technicians in different states will be deploying machines, but we want to keep a centralized repository of images and answer files so when changes are made, we only have to do it in one location. I don't know if there's other facets to this that I need to plan for, but we really are totally new to imaging.
  2. That's true. I had the original instance installed on my work laptop, but in an effort to centralize the solution so multiple technicians in multiple locations could deploy images, our Rep suggested we spin the main console up on the server. W/out having any experience with imaging solutions, it's difficult to come up with 'outside the box' thoughts because I don't have any foundation to even theorize from, but I thank you for the prompt response, Aaron
  3. I'm absolutely new to imaging and I'm having to find a workaround for this issue. I have the console running on a VM in Hyper-V so I'm unable to 'pass-through' the thumb drive to the console machine. I need to create bootable media because I don't intend to spin up a new machine, install the deployment agent, and THEN push the deployment. I need to image a machine from boot. What's the best option (and steps) to creating a deployment package WIM and then creating a bootable thumb drive that's going to be able to utilize that WIM? I'm hoping I can get a faster response on here than I
  • Create New...