PXE Services causing issues with DHCP

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

About 6 months ago I started testing Acronis Snap Deploy at one of our locations. I installed Snap Deploy on our DHCP server, along with the PXE services, and have had no issues running the two. I do not have options 60, 66, or 67 set and everything works as it should.

We decided to move forward with Acronis at all of our locations so I installed Acronis snap deploy and the PXE services on 3 more servers. These are on different IP ranges than the original, all locations tied together via MPLS.

The day after installing on the new servers, 2 of them started having issues. We have VLAN2 set up on our switches for Voice so we have a second DHCP scope for voice as well. Suddenly phones were unable to connect to DHCP to get an IP address. Data seemed fine during our trouble shooting. At first Acronis was not even on our radar since we had been running it fine at the original testing location without issue. But we got Microsoft involved and after a couple of hours he noted the PXE server was causing the issues.

As of now we have disabled PXE on the 3 new locations and will be moving forward with boot discs until we get this resolved. Meanwhile I am trying to figure out what caused the issue. Any ideas? Let me know if you need further info and I will try to answer any questions you have.

Mon, 02/16/2015 - 19:53
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 1

Think I solved my own issue. Looks like the DNS Domain name entry in the Voice scope is causing the problem. I added this to the Houston server and it crashed the phones. Removing it initially didn't fix it, but after restarting all Acronis services it worked again.

Mon, 02/16/2015 - 22:20