Jump to content


Established Members
  • Content Count

  • Joined

  • Last visited

  • Days Won


WinOutreach4 last won the day on October 18 2017

WinOutreach4 had the most liked content!

Community Reputation

2 Neutral

About WinOutreach4

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender

Recent Profile Visitors

1,500 profile views
  1. Have you removed the administrative shares on the machine? This Wiki article shows this as a possible cause of the error message that you posted. Have you tried the command line method of changing the folder location? wdsutil /Uninitialize-Server wdsutil /Initialize-Server /REMINST:”Z:\deploymentshare\remoteinstall” For the Invalid UNC path error, can you navigate to that path in a CMD window? Does it only give this error when enabling multicasting? If you don’t check the multicast box, does MDT accept this UNC path? Hope this helps, David Windows Outreach Team – IT Pro T
  2. Another method would be to use the UNC path. For example: \\server\folder\file The TechNet Article ‘RunSynchronous’ has examples of the XML with this path structure. Hope this helps, David Windows Outreach Team – IT Pro The Springboard Series on TechNet
  3. Jorgen is correct. You need MDT 2013 and the Windows ADK for Windows 8.1 in order to use MDT on a Windows 8.1 or Windows Server 2012 R2 computer. Hope this helps, David Windows Outreach Team - IT Pro The Springboard Series on TechNet
  4. I would recommend the Microsoft Deployment Toolkit (MDT). It is a free deployment solution from Microsoft and is very powerful. MDT can create media for deployment by USB devices or DVD, in addition to being able to integrate with WDS for those systems that can access your WDS server. MDT can deploy your custom WIM image easily, but it can be much more flexible and powerful than that. MDT can manage device drivers for hardware independent imaging, install software after Windows is deployed, edit the answer file, name the computer, join a domain, and much more. These two videos are a great
  5. According to the MDT help files, if you set UserDataLocation to AUTO: “The deployment scripts store the user state migration data on a local hard disk of space is available. Otherwise, the user state migration data is saved to a network location, which is specified in the UDShare and UDDir properties.” You should set UserDataLocation=NETWORK in order to get the file to save to the network location you have specified in the UDShare and UDDir properties. You could use the UNC path (not variables) for the UserDataLocation property, but based on your last post, just changing AUTO to NETWORK s
  6. WDS has a ‘Filters’ feature to help you manage your drivers specifically for situations like this. You can create filters to make sure that only the drivers for that model are used. The TechNet Article ‘Managing and Deploying Driver Packages’ has detailed instructions that should help you with creating your filters. Hope this helps, David Windows Outreach Team – IT Pro The Springboard Series on TechNet
  7. That should not be the case, however the ADK should not be installed on the same machine that the AIK is installed on, as that can cause problems. Do these models have Secure Boot turned on? According to the TechNet article ‘Secure Boot Overview’: “The firmware may not trust the operating system, option ROM, driver, or app because it is not trusted by the Secure Boot database”. You may need to disable Secure Boot and possibly change from UEFI BIOS to Legacy BIOS in order to deploy Windows 7 to these machines. Hope this helps, David Windows Outreach Team – IT Pro The Springboard Ser
  8. Since you say that you are having this issue during the boot to your LiteTouchPE_x64.wim file, I have to ask if you updated the deployment share and re-created the boot images in order to get the new drivers in the boot image, and replaced the boot images on your WDS server with the new ones? Hope this helps, David Windows Outreach Team – IT Pro The Springboard Series on TechNet
  9. From what you are writing, it seems that you are doing things in the wrong order. Replacing the boot images in WDS is the last thing that you should do. 1. Edit bootstrap.ini (either in the Control folder of the new deployment share, or by right clicking on the share name in MDT and choosing properties, rules tab, and clicking the button to edit the bootstrap.ini file) 2. recreate boot images 3. replace boot images on WDS with new boot images The bootstrap.ini file is placed inside the boot images during the regeneration process. So you must edit it first, then regenerate, then repla
  10. When you recreated your boot images, did you use those new ones to replace the current ones in WDS? Any time there are changes to the bootstrap.ini, the boot images must be re-created and the new ones have to replace the ones in use by WDS. The deployment share location is in the bootstrap.ini file. Hope this helps, David Windows Outreach Team - IT Pro The Springboard Series on TechNet
  11. While it is commonly referred to as the ‘Sysprep limit’ it is actually an activation reset limit. The TechNet article ‘How Sysprep Works’ has a section titled ‘Resetting Windows Activation’ that explains this in detail. To summarize, when Windows starts for the first time, it triggers the activation clock (30 days to activate Windows). So when you install Windows on a reference machine and start it up to customize, you have started the activation clock. When you sysprep this image to capture it, you have used the first reset (specifically, if you use the /generalize switch). Later, if you load
  12. You can use DISM to inject most updates to an offline image. This article from the ConfigMgrDogs blog on TechNet shows how this is done. MDT can inject updates during the deployment if you add the updates as packages, or you can set MDT to look to your WSUS server or Windows Update during the deployment to make sure it is up to date. Since you have some versions of Windows that can’t use WSUS, having MDT call Windows Update is probably the best solution for your situation. Another solution that I’ve seen used is to keep your base images running in VM’s, and when you need to update your
  13. Specifically, the setting <Extend>True</Extend> is what makes the partition use the remaining space. The Extend page from the Unattended Windows Setup Reference explains this in detail. Also, setting this as ‘False’ on other partitions is not necessary, as False is the default value. Hope this helps, David Windows Outreach Team – IT Pro The Springboard Series on TechNet
  14. Double click on the failed package name (in the first screen), and you can see details about that package. In those details you will see that this package is unsigned. You can also get more detail on the failure by trying to add the package manually. For example, from an administrative command prompt, use this command and replace “PathToDriver.inf” with the actual path to the driver and keep the quotes around it: WDSUTIL /verbose /Add-Driver Package /InfFile:”PathToDriver.inf” For this driver package, it returns: Error code: 0xC10301B3 Error Description: This driver package is not
  • Create New...