agarabaghi

Went to pxe boot this morning, and now im getting an Windows PE has encounter and environment error? This is a pop up at the splash screen for MS Solution Accelerators

I guess the machines which I want last user not remembered and disabling of ALT CTRL DEL screen are the labs, so they will be on the domain. Time to knock on the AD guys door!

Looks like i can run batch files off a networkshare if i select application without source files / network share option!

The command line worked. The machines activate themselves weather on the domain or not. Has anyone used the "Join Domain Prompt" does it work? That would be nice for lab machines. Will give it a try tomorrow. I was wondering if anyone knew how to set certain local security rules? I could edit them via command line if it is possible? I want to remove remember last logged on user, and AlT-CTRL-DEL screen to not appear. Also, is there a way to launch a bat file as an application? It would be nice to see in the list of application to install a box with [CSS LAB SCRIPTS] [DOMAIN USER SCRIPTS] as choices?

Ahh strange. Well i just applied for the adobe reader and flash distribution license. Thanks!

So the installers i downloaded delete themselves once ran, where can i find the proper installer for these 2 applications?

what;s the best approach for running a script using MDT? I need to run the windows activation script cscript //b c:\windows\system32\slmgr.vbs /ipk cscript //b c:\windows\system32\slmgr.vbs /ato unless there is another way to activate machines not on the domain...

1st deployment worked!!!

Yellow warnings last time, setup issue. I will nuke the machine manually. THanks for all the help guys. Ive made more progress today than all of last week! Does anyone know about my driver question? If i load all the drivers for a T420s and T410s will it work?

weird i tried another T420s and it worked just fine.

ive loaded all the drivers for this laptop into MDTs. I was able to boot into it earlier, and now i cant =(

so i went to lunch and came back and now im trying to boot off the lan again, and im getting this weird issue, it loads the background of MS | Solution Accelerator but then it reboots the machine. usually it would launch the option to start deployment or command prompt?

If I was to load all the drivers for several laptops into 1 deployment share, would it only pull the drivers needed??

Ive just build an MDT deployment share, hopefully this deploys properly

im just gonna build an image hehe

yup ive built an image in mdt and deployed via usb. Could i capture and image through MDT? Using the task sequence sysprep and capture?

Ok, well i created the task sequence to deploy, but it errored out ERROR - Unable to find SETUP needed to install the image? I should prob try with a fresh Deployment

So i loaded the driver as out of box driver, and then updated the deployment. It said injecting drivers etc... then finished. I then went into WDS and "Replaced Image" the boot image with the new LiteTouch_x64.wim... but it still errors out with the network card driver device ... oj hwait it wotrk now!

updating image now... let's see what happens.

We got PXE booting working... but i get this error now: A connection to the deployment share \\imaging\deploymentshareT420s$ could not be made. The following networking device did not have a driver installed PCI\ Im assuming i should add Out of Box network driver to the deployment share, then hit update?

network guy is going to check the settings from that link "On your DHCP server, set the following 2 Server Options (not scope options): Option 66 - set the IP address of the WDS server Option 67 - boot\x86\wdsnbp.com I had the same problem when I changed over in February"

When i check the boxes it says MS DHCP is not running on this server.

We have this machine in a different vlan for testing. Im no network engineer, but we currently have KACE up and running, but trying to get away from it. It pxe boots just fine, so i thin there is some setting my network buddy has to fix.

I press F12 to boot from LAN, and it get this, then it goes back to select boot device screen Interl® Boot Agent GE v1.3.66 Copyright © 1997-2010, Intel Corp Client MAC Addr: F0 DE F1 99 72 C6 GUID: 81F1D9AE AA51 CD11 B3A0 8E5CCB381DF1 Client IP: 172.18.68.24 MASK: 255.255.252.0 DHCP IP: 10.20.1.10 GATEWAY IP: 172.18.68.1 TFTP PXE-M0F: Exiting Intel Boot Agent

i found the boot file, it's called litetouch x64.wim ... i think my network guys need to fix the pxe booting. It doesnt seem to be connecting to the WDS service.