Snap Deploy 5 -No network interfaces are available- Toughbook CF-54

I've seen similar issues mentioned in other posts and just want to see if I am understanding the solution properly. When I tried to deploy the image, I boot the machine over the network into the Snap Deploy agent (5.0 1656). That goes fine as it usually does but it never connects to the server because "No network interfaces are available." The image has Windows 10 Professional. I've imaged many machines here including Panasonic Toughbook CF-53s and this is the first time I've had this issue.

The 64bit Windows 10 I219 LAN driver Panasonic makes available is an exe file. When I open that up with 7zip, there are numerous .inf files. Can I upload those to the Acronis PXE Server in the Snap Deploy 5 Management Console? Is that likely solve this problem?

I am sending you a PM with 1666 beta. You're using an older version. 1660 is the current release, but lacks drivers for the newer Intelc Nics and newer PCIE NVME hard drives. 1662 beta is the same as 1660 but with better NIC drivers and 1666 beta is the same as 1660 with the addition of NVME PCIE drivers.

Hello, I just recieved New computers for a classroom, and Snap Deploy 5.0 does not see the network card unless I use a usb adapter , the machines are M900 with the new intel NIC. Can I have the 1666 Beta as well?

I'm also having trouble imaging a Dell Latitude E7470 Ultrabook. I boot the pc to a cd with the bootable media I created with Acronis Snap Deploy 5.0 (5.0.1,660) management agent but the agent states that there are no NICs available. This laptop has multiple NICs and I have disabled all of them aside from the Intel(R) Ethernet Connection I219-LM and I booted the laptop again with the same cd and it still doesn't recognize the NIC. I'm think that my problem is also related to Acronis not supporting this NIC. Would I need the beta version as well? And if so, should I download these same files?

Hi Liz, yes, you need the 1666 version. I am sending you a PM with the download link. I would suggest that if you upgade over the top of 1660 with it, that you then remove the PXE componentn completely, reboot and go back and install the PXE component again (to make sure it's working correctly). 1666 is basically the same as 1660 but has better driver support with the Linux media (server deployment and the linux offline reocvery media) for newer Intel Nics and newer PCIE NVME hard drives.

Eric, it's been sent. FYI, I keep a generic USB 3.0 to GB ethernet adapter handy - just in case. Alternatively, you can also create a WinPE .wim using Windows 10 ADK and that should have the drivers by default. You can upload the .wim to your deployment server and use that as well. It's slower than the default Linux environment, but can be handy for systems with uinque hardware where you need to inject your own drivers too (RAID controllers, etc.)

I've seen similar issues mentioned in other posts and just want to see if I am understanding the solution properly. When I tried to deploy the image, I boot the machine over the network into the Snap Deploy agent (5.0 1656). That goes fine as it usually does but it never connects to the server because "No network interfaces are available." The image has Windows 7 x64 Professional. I've imaged many machines here including Lenovo m800 and this is the first time I've had this issue.

The 64bit Windows 7 I219 LAN driver Lenovo makes available is an exe file. When I open that up with 7zip, there are numerous .inf files. Can I upload those to the Acronis PXE Server in the Snap Deploy 5 Management Console? Is that likely solve this problem?

bulent.ozgur@iclo, the issue is simply that version 1656 is an older version without the drivers. 1660 has been the last available release for over a year now, but also missing some of the drivers for newer Intel Nics. 1666 beta has the drivers you need built in and should be the key.

The alternative is to build a WinPE version and include your NIC drivers in the build. Then save it as a boot.wim file. Upload the boot.wim file to the deployment server and you can pick that instead of the default Linux media (although this method seems to be much slower to finally load the Acronis application over PXE boot). Ultimately, if you just grab 1666 beta from the sticky and use that version instead, you should be good to go.

Bryan, after upgrading to 1666, if the NIC is not working or being detected, I would recommend removing the PXE component from the server (control panel) and rebooting. Then reinstall the PXE component again (shouldn't need to reboot after that, but would be recommended if you can do this without disruption a second time). That should ensure the PXE components are good to go again.

If you want to test network capability on the local machine, create a recovery disc or flash drive and boot the machine directly to it - does networking work with it? If so, the PXE re-do on the server should work.

If the default linux recovery media still does not work with your NIC, it's a driver issue. In that case, you would want to create a WinPE .wim recovery in the SD5 console and upload the WIM to your deploymennt server. You could then PXE boot to .wim file and that should work. The downlside with using WinPE files in SD5 is that, currently, the "stand-a-lone" option is not available in it like the default Linux rescue media. However, stand-a-lone is not in the server deployment anyway, and only available on the localy offline recovery media.

Thanks for your reply Bobbo, unfortunately after following the steps and creating the .wim file, we are still running across the network card issue. To clarify we have upgraded to the beta release first, with no success, and after the upgrade followed your instructions to add the driver. When the machine boots into the OS, both the wired and wireless adapters work as expected. Unfortunately we bought this product to deploy images to 65 new devices and cannot get past this point, if there is no resolution we will return this product and licenses to our vendor and go with a competitor. I would hate to start this project over from the beginning, but unless there are other options to make this product work, I would have to go that route, and give our business to another competitor.

Bryan, I'm not an employee, but try to help. I'm sure there is a solution though, but I'd also recommend you contact technical support for assistance as well if you have not gone that route either.

We need to determine if your WIM really has the correct drivers or not - currently there's no way for me to know if you have any network connectivity when booted to it. Here's how we'll test...

FIrst, go back and remove the PXE component from control panel, reboot. Then install the PXE component and reboot. Now try again - any change - after upgrading to newer versions, sometimes this helps with network issues. If that does not solve it on its own...

1) Have you built WinPE rescue media with Snap Deploy yet? If not, please do so as you'll need it for testing. This will essentially be the same .wim as you've uploaded to the sever (at least from a driver standpoint which is what we want to test).

2) If (or when) you have your WinPE rescue media, boot to it directly on the system you plan to deploy to, instead of using PXE.

