lbhans

Member
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About lbhans

  1. Greetings, I am having some difficulties in deploying Windows 2008 R2 SP1 from a VmWare template. I created a blank VM in vSphere 4.1 U1 and installed W2L8R2 to it with no problem. The problem arises when I deploy the template to a new VM. None of the prior customizations I made to the image translate to the VMs I deploy to. Only added roles and features are carried over. I renamed the Administrator account and it did not translate to the new VMs I suspect that it is because SYSPREP strips out all uniquness. I tried creating a setupcomplete.cmd file with the following line added to it wmic useraccount where name="Administrator" call rename name="NewAdmin" The setupcomplete.cmd is supposed to run after the Sysprep operations complete and before the server reboots, but this does not seem to work. I also tried going into the Local Securoty Policy view in Administrative Tools and setting a policy to rename the Administratoe account to one f my choosing. This setting was also stripped after SYSPREP ran. Any insight into a possible solution would be most appreciated. Thanks!!
  2. If you just want to Sysprep and Capture an image that you have built manually and tweaked, you have to have the machine that you built up and running. Then map to the deployment share in MDT. There is a scripts folder that has a file called LiteTouch.vbs. If you run this file, it will bring up the same GUI as when you boot from the PE media and allow you to run task sequences from the deployment share. Assuming that you have already set up a task sequence for Sysprep and Capture, just run the sequence and sysprep should run, reboot the machine back into the PE environment and capture the image. After the capture, the image should appear as a WIM in the Captures folder in the deployment share. I didn't see this in any MDT documentation. The process is rather time consuming because I have no yet discovered how to tweak the NIC driver to force a 1000/Full connection. Hope this helps L
  3. If you just want to Sysprep and Capture an image that you have built manually and tweaked, you have to have the machine that you built up and running. Then map to the deployment share in MDT. There is a scripts folder that has a file called LiteTouch.vbs. If you run this file, it will bring up the same GUI as when you boot from the PE media and allow you to run task sequences from the deployment share. Assuming that you have already set up a task sequence for Sysprep and Capture, just run the sequence and sysprep should run, reboot the machine back into the PE environment and capture the image. After the capture, the image should appear as a WIM in the Captures folder in the deployment share. I didn't see this in any MDT documentation. The process is rather time consuming because I have no yet discovered how to tweak the NIC driver to force a 1000/Full connection. Hope this helps L
  4. If you just want to Sysprep and Capture an image that you have built manually and tweaked, you have to have the machine that you built up and running. Then map to the deployment share in MDT. There is a scripts folder that has a file called LiteTouch.vbs. If you run this file, it will bring up the same GUI as when you boot from the PE media and allow you to run task sequences from the deployment share. Assuming that you have already set up a task sequence for Sysprep and Capture, just run the sequence and sysprep should run, reboot the machine back into the PE environment and capture the image. After the capture, the image should appear as a WIM in the Captures folder in the deployment share. I didn't see this in any MDT documentation. The process is rather time consuming because I have no yet discovered how to tweak the NIC driver to force a 1000/Full connection. Hope this helps L
  5. Yep, I did load the System and Software hives and made the changed prior tp prepping the image and committing it. Still no go. I am getting ready to go with BartPE. It has the networkig configurator built in and the documentation is much more intuitive and comprehensive.
  6. I think I know why PENETCFG does not work. When I apply the registry settings to the Booted WinPE iamge, they do not activate and require a reboot, which of course brings the machine back up without the TCPIPREG.Sys working. I need to incorporate those Registry settings in the PE image before I commit it so they will become active as WinPE boots off of the CD. However, the instructions for making the registry changes do not seem to apply since the command lines do not work. I am going to build a separet environment and attempt to make the premanent registry changes before the image is prepped.
  7. Greetings, I am new to WinPE and I am having some difficulty with the network settings. I have built the WinPE environment and have created CDs to boot a system and image it to a locally attached USB drive with no problem. My problem is when I try to image over a network connection. When I boot WinPE, it leases an IP address and connects to the network with no problem. However, when I start the image process from Ghost32, the speed is ridiculously slow. i am pretty sure that it is because the NIC is set to auto detect the speed and duplex whereas the swith is hard set to 100/Full. In our environment, this combination does not work. I need to find a way to force the NIC to 100/Full from withing the WinPE environment. Here is what I have tried already: 1. Downloaded a utility called PENETCFG from a website called "The Truth" It work in an XP environment, but not on WinPE since version 2.0 uses a Vista Kernel. At the uggestion of "The Truth", I copied the TCPIPREG.SYS file to the WinPE image and imported the appropriate registry keys to make it work, but still nothing. Is there any other way to configure the NIC settings from within PE? Is there a way to build a PE Image using the XP OS? Any help would be mot appreciated L