Trub

Solved! So as it turns out our AD sites and services was not setup correctly and the VLAN that the laptop booted up on was not there. I manually added the boundary for that VLAN, add that boundary to the boundary group and the task sequence works as designed. Thanks again for direction!

Thanks for the replies, Mike and Rocketman, We are a small shop and there were no boundaries configured so I checked the two boxes in AD Forest Discovery to allowed it to automatically create the AD and IP boundaries. I then created two Boundary Groups, added the IP ranges and AD sites to each respective group and assigned our single site to each group. Gonna give that some time to simmer this morning and I will report back! Thanks again for the responses!

Greetings! Looking for some help with an OSD task sequence. I have a stand-alone site that does everything, no boundaries or boundary groups. I enabled PXE boot and have that working. Created a task sequence to install Windows 8.1, PXE boot the laptop, select the TS and it fails instantly with "The task sequence cannot be run because the program files for WRI0001F cannot be located on the distribution point." Copied off the SMSTS.log file from the client and found this I done a lot of searching and found lots of folks having this problem and a lot have been resolved by correcting the boundaries and boundary groups or by making sure the packages are distributed. As I said earlier I don't have boundaries and boundary groups configured and I have made sure the content is distributed via the Content Status And verifying the SMSPKGD$ share Strange thing if I create another TS say for Windows 10, it will fail but for a different package, like the Config Manager Client or the USMT. Or if I delete the Windows 8.1 TS and create it again, it will fail but for one of the other packages. Any help is greatly appreciated!

This has been resolved. The problem was with the share permissions for the migration data folder. I removed the role from the site, waited a few minutes and re-added the role. It was then able to create the SMPSTOREC_XXXXXXXX$ share inside of the specified folder. I also started using the cmtrace.exe tool that highlights the error messages in the log files. It can be found \Program Files\Microsoft Configuration Manager\Tools directory.

Greetings, Wonderfully helpful forum, I'm learning a ton reading through all the post, thank you for creating this site! I'm having a problem with a site server starting the State Migration Point component. I have a primary site server and 2 site servers that should be configured exactly the same. One site server doesn't have any problems with the SMP component starting but the other one does. In the SMPMGR.log file I see; HandleSMPRegistryChanges failed. error (0x80070002). $$<SMS_STATE_MIGRATION_POINT><05-08-2013 10:24:30.338+300><thread=1484 (0x5CC)> SMPManager failed to start, Error = (0x80070002). $$<SMS_STATE_MIGRATION_POINT><05-08-2013 10:24:30.338+300><thread=1484 (0x5CC)> I've searched for those two error messages but haven't been able to find anything related to my problem. TIA!