SmartDeploySupport

Hi Tim,

We do have customers ask about his every once in awhile. The reason we include Lenovo's and not Dell's or HP's is because the Lenovo utility is the only one that is good at detecting installed driver versions when those drivers have been installed via PnP.  What I mean by that is that on a Dell Latitude 5490, where all the drivers are up to date via PnP, the Dell Command Update software will want to reinstall the same versions of the Intel Management Engine, Intel Ethernet, and Intel Wireless.  This would be true if you used their SCCM pack as well.  Always hoped this would improve, but it hasn't. I understand wanting to use it, but for us it's hard because it makes our platform packs appear out of date when they are not.

That being said, when purchasing a bunch of a particular model, that's a good time to submit a platform pack update request to us for those models.  In this case the 7400 pack was just updated 5 days go, and I updated the 7410 pack today.

Thanks,

Allen M.

Hi wsova,

We'll want to see a complete logset to troubleshoot this further, and I've opened a support ticket with you to troubleshoot this further.

Unfortunately, there is no single, specific answer to domain join failure, but broadly speaking, the failures tend to occur due to bad credentials, a bad FQDN for the domain, a bad Distinguished Name for a specified OU, or a failure to connect to a domain controller during the SPECIALIZE phase (which can occur with certain network adapters that fail to initialize without a reboot).

The logs can usually tell us where to look, so that's where we'd need to start.

Glenn
SmartDeploy Support

Hi Dejeon,

We will need to take a look at some deployment logs. Boot the 5480 from your SmartDeploy boot media and select Collect Logs. Save the resulting zip and send it to support@smartdeploy.com. The subject: 5480 Issues

Be sure to reference this thread.

Thanks,

Devon

SmartDeploy Support

Hi Dave,

When you push the Application Pack out to an endpoint, all of the files in the pack will be extracted to a folder on the target device, which can be referenced using the path variable [ApplicationsFolder].

So in this case, in the Arguments field, you can reference the MST with the path:
[ApplicationsFolder]\Files\10.0.0.35798\FoxitPhantomPDF100_enu_Setup_Website_FCT.mst

I've opened a ticket for you and will send you an email with this information shortly, so please follow up with us via email if you have any questions.

Glenn
SmartDeploy Support

Hi Chin,

Client machines should automatically update themselves. If they're not, then something is causing a disconnect in communication to the host.

We can certainly take a closer look at this. Please submit a request to support@smartdeploy.com and we can further troubleshoot the issue.

-Chris

SmartDeploy Support

Hello Brad H,

We try our best to update the Platform Packs routinely, but generally our customers notify us if one needs to be updated or experience issues. If there is a Platform Pack you'd like us to update, please definitely submit a request including the make and model to support@smartdeploy.com and we can take a look.

-Chris M.

SmartDeploy Support

Hi all,

If anyone reading this needs assistance scripting a custom computer name, please reach out to support@smartdeploy.com and we'll be happy to assist. Its feasibility depends on your specific scenario, but we'll be happy to assist if we can.

Glenn
SmartDeploy Support

Hello Aaron@Shared,

What we recommend doing is to install another instance of SmartDeploy on a physical workstation. Then you can create USB media, using your Answer File, Image, and Platform Pack via network shares from your main console host. 

On 6/5/2020 at 5:01 AM, Mark Andersen said:

I have the exact same problem as @olydrh .

 

Is there anywhere i can see a list of Windows Versions that is supported by SmartDeploy?

Hi Mark,

Apologies for the delayed response. You can see this information in the Release Notes (available on the SmartDeploy.com portal or via the Tools view in the console), which will list when support for specific versions was added along with a new version of the SmartDeploy software. When a new version of Windows 10 is released, our testing process takes time, and depending on whether or not changes to the software need to be made, it may be a few weeks following general availability before we support that version.

1903 and 1909 did not require any changes to SmartDeploy to support those versions, but 2004 did require some, as have previous versions.

We recommend keeping all of your old images and files until you have had a successful test of the new version.

If you have any questions, please feel free to reach out - support@smartdeploy.com.

Glenn
SmartDeploy Support

Hi all,

Yes, that is correct - SmartDeploy version 2.0.3080 was released today, and it does support Windows 10 Version 2004.

Please note that as with any new version of Windows 10, we do not recommend performing in-place upgrades on an existing reference VM that was created with an older version of Windows 10 Version 2004. You should create a new, blank VM and install Windows 10 Version 2004 using OS media from an official Microsoft source (such as the VLSC or the Media Creation Tool) which includes that version.

If you have already created a suitable reference VM and captured it using an older version of SmartDeploy, you can keep using the same reference VM, but you will need to recapture your image using SmartDeploy version 2.0.3080. This is because the partition structure has changed, and we had to make changes to the product on both the capture and deployment side to support this new structure.

If you have any questions or issues, feel free to contact us at support@smartdeploy.com.

Glenn
SmartDeploy Support

Thanks!

Yes, I do expect we'll be sending out an email to announce when Windows 10 Version 2004 is officially supported.

Glenn
SmartDeploy Support

Hello,

As of this writing, Windows 10 Version 2004 is not yet supported in SmartDeploy. Microsoft made several changes to the default partition structure which has required some changes on our end as well. We're working on a version that will support Windows 10 Version 2004, and it should be out in the next week or two.

What you're describing sounds like a Sysprep error, which is interesting - it's not an error we've seen in our testing. We'd like to take a look at a logset from this deployment if you're willing to send one in - I'll reach out via email with instructions for that.

