Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Posts

    904
  • Joined

  • Last visited

Posts posted by SmartDeploySupport

  1. Hi Tim,

    If the console and target device are unable to communicate after 5 minutes of trying, then the Connection Type should change from Local to Cloud automatically. Is it possible that the console is still reachable from the target device? Is it perhaps on the same domain, or connected via a VPN? 

    Glenn
    SmartDeploy Support

  2. Hi Tim, 

    When you say you couldn't get the computer to show up with a Connection Type of Cloud, does this mean the computer was in the console with the Local connection type, or does it mean that the device failed to show up at all? 

    Just for a bit of context, the console will preferentially select Local deployment over Cloud - if the device is reachable over the same network, it will not attempt to perform a Cloud deployment. So if you're testing cloud deployment with an on-prem device that is on the same network as your SmartDeploy console, this would not be a viable test of the Cloud Broker. 

    Glenn
    SmartDeploy Support

  3. Hi Tim, 

    This is accomplished via the Cloud Broker, which is a deployment option available (in beta) as of SmartDeploy version 2.0.3010 (a couple versions ago as of this writing). It's accomplished using the same SmartDeploy client that you would use for local/on-prem console-initiated deployment. Computers with the client installed will appear in the Computer Management view, and there is a new column in this view called Connection Type. If a target computer cannot be reached over the local network ("Local"), then it will appear as "Cloud". The target computer (in your employee's home, e.g.) will have to be powered on and have an internet connection, but other than that, it should behave exactly the same way as an on-prem console-initiated deployment. You right-click the device in Computer Management, click Deploy, and select either now or scheduled, and select a cloud deployment package (which you would need to precreate). See the section starting on p. 38 in the User's Guide for details on creating a cloud-based answer file - this answer file can be used with any media type, including USB (if you want the user to be able to initiate the cloud deployment from their end), or deployment package (for console-initiated deployments). 

    If you have any questions getting started, please feel free to open a support ticket or email us at support@smartdeploy.com.

    Glenn
    SmartDeploy Support

  4. Hi Tom,

    Thanks for reaching out, happy to explain.

    This setting has been deprecated as of a few SmartDeploy versions ago. Microsoft changed the default behavior with regard to the local admin account in Windows 10, so a checkbox no longer made sense, as it would not behave in a consistent manner across different OS versions. We removed the checkbox, and now we simply check your image to see whether the VM had the local Administrator account enabled, and then we duplicate that result on the target device. If it was enabled, it will be enabled - if it was not, it will be left disabled. No action required on your part.

    There is still an item for this setting in our answer files to maintain backward compatibility, but it is no longer used at deployment time. Our expectation is that this setting should not cause any problems at deployment time for you (it's been this way for a while now), but please feel free to reach out (support@smartdeploy.com) if you have any questions or issues. 

    Regards,

    Glenn
    SmartDeploy Support

  5. Hi Dan,

    We'll need to see a logset from this device in order to troubleshoot further - please submit one via the support form. 

    Please boot to SmartDeploy media on the affected device (ideally with USB boot media with no answer file, to avoid starting another deployment and wiping the previous logs), click the Collect logs option, save the resulting zip file to an external location, and submit it via the Support formIn your ticket, be sure to include a link to this DeployCentral thread. 

    Glenn
    SmartDeploy Support

  6. The last thing that happens in the setupapi.dev.log pertains to McAfee.

    SetupCopyOEMInf - C:\ProgramData\McAfee\Agent\Evaluation\ENDP_GS_1060\Install\0000\x64\mfenlfk.inf

    cmd: "C:\ProgramData\McAfee\Agent\Evaluation\ENDP_GS_1060\Install\0000\\mfehidin.exe"

     

    I would try deploying an image that does not contain McAfee at all.  We've seen security software get in the way of mini-setup before.  It's usually best to install it as a first boot task.

    If you need a clean Windows 10 1803 image to test with we can provide one directly to you.

  7. Once the bluescreen happens, reboot the machine back to SmartDeploy.  At the splash screen, click Collect Logs.  Save the resulting .zip to USB or Network and email it to us.  support @ smartdeploy.com

    Additionally, open a command prompt, change to where Windows is installed, usually C:\ or D:\ and then see if there is any *.dmp files in \Widnows\Minidump.  If there are are, please send us those as well.

  8. Hi camlen92,

    Thanks for the update! You're likely not the only user to run into this issue, so hopefully this will be helpful for others. Unfortunately, the updates to the Sysprep\CopyProfile procedure (which has been around since the 1990s) have been a bit piecemeal - the entire procedure touched so many different parts of the OS, that different aspects of it have been deprecated (with or without any accompanying documentation) as each product group has changed its approach to deploying that particular setting over time. At least that's our best best guess in our long experience dealing with changes in Windows deployment over time. 

    If you ever hit a wall with how to deploy a particular setting, please feel free to reach out to support@smartdeploy.com - we're happy to work with you further to try and find a solution for your specific need. 

    Regards,

    Glenn 
    SmartDeploy Support

  9. Justin is correct.

    We do have a build in test that is successfully deploying 1809, but Microsoft has pulled the 1809 update as well as from the Windows 10 Media Creation tool. We want to ensure SmartDeploy on the latest build of 1809, so once they do, we will ensure our build works with Microsoft's latest ISO. As of today the update is still pulled.

    I would suggest building a fresh virtual reference machine with 1803 Windows 10 media then capture/deploy that or wait until MS releases 1809.

    Sorry for the inconvenience, but it's something we cannot control at this time. Once MS releasing a final build and we will test it and will announce to our customers that we support it officially. 

  10. Hi Dustin,

    SmartDeploy supports the following virtualization software:

    • Citrix® XenServer™ 5.0 or newer
    • Microsoft® Windows Server 2008 R2 or newer with Hyper-V (Generation 1)
    • Oracle® VM VirtualBox™ 3.2 or newer
    • VMware® ESX 4.0 or newer
    • VMware® Player 2.5 or newer
    • VMware® Workstation 6.5 or newer

    If the virtualization software supports snapshots and you decide to create a snapshot you will have to capture the virtual machine via warm capture. 

    support.smartdeploy.com/kb/article/35-performing-a-warm-capture/

    I hope that answers your question,

    Thanks,

    SmartDeploy Support

×
×
  • Create New...