Search the Community
Showing results for tags 'smartpe'.
Found 4 results
Hi there, Just starting the trial period to see if this is something that will work in our environment before purchasing, on paper seems good, it's the gotchas we are trying to work out. We virtualize everything, and for testing purposes I'd like to use VMs to ensure that everything is working. I'll skip the "not being able to have VMware Tools" in the image which makes it impossible to mouse control the gold image, so I'm leaving them until the image is built, and then removing, rebooting, exporting the VMDK from vSphere and then capturing from there so I can at least get an image. Unfortunately after creating boot media and starting a new VM up using that so the SmartPE environment loads, it's mouse only. Cannot use the keyboard to navigate between the options of "capture an image", "deploy an image" etc and the mouse control is crazy. Tried differen things such as using VMware Workstation to attach to the console, using the VMware Web Console etc, but it's uncontrollable. I did on one change by madly clicking and moving the mouse very slightly each time get into the Deploy an image, but as I am testing deploying from cloud I was never able to successfully click into the folder that the image was stored and download. Surely it cannot be impossible to test this on a VM environment? If it can only be tested on physical hardware then it's a non-starter, our EI deployment team does a fair bit of telecommuting and if we can't work on this remotely then we can't work on it at all. And why not, lets get back to the "no VMware tools" in the image as you won't let me capture it. We are looking at a replacement for VMware Mirage, and the gold image there is kept in vSphere, with the VMware Tools installed, and that image gets captured and pushed. Nothing stops us (or you including as an option) of adding a script post-deployment to uninstall any instance of VMware tools if it is required. It's like the option for no snapshots. I'm not going to leave my image builders in the lurch of not being able to roll back from any mistakes, of course I'm going to use snapshots, and of course I'm going to deploy the gold image in vSphere so it can be backed up. This is not a terrible burden, except that to capture a machine with snapshots from what I've read I have to use the SmartPE environment and do the capture from there. Great.. except I can't because it's a mouse-only application and you don't have the VMware Tools in the SmartPE environment so I can't capture that way. There must be something simple I'm missing and can't find because I'm not reading documentation thoroughly, and unfortunately the getting started videos seems to be of the "click this, this, this and this" which is great if there are no issues, if the environment the customer is using is exceptionally simple and only like the one in the video. Sorry for the overly long message, been a long two days trying to get a working option to show for Monday and there's clearly great technology here, but getting to it and using it safely (e.g. snapshots, central images, testing in VM environments) is seeming to be a tad frustrating. Thanks Chris
Hello, I captured an image from a Windows 10 1703 64-bit reference computer. When I deploy (through WDS) I get the message "SMARTPE (32-bit) is required to deploy a 32-bit image". I know for sure that the reference computer is 64-bit, I created a Smartdeploy 64-bit media to boot and I use the latest version of Smartdeploy. I have no problem to deploy a Windows 10 1607 64-bit image. Can anyone help? Thank youi! Maarten.
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!
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