Jump to content


winoutreach5

Established Members
  • Content Count

    43
  • Joined

  • Last visited

  • Days Won

    1

winoutreach5 last won the day on December 20 2012

winoutreach5 had the most liked content!

Community Reputation

2 Neutral

About winoutreach5

  • Rank
    Advanced Member

Profile Information

  • Gender
    Female
  1. I was testing a few things out in my own lab environment to recreate the scenario you are in in an attempt to reproduce the error you are experiencing. I, unfortunately, could not recreate it. So, with that said here are a few things to check -- first, have you pulled the network driver directly from the manufacturer’s site? For example, if the NIC is integrated have you check with Realetk, Intel or whoever makes the NIC in question? Presuming that the issue does lie within the driver store there are a few things you will also want to check; there are three steps in the driver injection process and each one needs to be verified. I understand you have already check the ZTIDrivers.log, but just to confirm the other 2: · Were the needed drivers copied locally by ZTIDrivers.wsf? · Did SETUP inject the drivers into the driver store? · Did PNP install the drivers from the driver store? The log files to review for the driver store are ZTIDrivers.log, setupact.log, cbs.log and setupapi.dev.log Also, while looking for a solution to your problem I came across this thread from the TechNet forums in which Johan helped a poster with a similar issue to your own by checking the driver store; it might be worth it to check the thread out and see if any of Johan’s tips assist you. Finally, I would strongly recommend upgrading, if possible, your MDT Toolkit version to the latest version as driver injection stores as well as other features have been improved greatly. I understand your need for approval in your situation but I do feel that upgrading to the latest toolkit version could help alleviate some of the issues above in addition to significantly simplify your hybrid image deployment process. Keep me posted! Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet
  2. I have a few questions regarding your post. First, is there a particular reason why you are using MDT 2010 Update 1 as opposed to MDT 2012 Update 1 or MDT 2013? If you are deploying Windows 7 and later, you should be able to use MDT 2013. My next question is regarding the C:\Drivers\Nic directory – is this a directory you created? I ask because the directory you specified is not a default directory for drivers. You might want to also check out the setupapi.dev.log for troubleshooting drivers. Typically speaking, you would import the needed drivers into the out-of-box drivers in your deployment share and then you will want to select the selection profile in the desired task sequence. More on Out-of-Box driver management can be found in this TechNet blog article. Keep me posted! Jessica Windows Outreach Team – IT Pro
  3. According to the TechNet blog post, Configuration Manager PXE Service Point Errors, the error code 0xC1030104 could imply that your WDS Server is actually not configured properly. I believe RocketMan is on the right track, however another step you could try is to initialize the server at the command line by running the following command: “wdsutil /initialize-server /REMINST:"D:\remoteinstall" (without quotations) where D:\remoteinstall is the directory that Configuration Manager had configured WDS to use. You also might try to stop and restart the Windows Deployment Services Server in the services.msc to see if that will resolve your issue as well. Keep us posted! Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet
  4. Hi Snehal, The first link in my response offers two unattend.xml files. Within those files, you will find lines you can add to your unattend file within Windows SIM. An excerpt from an unattend.xml file for x86 can be found below: (Please note, this is put in the oobeSystem settings pass) <SynchronousCommand wcm:action="add"> <CommandLine>%windir%\Distribution\Bitlocker\EnableBitlocker.vbs /on:tpm /rk /promptuser /l:%windir%\Distribution\Bitlocker\enable.log</CommandLine> <Description>Enable Bitlocker with TPM only and create recovery password and recovery key</Description> <Order>3</Order> </SynchronousCommand> Please let me know if you are looking for something else. Thank you, Jessica Windows Outreach Team – IT Pro The Springboard Series on TechNet
  5. You might want to check out the unattend files available from the MSDN page here as they may be able to assist you with configuring settings in your own unattend files depending on the type of operating system and architecture you are deploying. Also, since you have a dedicated server for WDS you might want to consider using the Microsoft Deployment Toolkit (MDT) for both the imaging process as well as the deployment process. First off, MDT is free. MDT can integrate directly with WDS and can be setup to PXE boot for both a Sysprep and Capture task sequence and lite-touch deployment. While I understand you do not want to recapture the image, MDT greatly simplifies the sysprep and capture process. Next, MDT can be used to deploy Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008 and Windows Server 2008R2. Using MDT, you can easily add both applications and drivers, manage Windows updates, create task sequences, prompt for a computer name, join a domain, add a KMS or MAK product key, create an administrator account, specify time zone, etc. You can also import all user data into the new environment using the User State Migration Tool (also free). In addition to creating standard client task sequences, as stated above, you can create sysprep and capture task sequences that will do just that – sysprep and capture an image of your reference machine. To become familiar with the process of using MDT, you might want to check out these videos from the Springboard Series page on TechNet: Deployment Day Session 1: Introduction to MDT 2012 Deployment Day Session 2: MDT 2012 Advanced Hope this helps and keep us posted! Jessica Windows Outreach Team – IT Pro
  6. The more information you could provide about your setup and how you are attempting to run setup, the better we will be able to assist you. From the limited description of your process and the error you are encountering, I have to wonder if you are running sysprep with the /generalize switch. The generalize switch removes all system specific information, including the computer name, which would then cause Windows Welcome to prompt for computer name after reboot. More on how sysprep works can be found on from the Springboard Series on TechNet article here. Keep us posted! Jessica Windows Outreach Team – IT Pro
  7. As Btag stated, you will need to ensure that the system is properly joined to the domain. I know you stated that you were able to join the machine to the domain but just to double check you will want to read the TechNet library article, Join the Computer to the Domain for assistance with this process. Also, you will also likely benefit from the TechNet article, Automating the Domain Join, as it explains the process of editing your unattend file to automate the process of joining a domain. Finally, when looking for a solution to your problem I came across this TechNet forums thread in which a few members suggest various ways to properly logon to the system as a domain user. Typically speaking, you will select the option to connect as an “other user” from within the Windows 7 logon welcome screen. When prompted for another user, you should see a username and password field. In the user name field you will type the following information in the following format: domainname\username As far as the password field is concerned, you will type the password for the domain user in to the password field. Also, for additional information on managing domains and configuring Windows Client you might want to check out the Springboard Series on TechNet. Jessica Windows Outreach Team – IT Pro
  8. You might want to look into using the Microsoft Deployment Toolkit (MDT). MDT acts as a common console for all of your images; plus, it’s free and it can be used to deploy Windows XP, Windows 7, Windows 8, Windows Server 2003, Windows 2008 and Windows 2008R2. Using MDT, you can easily add both applications and drivers, manage Windows updates, create task sequences, prompt for a computer name, join a domain, add a KMS or MAK product key, create an administrator account, specify time zone, etc. You can also import all user data into the new environment using the User State Migration Tool (also free). In addition to creating standard client task sequences, you can create sysprep and capture task sequences that will do just that – sysprep and capture an image of your reference machine. To become familiar with the process of using MDT, you might want to check out these videos from the Springboard Series page on TechNet: Deployment Day Session 1: Introduction to MDT 2012 Deployment Day Session 2: MDT 2012 Advanced You can also create bootable media directly from MDT since you will not likely go with the PXE boot method. Upon booting into the LiteTouchPE environment, you can select the image you wish to deploy, which task sequence you wish to use and then proceed to enter the necessary computer name and domain you wish to join. Also, if you don’t already have the Windows Assessment and Deployment Kit (Windows ADK) for Windows 8, I strongly recommend downloading it today. You will specifically want to pay special attention to the Windows System Image Manager (WSIM) as it offers an easy to use interface for editing your unattend.xml file. The Windows ADK will also come in handy if you go the MDT route. Hope this helps and keep us posted on your progress! Jessica Windows Outreach Team – IT Pro
  9. I am so happy to hear that, tmcgraw, and please feel free to let me know if you need any help in the future. Jessica Windows Outreach Team -- IT Pro
  10. Since the domain join usually happens as part of the task sequence after the deployment completes, I wonder what your BIOS boot order is set to. If every time your system starts and launches directly to your deployment share, then you may want to alter your boot order. It would be helpful to know how you are deploying Windows client via MDT and whether you or not you are booting to removable media or PXE connection. Regardless, you will typically want to ensure the hard drive is next in the boot list after the first boot option is not found so that Windows can proceed to boot into its OS and finish the specified tasks as a part of the selected task sequence. If you haven’t checked out the Springboard Series on TechNet, I strongly suggest you at least watch the following videos as you become more familiar with MDT and the deployment process: · Deployment Day Session 1: Introduction to MDT 2012 · Deployment Day Session 2: MDT 2012 Advanced Finally, anytime someone is attempting to do a capture process and / or deployment I always recommend the following videos: · Alphabet Soup Deployment: Understanding MDT, WDS, MAP, ACT, SCCM, and USMT · Deploy Windows 7 The Easy Way: Using WDS, MDT and AIK – Step-By-Step Hope this helps and keep us posted! Jessica Windows Outreach Team – IT Pro
  11. The Windows Assessment and Deployment Kit (Windows ADK) is the upgraded version of Windows Automated Installation Kit (Windows AIK). As you can see from the system requirements listed here on the Microsoft Download page for the Windows AIK, Windows XP and Windows Server 2003 are no longer supported but Windows Vista, Windows 7, Windows 8, Windows Server 2008, Windows Server 2008R2 and Windows Server 2012 are. You also might want to check out the Windows Deployment with the Windows ADK library document from the Springboard Series site on TechNet. You will want to uninstall Windows AIK prior to installing the Windows ADK to prevent any issues from arising. After you do that, you should be able to proceed with your deployment and migration. If you still need to be able to deploy and maintain Windows XP images for deployment, you might want to consider setting up a separate workstation with MDT and Windows AIK to maintain Windows XP deployment capabilities. You also might want to check the Deliver and Deploy Windows 7 page from the Springboard Series on TechNet as there are a great deal of resources available to assist with the migration process. Hope this helps! Jessica Windows Outreach Team – IT Pro
  12. Just as Jorgen touched on, you might want to take a look at the Microsoft Deployment Toolkit for your deployment and imaging needs. First off, it is entirely free and can deploy images via USB drives and DVD; it can even integrate with WDS for network deployments. In addition to the above, MDT can also manage multiple images, drivers, packages and software for nearly any Windows Operating system deployment including Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012. By using MDT in tandem with WDS you will be able to keep a thin image, which could be the base install.wim from the OS DVD. You can create a new standard client task sequence for the newly captured image of your reference machine and you can add all your necessary settings such as domainjoin, systemlocale, time zone, etc. You can then add all necessary drivers specific to each hardware configuration and MDT will install the proper drivers based on PnP calls. Applications can be installed as post installation tasks, so when a new version of an application or driver is released it can be changed in MDT easily. There is no need to refresh the image. Finally, you can integrate it with Windows Update or WSUS to make sure the deployment is fully updated; alternatively, you can put the updates into MDT as packages to be installed during deployment. To become more familiar with MDT you might want to check out the following videos from the Springboard Series page on TechNet: · Deployment Day Session 1: Introduction to MDT 2012 · Deployment Day Session 2: MDT 2012 Advanced Alternatively, should you still want a walkthrough for using WDS for deployments, you might find the Deployment Day Session 3: Deployment using WDS video helpful as well. Hope this helps and keep us posted on your progress! Jessica Windows Outreach Team -- IT Pro
  13. First, it always is helpful when we know what tool you are using for deployment. You mentioned that you are having trouble with a litetouch script but that your deployment is supposed to be zerotouch. When it comes to errors during deployment, it is always a good idea to check the logs first. If you are using the Microsoft Deployment Toolkit (MDT) or System Center Configuration Manager (Config Manager) for your deployment, you might want to read the Springboard Series TechNet article Inside Setup - Troubleshoot Windows Deployment Issues as it walks you through the process on how to check the log files and provides a link to where the log files can be found. Another library article that may also be helpful is Understand Failures and Log Files also from the TechNet page. Hope this helps and keep us posted on your progress! Jessica Windows Outreach Team – IT Pro
  14. To start, there is a great wiki on TechNet that describes, in detail, the process of adding a boot image to a WDS server. If you have other Windows 7 Enterprise installation media around, it might be a good idea to try and import the boot.WIM file from an alternate source as it is possible the disc you are currently using is scratched or damaged. Also, when looking for a solution to your problem, I came across this post from the TechNet forums site in which the poster had a very similar issue to the one you are currently experiencing. There are several suggestions in the thread which ultimately helped resolve his issue; it might be worth it to check it out. Another thought that you might be interested in is to check out the Microsoft Deployment Toolkit (MDT) because it acts as a common console for all of your deployments. First off, it is entirely free and can deploy images via USB drives and DVD; it can even integrate with WDS for network deployments. In addition to the above, MDT can also manage multiple images, drivers, packages and software for nearly any Windows Operating system deployment including Windows XP, Windows Vista, Windows 7, Windows 8, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and Windows Server 2012. By using MDT in tandem with WDS you will be able to keep a thin image, which could be the base install.wim from the OS DVD. You can create a new standard client task sequence for the newly captured image of your reference machine and you can add all your necessary settings such as domainjoin, systemlocale, time zone, etc. You can then add all necessary drivers specific to each hardware configuration and MDT will install the proper drivers based on PnP calls. Applications can be installed as post installation tasks, so when a new version of an application or driver is released it can be changed in MDT easily. There is no need to refresh the image. Finally, you can integrate it with Windows Update or WSUS to make sure the deployment is fully updated; alternatively, you can put the updates into MDT as packages to be installed during deployment. To become more familiar with MDT you might want to check out the following videos from the Springboard Series page on TechNet: · Deployment Day Session 1: Introduction to MDT 2012 · Deployment Day Session 2: MDT 2012 Advanced Hope this helps and keep us posted on your progress! Jessica Windows Outreach Team – IT Pro
  15. First off, congratulations on deciding to use the Microsoft Deployment Toolkit! Judging from your list of things you want, MDT will be able to meet all of your needs very easily. While MDT can be used for all deployments, including Windows XP, you will also be able to use it for Windows 7 and Windows 8. Through your research you may have already discovered that you can integrate MDT with Windows Deployment Services (WDS) which can help streamline deployment by allowing you to push images out via PXE boot. A good place to start when it comes to drivers and using the driver storage feature within MDT is with this blog post from the Windows Server Core team. Presuming your image files are in WIM file format, you should be able to import the desired WIM files into your deployment share within MDT and then create associated task sequences with all necessary settings. You may have already seen them but I always recommend the following videos from the Springboard Series on TechNet to become more familiar with imaging and deployment using MDT: · Deployment Day Session 1: Introduction to MDT 2012 · Deployment Day Session 2: MDT 2012 Advanced Hope this helps and please keep me posted on your progress and any questions you may come across! Jessica Windows Outreach Team – IT Pro
×
×
  • Create New...