Systems that PXE boot to production in Subnet A PXE boot into Automation when moved to Subnet B
|Article:TECH199993|||||Created: 2012-11-21|||||Updated: 2012-11-21|||||Article URL http://www.symantec.com/docs/TECH199993|
Systems that PXE boot to production in Subnet "A" PXE boot into Automation when moved to Subnet "B"
Customers have noticed that when a system that boots to production in Subnet A is moved to Subnet B the system now boots into Automation
DS 7.1 SP2 and DS 7.1 SP2 MP1
The reason why the system now boots back into WinPE is because the two NSinterfaces - which are in separate subnets - are not communicating with each other.
By default, NSinterfaces ONLY communicate to other NSInterfaces in the same subnet.
Functionality was added in MP1 to resolve the issue. To address the issue do the following on all PXE Site servers - including the NS:
1) Open Regedit
2) Browse to HKLM\software\altiris\deployment\symantec Boot Services
3) Change the value of the value 'SubnetFiltering' from '1' to '0'
4) Restart all your PXE services
5) The NSinterfaces will now all communicate with each other and this problem will go away.
Note: In large environments (180+ site servers) it can take up to 15 minutes for the NSinterfaces to all communicate but it does happen. This shouldn't be a problem because customers do not move computers from one subnet to another this fast.
Article URL http://www.symantec.com/docs/TECH199993