nerdynerd

Do "Script" Application packs run before or after the domain is joined? Do they run as the user that's entered in the answer file or is it ran as some built in user like SYSTEM? I'm hoping to run a batch file or a powershell script after the imaging is complete to call our to our software deployment system for some packages. I have a working script so I'm just trying to integrate that with SmartDeploy and understand when and by whom it's going to run.

One of the commands mentioned by SmartDeploy Support cleared out that error message, so I created an Application Package which I've outlined below. I'm not sure the error message was actually hurting anything since the system was activated by our AD activation service, but I thought it looked sloppy for it to say the previous activation had failed. Application Pack: Executable location: c:\windows\system32\cscript.exe Arguments: //B "C:\Windows\system32\slmgr.vbs" /ipk [GLVK key without brackets] Full command: "C:\Windows\System32\cscript.exe" //B "C:\Windows\system32\slmgr.vbs" /ipk [GLVK key without brackets]

We are using Active Directory activation for Windows 10 and I'm running into an issue with my SmartDeploy images. My images are built off of VL media and I do not modify the Windows key on the image prior to capture, so it's got the GLVK only on it. I've captured the image in SmartDeploy without entering a key and have tried my answer file with and without the GLVK key and get the same result. The issue is that I get the message below. The systems appear to be properly activated by AD, and I think the message is due to the PCs having an OEM license that might be trying to activate, but I'm not sure. I've found that after imaging, if I manually change the product key to the GLVK, the error goes away. Are there certain steps that must be taken in the SmartDeploy workflow to activate systems against AD that I'm possibly missing?