jaminben Posted March 10, 2014 Posted March 10, 2014 Is there a way to take the standard install.wim from the Windows 7 and slip stream the updates in or is B&C the way to go? I use SCCM to update the image every other month or so... not had any issues with it recently but it has killed one of our images in the past.
ptotham Posted March 10, 2014 Author Posted March 10, 2014 snagrat please find attached my smstslogs file thank you for taking a look. since this last updated itself I recreated everything and now the task sequence wont run as it moans straight away about the boot image not being on the distribution point even though it is as when I do the distriubte content for task sequence no DP come up which indicates that everything is there.
Sam_Brown Posted March 10, 2014 Posted March 10, 2014 Right click the TS in SCCM and go to the Advanced tab. Under "Use a boot image" is it set to the correct Boot Image?
snagrat Posted March 10, 2014 Posted March 10, 2014 You could try removing all the relevant packages and distributing them again. I'll look at the log when I have cmtrace to hand next
ptotham Posted March 11, 2014 Author Posted March 11, 2014 You could try removing all the relevant packages and distributing them again. I'll look at the log when I have cmtrace to hand next thank you.
ptotham Posted March 11, 2014 Author Posted March 11, 2014 I decided to rebuild my sccm sever in case I had miss something along the line when setting up and to check the relevant logs files as I went along, I have just enabling PXE Boot on my DP and when I checked the logs I had error message already to do with the boot images (i have created these boot images) I have attached the distmgrlog not sure if the failures are to do with permissions.distmgrlog.txt
ptotham Posted March 12, 2014 Author Posted March 12, 2014 right think I have managed to sort out the distribution point problems and am finally getting a a error message on my TS, I have attached the logs could someone have a look and why and where its going wrong?smstslog.txt
Sam_Brown Posted March 12, 2014 Posted March 12, 2014 What error message are you getting on the TS? Log file doesn't show anything obvious.
ptotham Posted March 12, 2014 Author Posted March 12, 2014 the error is 0x80070002 which i think is to do with network share access problem.
Sam_Brown Posted March 12, 2014 Posted March 12, 2014 Either permissions or not having the correct network card driver in the WinPE image. Assume you can press F8 and bring up the command prompt? Can you do an ipconfig and try pinging some things on your network to make sure that side of things is ok. As for permissions I got this sorted by having a sccm share on the server called SOURCEFILES and everything to do with distributing apps and OS was under that. That way only had one place I needed to make sure the permissions etc were set currently.
Norphy Posted March 12, 2014 Posted March 12, 2014 Are you still trying to install from an original install source? That stopped working in SCCM 2012 SP1. I had this problem when I first put SCCM 2012 SP1 in and I ended up doing basic Windows installs from the Install.wim instead.
Sam_Brown Posted March 12, 2014 Posted March 12, 2014 This thread MIGHT help as well... http://www.edugeek.net/forums/enterprise-software/107527-sccm-2012-sp1-w7-osd-issue.html
Norphy Posted March 12, 2014 Posted March 12, 2014 That was my thread and I only got it working in my dev environment. Once I moved it to real hardware, what I did there didn't work. Believe me, installing from the install WIM is a lot easier
ptotham Posted March 12, 2014 Author Posted March 12, 2014 I have solved this issue now under the DP I needed to tick "Allow Client to connect anonymously" as soon as I ticked this the build started working. thank you everyone for your help
heckle Posted March 16, 2014 Posted March 16, 2014 We build our wim files on virtual machines. Once built and configured as a base image, then we capture the virtual machine.
jaminben Posted March 16, 2014 Posted March 16, 2014 We build our wim files on virtual machines. Once built and configured as a base image, then we capture the virtual machine. This is what we do except using MDT... we just setup MDT with all its task sequences point Hyper-V to the boot image created by MDT and let it run automatically. Once its done its thing your left with a clean (not touched by human hands) driver agnostic .win file which is then imported into SCCM.
ptotham Posted March 17, 2014 Author Posted March 17, 2014 Thanks for everyone help and advice finally got my TS working as they should do.
Sam_Brown Posted March 17, 2014 Posted March 17, 2014 Did you manage to figure out exactly what the issue was at all? Just in case someone has a similar issue and finds this thread in the future!
Norphy Posted March 17, 2014 Posted March 17, 2014 It's a permissions issue by the sound of it. Allowing anonymous access on his DP fixed the issue for him. The downside of that is that literally anything can now use his DP.
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