Kevin79 Posted October 4, 2010 Report post Posted October 4, 2010 I have a secondary site setup with Server 2003. I am having an issue with OS deployments. I am using bootable media instead of PXE, I can't try PXE until tomorrow at the earliest because of the setup. Anyhow, my log says that it can't find the package that contains my boot.wim file. The file is there and permissions seem to be fine (I.e. the permissions are the same as they are on my primary site server). Is there something special that I have to do on my secondary servers? I can PXE boot and deploy in my primary site fine. I've attached the smsts.log file. smsts.log Quote Share this post Link to post Share on other sites More sharing options...
Paul H Posted October 5, 2010 Report post Posted October 5, 2010 Is the boot.wim present on the distribution point in your secondairy site? Quote Share this post Link to post Share on other sites More sharing options...
Kevin79 Posted October 5, 2010 Report post Posted October 5, 2010 Is the boot.wim present on the distribution point in your secondairy site? Yes. It is on the DP and the SMSPXEIMAGES$ share. Quote Share this post Link to post Share on other sites More sharing options...
Paul H Posted October 5, 2010 Report post Posted October 5, 2010 And the network access account you use has permissions in the subdomain? I read in your first post permissions are the same as in your primairy site, but i don't know if these permissions also apply to subdomains. I'm assuming your site topology matches your domain topology here. check the effective permissions in the advanced security settings of the folder where the package is. If this seems fine, try to remove the package from the DP, check if its gone, and redistribute it. Quote Share this post Link to post Share on other sites More sharing options...
