Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. When you create your Answer File, you'll be prompted to specify the location of your image, Platform Packs, and Answer Files. These shares do not have to reside on the SmartDeploy console host, they can be anywhere. When you create your Deployment Package, you'll include that Answer File. Any network deployments you start with that Deployment Package will use the paths in the Answer File to find your everything.
  3. Hello, You will want to create a single virtual disk file.This will allow for the SmartDeploy's Capture Wizard to select and capture the virtual disk to convert it into a .WIM. That being said, you can create split virtual disks, but it requires a warm capture in order to capture it. You can find out more about warm captures here. The reason you're seeing the Media Wizard split images is because it needs to split the WIM into 4GB splits in order to create Fat32 media. Fat32 is required for UEFI deployments. Hope that makes more sense now. Devon SmartDeploy Support
  4. Our SmartDeploy console is one one server (a VM just for Smart Deploy) and I'm planning to store the image files on a network share. My questions is, to do a network deployment, what files need to by copied to the network share? Obviously the image file. But what about the answer files, platform packs and deployment file? Do those also need to be copied over to the network share? Or do all those other files get sent directly from the console to the client as part of the deployment package? And after the client receives them and reboots does it then just need to get the image from the network share?
  5. I'm noticing when I create a new virtual machine in VMware it asks if I want to split the machine in multiple files or build as a single file. Also it looks like the deployment packages are splitting the previously made single file images. Is there a preference here for Smart deploy? cCapture 1 file as an image or capture multiple files as an image ?
  6. thanks Jeff. I'm testing different methods for gathering drivers for different machines. though keeping everything organized is probably best, for testing sakes, I'll try a single folder and see how it gets along
  7. Organizing them into folders is recommended, in order to make management and troubleshooting easier. However, it's not required.
  8. I've watched the short video on the creating custom fixture packs and have a question. Is the file structure more important for the user or the deployment process? I'm curious to know if I have most of my drivers saved from another machine, can I toss them in a single file ,build a fixture pack with it and let windows sort them out ? Or does it have to be structured so each driver is separated based on its purpose/use. hope the question makes sense. Thanks All !!!
  9. This happens shortly after I login. I will look into the ports. Thanks.
  10. Hello Chris Dietz, Does this occur right after you login? Or does this error present itself once you click Deployment packages. Please ensure the following ports are opened on your network: TCP 80 - HTTP TCP 443 - HTTPS TCP 8732 - ConsoleServiceWCF TCP 8733 - ClientServiceWCF TCP 8734 - ConsoleServiceSLWCF TCP 8735 – ConsoleServiceMCWCF If you still issues, we may need to take a closer look at your console.log located in C:\SmartDeploy\Logs from the SmartDeploy host machine. You can submit a ticket here. Please refer to this thread. Thanks, Chris SmartDeploy Support
  11. Has anyone seen the error attached before?
  12. This appears to have worked. I came back with an error the first time, asked if I wanted to run again, then proceeded to write the media successfully. Thanks Admin !
  13. I only have 1 usb drive . not sure if this would happen on other usb drives
  14. It may provide a different error/code that may be helpful to see what may be going on. Does this happen on all USBs? We would really need to see the media.log in order to see what is happening. Thanks, Devon SmartDeploy Support
  15. how is this different from using the DISK MANAGEMENT ?
  16. Try formatting the USB via via diskpart. Open an administrative command prompt and type the following: diskpartlist disk [determine which disk is your external USB stick, probably disk 1]select disk 1 [use the correct disk number here]detail disk [read the disk info; make sure you have your USB stick selected]clean [this destroys all data and partition/volume info on the selected disk]create partition primaryactiveformat quick fs=ntfs [Media Wizard will convert this to FAT32 later]assignexit Then relaunch the Media Wizard and attempt to create new media. If you still have issues send your C:\SmartDeploy\Logs\Media.log from the SmartDeploy host. You can submit a ticket here. Please refer to this thread. Thanks, Devon SmartDeploy Support
  17. I've reformatted my USB drive in every format, I've partitioned it to various sizes and the media wizard still hangs on which media type to use when creating a deployment package. The Media Wizard stalls with a message of " Checking removable drive properties, please wait ...." anyone experienced this ?
  18. OK thanks for the reply from both of you. I figured it out. The option I was looking for is in the deployment wizard.
  19. Chris, The image was not captured for WDS. You will want to capture your virtual reference machine via the Capture Wizard. During the process ensure you check "For use with WDS." This will ensure the image will be able to successfully be imported into the WDS role.
  20. You have to create a new WDS Deployment for WDS to work. It cannot use the Deployment media created within SD. Run the deployment wizard and select WDS, then proceed. It will put into a \Media folder under SmartDeploy.
  21. All, Tried to follow instructions to integrate Smart Deploy with WDS from the Smart Deploy site, but I am getting an error when trying to import the install image to WDS. Here is a screenshot of the error. Using hyper-v to make the vhds. Any clarification on capturing the image would be helpful. Thanks.
  22. Earlier
  23. Hello, I'm sorry you feel as though we are not helping and becoming frustrated. We cannot reproduce this issue on our end. I just replied again for you to perform a clean installation. Let us know your results after you follow my steps in your ticket. Thanks, Devon SmartDeploy Support
  24. Having the EXACT same issue! Tried SHUTDOWN /S /T 0 to no avail. No anti-virus software on this image. Completely blank slate image that was just created. And it won't let me import as a reference machine to get converted into a Smartdeploy image. Any answers???? @Chris Chandler @SmartDeploySupport
  25. Hello, We have created images in the past using Smartdeploys method. And it used to work flawlessly. But now, it keeps giving us the error that the registries are still in use no matter what we do. We have tried SHUTDOWN /S /T 0 multiple times. We checked the registries. There is no snapshots being taken. We created two other reference machines from scratch, didn't even boot up those images via VMworkstation, and they still can't be imported as a reference machine to get converted into a Smartdeploy Image. What is happening?! How can I fix this? Smartdeploy support isn't helping at all.
  26. I'm getting this exact same error, but only when trying to deploy Windows 10 Enterprise version 1903. I haven't tried an older version of Windows 10 Enterprise, but Windows 10 Pro (any version) is working fine. recapturing the image = same error even remaking the VM + image = same error. Smartdeploy version is 2.0.3050.10466
  1. Load more activity
  • Create New...