Imaging and Deployment Software

[dlock13]

Hello there,

Our company uses Active Disk Image to capture images from a build and deploy it to machines. It does not work properly with Windows 8 and UEFI bootloaders. We need a software that will allow us to create an unlimited number of builds for unlimited devices and allow us to deploy it to said devices. The version of Active Disk we've been using has allowed us to do that, but like I said, it does not work properly with UEFI.

Does anyone have any kind of recommendation for a software out there? What we need it to do is boot from a USB drive (external HDD or flash) and allow us to capture the image from said bootable.

Thanks!

 

[raf051888]

Do you have the option of capturing to a network share? Microsoft Deployment Toolkit will be one of the better options and more than likely is free to your organization.

 

[Kaido]

Macrium Reflect:

http://www.macrium.com/

It uses its own image format (.mrimg).

 

[VirtualLarry]

There was some talk in another thread in the OS forum, about the new "features" of UEFI, especially relative to cloning disk images.

Unlike MBR, which functioned solely off of BIOS selecting which physical device to boot off of, and then the device containing all of the boot info, UEFI is different.

Not only do you need the GPT partition info correct on-disk, but that also has to be "registered" into the UEFI of the machine in particular, in order to properly boot off of it.

This is why, after installing a UEFI-compliant OS on one of those motherboards, when you go into the BIOS / UEFI to select the boot device, it also has the OS in question's bootloader listed BY NAME.

So if you wanted to clone that drive's OS install to another drive, and put that new drive into another identical machine, you still need an additional step to "register" that new drive's bootable OS partition into the UEFI as an OS bootloader.

Edit: This is why simply cloning the disk, may not work for UEFI PCs.

 

[dlock13]

Do you have the option of capturing to a network share? Microsoft Deployment Toolkit will be one of the better options and more than likely is free to your organization.

Nope. We won't be able to do that.

Macrium Reflect:

http://www.macrium.com/

It uses its own image format (.mrimg).

Does it allow you to capture the UEFI bootloader partition properly like VirtualLarry mentioned?

There was some talk in another thread in the OS forum, about the new "features" of UEFI, especially relative to cloning disk images.

Unlike MBR, which functioned solely off of BIOS selecting which physical device to boot off of, and then the device containing all of the boot info, UEFI is different.

Not only do you need the GPT partition info correct on-disk, but that also has to be "registered" into the UEFI of the machine in particular, in order to properly boot off of it.

This is why, after installing a UEFI-compliant OS on one of those motherboards, when you go into the BIOS / UEFI to select the boot device, it also has the OS in question's bootloader listed BY NAME.

So if you wanted to clone that drive's OS install to another drive, and put that new drive into another identical machine, you still need an additional step to "register" that new drive's bootable OS partition into the UEFI as an OS bootloader.

Edit: This is why simply cloning the disk, may not work for UEFI PCs.

That is kind of what I figured. Is there another way to grab at least a base image of a machine that is UEFI?

 

[dlock13]

Using WinPE right now, and it boots perfectly fine. Is it possible to capture JUST the Windows partition as a .wim, and then deploy that to an identical device? I want to set up C:\ with our own unattend file and software, and then I want to copy and transfer that exactly how it is to an identical device.

Is that possible? If it is, then I may have found a way, a slow way, but a way none the less.

 

[takeru]

symantec ghost solution suite 3.0
http://www.symantec.com/content/en/...1&elqTrackId=e4ab1d8dd214407a85143e904d06e428

supports up to winpe5.1 and uefi systems

What’s New in Ghost Solution Suite 3.0

General Enhancements and Improvements
Ghost Solution Suite 3.0 has made a number of technological fixes and improvements based on numerous customer requests, including adding support for new
operating systems and hardware. Some of the new general enhancements include:

New OS and Hardware Support
Support for Windows Server 2012 R2, Windows 8.1, Mac OS X 10.10 Yosemite
Updated hardware support (UEFI 32-bit and 64-bit)
Support for WinPE 5.1pre-boot operating systems
Includes LinuxPE pre-boot environments (x86 and x64) – [Note: it is the same version as shipped with Deployment Solution 6.9 SP6]

Updated SQL Database Support
Support for Microsoft SQL Server 2014 and SQL 2014 Expres

 

[xSauronx]

