SmartDeploySupport

Hi BSmith,

Glad to hear it - please feel free to reach out if we can assist with anything else.

Glenn
SmartDeploy Support

Just to clarify, when is the reboot happening? Are you able to get into the SmartDeploy boot environment and apply the image?

Hello,

Yes, you can deploy to a virtual machine. 

Thanks,

Devon

SmartDeploy Support

Hello,

Just to clarify, I assume you don't want that license file on every deployed machine then? If so, you could simply put the license file on your image.

If you want the license file deployable, you would use the copy task in the Application Pack manager like below.

Thanks,

Devon

SmartDeploy Support

Hi Sergio,

You simply need to use a user account that is a local admin on the console host, and which has these privileges available. A domain administrator would generally have these, although for security reasons, I might suggest you use a service account that only has the privileges required.

If you open an admin command prompt and run the whoami /priv command (as you did), if the privilege appears on the list at all, then the user has that permission. The enabled/disabled column simply indicates whether the privilege is in use by the current process (the command prompt itself). So if you see the privileges on the list, the current user account can use SmartDeploy.

Glenn

SmartDeploySupport

Hi Melissa,

We'll reach out to you via email regarding this. There's no reason that we're aware of that is specific to the 1909 ISO that should be causing this failure, so we'll need to investigate this further.

Glenn
SmartDeploy Support

Hi Stone,

We'll reach out via email to troubleshoot this further.

Glenn
SmartDeploy Support

Hi Brad801 –

We appreciate your interest in SmartDeploy and for taking the time to provide thoughtful feedback. From the copy presented and graphic, I can see why there would be some confusion. We’ll take a look at making copy edits so that it is more clear, we certainly don’t want to deceive or mislead our customers.

The graphic and copy are attempting to represent that SmartDeploy gives you efficient ways of managing each of these content layers. The idea is to get customers thinking that you don’t have to have monolithic, hardware-dependent images. You can decouple workflows for managing these different layers and that is really the point. SmartDeploy allows you to:

• Migrate user data and settings from one machine to another. User data and settings can also be retained when re-imaging the same device.
• Push discrete applications, updates, and execute scripting commands to devices after imaging them. You can include apps in your images too, most customers do. You can also script the application install process as part of an imaging process as well.
• We use a VM to create your golden image. When we capture that VM, we make a WIM of it and sanitize it so the WIM is free of anything other than software information (OS, patch level, and applications). Works with any version of Windows from 7 to any flavor of 10. The graphic is meant to show this flexibility.
• Hardware information is managed with Platform Packs, bespoke, curated driver packages that have all the hardware-specific drivers and information. You download these from our product and allows your image, apps, and data to be applied to whatever hardware you like.

I hope this helps, if we can be of any further assistance to you at this time, please call 888-7DEPLOY or email sales@smartdeploy.com or support@smartdeploy.com.

Best regards,

-Spencer

Hi Guy,

Ah, understood. In that case, we'll want to have a look at a logset from this deployment. I'll reach out to you via email with instructions.

Glenn
SmartDeploy Support
 

Hi Guy,

When you run tasks during the same phase (such as your two FIRSTLOGON tasks), they don't necessarily run in the order you've specified, and one does not wait until the other has completed before running. So it's possible that your command to copy the script from C:\Windows\Setup to C:\Platform is not finishing before Windows attempts to run the other command, so it's failing because it can't find the script.

You could put the copy command into FIRSTBOOT instead, but I'm not quite clear on why it's necessary at all. I assume that sd_postimage_bas.cmd is copying it into C:\Windows\Setup in the first place? Is there any reason why it couldn't just be copied directly to C:\Platform? (in WindowsPE, this would be T:\Platform, but it's the same folder), or (alternately) executed directly from C:\Windows\Setup?

It just seems to me that the copy command is an unnecessary point of failure.

Glenn
SmartDeploy Support

Hello wajtech,

There shouldn't be and none that were aware of. Are you experiencing any roadblocks or issues from pushing apps out?

If so, please go ahead and email us at support@smartdeploy.com and we can surely take a look.

Hello Livesystems,

Similar as to mentioned above, we'll need to take a look at a log set to see what's going on. Could you email our support email support@smartdeploy.com ?

