Jump to content

Gantlett

Member
  • Posts

    89
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by Gantlett

  1. If anyone could assist me with this I would greatly appreciate it. Thanks in advance.
  2. arr... Can you elaborate? Is my script missing something? Thanks again.
  3. Hi and thanks for your reply. Sorry for the late reply, for some reason I didn't get an email notification even though Im subscribed to this thread… Anyhoo, the article I linked above to certainly instructs to create a custom partitioning script and thats just what Ive done. After some tests, I found that the deployment works if the partition is pre-formatted to NTFS. So the problem is definitely in the partitioning script, I just dont know what it is… Heres the script Im running: SELECT disk 0 SELECT partition 3 FORMAT FS=NTFS LABEL="Bootcamp" QUICK EXIT
  4. Hello, I'm running MDT 2010 and Windows Deployment Services on a Windows Server 2008 SP2 x64. I would like to deploy Windows onto a BootCamp partition using MDT2010 and WDS. Since Macs won’t PXE boot from a Windows server, the way to get the Mac to boot into the WinPE environment is by burning the WinPE ISO to CD and booting the Mac from the bootable ISO. I followed the following guide to build the correct Task Sequence in MDT 2010: http://blog.physh.net/2010/02/deploy-windows-on-macs-using-mdt-2010.html I added BootCamp drivers to the distribution share and created a WinPE ISO using the above instructions. I can boot into WinPE and I have network access, however the LiteTouch process ends at the disk format stage with the following error: ZTI ERROR - Non-zero return code by LiteTouch, rc = -2147467259 0x80004005]LOG]!><time="02:16:14.000+000" date="09-13-2010" component="LiteTouch" context="" type="3" thread="" file="LiteTouch"> I’ve made some research and quickly found that this is a very generic error and basically doesn’t say much. I was able to grab the LiteTouch log files to take a closer look, but there’s no further information available. In WinPE, I manually ran the commands described in the DiskPartMac script and they work fine. Does anyone know why the process is failing? Thanks in advance.
  5. Hello, We have a client in a very small environment consisting of two sites, with two computers in each site. The client needs an IM solution, but the solution must support user restrictions. We must be able to restrict users from logging in using their personal IM accoutns and/or adding their friends. Does anyone know of such a solution? I've googled around but couldn't find anything. Thanks in advance!
  6. On an interesting note, looking at the NIC driver in the “Out-of-Box Drivers” section of the MDT2010 deployment share, it would appear that this driver is unsigned: the “This driver is WHQL signed” checkbox is un-ticked. This is not the case with the MassStorage drivers though - those are signed. So in that case, this means that if I wanted to integrate the NIC driver to the Windows 7 DVD boot.wim using any of the methods described at the first post in this thread, I would have to use the "/forceunsigned" switch, meaning the whole idea of using DISM is doomed for failure anyway... Just a thought.
  7. OK - I found an amazing solution! Did some more research and it turns out that my whole approach is wrong. The way to deploy Windows in our day and age is by using an additional tool together with WDS, and that is Microsoft Deployment Toolkit 2010. The idea is to use MDT2010 to create custom installations with drivers, applications and an install script, and use WDS purely as a PXE boot server to fire-off the custom install. I have to say, MDT2010 is the most amazing tool I have ever seen released by Microsoft! It's dead easy to use and does everything through an easy to use GUI! It just takes care of everything and I'm simply impressed by the incredible job they've done with the whole Windows deployment process (as far as Windows 7 is concerned). Just read through these simple guides to gain an understanding of how the two fit together and how to achieve super-easy deployments: http://edge.technet.com/Media/Deploy-Windows-7-The-Easy-Way-Using-WDS-MDT-and-AIK-Step-By-Step/ http://www.the-d-spot.org/wordpress/2009/11/01/windows-7-lite-touch-installation-with-mdt-2010/ http://www.the-d-spot.org/wordpress/2009/11/16/windows-7-lite-touch-installation-with-mdt-2010-part-2/ I used MDT2010 to create a custom install process which includes the injection of the NIC and SATA drivers required for my new Dell 980's and it worked like a charm! Cheers!
  8. Thanks for the replies guys. The driver I got is definitely from Dell - it's from the 980's driver downloads page. I'll try your suggestions and see if I get lucky!
  9. Hello everyone, I'm running Windows Deployment Services on a Windows Server 2008 R2 x64 system. Currently, we have two boot.wim images on the server which are working fine. These boot.wim files were taken "as is" from Windows 7 ISO's. We have a 32-bit one and a 64-bit one. The problem is that we bought a shiny new Dell workstation (OptiPlex 980), and when I PXE-boot this baby into WDS, WinPE starts to boot, starts loading the GUI with the blue Windows 7 background and then says that network drivers cannot be found. This brings us to my problem: I tried integrating the correct NIC driver into the boot.wim image, but I'm experiencing some issues. Here are the two methods I've tried integrating the drivers and their respective results: Method 1: 1. I installed WAIK for Windows 7 on a Windows 7 workstation. 2. Copied the original Windows 7 ISO boot.wim file to a local folder. 3. Ran the "Deployment Tools Command Prompt" (DISM) as Administrator 4. Fired off the following commands in the following order: a. DISM /Cleanup-Wim b. Dism /Mount-Wim /WimFile:C:\winpe_dell\boot.wim /index:1 /MountDir:C:\winpe_dell\mount c. Dism /image:C:\WinPE_dell\mount /add-driver /driver:"C:\Users\erez\Desktop\Optiplex 980 Drivers" /recurse /forceunsigned b. Dism /Unmount-Wim /MountDir:C:\winpe_dell\mount /Commit The result: Immediately after selecting the boot image in the PXE menu, a black screen appears complaining about a recent hardware change and saying Windows cannot start. Method 2: 1. Using the same WAIK for Windows 7 on the same Windows 7 workstation. 2. Fired off the following commands in the following order: a. DISM /Cleanup-Wim b. copype.cmd amd64 c:\WinPE_dell c. copy "c:\program files\Windows AIK\Tools\amd64\imagex.exe" c:\WinPE_dell\iso d. Dism /Mount-Wim /WimFile:C:\winpe_dell\winpe.wim /index:1 /MountDir:C:\winpe_dell\mount e. dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-scripting.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-scripting_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup-client.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-setup-client_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-setup-server.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-setup-server_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-wds-tools.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-wds-tools_en-us.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\winpe-wmi.cab" dism /image:C:\winpe_dell\mount /Add-Package /PackagePath:"C:\Program Files\Windows AIK\Tools\PETools\amd64\WinPE_FPs\en-us\winpe-wmi_en-us.cab" f. dism /image:C:\WinPE_dell\mount /add-driver /driver:"C:\Users\erez\Desktop\Optiplex 980 Drivers" /recurse /forceunsigned g. Dism /Unmount-Wim /MountDir:C:\winpe_dell\mount /Commit The result: WinPE starts to boot, starts loading the GUI with the blue Windows 7 background and then says that the setup language cannot be determined. Can anyone please point me to what I'm doing wrong here? Thanks in advance!
  10. Hi and sorry for the delayed response. Your suggestion did the trick! Thank you so much for your kind help!
  11. Hi and thanks for your reply I've edited the original post to include correct attachments. I tried attaching it to the server, and when that failed, I tried attaching it to the image.
  12. Hello, I am trying to set up an unattended deployment system for Windows 7. I installed WDS on Windows Server 2008 64-bit Enterprise Edition SP2. I compiled an answer file and applied it to the Server Properties\Client tab. However, the WDS client completely ignores the answer file. I tried removing the answer file from the Server Properties\Client tab and applying it to the install image, but the client still ignores the answer file. I was able to grab the log file from the client, and it looks like the answer file arrives OK. I have attached the WinPE client's X:\Windows\panther directory below, as well as the XML answer file: panther.zip WDSUnattend.xml What am I doing wrong? Thanks in advance!
  13. Hello I have a Server 2008 R2 x64 Windows Deployment Server running and I'd like to deploy XP and 7 through it. I would like to integrate mass storage and NIC drivers to the winpe.wim image. There are two ways of doing this: 1. Using DSIM to integrate the drivers to an offline WinPE image 2. Using Windows System Image Manager to create a distribution share with drivers, point an answer file to the driver path, and have WinPE query that path for drivers when WinPE boots up. I would like to use method 2, as it is more modular and easier to maintain - if a driver is causing problems, or if you need to add a driver, simply add or remove .inf files from the distribution share (I can't believe I'm saying this, but very cleverly done by Microsoft). No need to modify the boot.wim image. According to the Windows System Image Manager help, and according to Microsoft's TechNet AIK 2.0 guide, to add a driver path to an answer file, one must add to the answer file a component called Microsoft-Windows-PnpCustomizationsNonWinPE. This is where my problem is: I can't find such a component in the WinPE.wim image! It simply isn't there! My WinPE.wim file was created using copype.cmd x86 c:\WinPE_x86, so it's a clean file. I tried adding all the available packages, but that hasn't added any new components. I've googled and couldn't find anyone experiencing this problem at all. What am I doing wrong? Thanks very much.
  14. I need to be able to deploy an OEM version of WinXP Pro through WDS 2008. The problem is that when booted into WinPE to capture the sysprepped system, the drop down menu is empty when I try to capture an OEM system. This problem does not occur when I try to capture a VLK system. I found this MS article which states that MS don't support sysprepping an OEM system. How can I get around this problem and deploy an OEM XP image through WDS 2008? This is so annoying...
  15. Hi This thread can be closed because a few things have changed in my scenario - I have a new problem and I'll open a new thread for it. Thanks everyone!
  16. I looked into Linux solutions, but from what I found it seems that there's no proven way of doing this. I only found very complicated and vague guides. The problem is that I have a limited amount of time for this project and I can't mess around with it too much... I'd love to use any solution, as long as someone has had success with it.
  17. Since I must use Server 2008 (which will only support WDS, which will only support image based deployments...), I am worried that a syspreped XP image (made on a VM) will have hardware dependencies I can't predict. How realistic is my concern? I'm worried I might attempt to deploy XP to a machine and I'd get a "Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll. Please re-install a copy of the above file."
  18. Hello I am looking for a solution to install Windows XP and Windows 7 from a PXE server with a boot menu, where I can choose to install one of the OS's. In addition, I want the XP install to NOT be image based, rather it should run from a shared folder on the network. The reason I want XP to be installed from a network share, as opposed to an image, is that I want the XP install to be hardware independent. I tried installing WDS 2008. It plays very nice with Windows 7, but it only supports WIM based installations. Deploying XP through WIM format means deploying a syspreped image which will have some hardware dependency and I want to avoid that at all cost. I also want to avoid booting the target machines from a floppy disk - a PXE menu is the most elegant way I can think of to install an OS. How can I achieve this? Thanks in advance.
  19. Nuhi Thanks for your reply - I'd like to help you as quickly as possible, but I won't be able to do that in the close week or so as I'm too busy (pretending to be) working. I'll definitely try your suggestion after the pressure goes down a bit. Speeddyomn I had a look at one of the machines which asks for the XP CD every time a device driver is installed and the driver signing policy was already set to "Ignore" and "Make this action the system default" was already checked. Thanks. ------------------------------------------------------------------------------------------------------- As a side note, after reading the nLite EULA, and in light of this thread, all the machines running an nLited version of XP (and there are five such machines) are now scheduled for a re-install from the retail (non nLited) CD. By the way, the nLited machines all work great, aside from the ones with the WFP CD prompt. But even this problem isn't something that prevents users from working, so I can wait with the re-install till the weekend and do this in an orderly manner. Plus, I told my superiors about my mistake and how I already have a plan to remedy it, and not only are they not angry at me, but they were impressed with my honesty and professionalism and decided (among other reasons) to give me a raise. Just something for everyone to think about. (and just trying to extricate all the bad vibes, negativity, bad manners and poison one user has been trying to infect this thread with)
  20. Thanks for your help! I shall look into that. You said "who knows", well I was hoping I asked this question in the right place! (and I know I did) There are two weird things however: 1. This happens on some machines and not all. 2. I don't even understand why the ones that ask for the CD do that, since they too have a DLLCache folder... so theoretically there's no need for the CD because all the source files are already available locally... Thanks again in advance!
  21. jaclaz In that case - I apologize from the bottom of my heart. I did not mean to do anything unethical or unfair and I certainly did not read the nLite EULA lately. In light of this I will cease any use of nLite at work right from this minute. As for the above mentioned user (which should be BANNED from this forum for libel) - that is not accurate. It accused me of other things and very much deserves my wrath for being a cheeky little puppy. Attacking him is anything but needles, it is a must, as he was falsely and maliciously accusing me of illegal activities which I have no part of.
  22. You are the one here looking for help with the multiple illegal installations you did while pretending to be an IT guy and I'm being offensive? What you have done is highly illegal and hazardous therefore you should be, at the very least fired. If not brought up on charges. You are WAY out of line here, you who calls himself "kelsenellenelvian". 1. Any Windows XP copy I use is PERFECTLY legal - accusing me of illegal acts without any grounds to your claims is not something you can do just like that! DO YOU UNDERSTAND ??? 2. If anyone is pretending something here, it's you. Sitting behind your little keyboard and flimsy laptop saying things to (non) virtual people when in reality (yes. there's such a thing) you wouldn't have the guts to say FACE to FACE. Or are you going to "edit" my post like a little baby because you are a "mod" (I'm trembling here, seriously)? 3. If anyone is going to be prosecuted here it is probably going to be YOU TOO. What you said there is LIBEL, and that's AGAINST THE LAW. OK Bub? SO BRING IT ON BABY! I'M WAITING! --------------------------------------------------------------------------------------------------------- For the record, I have the utmost respect for everyone here. I'm sorry mr. "kelsenellenelvian" had to ruin this thread by introducing aggression and impolite and disrespectful behavior. Any help from other members will be greatly appreciated. Thanks again!
  23. I DO get it. And you can stop being so defensive (or offensive to be exact). I AM NOT BLAMING ANYONE, I AM MERELY LOOKING FOR HELP. "#2 SFC is always going to come up after removals have been done unless you disable it." Thank you. That's helpful. But I removed applications, not device drivers. So why does this happen at all? Furthermore, why does this happen only on some machines and not all? As far as you or anyone else here know - are there any other issues I might be facing in the future with these machines? Thanks again.


×
×
  • Create New...