Do you have the option of capturing to a network share? Microsoft Deployment Toolkit will be one of the better options and more than likely is free to your organization.

this is the way to go but there is documentation to use MDT and ADK for a USB deployment.

i use it for network deployments. its free, microsoft supplied [and used], allows for a ton of automation and and has loads of documentation and help available via user forums, blogs and video examples.

Deploy Windows 8.1 from a USB stick
https://technet.microsoft.com/en-us/windows/dn481547.aspx

but really...network deployment is great.

 

[dlock13]

this is the way to go but there is documentation to use MDT and ADK for a USB deployment.

i use it for network deployments. its free, microsoft supplied [and used], allows for a ton of automation and and has loads of documentation and help available via user forums, blogs and video examples.

Deploy Windows 8.1 from a USB stick
https://technet.microsoft.com/en-us/windows/dn481547.aspx

but really...network deployment is great.

The sad truth is that we don't have the infrastructure to support network deployments. Ideally, that's where we are heading, but right now, we can only have our technicians do imaging via USB.

So wait, if I use this tool, I would be able to build the image I want from another PC and then deploy it to the PC I want. Right? That is a little more involved than I can get right now due to time constraints. I just need to capture the image and deploy it to another machine. Once I get that ability, I can then work on getting an automated process in place.

 

[raf051888]

The sad truth is that we don't have the infrastructure to support network deployments. Ideally, that's where we are heading, but right now, we can only have our technicians do imaging via USB.

So wait, if I use this tool, I would be able to build the image I want from another PC and then deploy it to the PC I want. Right? That is a little more involved than I can get right now due to time constraints. I just need to capture the image and deploy it to another machine. Once I get that ability, I can then work on getting an automated process in place.

Yes, MDT is hardware independent. I currently build my images in a VM and deploy to many different models. This includes Dell laptops and desktops, and Surface Pro 3.

I used to build on physical hardware, but in my opinion VMs are the best way, because I can revert snapshot and not mess with the re-arm count.

 

[dlock13]

Essentially, this is what I am looking for.

My one question remaining..... Since the laptops arrive EXACTLY the same, can I just copy the Windows partition from the Master computer and deploy only that partition to the target machine?

 

[dlock13]

Yes, MDT is hardware independent. I currently build my images in a VM and deploy to many different models. This includes Dell laptops and desktops, and Surface Pro 3.

I used to build on physical hardware, but in my opinion VMs are the best way, because I can revert snapshot and not mess with the re-arm count.

That sounds fantastic! It is definitely something I'm going to talk to my department about and see if we can get MDT up and running at least in our local office. It would benefit us so very much.

 

[raf051888]

That sounds fantastic! It is definitely something I'm going to talk to my department about and see if we can get MDT up and running at least in our local office. It would benefit us so very much.

Just a tip for MDT, you really don't need more than a file share unless you are wanting to do PXE or Multicast.

Also, if you mainly a Dell shop, download the PE drivers, so you don't have to constantly update boot media.

This link is for the Dell Enterpise cabs, note these aren't perfect. I've had to upload specific drivers when using there cabs. I recommend the newest video driver from nVidia or AMD for those cases.

I've been working with MDT for a while, so don't hesitate to ask if you have questions.

 

[dlock13]

Just a tip for MDT, you really don't need more than a file share unless you are wanting to do PXE or Multicast.

Also, if you mainly a Dell shop, download the PE drivers, so you don't have to constantly update boot media.

This link is for the Dell Enterpise cabs, note these aren't perfect. I've had to upload specific drivers when using there cabs. I recommend the newest video driver from nVidia or AMD for those cases.

I've been working with MDT for a while, so don't hesitate to ask if you have questions.

Awesome. Thank you very much. We mainly use Dell Optiplex machines and Lenovo ThinkPads, so that will definitely come in handy for the Dell machines if we ever get MDT up and running around here.

Can you please look at my previous post? I have a question about deploying an image of 8.1 on UEFI to another identical machine on UEFI.

 

[xSauronx]

The sad truth is that we don't have the infrastructure to support network deployments. Ideally, that's where we are heading, but right now, we can only have our technicians do imaging via USB.

i only sort of do. i set it all up last year when we had 100 PCs to replace. i took an old gig switch we had in the closet and set it up on a table with an old kvm and had a deployment area. I technically can image over the network in the home office; but we do not do that [yet. if we upgrade to windows 10 i might start]