Hello,

No, this does not sound normal. We'll contact you via email to troubleshoot further.

Glenn
SmartDeploy Support

Hello,

Unfortunately, the in-place upgrade to 1903 is most likely to be the cause of the issue. We do not recommend installing in-place upgrades on your reference VM, because it can lead to Sysprep errors of the type you've described.

Our best recommendation would be to create a new, blank virtual machine, and install Windows 10 Version 1909 using the latest OS media from an official Microsoft source, which includes this update. Then install all updates, shutdown gracefully (shutdown /s /t 0), and run a test capture and deployment.

If this is successful, then back up a copy of the VM in this known-good state, and then you can power on the VM and begin installing software. This way, you'll have a copy of the VM that you can roll back to, in the event that any specific software installation or configuration change results in a deployment failure.

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

Glenn
SmartDeploy Support

The new version is now utilizing TLS/https for improved security and we have seen proxy/web monitoring cause issues. Please try the following and let us know your results. 

• Stop the SmartDeploy Console Service in Services.msc 
• Open a command prompt as admin and browse to C:\Program Files (x86)\SmartDeploy\SmartDeploy Enterprise\Resources\ and run Consoleservice.exe /console like the following:

• Let that run for a minute or two then re-launch the SmartDeploy console and let us know if you still encounter the error. 

Thanks,

Devon

SmartDeploy Support

Hello,

This should occur automatically in due course, without any action required on the console side. We will follow up by email for further troubleshooting if needed.

Glenn
SmartDeploy Support

We have purchased and tested the Surface Pro 7, and it works fine.  You'll need to try with a clean test image, even though your image may work on older hardware.  Please email support @ smartdeploy.com to create a ticket.

Hello,

You will want to create a single virtual disk file.This will allow for the SmartDeploy's Capture Wizard to select and capture the virtual disk to convert it into a .WIM. That being said, you can create split virtual disks, but it requires a warm capture in order to capture it. You can find out more about warm captures here. 

The reason you're seeing the Media Wizard split images is because it needs to split the WIM into 4GB splits in order to create Fat32 media. Fat32 is required for UEFI deployments.

Hope that makes more sense now. 

Devon

SmartDeploy Support

Hello Chris Dietz,

Does this occur right after you login? Or does this error present itself once you click Deployment packages.

If you still issues, we may need to take a closer look at your console.log located in C:\SmartDeploy\Logs from the SmartDeploy host machine. You can submit a ticket here. Please refer to this thread.

Thanks,

Chris

SmartDeploy Support

Glad it worked out!

Devon

SmartDeploy Support

It may provide a different error/code that may be helpful to see what may be going on. 

Does this happen on all USBs? We would really need to see the media.log in order to see what is happening.

Thanks,

Devon

SmartDeploy Support

Try formatting the USB via via diskpart. Open an administrative command prompt and type the following:

diskpart
list disk [determine which disk is your external USB stick, probably disk 1]
select disk 1 [use the correct disk number here]
detail disk [read the disk info; make sure you have your USB stick selected]
clean [this destroys all data and partition/volume info on the selected disk]
create partition primary
active
format quick fs=ntfs [Media Wizard will convert this to FAT32 later]
assign
exit

Then relaunch the Media Wizard and attempt to create new media. If you still have issues send your C:\SmartDeploy\Logs\Media.log from the SmartDeploy host. You can submit a ticket here. Please refer to this thread.

Thanks,

Devon

SmartDeploy Support

Chris,

The image was not captured for WDS. You will want to capture your virtual reference machine via the Capture Wizard. During the process ensure you check "For use with WDS." This will ensure the image will be able to successfully be imported into the WDS role. 

Hello,

I'm sorry you feel as though we are not helping and becoming frustrated. We cannot reproduce this issue on our end. I just replied again for you to perform a clean installation.

Let us know your results after you follow my steps in your ticket. 

Thanks,

Devon

SmartDeploy Support

Hi Palle,

Would it be possible to upload your platform pack so we could take a look? Also, please send us your C:\SmartDeploy\Logs\Media.log from your SmartDeploy host and we can verify if the drivers are getting injected. Submit a ticket here and refer to this forum post.

Thanks,

Devon

SmartDeploy Support