Images Name in Library Bug

[tim.cummings@juhsd.net]

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.

 

 

[SmartDeploySupport]

You could try right-clicking on that image and select refresh.  If that doesn't work could you send the following to support @ smartdeploy.com and we'll take a look.

c:\smartdeploy\logs\console.log

c:\windows\system32\SmartDeploy.sdf

Thanks,

SmartDeploy Support

[tim.cummings@juhsd.net]

Yeah that was like the first thing i tried.

Console.log

SmartDeploy.log

[SmartDeploySupport]

Need the SmartDeploy.sdf, not SmartDeploy.log.

Also, the image metadata would be helpful. Open the "SmartDeploy Enterprise Command Prompt" as admin, and run the following command against the image in question and send us the output.

smartwim /info your.wim

[tim.cummings@juhsd.net]

sent info in pm

[SmartDeploySupport]

Can you run diskmgmt.msc in the VM this image was captured from and send us what it looks like?

Thanks!

[tim.cummings@juhsd.net]

here you go

[SmartDeploySupport]

The console is expecting the partitions to be in the default Windows 10 order of a 500MB system and the rest of the drive as the boot partition.

So, we've filed a bug to have the console find the correct index of the .wim that contains the Windows node and use the name of that Index.

But, curious how your VM was created to end up with that partition structure?

Thanks,

SmartDeploy Support

[tim.cummings@juhsd.net]

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?

[SmartDeploySupport]

The only way I can think it would end up like that is you used the VMware "Easy Install", which automates Windows setup and forces Windows to use a single partition.  Then perhaps this VM was upgraded from one version of Windows 10 to another, like 1511 to 1607, and that process created the 450MB recovery partition at the end of the drive.

Can't really fix the partitions now. Would need to create a new VM, not use the Easy Install, I.e. just select "I will install the OS later".  Once the VM is created attach the latest Windows 10 .iso and install Windows.  Or, you can just use the SmartDeploy Build Wizard to create your VM.

Thanks,

SmartDeploy Support

[tim.cummings@juhsd.net]

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.