Jump to content
DeployCentral

Search the Community

Showing results for tags 'wds'.



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

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

Found 6 results

  1. WDS Multicast error

    So I keep getting this error code when attempting to multicast: 3240165637. I can unicast fine and have been able to use multicast from my WDS before.
  2. While imaging less than 10 computers at a time (sometimes less than 5 computers), we are getting reports from our network infrastructure team that network bandwidth is maxed out and saturated to the point that all users on campus cannot utilize any network assets. We have a 1GB backbone/switches throughout campus and all imaging communication resides on premise inside our DMZ. We usually image via unicast to our WDS server and expect to be able to image up to ~25 without speed issues before going with multicast transmissions, but are still having network speed issues with less than 10 at one time. We have been able to image successfully in the past without speed issues, but we are trying to pinpoint what has changed since then causing our bottle-neck. Our image size has actually decreased in size to 10.4GB. Any input is appreciated.
  3. Hello, I am trying to deploy an image via Windows Deployment Service and so far the image has been applied to client machines. However, platform packs and Smartdeploy.xml is not being applied to the machine after the imaging process. As a result, the image doesn’t have any drivers installed including the network card, graphics card and etc. My question is: What is the exact location that I can put the platform packs (default.ppk) and .xml file in WDS server so clients will point to it while deploying the image. I tried putting a driver package to WDS server under Drivers and I was getting an error: “E:\RemoteInstall\Images\Default.ppk is not a directory. Please enter an existing directory”. Any help would be appreciated. Thank you.
  4. Customizing Windows PE

    I'm currently using Smart Deploy along with a WDS server for PXE booting and Multtasking (works great and I'm loving it). However I'd like to customize the Windows PE enviroment some to allow for other tools besides Smart Deploy to be used in the Win PE enviroment. I'm thinking specifically of DiskWipe, and possibly some anti-virus and malware tools that would benefit from running in the Win PE space. Right now I've got a drive of tools automatically mapping on the network with a custom XML file (this also maps the imaging folder), and I can hit shift+F10 to get to the command prompt to launch the tools. I'm wondering if there's any way to further customize the Smart Deploy Win PE enviroment in order to make getting to these tools more convenient. Obviously I can create my own Win PE and put the tools there and use that to boot, but I'd prefer something more consolidated. Thanks Greg
  5. 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!
  6. Automating WDS Image Deployment

    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
×