other PCs get returned here for re-imaging, but once we upgrade some servers i think the next biggest site [PC wise] will have a VM that I will set up for deployments there.

still, getting MDT set up to work via USB will just mean once you are allowed to do deployments over the network you have nada to do. MDT Is fantastic once you get it going.

 

[raf051888]

Essentially, this is what I am looking for.

My one question remaining..... Since the laptops arrive EXACTLY the same, can I just copy the Windows partition from the Master computer and deploy only that partition to the target machine?

dlock, I think this is the post you were referring to. I'm pretty sure MDT does this already, as a quick search shows it uses ImageX. One thing to note, the MDT captures have to be started from within Windows, not PE.

Are you referring to capturing the images that come on the machines from Dell or Lenovo? If so, you would be a whole lot better off to just build your own.

 

[dave_the_nerd]

Fog?

Works via PXE, but it uses Linux DD to grab the whole drive, all partitions, etc. Haven't tried it on newer hardware with UEFI, but it seems like it might fit the bill.

 

[dlock13]

dlock, I think this is the post you were referring to. I'm pretty sure MDT does this already, as a quick search shows it uses ImageX. One thing to note, the MDT captures have to be started from within Windows, not PE.

Are you referring to capturing the images that come on the machines from Dell or Lenovo? If so, you would be a whole lot better off to just build your own.

While building our own would be a great idea, we don't have the time at the moment. I'm trying to build an image on a test device, and it needs to be done in a certain amount of time. I figured it would be easy to just grab the Windows partition and then put that onto the next device in the same partition. Does that make sense? Since they're built identically, it would seem like I could just, essentially, copy and paste.

 

[xSauronx]

While building our own would be a great idea, we don't have the time at the moment. I'm trying to build an image on a test device, and it needs to be done in a certain amount of time. I figured it would be easy to just grab the Windows partition and then put that onto the next device in the same partition. Does that make sense? Since they're built identically, it would seem like I could just, essentially, copy and paste.

sort of. if you are going to do it the i-dont-have-time way you are supposed to at least use sysprep. audit mode is for configuring the pc, then the oobe option is used before you shut down so you can boot with imaging software and take your image.

do not deploy non sysprepp-ed machines into a domain. you shouldnt do it at all, but you definitely shouldnt deploy them in a domain.

that way every applied image is sysprepped [new SID is the big deal here] and lets you log in as though it were a new pc
-- which i hate. and which is another reason MDT is great. so much stuff is scripted and automatically handled that i forget a lot of the details of a one-off image other than it being a pain. MDT does my windows updates, joins the domain, installs software, moves a PC to my custom setup OU , yadda yadda.

 

[dlock13]

sort of. if you are going to do it the i-dont-have-time way you are supposed to at least use sysprep. audit mode is for configuring the pc, then the oobe option is used before you shut down so you can boot with imaging software and take your image.

do not deploy non sysprepp-ed machines into a domain. you shouldnt do it at all, but you definitely shouldnt deploy them in a domain.

that way every applied image is sysprepped [new SID is the big deal here] and lets you log in as though it were a new pc
-- which i hate. and which is another reason MDT is great. so much stuff is scripted and automatically handled that i forget a lot of the details of a one-off image other than it being a pain. MDT does my windows updates, joins the domain, installs software, moves a PC to my custom setup OU , yadda yadda.

Well, I don't have to worry about the domain part, because we don't use active directory. I wasn't planning on deploying it without sysprepping it. We need to due to the software we use requiring a unique SID.

What we currently do is set up a PC with the proper software, and then we take an image of that. We then put that image on another machine, so technically, it has the same exact SID.... But! After we put the image on there, we run sysprep which changes the SID and sets a few settings how we need them.

We're trying to set up this Lenovo device which has 8.1 on it, but I can't seem to get the sysprep/unattend file to run properly.... but I have to get the imaging part done first before I continue to work on the unattend file.

 

[xSauronx]

Well, I don't have to worry about the domain part, because we don't use active directory. I wasn't planning on deploying it without sysprepping it. We need to due to the software we use requiring a unique SID.

What we currently do is set up a PC with the proper software, and then we take an image of that. We then put that image on another machine, so technically, it has the same exact SID.... But! After we put the image on there, we run sysprep which changes the SID and sets a few settings how we need them.

