Jump to content
DeployCentral

Jeff Harris

Members
  • Posts

    269
  • Joined

  • Last visited

Everything posted by Jeff Harris

  1. In the Computer Management console; are the clients generating this error appearing in bold/regular text?
  2. Interesting. Do these errors stop if you enable the wireless adapter?
  3. On a second look, this blog post has instructions for creating an MSP file which would automatically be applied when setup is run. It mentions MDT, however if you can create the MSP file and configure it per this blog, then you should be able to add the Visio install folder to an App Pack, in which setup would be run, detect this MSP file and install as configured. https://web.sas.upenn.edu/jasonrw/2015/11/03/automate-the-install-of-microsoft-office-2016-with-an-msp-file/
  4. I do believe that you'd want to put your XML in the same older as setup.exe, then add that folder to the App Pack. Then you'd add the arguments: /configure installconfig.xml
  5. Can you share a screenshot of the App Pack, where you have the commands set?
  6. Sorry, but SmartDeploy does not support OSX. Unfortunately we do not have any recommended solution for that platform.
  7. I'd add that a/v or other security software on the Ref VM can cause the same thing. It's less common, but it can even happen with other random software. You didn't perform an in-place upgrade to v1809 did you? That's another thing that causes all kinds of problems in capture/deployment. Finally, a great alternative to issues like this is to rule out the host, and perform a warm capture. Here's a guide for that: https://support.smartdeploy.com/kb/article/35-performing-a-warm-capture/
  8. Any current line of support you have with your ticket is likely your best bet for a resolution.
  9. You want to avoid installing the client on the Reference VM. You can configure the SmartDeploy Answer File to automatically install the client as part of deployment, which is the preferred method.
  10. Cedar, you can install them while you work on the VM, but you'll want to remove them and restart before shutting the VM down to capture the image. Sometimes some reg keys can get stuck and make SmartDeploy think they're still installed. You can remove these keys manually if that is the case: VMware: HKLM\SYSTEM\ControlSet001\Services\VMToolsVMware: HKLM\SYSTEM\ControlSet001\Services\VMwareToolsVMware: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{FE2F6A2C-196E-4210-9C04-2B1BC21F07EF}VMware: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{96B74176-0BA4-4F5D-B3A5-466EAD9E73BD}
  11. SmartDeploy adds information specific to your SmartDeploy account among other information to the image meta-data that SmartDeploy is going to look for when deploying the image. You'll want to capture your images using the Capture Wizard.
  12. Here's a link to the video; https://www.youtube.com/watch?v=AlTa8KYyBAI Can you test app deployment with one of the smaller apps we have available for download? It could be that port 8733 is being blocked along the way.
  13. Romulo; You can place as many images on your USB drive as you can fit. When you create your Offline Media, whichever Image you have set in your Answer File will be copied to the USB drive by the wizard. You can then use File Explorer to copy additional images to the \z\ folder, and then interrupt the unattended deployment, and use the Deploy wizard to select the alternate image you want to deploy. Alternatively, you can create media without an Answer File altogether and manually step through the Deploy Wizard, selecting whichever image you want to deploy that you've copied to your USB drive.
  14. In the Tools workspace of the console there’s a tile for Generate Client Setup. You’ll specify your console host info and then save the MSI file that you’re looking for.
  15. Hey Aaron, If you keep an eye on our YouTube channel, a video I just created stepping through the whole App Package process will be posted as soon as the marketing team throws their spin on it. In the mean time, the important thing is to make sure you have the ports open for App Deployment to work. Test with one of the Application Packages that we've made available to see it in action, and then look to make your custom pack. Regarding custom packs, the important thing to look to is the run command. Test the installation of the application you want to deploy on a client via command line, silently. Then add that in the tasks field. Here's an image of a Pack I made for a demo, using Team Viewer.
  16. If your workstation is that much faster, I recommend leaving the VMs there, shutting them down and then capturing your images locally, and then copy the images to the Server host for deployment. You can have the console installed on more than one workstation without a license penalty. Then it could be a worthwhile test to use the Media wizard to create a SmartDeploy ISO and boot a new VM to that, and test-deploy your image, however I would still recommend using USB media to test it on one of the devices you're attempting to PXE boot, Lastly, if your devices are in UEFI mode, you will want to enable Secure Boot. If your system is in UEFI mode, but you temporarily boot to the Legacy BIOS mode network card, then SmartDeploy is going to detect that it's in Legacy BIOS, and then deploy the image in BIOS mode. Your system will then restart, back into it's normal UEFI mode and thus won't be able to boot. You should be able to manually enable the UEFI Network Stack in the System Settings, but keep in mind that there is additional configuration needed to PXE boot and deploy devices with WDS in UEFI mode.
  17. Aaron, So I understand this correctly; You're creating your virtual machines and then capturing them on your local workstation, and then copying/importing the WIM file to your SmartDeploy console on the server, yes? If you create USB media, boot to SmartDeploy and deploy your image, does it succeed? Are your clients that you're attempting to deploy to via WDS in UEFI mode?
  18. Nicholas; Can you tell me which version of Windows you're running? Regarding your questions: Are there new Hardware Requirements/Recommendations for those who plan to use this feature moving on? --No specific requirements regarding hardware that we have run across. Does the size of Application Packs reflect on the amount of memory used during deployment? --Yes and no. We are streaming the application package to the device over the network. The streaming mechanism automatically allocates memory for the download and flushes to disk when appropriate. When deploying to a group of computers, is there a predetermined amount of computers that receive that pack at once, or is the number determined by the size of the pack and/or the amount of memory in the host system? --We process messages in chunks of 5. Meaning you can deploy to 20 machines and it will do four loops to get all 20. If deploying a large application package it will take a while to get through them all as we wait for the file to download before continuing. When deploy an Application Pack to a group of computers, does client get it's own session, like a unicast, or do they get the same packets at the same time, like a multicast? --Unicast session to each device, so yes could take up some network bandwidth.
  19. Sorry, but using PowerShell to invoke any SmartDeploy actions is not possible.
  20. Hi Nicholas, Thanks for sharing this.I'm taking this back to the dev team, but can you share with me the software you were deploying?
  21. In theory, if you were to export the VM from the Server Hyper-V host, and Import it to the Hyper-V console on your Windows machine, and the VM is able to boot and run successfully, there'd be no reason why it wouldn't successfully Sysprep. There's not a rule against that, that I've heard of.
  22. Worcestersoftware; Thanks very much for sharing this. I will make sure this gets shared internally and tested as a reliable solution. I believe this is similar to the solution when Windows 10 sysprep was broken in v1511, if I'm recalling correctly. We have noted 2 different sorts of failures; one resulting from what is best described as a "bad upgrade" where the sysprep logs will have grown over 85MB in size.
  23. Boomerman; Our recommendation is to always build a new VM when looking to deploy a new major version of Windows 10. The upgrade processes of the Spring/Fall updates has consistently, yet unpredictably broke the Sysprep process in which we rely on.
  24. That is certainly pretty odd. If you can, I'd reset my password, wait before reconnecting my local system to the account, and re-upload. Check to see if the image stays where it's supposed too, and then reconnect your local OneDrive app.
  25. Hey Stephen, You can indeed install SmartDeploy on a host at each site, and configure the local clients to point to that host, copy the image to the local network, and then create an Answer File and Deployment Package that points to the local image and perform deployments that way.
×
×
  • Create New...