Search the Community

Showing results for tags 'platform packs'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Windows Deployment
    • SmartDeploy Enterprise
    • General Deployment Discussion
  • Deployment Components & Tools
    • SmartDeploy Imaging Component (SmartWIM)
    • SmartDeploy Virtual Disk Component (SmartVDK)
  • Knowledge Base
    • SmartDeploy Enterprise

Calendars

  • Community Calendar

Blogs

  • Smart Image Deployment
  • Devon's Blog
  • Allen's Blog
  • Erik's Blog

Found 3 results

  1. Why are there no platform packs for so many modern machines? For example, I have many Intel NUC5i5RY models with 16GB RAM and SSD drives, that will happily run Windows 10 and are supported however,I cannot use Smartdeploy to deploy to these because the only platform packs are for Windows 7 (so with no platform back, after network deployment starts and the machine loads SmartPM it has no network and thus cannot deploy). This is just one example of the limits we are running into with this software. Support is frequently not helpful and seem like they are just in a hurry to get you off their back. Anybody else having similar issues?
  2. I frequently encounter Platform Pack corruption upon updating or downloading platform packs (several SmartDeploy servers with different internet connections exhibit this). This morning, for instance, after kicking off a number of platform pack updates last Friday, I went to build media, and was warned that 4 of the platform packs were corrupt. I It looks like the download may be getting interrupted. I really like the new feature that shows when an update is available, and the ability to right click and select "update". Would it be possible to eventually implement some sort of automatic check that a downloaded/updated platform pack is viable?
  3. After deploying over a hundred computers, this is the problem that seems to crop up the most. I'll download the platform pack specified for the computer models, or I'll have to make one, and then, after deploying the imaged and reporting that it was done successfully, the computer in question will start to boot Windows, then get a blue screen and reboot. Unfortunately, there is no way to record this, as it happens too fast to either get a picture of or write down the error code. It seems to be related to platform packs, as when I make alterations to the pack in question or make a new pack, it sometimes will fix the issue. An important note about the new packs is that they rarely contain the same drivers. And sometimes I stuff different platform packs into one pack, without the model differentiation that is possible and recommended to set up. This is normally what works the best. It's just time consuming and doesn't always work. Is there anyone that can shed some light on why this happens in the first place or a fix for it? I assume it's because of a missing driver or something, but it shouldn't keep it from booting in the first place.