denmyos

No the wds/mdt is a standard alone (workgroup), the dhcp is on another network. BUT the clients gets a IP address from the dhcp when pxeboot. Yes option 66/67 is sat up.

I'm running a vmware environment vmware workstation 10 server 2012 r2 wds MDT 2013 When I pxeboot within vmware everything works fine. But when i pxeboot from a physical computer I get no connection. I get the correct IP address and DHCP address I getting thise error TFTP. PXE-t04: Access violation DASH-E36: Error received from TFTP server DASH-M0F: Exiting option ROM Our network administrator is pulling hairs to figure out what is going on. In INFOBLOX we have put in this path \\servername\reminst\boot\x86\wdsnbp.com Is that the correct path? When my client boot into windows it can ping the wds and vice versa, and see the share \\xxxxx\reminst\boot My client is a Lenovo M78 windows 7 I also tried a "old" HP I got the same error. I reinstalled the wds again (twice) with no change. Any help is appreciated. Also see here for further info. http://www.edugeek.net/forums/o-s-deployment/139450-reinstalling-wds-share-name-already-use-server.html

Hi Kmount I will start a seperate thread about this. since it is a big mystery to both me and our network administrator. Thanks you for your help.

Well, I ended up capturing the image without sysprep it first, (I turned off a switch in TS) BUT that leads to another problem. It seems like I can't deploy any applications, customsetting.ini, language packs etc to the image.? Is that because its not sysprep first? There as to be a way to do this, so I get the image I want and can be able to deploy applications etc on to it, as I please.?

yes, Correct Yes, correct Same Vlan But I can't confirmed that its on the same switch. But my network administrator assured me that I was good to go. Is there a way to test if the pxe boot actually is trying to reach my wds, and where it gets stopped.? When the physical client boots into windows it can share foldes with the MDT/WDS server, so there is some kind of connection.

I'm having the MDT and the wds on the same server. The Dhcp is on a different network/segment, which i have no control off.

Not sure how to check that. When i pxe boot my client it boot into dhcp......... and the goes to .......no file name received.. And the boot into windows. In windows client the ip, subnet, gateway is the same as my vmware server Yes there is a lease being issued on the client. And its the same dchp server for both vmware server and physical client BTW: i'm in a workgroup

yes totally the same. I checked And i can ping between the real client and the vmware server and back.

Please tell me why why WHY this sysprep is so fancy!! My image has two accounts a local administrator and a normal user. When i go to audit mode to set up my image, add the normal user, install software etc, I then login into my newly created normal account, and install software etc. BUT then when i want to get back into my administrator its disable,,,,why WHY!!!!!! What is it i don't understand, what i'm i doing wrong. I'm new to mdt/wds sysprep etc I just want to capture my Image, the way i made it, so i can deploy it to my computers. Why is that so hard to do.!!!! ????

Thank you, that worked. I was close to giving up. :S are you hardcore at Vmare.? I need to pxeboot from a real client, into my MDT/WDS server. I can ping both ways, but when i try to pxe boot my client it just timeout and goes into windows. I can pxe boot all my virtuel clients into the MDT/WDS and get a image, so I know it's working.

I had to reinstall my WDS but when i want to configure it i get a "the share name is already in use on this server" I try to give the share a different name, but i still get the same error. I tryed this commands WDSUTIL /uninitialize-server WDSUTIL /initialize-server /RemInst:E:\NewRemoteInstall But no cigar I'm very close to deleting my whole server MDT/wds and start all over. :(

