tim.cummings@juhsd.net

using  2.0.3000, 

We recently received 10 Dell Latitude 7490, we are having trouble deploying the image on them, it cannot seem to see the SSD.  Anyone have trouble with this or resolve this before?

When I took the image, I selected for use with WDS and only selected the OS partition, that seems to have worked.

You know what it started doing the error again.  I had to make a change in the image and tried to take the image all over again using the iso to put in the vm, and gets all the way to the end before i get the error.

logs: https://1drv.ms/u/s!AhwoICTP_02ug-4oQrAIKNYyEhgxIQ

8 hours ago, Milan0 said:

@tim.cummings@juhsd.net 

Out of interest, how are you managing the built in apps? Are you leaving them or stripping them, and if you're stripping them how are you achieving that with Smart Deploy. Thanks.

I am just leaving them in, as I found in the past major issues when messing with them.  I do have some GPO's though that push a custom start menu and desktop from some users.

for 1709 I had to start over from scratch for my images.

Using a ISO seems to have worked.

I got an error when trying to capture and new fresh image of windows 10 enterprise 1709

"the specified image does not contain a <customdata> node and cannot be used for deployment"

not sure what the issue is here. Capturing from vm on ESXi 6.5 host using pxe boot and capture.

see logs

https://1drv.ms/f/s!AhwoICTP_02ug-4TJbBesh7u6f8z_g

12 hours ago, eburnett said:

My test failed - SD came back unable to find wim. So, basically it only takes the "differences" from then creates the file. This makes it useless for me if you have to recut the dwm everytime there is a change to the original, plus to make edits to the machine where the dwm was cut - might as well just keep it as a standard image for me - this is been my impression so far.

On the upside, I just worked through my issues on my push install from client - couldn't tell if it was on the SD side or my answer key - the package wasn't being dropped, when I try to edit it defaults to D. I still get a warning box from the deploy page but it goes through ok, package and all.

Yeah, we have to do adobe too, but we don't control our destiny - which is such a headache because we have no control over how the packages are created or when they will be updated. Also I see another password cluster**** down the line, with 365 - everyone came to us and said "don't you know my password?" with all the iterations I believe they will associate with old forgotten 365 passwords and - de ja vu. At least with 365 we had access to central management, not for us with Adobe.

 

Thats a good point, yeah you will have to make your differencing image again if you modify the master wim

I am trying to use it right now for the purpose of have a base image that is updated and deploys everywhere, but a differencing image that has adobe cloud creative suite apps installed., which would take the techs a long time to do after imaging, and the way our license is we only want to use it on a couple of labs at each site.

turned out the platform pack was corrupt and deleted and re-downloaded it and it is working now

Hi,

I am happy with smartdeploy so far, great tool.

I have a couple of enhancement and features requests as i am sure others do as well.

1. To be able to change an image description after capture

2. to be able to use the drop down menu in the deploy wizard for differencing images of the same image.

3. wim to vmdk conversion tool.

4. operate deploy wizard without mouse

5. Advanced custom tasks per image

6. Centralized Technician Console on a server, and a client to connect to it from workstation.  (makes it easier for multiple techs to use)

If I think of some more I will add them inline.

When deploy a differencing image shouldnt that be selectedable from the Image name: drop down menu?, what is the purpose of the drop down menu if it only has one thing in it?

I am also having trouble using smart deploy on a latitude 7480, one smart deploy boots in legacy mode from pxe, i cannot select anything and there is no mouse control

I'm pretty sure I didn't use the VMware easy install, but there was a significant update to windows 10 and maybe that caused it. In which case I'm sure others may have the same issue.

It was just created in VMware workstation 12, just by using a iso to install windows just as you would baremetal nothing custom done. Should I try to fix the partitions?

here you go

sent info in pm

Yeah that was like the first thing i tried.

Console.log

SmartDeploy.log

I am having a bug where one particular image in my library keeps showing a hashed name instead of the simple image name. Imaging still works fine, just some weird bug and was wondering if anyone else had this or new a way to resolve it.

I also had the same error when trying to use WDS with multicasting, but when just using the unc path without multicast i can image.