Search the Community
Showing results for tags 'Windows 7'.
Found 4 results
I see there are platform packs for the Intel NUC models NUC5i5RY and NUC5i7RY. I have many devices that are the NUC5i5RYH / 5i7RYH and am not able to deploy to these machines. There are very minimal hardware differences. Has anyone been successful with these models? It seems the platform packs should work, but alas they do not, in multiple tests. Thanks. N
Having a problem deploying an image from bootable media onto a Lenovo Thinkstation S30. I created offline bootable media with the Media Wizard and changed the boot settings but the USB drive won't show up as an option when I press F12. Secure Boot is disabled but I can't change UFEI or CSM. BIOS version is A2KT36AUS 01/09/2014. The computer came with Windows 8 pre-installed. I'm trying to deploy a Windows 7 image onto it. Does anyone have recommendations?
Devon posted a blog entry in Devon's BlogHere 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!
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