If anyone else is reading this at a later date and has questions about Windows 10 Version 2004 support, please reach out to support@smartdeploy.com.

Regards,

Glenn
SmartDeploy Support

Hello Aaron@Shared,

Can you try disabling Sophos to see if it produces better results?

Then for further troubleshooting, please go ahead and reach out to support either via email, (support@smartdeploy.com) or submit a ticket here

Thanks,

SmartDeploy Support

If you have any anti-virus running on the SmartDeploy host, disable it and try saving the file. If you still have issues, please create a ticket here and then send us your C:\SmartDeploy\Logs\Console.log from the SmartDeploy host and reference this forum post please.

Thanks,

Devon

SmartDeploy Support

Steven,

Correct, it's not something currently built into the product.

Thanks,

Devon

SmartDeploy Support

Hi Steven,

We can do this, but it's a manual process on our side. Can you submit a ticket here and reference this thread? I will then reach out with further steps.

Thanks,

Devon

SmartDeploy Support

Hello cnelsenxx1,

You'll need group policy to backup your recovery key. This is outlined in the link of that KB you found and here below:

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-7/dd875529(v=ws.10)

Yes, the instructions you found to suspend Bitlocker looks correct.

If you have any further questions, please reach out to us at support@smartdeploy.com.

Thanks,

Chris Mendoza

SmartDeploy Support

Hello cnelsenxx1,

By default Sysprep resets all users settings that were defined in the reference image.

If you plan on disabling IPv6, you can apply this by running a netsh command like

netsh interface ipv6 uninstall

Let us know if you have any further questions. Please submit a request to support@smartdeploy.com

Thanks,

Chris Mendoza

SmartDeploy Support

Hi Mitchell,

It is not possible to burn two ISO files to the same disc. You will need to use two discs. There seems to be some sort of disconnect on this issue - to be clear, the reason why two ISO files was created is (presumably) because the .wim file was split up. The architecture of the .wim file format is such that while a .wim can be split apart into multiple split-wims, it cannot split individual files. So the size of the resulting .swm files is dictated by the actual files contained in the .wim. You may end up with a pair of ISO files that seem as if they could both fit onto a single DVD, but that is not possible. You need to use separate discs. If you wish to avoid using discs entirely, you'll need to use USB media, or store your image and Platform Packs somewhere else besides on the media itself (such as on a network share, or on a separate USB drive).

Our records indicate that you only have one ticket open at this time (which appears to be waiting on results from another test deployment from your end, after removing a/v from your reference VM). That ticket is not on the subject of offline deployment media, and I do not see any ticket on that subject that is pending. While the Basic support level does only include 1 ticket per month, we're certainly happy to assist further on this, because it sounds like the process has been frustrating - so please do reach out if needed.

DeployCentral is not a more direct avenue to support than emailing us - it all goes to the same place. I'm sorry to hear this has been a frustrating process for you, but I would encourage you to continue engaging with us, and we will get this working for you.

Glenn
SmartDeploy Support
 

Hello cnelsenxx1,

To investigate this further, could you provide us with a screenshot of this prompt? As well as your console.log located in C:\SmartDeploy\Logs of your host machine?

Please submit these to support@smartdeploy.com and we'll review these.

Thank You,

Chris Mendoza

SmartDeploySupport

Hi Mitchell,

I'm not quite sure I understand the issue - this behavior is by design, and if your intention is to burn the ISO files to disc, you can simply copy the ISO files to any workstation and use any disc-burning software to burn it to two dual-layer DVDs.

If your objective is to create a USB flash drive, you cannot use ISO files for this purpose. You would need to install SmartDeploy on another workstation, copy down the image and Platform Packs and (optionally) answer file to that workstation, and then run Media Wizard to create offline deployment media. If you select offline deployment media, then the image and Platform Packs are copied to the media. If you select boot media, then all the media gets is SmartPE + your answer file + any WindowsPE drivers that may be included in the Platform Packs you selected. So I suspect if the flash drive "was not getting everything needed", you may have selected boot media accidentally.

If you have any questions, please feel free to reach out at support@smartdeploy.com.

Glenn
SmartDeploy Support

Hello JMcDonald,

Are you attempting to upload to OneDrive? I went ahead and started a ticket request for you regarding this.

Thanks,

Chris Mendoza

SmartDeploy Support

Hi cnelsenxx1,

I do see the issue - you're referencing the path where the MSI exists on your SmartDeploy console host, not the MSI stored inside the Application Pack, which would include the relative path variable [ApplicationsFolder], which is a stand-in for the folder on the target computer where the pack will be extracted prior to installation.

To insert this path automatically, click on the Run MSI Package task on the left pane, then - next to Executable location, click the Select button. Select the MSI and click OK - and the path will update automatically.

I would suggesting adding ALLUSERS=1 to the Arguments field - it's required for many pieces of software when being installed by the LOCALSYSTEM account. Click File | Save, and then exit and retry the Application Pack.

If you continue to have issues, go ahead and email us at support@smartdeploy.com, and reference this thread.

Glenn
SmartDeploy Support

 

When you created your answer file, did you create a cloud answer file?

I would suggest recreating your answer file and ensure you select the Cloud Storage Provider option. During the process you will connect to your cloud provider and browse to your image. If you still have issues, please create a ticket here and reference this thread and I can investigate further.

Thanks,

Devon

SmartDeploy Support