All Activity

I'm having trouble getting re-imaged computers to join the domain. Re-joining computers with an existing name wasn't an issue until recently. Research has pointed me to KB Article KB5020276. I also found possible solutions, but so far nothing I tried has helped. Even searching through the Deploy Central posts hasn't provided anything recent. How are others coping with this issue?

Hi, For a long time when I've been making and deploying Win10/11 images, I have been pre-populating the license field with the generic KMS key, which the machines have no trouble using (though we've switched from KMS to on-prem AD activation, fwiw). At the same time, once the machines are placed in their destination OU, they get hybrid-joined to Entra ID (formerly Azure AD) which introduces user-based licensing from the cloud ... which I presume supersedes/overrides the previous license/activation config. I was pondering - do I need to make any changes in image creation or deployment config as a result of the new Azure-licensing method? Are there any new best practices in light of this? (eg, what if we ditched on-prem AD and went Azure-native?) Cheers.

Has there been a resolution to this? This appears to still be an issue.

Good afternoon, The release notes state "After the new version installation is complete, re-run the Media Wizard to recreate deployment media." We have many USB thumb drives in the field that techs use to image devices.. My question is, if I do the 3.0.1065 to 3.0.1095 update/upgrade, will those still continue to function and properly kick off imaging, or is new boot media absolutely required to function? Thank you, -Corey

Any luck with this anyone? I have just upgraded and am having the same issue now.

Curious about any resolution as we are getting this as well. I would just re-create the application pack, but I can't even get in to check the config selections. It was working great so I was hoping to at least be able to do that. it was our O365 application pack. Thanks

Are you looking for a remote option from within the console? If so one doesn't exist. However per SmartDeploy FAQ you can do the following on the machine itself: "When this happens, use the Task Manager to end the installation process, or restart the client PC. Then, delete the SD folder in C:\Windows\Temp if present." https://smartdeploy.pdq.com/hc/en-us/articles/12982169564955-Troubleshooting-Application-Pack-Deployments