what is the problem with the unattend file?
you are costing yourself time at deployment with your method, you would really benefit from spending a few more minutes doing the prep so that deployment is easier.

send new pc into sysprep audit mode
configure this, that and the other
install that stuff
do updates
then do sysprep to oobe and call your unattend file
sysprep /generalize /oobe /shutdown /unattend:unattend.xml

boot into something to capture an image, and then at each deployment...you dont have to do the sysprep steps as soon as you deploy.

 

[raf051888]

I completely agree with xSauronx. I would recommend sysprep on the source machine as opposed to the destination.

Can you explain whats going on the the unattend.xml file from Win 8.1?

 

[dlock13]

what is the problem with the unattend file?
you are costing yourself time at deployment with your method, you would really benefit from spending a few more minutes doing the prep so that deployment is easier.

send new pc into sysprep audit mode
configure this, that and the other
install that stuff
do updates
then do sysprep to oobe and call your unattend file
sysprep /generalize /oobe /shutdown /unattend:unattend.xml

boot into something to capture an image, and then at each deployment...you dont have to do the sysprep steps as soon as you deploy.

That is such a smart, smart idea. I have no idea why that hasn't been implemented a long, long time ago.

I'm definitely going to do that right now.

I tested the unattend file on a Lenovo Yoga that has our company image on it. It kept coming up with errors pointing to so many different things. First, it had an issue with the apps installed, so I searched for an answer for that which got it past that. Then it had an issue with something else which I can't remember. I didn't really document it.

If I send you the unattend file that I'm trying to use, will you be able to look at it and help me understand what I'm doing wrong?

 

[dlock13]

Ran into an issue trying to apply the image back onto the system I'm building.

Booted up Win PE.
Captured image while the PC is in Audit mode
Went to try and restore back to the original stock image to verify I am able to
Got an error after trying to run:
DISM /Apply-Image /ImageFile:E: \IMAGELOCATION\image.wim /index:1 /ApplyDir:C:

Error: 5
Access is denied/
The DISM log file can be found at X: \Windows\Logs\DISM\dism.log

I can't seem to get the image to apply at all.

EDIT:
So I got the log file, and here is what it is dying on:

2015-04-28 16:26:56, Info DISM DISM Provider Store: PID=936 TID=552 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
[936] [0x80070005] RestoreDirMetadata: (3768): Access is denied.
[936] [0x8144012d]
2015-04-28 16:26:57, Warning DISM DISM WIM Provider: PID=936 [RestoreDirMetadata: (3774) -> Error restoring directory metadata] C: \Program Files\WindowsApps\E046963F.LenovoCompanion_2.0.40.0_neutral_split.scale-140_k1h2ywk1493x8 (HRESULT=0x80070005) - CWimManager::WimProviderMsgLogCallback
[936] [0x80070005] RestoreDirMetadata: (3904): Access is denied.
[936] [0x80070005] WimCreateDirectory: (4384): Access is denied.
[936] [0xc144012e]
2015-04-28 16:26:57, Error DISM DISM WIM Provider: PID=936 C: \Program Files\WindowsApps\E046963F.LenovoCompanion_2.0.40.0_neutral_split.scale-140_k1h2ywk1493x8 (HRESULT=0x80070005) - CWimManager::WimProviderMsgLogCallback
[936] [0x80070005] RestoreDirTree: (4665): Access is denied.
[936] [0x80070005] WIMApplyImageInternal: (1069): Access is denied.
2015-04-28 16:26:57, Error DISM DISM WIM Provider: PID=936 TID=552 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1095 - CWimManager::Apply(hr:0x80070005)
2015-04-28 16:26:57, Error DISM DISM WIM Provider: PID=936 TID=552 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:4205 - CWimManager::InternalCmdApply(hr:0x80070005)
2015-04-28 16:26:57, Error DISM DISM WIM Provider: PID=936 TID=552 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070005)
2015-04-28 16:26:57, Error DISM DISM WIM Provider: PID=936 TID=552 base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:1936 - CWimManager::ExecuteCmdLine(hr:0x80070005)
2015-04-28 16:26:57, Error DISM DISM.EXE: WimManager processed the command line but failed. HRESULT=80070005

 

[xSauronx]

lots of access denied errors. format the disk first.