Search the Community

Showing results for tags 'SmartDeploy'.



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 8 results

  1. In addition to a number of fixes and performance improvements, SmartDeploy Enterprise v1.1.4000 and later supports UEFI enabled devices, such as the Microsoft Surface Pro 3. If you’re upgrading from a previous version of SmartDeploy, you may notice a few changes. We’ve prepared this blog post to help you understand what has changed in order to make your upgrade process as smooth as possible. Simple SmartDeploy upgrade Simply download and run the installer. That’s it! Your previous SmartDeploy license key automatically carries forward into the new version. If you need to install SmartDeploy on a different computer and do not have your license key on file, email licensing@smartdeploy.com. Track your SmartDeploy license utilization SmartDeploy, like most enterprise software offerings, is licensed on a per-machine basis. You need a license for the total number of computers that you deploy with the software. You can login and see what devices that you’ve deployed through the SmartDeploy Licensing Portal. UEFI support requires Windows PE x64 There is a new dropdown available in Media Wizard to create x86 or x64 boot or deployment media. Support for UEFI requires an x64 WinPE environment, and this is now the default option in SmartDeploy. Optionally, you can still select an x86 environment to deploy x86 or x64 Windows operating systems to legacy devices. UEFI requires FAT32 media formatting UEFI is an industry standard replacement for legacy BIOS. All UEFI-enabled USB media must be formatted with a FAT32 file system. SmartDeploy has always used NTFS formatting for boot media but in order to support UEFI devices, we had to make this change. Existing customers that have WIMs or PPKs larger than 4GB should be aware of this change. As you may already realize, the FAT32 standard does not support single files larger than 4GB. If you select offline deployment media, SmartDeploy will automatically split WIMs that exceed the 4GB size limitation when you run the Media Wizard. However, if you have a PPK larger than 4GB, you will need to use individual PPKs. SmartDeploy can still process a Default.ppk file that is less than 4GB, but you no longer need to combine PPK files. Simply download each PPK and place them in the same directory. When you run the Media Wizard, browse to that directory and SmartDeploy will take care of the rest. Please note, if you’re currently using network (PXE) boot to distribute your boot image over WDS, or if you’re using USB boot media to point to an image that is stored on a mapped network drive, you don’t need to worry about 4GB FAT32 file size limitations. Your WIM files and Platform Packs will continue to work exactly as they did before. Download the latest Platform Packs We have updated nearly every PPK in the library to support the newer versions of our product as well as new drivers from the manufacturers. Please check the version of the PPK that you have against the latest version on the website. If there is a newer version available, it is recommended that you use that version. After you’ve updated you PPK library, simply re-run the Media Wizard before your next deployment.
  2. 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?
  3. I am getting the following error on a batch of 20 or so HP 8300 workstations when re-imaging them with Windows 10. One of my engineers created the image using SmartDeploy and incorporated the Platform Packs.. I've used my Image Disks for various flavors of HP systems in our environment (8000, 8200's, 8300's) with no major issues (total of about 500 machines) I had the installer verify the BIOS / Firmware levels and they appear to be the same. I'm going to have of the failed ones Fed-ex'ed back to me... Since SysPrep is failing our default admin acct hasn't been created and I can't login as administrator since the account is disabled (I can get around this with special boot disks) I'm wondering if a BIOS setting or a Fiber NIC card at this particular location would be causing this error. Anyone else encounter this or have any ideas? Thanks, Jeff
  4. Hi Support, SmartDeploy has announced that, from now on, the Platforms Packs will no longer be downloadable through the website as until now and they must be downloaded from inside the application. This "feature" effectively prevents those customers using older versions of the product from downloading new and updated Platform Packs, thus forcing us to upgrade to version 2.0 and completely redo our current platform in the next maintenance cycle, what will make us employ more time and efforts on it than usual. Furthermore, in my opinion making such announcement on a mid-August Friday at 18:01h is at least upsetting. I must say I'm very disappointed with this new policy. I expect you can provide us with a feasible workaround for this issue, so we can keep maintaining our current platform without having to completely rebuild it. Thanks in advance and best regards, -- Javier Llorente
  5. I'm trying to image a Latitude E7270 with Windows 7, but after the computer restarts after the setup, an error pops ups stating "One or more required services are not running." I hit ok and the computer boots up with the image but none of the drivers are recognized and the resolution of the display is incorrect. Has anyone seen this error before and found a fix? I've made sure that the all of the updates for windows 7 were installed in the reference virtual machine before capturing it.
  6. I am trying to re-image a client PC and every time smart deploy reaches the end of the set up process, a message pops up saying that "the drivers were not successfully injected into the computer." Despite this pop up the drivers seem to be installed in the computer and everything works fine. It's really not a huge deal just something that I would feel better about knowing it worked perfectly. Thanks. Does anyone know why this is happening? Is it a problem at all? Solution?
  7. Here are some handy logs and locations to check out if you run into any deployment issues. You can always view the following logs in: C:\Windows\Debug - Deploy.log is created by SmartDeploy Enterprise and will show you deployment errors that may have occurred with SmartDeploy. - Netseteup.log will show any issues with the deployed machine joining the domain. If you are running windows 7, the windows setup logs are located in C:\Windows\Panther If you are having issues with drivers on your deployed machine, be sure to check out C:\Platform\Dism.txt. This log will show you what occurred during driver injection. Of course, if you run into any issues when using SmartDeploy Enterprise, we'll be glad to help!
  8. SmartDeploy now fully supports OS image capture for deployment using Microsoft's Windows Deployment Services (WDS). Devon's blog does an excellent job of over-viewing the process to capture a WDS compatible SmatDeploy image file. The process is wizard-driven and truly extends the capability of the product. In a large computer lab settings, it is very desirable for you to be able to automate the deployment wizard using an answer file. For example, some of the large labs I support include upwards of 40 systems of a single hardware type requiring the same platform pack. I will discuss how to integrate an answer file into your SmartPE media to create a fully automated method of deploying a specific SmartDeploy Windows image file to a large number of computers that require the same image with the same platform pack. Below is a screen shot from the Summary page of the Deployment Wizard. This is step 16 on part 7 of Devon's How To Integrate SmartDeploy With WDS blog. Now go ahead an export your answer file using the 'Export' button. Then create a new SmartPE image file using the Media Wizard that incorporates your WDS answer file. This is the screen shot from step 7 of Part 2: How To Integrate SmartDeploy With WDS. Click the 'Browse' button to import your WDS answer file. Then complete the wizard creating your new SmartPE media. Now you will have be able to re-import your new SmartPE media containing the answer file into your WDS to further automate image deployment in a lab environment. Similarly, image deployments that require the same Deployment Wizard answers (including the image file and platform pack) could merit their own SmartPE boot image that contains each unique answer file. I recommend naming the PXE boot image a specific file name to make it obvious it contains an answer file and for which configuration (e.g. image file + platform pack + Lab_Name). You should be able to judge how many SmartPE boot images containing various answer files based on the frequency you use an image file and platform pack for deployment. The more frequent you use an image set, the more likely you will want a boot image that answers the wizard questions for you. Things to keep in mind: You can use the Platform Manager to combine multiple platform packs which could further limit the number of SmartPE boot images required for your scenario. If anything needs to change (path to the image file, platform pack, etc.) then you may want to edit the answer file and create a new SmartPE boot image for that different imaging task. Finally, if you don't specify a platform pack it will automatically integrate one named DEFAULT during the deployment process. By storing platform packs for specific models in the root image directory on your WDS then naming it DEFAULT, you could avoid changing the answer file except in cases of image path differences. Final thoughts. Integration of WDS is a leap forward for SmartDeploy and image deployment professionals. I welcome more time saving tips and walk-throughs to reach further development our community's best practices with SmartDeploy Enterprise. Aaron Lines IT Consultant