Jump to content
DeployCentral

Jeff Harris

Administrators
  • Content Count

    128
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About Jeff Harris

  • Rank
    Support Team

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Jeff Harris

    Application packages

    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.
  2. 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.
  3. Jeff Harris

    Application Packs

    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.
  4. Jeff Harris

    WDBoot.sys BSOD

    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.
  5. Jeff Harris

    WDBoot.sys BSOD

    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?
  6. 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.
  7. Jeff Harris

    Initiate deployment via powershell

    Sorry, but using PowerShell to invoke any SmartDeploy actions is not possible.
  8. 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?
  9. Jeff Harris

    Importing GI from another machine

    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.
  10. Jeff Harris

    Windows 10 1809 - Sysprep Fail

    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.
  11. Jeff Harris

    Windows 10 1809 - Sysprep Fail

    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.
  12. Jeff Harris

    Cloud Deployment disappearing

    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.
  13. Jeff Harris

    Deployment Across WAN Slow

    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.
  14. Jeff Harris

    remote agent

    Per the guide; you'll use the console to generate the MSI to install the client that will have information regarding your account in it. You can connect to the client at the remote site to do this. If the client can't connect to the SmartDeploy Console host on your main network, it will then look to the internet to reach our Cloud Broker service which will connect it with your host, in which you'll see the connectio type; Cloud. The client service will re-check connectivity periodically and attempt to connect via the local network.
  15. Jeff Harris

    remote agent

    You could have a VPN established to the remote site so that the endpoint could reach the SmartDeploy host, however it's not recommended to do it this way. If the SmartDeploy Client Agent is unable to reach the SmartDeploy Console Host on the local network, it will use the Cloud Broker service to reach the SmartDeploy Console host. Clients in this configuration will list “Cloud” in the Connection Type column in the Computer Management workspace. If it's not appearing in the Console, contact support to make sure the feature is enabled for your account, and that you're on the latest version.
×