zeezam

How can it activate as OEM licens if your using a MAK license ? I have both license but for oem computers I use the oem license. I use the dell and lenovo image that comes with the computers and then you don't need a key. I just wonder if I use the MAK key in the unattend file for the oem image - is it then going to use the oem license anyway?

ok, what does the first line do?

Now I have different images, one with oem image that is autoactivating without any key. If I use the same unattend.xml that I use for the the images with MAK, does windows activate it as OEM license then?

I tried to put some scripts in FirstLogonCommands that is used after autologon with built-in administrator local account but nothing happends with this codeline; powershell.exe add-computer -domain domain01 -cred domain01\administrator Any ideas? I want the credentials prompt to pop up so I can enter and reboot the computer.

Seems to work. Now I just want a script that joins my computer to the domain. Doesn't mather if I get a popup with credentials... Tried with this but nothing happends. powershell.exe add-computer -domain domain01 -cred domain01\administrator

Is it possible to add FirstLogonCommands that runs with the local user account that I create during the the finish of windows 7 installation? I don't have any autologon un the unattend xml.

Anyone using cscript in unattend.xml to activate under w7 under installation? I have a MAK key and want it to activating during installation...

I got No driver package were found when trying with dism /image:"C:\mount" /add-driver /driver:"C:\DRIVERS\WIN\ETHERNET\PRO1000\Win32\NDI62\elk6232.inf" After trying again I succeeded with adding the drivers. Finaly I can boot with my new lenovo models. Thanks for helping me out!

I'll try to inject the driver with DISM. Thanks for info. I'm not using MDT, I'm using WDS. In W2K8 R2 you can add drivers directly to the WDS server; http://technet.microsoft.com/en-us/library/dd348456%28WS.10%29.aspx Edit; Is it this tool that you mean? It's to the install.wim. Isn't it to my boot.wim I want to add the drivers? I got the error when try to boot on my boot.wim...

Ok. I think maybe I extract the wrong inf files. Now I tried with the inf files from this setup - http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=18713〈=eng Same error in WDS but no info in the setupapi.app. That tech article are explaining using install.wim. Isn't it boot.wim I should use? Anyone having a working boot.wim for lenovo t410 and x201 models that I can download from somewhere?

Gotcha, was editing my message while you were replying, here is the easiest thing to try. What I would do is use WDS to create another boot.wim (clean no drivers), then integrate all the drivers except the wireless nic(s) and see if that doesn't solve the problem. (thinking is that if no driver is found, it does not cause error). Which is pretty much what arwidmark is saying. I'll try that. I assume it's the 32bit inf files that I need? It's a Intel 82577LM Gigabit NIC. Edit: Strange, same error in setupapi.app with new fresh boot.wim with e1k6332.inf installed.

I added the inf files from this setup. http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-74429

Yes, that is confusing. I'm booting with PXE over ethernet. Works fine on all my older lenovo models and dell etc. I'm running WDS on W2K8.

I have new lenovo x201 and t410 models that fails loading nic driver when booting on my wds boot.wim. I have successfully loading the needed inf files with imagex and peimg. Now with updated boot.wim I got; " WdsClient: An error occurred while starting networking: there was a failure while installing the network card driver for your machine. Please contact your Administrator " from WDS. Here is what the setupapi.app.log says; [DIG_SELECTBESTCOMPATDRV - PCI\VEN_8086&DEV_10EA&SUBSYS_215317AA&REV_06\3&B1BFB68&0&0&C8] Section start 2010/04/28 06:51:09.196 cmd: X:\Sources\setup.exe !!! dvi: Loading module 'X:\Windows\system32\wlaninst.dll' failed. !!! dvi: Error 126: The specified module could not be found. !!! dvi: Error 126: loading CoInstaller (wlaninst.dll,WlanDeviceClassCoInstaller) !!! dvi: Error 126: The specified module could not be found. !!! dvi: Loading module 'X:\WINDOWS\system32\wwaninst.dll' failed. !!! dvi: Error 126: The specified module could not be found. !!! dvi: Error 126 loading CoInstaller (wwaninst.dll ,WwanDeviceClassCoInstaller) !!! dvi: Error 126: The specified module could not be found. <<< Section end 2010/04/28 06:51:09.228 <<< [Exit status: SUCCESS]

Bad news, that section of the GUI is a combined page, it is all or none. You cannot separate them, this is a limitation of the windows 7 installation GUI. Your best bet is to fully automate both settings with your unattend.xml, then run a VBS script during SetupComplete.cmd using the old InputBox to enter a computer name. Rename.vbs strRename = InputBox("Enter new computer name") strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colComputers = objWMIService.ExecQuery _ ("Select * from Win32_ComputerSystem") For Each objComputer in colComputers err = objComputer.Rename(strRename) Next You also need to schedule a reboot before it will take effect. Ok, because I creat local accounts in unattend.xml. I thought I had a setup before where I just get prompted with the computer name and after that were able to log in with my created account.

Exactly.

I have several images uploaded to my wds server and two different unattend file, one to the image and one for the whole wds. After I have installed the image to a new computer I get prompted with user account and computer name. I only want to get prompted with computer name, not any creation of local account.

Ok. I got stuck when try uploading the image to MDT; "A connection to the deployment share \\Server\Distribution$ could not be made. The Deployment will not proceed" If I not remember wrong I got same error if I import a custom install.wim to the MDT.

Okey. Many use MDT 2010 instead or just WDS as a complement for the boot.wim. Is it possible to connect a boot.wim to the install.wim?

Is there anyone using more than one image in your WDS? How did you solve the unattended file? I must have one for the WDS and one for the image. It's impossible to make it full unattended with multiple images? ...Or Can I let WDS choose image based on hardware? I want to separate desktops and laptops.

I capture with pxe boot image on my WDS. Works fine!

Doing so will add another option to the PXE list of choices. Be sure to give a descriptive name so you know which option is your "capture" image. Yes, but that is in WDS? I have done that before, MDT also have an capture option but that is maybe another thing?

Anyone using MDT 2010 + WDS? I'm trying to just use the capture process in MDT but it seems that I must do a install with that function?

WAIK it doesn't add anything unless you add it, it don't know you are using 1 pass from the other. its basically stupid Ok, but do you use your unattend file for the whole WDS or specific to one image? You maybe have just one iso? I want to have one unattend file for the WDS boot image and one separate for each image I have on the server. Which settings should I have for the image of these? <settings pass="windowsPE"> <settings pass="offlineServicing"> <settings pass="generalize"> <settings pass="specialize"> <settings pass="auditSystem"> <settings pass="auditUser"> <settings pass="oobeSystem">