Search the Community
Showing results for tags 'pxe'.
Found 3 results
Hello, I just picked up a Microsoft Surface Pro 6 for a trial run. I'm attempting to image via PXE. BIOS has been changed and secure boot has been disabled. I'm still unable to boot to PXE because my thought is the USB dongle (3rd party) gets no network traffic/activity until the OS starts or finishes loading. Anyone have success with Surfaces and PXE minus a dock or MS specific dongle? Thank you.
Ok so here is the situation. I haven't purchased the License yet to this service because I wanted to make sure that it would work, so I took an old computer i7 2nd gen, 12 gb ram, stock intel board. I installed Server 2012R2 (ill refer to this as host from now on) and then installed the Hyper-V role and created another windows server 2012r2 (SmartDeploySrv) image and I also made my reference machines on the host. It has all worked super smooth until now. I was able to make the reference machine and capture their image and download the ppk for the machine and I even configured it with WDS and can PXE boot to the WIN PE. Now I have tried to add the network share booting from the flash drive and also PXE boot. Both times I had a valid IP address in the corner and when I go to add the share I get Error 67. I have the right credentials. I am not in a domain so the creds are local credentials for the SmartDeploySrv. I got it to work with the offline installer and that is fine but I don't want to have to create a new flash drive every time i want to image a different machine, so I know it is not an issue with the machine. Any Ideas or suggestions would be appreciated.
Hello, I am trying to deploy an image via Windows Deployment Service and so far the image has been applied to client machines. However, platform packs and Smartdeploy.xml is not being applied to the machine after the imaging process. As a result, the image doesn’t have any drivers installed including the network card, graphics card and etc. My question is: What is the exact location that I can put the platform packs (default.ppk) and .xml file in WDS server so clients will point to it while deploying the image. I tried putting a driver package to WDS server under Drivers and I was getting an error: “E:\RemoteInstall\Images\Default.ppk is not a directory. Please enter an existing directory”. Any help would be appreciated. Thank you.