techie17 Posted February 7, 2019 Posted February 7, 2019 Ive just setup a remote distribution point at another site and when i pxe boot computers to build them, the task sequence fails when starting to apply the operating system. The message reads: "Task Sequence windows10 has failed with the error code (0x80070002) My other remote site and main is fine, just the new one i have setup. The distribution point is also set to allow clients to connect anonymously, and content has also been distributed to the new distribution point. Attached is the smstslog file but it cant seem to find any specific errors in there so can anyone help? Ive been trying to diagnose now for the best part of the day. Thankssmstslog.txt
techie17 Posted February 7, 2019 Author Posted February 7, 2019 Ive manage to get the deployment working as long as its in the same vlan as the servers. As soon as i put the client in the "Wired Clients" VLAN i get the issue. I have created the boundary group for the remote site and put the different subnets in that group but still no luck. Any other ideas anyone?
techie17 Posted February 7, 2019 Author Posted February 7, 2019 (edited) Have you put the DP in the boundary group? Do you mean the subnet that the DP point is in or the actual IP address of the DP? Basically i have a boundary group of the remote site with the subnets of that remote site in it. I also have an IP helper of the DP sever ip set in the vlan of the switch (vlan22) DP is in vlan24, and still not working when in vlan 22. Edited February 7, 2019 by techie17
FN-GM Posted February 7, 2019 Posted February 7, 2019 Do you mean the subnet that the DP point is in or the actual IP address of the DP? Basically i have a boundary group of the remote site with the subnets of that remote site in it. I can't remember off top of my head but you need to assign a DP to to the boundary group itself. The DP will be a server object within SCCM. 1
meakjoe Posted February 8, 2019 Posted February 8, 2019 If they're in seperate VLANs, there's no firewall blocking ports between them that SCCM may need to use? 1
techie17 Posted February 8, 2019 Author Posted February 8, 2019 If they're in seperate VLANs, there's no firewall blocking ports between them that SCCM may need to use? Actually there as as the sophos UTM does the inter vlan routing as the HP switch isnt L3. I will check the logs as i do a test build
techie17 Posted February 8, 2019 Author Posted February 8, 2019 turns out the firewall was blocking a url from VLAN 22 to VLAN24. Thanks everyone.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now