Jump to content
DeployCentral

SmartDeploySupport

Administrators
  • Posts

    904
  • Joined

  • Last visited

Posts posted by SmartDeploySupport

  1. Hi awaisner,

    This typically indicates (as you seem to have inferred) that something is interfering with the installation script for the Windows Assessment and Deployment Kit - typically, this is caused by either antivirus software or domain security policy blocking VBScripts.

    You can bypass the requirement by installing the ADK directly. We are currently using the ADK for Windows 10 Version 1803, which you can download directly by clicking this link:
    https://go.microsoft.com/fwlink/?linkid=873065
    (direct link to bootstrap installer)

    You'll need to install the Deployment Tools, Windows Preinstallation Environment (both x86 and x64), and User State Migration Tool (USMT). Once the ADK installation is complete, you can proceed with installing SmartDeploy.

    Alternately (or in addition to the steps above), you can try disabling any antivirus software or pulling the host off the domain and see if it resolves the behavior.

    Feel free to reach out to us at support@smartdeploy.com if you have any questions or issues.

    Glenn
    SmartDeploy Support

  2. Hello,

    According to your answer file, it's looking for \\AND-SMARTD-01\E$\SmartDeploy\Scratch\NaviSite Image.swm which is not the share you should be browsing to via the Answer File Wizard. That's where SmartDeploy temporarily writes the file, not the permanent location. 

    From log:

    3/11/2020 4:30:32 PM : 1  : .ctor,ParseAnswerFile,WriteToLog : The answer file specified image file '\\AND-SMARTD-01\E$\SmartDeploy\Scratch\NaviSite Image.swm' but the image file could not be found.

    You will want to recreate your answer file and browse to \\AND-SMARTD-01\E$\SmartDeploy\Images\NaviSite Image\NaviSite Image.swm

    Your location path to the Platform Packs is incorrect as well. It is also attempting to read the scratch directory.

    From log:

    \\AND-SMARTD-01\E$\SmartDeploy\Scratch\

    You will want to make sure that's \\AND-SMARTD-01\E$\SmartDeploy\Platform Packs, again not using the scratch directory. 

    Also, it looks as though the existing partitioning on the Latitude E7250 should be recreated. Once you boot from your boot media in the SmartDeploy boot environment click the link to open a command prompt in the white area of the SmartDeploy menu. Type the following

    Diskpart  
    select disk 0
    clean [this destroys all data and partition/volume info]
    create partition primary
    active
    format quick fs=ntfs
    assign
    exit 

    Redeploy and let us know your results.

    Thanks,

    Devon

    SmartDeploy Support

     

     

  3. We perform a wmi query on the motherboard to view the devices and IDs, serial number, etc. If you're curious you can download the script we run yourself here.

    Run that on the target machine and it will output a wmi.txt in the same directory you ran it from. You can then open the vbs in notepad to check it out. The wmi.txt is the output we use to create Platform Packs.

     

    Thanks,

    Devon

    SmartDeploy Support

     

  4. Bam,

    On the Select Image page can you click Browse -> Network and map the share to Z:\ successfully? If FQDN doesn't work, please try mapping via IP address to ensure there are any DNS issues. 

    If you still have issues, we would need to see log files. Dismiss the Deploy Wizard so you're returned to the SmartDeploy menu and click Collect Logs. Save the resulting zip and submit a ticket here and refer to this forum post.

    Thanks,

    Devon

    SmartDeploy Support

  5. Hi Bam,

    When you boot from your boot media into the SmartDeploy boot environment, do you have an IP address in the bottom right corner? Be sure you do as that will let you reach your image.

    We also see this occur if your credentials expired in your answer file and no longer and reach the network share to pull the image. Can you manually map the network share in PE? If so, try recreating your answer file with your latest credentials. 

    Let us know your results,

    Devon

    SmartDeploy Support

  6. Hi Sergio,

    Unfortunately, from what I can tell, there is no officially supported method to uninstall Office via command-line. It's possible you may be on the right track with the msiexec /x command, but you'd likely need to identify the MSI file that Windows retained when the software was installed...if the MSI was indeed retained (Office may be a special case, since it is often installed with a click-to-run installer).

    This thread may point you in the right direction, although it's unclear if this framework still applies to Windows 10.

    https://superuser.com/questions/473569/where-does-windows-store-msi-files-for-uninstallation
     

    Bottom line, if you're able to identify a command-line to uninstall Office, you should hopefully be able to push that out with an Application Pack - but finding the command-line is the first hurdle.

    Glenn
    SmartDeploy Support

  7. Just to clarify, you changed the SmartDeploy host name and want to point the clients to the new hostname, correct?

    If so, 

    •     Download the attached file, EditClient.txt.
    •     Open the file in Notepad, and add the new hostname or IP inside the quotation marks, as indicated here:
      28944
    •     Re-save the file as EditClient.vbs.
    •     Run the script on each device that currently has the SmartDeploy client installed, and it should now be pointing to the new hostname or IP. Alternately, you can push it out with Group Policy.

    Thanks,

    Devon

    SmartDeploy Support

    EditClient.txt

  8. Hi Tyler,

    We have seen this happen due to Windows Updates being in a bad state. Please perform the following:

    • Start the virtual reference machine and run Windows Updates. Install all updates.
    • Restart the virtual reference machine via the Start menu
    • Once back at the desktop, check open Windows Updates and select Pause Updates
    • Restart the virtual reference machine
    • Open Windows Store and check for updates and install them by clicking the dots in the top right corner
    • Open Windows Updates and resume the updates and check for more Windows Updates and restart again if any are found
    • Open an administrative command prompt and type: shutdown.exe /s /t 0
    • Recapture/deploy and let us know your results.

    Thanks,

    Devon

    SmartDeploy Support

  9. Hi Dejeon,

    Not a stupid question at all! Licensing is per deployment. 1 license is used per 1 unique deployment and it's tracked via the machine's hardware. You can re-image the same machine as many times as you want with any operating system we support and still only use 1 license. Renaming does not affect licensing.

    For more information regarding licensing be sure to read our licensing page here. Some users find the FAQ section at the bottom of the page helpful.

     

    Hope that clears everything up!

     

    Thanks,

    Devon

    SmartDeploy Support

×
×
  • Create New...