I'm running the sysprep from the MDT server, BUT I'm starting the Litetouch.vbs from within the client. More or less like this How to run a Sysprep and Capture Task Sequence From MDT 2010 - Ask the Core Team - Site Home - TechNet Blogs **A common mistake at this point is to boot the reference computer from your LiteTouch image and start this task sequence. The sysprep and capture task sequence is designed to be run from the desktop of the reference machine similar to a post OS installation task sequence. To launch this, you will need to establish connectivity to the deployment share and launch LiteTouch.WSF manually.** When i do it that way, I don't get the generalize switch. The reason I'm doing it from the client and NOT from MDT TS is that i got a lot of errors As described here, more or less. Error starts at 24:35min (but watch the whole thing, it's great watching.) I'm using the solution that starts at 28:29min, BUT mine does not get a error, like he does. I capture, reboot and everything is nice and dandy, BUT i don't get the generalize switch, it's just starts sysprep. Thus the image i'm getting has the administrator account disable, Netplwiz resat, no policy change. Acording to Bernard (guy in the video) its because i'm not in audit mode (oobe) The reason for that is that my Image is already installed, and I installed program, tweaks etc. I should get into audit mode by pressing the ctrl+shift+F3, when I get the oobe screen, But I'm not getting a oobe screen. Need help on getting the oobe screen. I have been trying to install a fresh win7 (in vmware) but I'm not getting a oobe screen, I'm just getting right to the desktop. I just what to duplicate the image, so I can deploy them out to my other machines, by next week. My set up is: Server 2012 MDT 2012 WDS Client windows 7 x86 it's all running on vmware 10 invironment. For the hell of it I try to pxboot from a client (outside the vmware invironment) to see if i could get a deployment going, but no cigar. it fails to reach my wds server. My (outside) client can ping my server (inside vmware) Need help on getting from outside the vmware to inside.?

No, i dont get one. Should I get one.?

I have spend a long time setting up MDT/WDS for deploying a image. It's all on a Vmware 10 Finally i got a image done, with apps (Office 2007, skype, picasa, open office, quicktime) 2 user profiles (adminstrator, and a "normal" user called Laaner) Netplwiz (control userpasswords2) was sat up so User "Laaner" would automaticly login. Did some mmc policy change so "Laaner" wouldn't have access to the control panel etc. Did a sysprep and capture my image. And deployed it to a virtuel client. I ended up with Administrator account disable, Netplwiz resat (so no automat login) And no policy change. And right now when i look a the client desktop all the icon images are missing. :( I'm i missing something here.? What am i doing wrong? EDIT: it looks like my Golden Image has change as well after it got sysprep. I just wanna capture the raw Image i made, EXACTLY like I made, and deploy it looking EXACTLY the way I made it.

I'm getting a error code 1619 ---ERROR_INSTALL_PACKAGE_OPEN_FAILED ---This installation package could not be opened. Verify that the package exists and is accessible, or contact the application vendor to verify that this is a valid Windows Installer package. When i use this switches Msiexec /I firefox-29.0.1-da /quiet /norestart /qn Msiexec /I jre-7u60-windows-586 /quiet /norestart /qn Msiexec /I NAESKOM_client_x86 /quiet /norestart /qn According to the msiexec.exe this apps should work with normal/stanard switches. This one works fine Msiexec /I SkypeSetup.msi /quiet /norestart /qn All apps are located in the same deploymentshare I suddenly realizied that i forgot to write Msiexec /I firefox-29.0.1-da.MSI /quiet /norestart /qn :S That seems to take care of the problem. It just took me 3 days to spot it. :S :S

I sat up the customsettings.ini to Joinworkgroup=workgroup That worked.

I have the workstation 10 But I used USB 2.0 (in the virtual Machine settings)

I would like to say thank you, both of you. The trick of deleting all drivers worked.

yes that's what I'm doing. I install vmware tools drivers, and Imporeted them to out-of-box driver, updated everything. Imported to WDS, restarted WDS. pxeboot into the new boot.wim (lite touch windows PE x86.) Didn't work. BUT Then i delete ALL my drivers in OUt-of-box drivers,,, Everything!!! And that seem to work :) BUT When I get to user credentials, it wants me to enter a DOMAIN, which i don't have, I'm sure i made the image as a workgroup. hmmm? But again i'm new and i have no idea of what im doing

I imported all drivers, and i do mean ALL drivers. :S Just to make sure i didn't miss anything. I'm new to MDT/WDS, but is it correct that the BOOT.wim should be taken from deploymentShare\Boot\Boot.wim AND the IMAGE should be taken from Deployment\operation system\Windows 7x86\sources\install.wim ?

Thank you, for you quick respond. I'll try that. My MDT/WDS is also vmware 10, just to clearify Working on it now, will report back with result.

Hi First post I have this problem with MDT/WDS When I try to install a boot.win (x86) on my client (on vmware workstation) When I get to the "Run deployment wizard to install a new Operation system" screen, my mouse and keyboard stops working. The funny thing is that, it works when i use the boot.wim (x64) I guess its some kinda driver problem, but I'm new to both MDT/WDS and vmware so i dont know where to begin. My host machine is a x64 bit, don't know if that has something to do with it. Vmware v10 MDT 2013 Server 2012 R2