3) Once booted, minimize the Acronis Window and you should see a command prompt in the background. Can you ping your deployment server? If it's not pinging, what does ipconfig /all return? This will help determine if you even have a nework connection or not.

FYI - Wireless is not an option in WinPE, it's not supported by Microsfot. You need to be hardwired for all image and deployment processes.

4) If you are unable to ping, then that would mean the correct drivers are still missing in your .wim file. You would need to ensure you have the correct drivers installed and would need to grab those from the manufacturer and include that in the "add driver"of the .wim creation process. Until you get the correct drivers in your boot.wim, you're going to be out of luck.

Question: What version of ADK do you have installed to build your .wim and/or recovery WinPE media? You should use the Windows 10 ADK 1511 (1607 is not supported with Snap Deploy yet). This will give you the best "out of the box" windows driver compatibility. However, even then, many third party drivers (Intel, LSI, etc) still may need to be added. When adding additional drivers, it's important to make sure you have the correct one to match the ADK you are building and the correct architecture as well (dont' include both 32-bit and 64-bit drives when you add them - only use the drivers for the type of WinPE you are building - either 32 or 64 bit).

5) If you are able to ping your deployment servr, can you get to the network share of the deployment server where the image resides? With WinPE, you'll need to use a net use command in the command prompt to connect to the share as mapped drive

Change the IP and the path to your image folder. If you're on a domain, then put the proper domain\ before the username (make sure apaces are correct as posted in the example too) and enter the actual password. If all is correct you should a successful notification. You would then be able to change directories in the command prompt to M: and/or navigate M: from the Snap Deploy GUI in the WinPE again.

If / when you've gotten to this point, you know that your drivers are good. You would want to then receate the .wim with those drives in Snap Deploy and upload that to the server and test again.

Make sure that your deployment template has the proper credentials to access the share as well - just in case. Again, if the share resides on a domain, you need to use domain\username instead of just username in the template for the username

I had already started to work with support by the time you replied, it took a few hours but what was realized is the beta build 1666 is not for the issue with the NIC but rather for issues with storage controllers. They have a beta build 1662 that is meant for the issue with the NIC. Had to completely uninstall 1666 and install with 1662, then it finally worked as expected.

Hi Bryan, 1666 should have nic and storage controllers. Some have had to manually uninstall the pxe components and reinstall them before they work when using 1666 though so I suspect that would work for you too. Main thing is you're working though but keep that in mind if you need to move to 1666 to support newer pcie nvme drives or systems using RAID as the SATA mode in the bios.

I've tried the same 1780 release and still cannot get it working. I've uninstalled the PXE server component, reinstalled, as well as created a WinPE 10 .wim file with the intel e1d65x64.inf file (For Optiplex 5060). I've also tried the Realtek ws640x64.inf (for Optiplex 3060).

Client system I get to the ASD5 Master Image Creator, and at the point where I should be able to browse over the network to send the image of the system to the image server, there's no network option. I cannot type the address/path to the system in either.

I feel like it's not loading the WinPE that I've created almost.

On the PXE Server side of things, the Preinstallation Environment option is PE Media and that's what I added using the .wim file I created.

1780 doesn't contain fixes included in 1761 - they will be available in the next official update. So for now it's recommended to install 1761. I'd recommend a clean install to make sure all components are on 1761 and re-creating a master image.

Do you know if the latest trial version (5.0.1.877) has the fix for NIC drivers not loading because i am having no luck connecting to Snap deploy OS Server? I have dell latitude 3590's. "No DNS" and "No Gateway" just pends "connecting" when using linux kernal agent. I have also used the WinPE and added the correct .inf drivers for Quacomm adapter. I am not sure if i am missing more files. Also if i'm booting from WinPE do i have to have a wired connection?

The best part about the current version of SD5 (for me), is that you can now use WinPE and do stand-a-lone deployments with it too. With this update, the Linux rescue media is old news now.

With WinPE, you can slip in any drivers you want. Furthermore, if you run the MVP custom media builder on the system where Snap Deploy is installed and have ADK installed, it not only will install the custom drivers you put in the folder (ahead of time), but it will give you some other nice options like a file explorer, start menu and web browser too. This tool will actually add all of the Acronis tools you have installed on the machine you run it from - in my environment, I have working WinPE with Windows 10 ADK 1809 that has Backup 12.5, Snap Deploy 5, True Image 2019, Disk Director 12.5 and Universal Restore all in one environment now.

FYI, you can also get driver packs for WinPE and/or full driver packs for specific Dell models using the links in my signature below (they are direct from Dell). Likewise, you can instead get specific Intel Ethernet Drivers from the Intel Link below - it has all of them. Download it, extract the one(s) you need and slip them into your WinPE rescue media with the MVP custom pe builder, or use DISMGUI or straight up dism command-line with ADK if you want.

Sounds good! Let me know if you need any assistance . I really think the MVP custom winpe builder will work great for adding in your custom drivers and the user interface. If you check it out, I'd be interested in the feedback too.