Biscuitgod

Alright... I'm pulling my hair out over here... i've just started messing with SCCM in the last 2 weeks.. I have a total of 4 models (so far) that i've been playing around with (All HPs). 2 of my models PXE just fine and things work great, but the other 2 models don't PXE boot at all... There's no errors or anything, just plain won't boot. At first i thought it was an issue with 32bit vs. 64bit, but this 2nd model is a 64bit machine... I see that PXE is loading on the screen (showing my MAC and GUID), then i obtain an IP (just like normal), then (depending on model), i'll either see 'TFTP......' which then switches to 'MTFTP.....', or just 'MTFTP.....'. It will just sit there and eventually time-out and boot to the HD. I cannot get these things to boot to WinPE! Anyone come across this at all???? it's driving me nuts... never before have I ever had issues PXE booting

I think all those steps have been done... i've double-checked my setup and it looks damn-near identical to what's in that article... We rarely will use the unknown computers collection... Any machines that are on our network will be imaged by us, so I'm curious about this right now for testing purposes only. Again, my problem is that the Install Updates section in my TS isn't working, as i watch a machine image, it simply flashes by the screen and doesn't install any of my updates. This is why i asked if i need to advertise the deployment management task to my TEST collection? Didn't know if it would get these updates to work or not within the TS. ALSO - One of the first steps of your article is to install WSUS but not configure it. Our environment was setup to use WSUS long before SCCM was utilized, so this step isn't accurate on our setup. We use WSUS for all software updates. The article you sent me is telling me to set it up a different way, but i cannot do this. How can i get this to work?? All I want is for the TS to install the updates while deploying my image.. That's it. All other software updates will be handled by WSUS after the fact, I just want it up-to-date as of imaging. Is this possible? Thanks

This is already in the TS. It's just failing to push out any updates.... Not sure how to do this.... Maybe this is my problem, but i'll need to know how to verify if this has already been done Do you have to adververtise the software updates to the collection BEFORE the TS will kick off properly to that machine?? Seems a bit redundant to me...

I'm very new to SCCM. This environment was setup well before I took this job over and I'm not sure on some of it's settings, so there may be a bunch of underlying issues causing this. My problem is: When I push out an image, I made sure to 'Install Software Updates' in my TS. I see this flash across the screen while in the act of imaging, but it flys by so fast (nothing is getting installed). My question is how do i get updates installed during the imaging process? My setup: I've done a lot of reading about this hoping i could figure out an 'easy' fix to my issue, but no go. I did read that WSUS OR SCCM could handle updates but not both. In our environment, WSUS was setup well before SCCM was, so that is what we use. Now that SCCM came along, a previous worker attempted to setup updates through it (from what i could tell, but i'm not 100% on that). I think the general consensus around here is to keep using WSUS. How can I make everything work together to push out updates upon imaging? Another question... Would it be best to let SCCM handle all updates? i think the worries right now are, a few people already know the procedure to approve and test updates, I think they're worried about messing that process up. Is this something that can still be done? Can I still have test groups and everything? (probably a dumb question, but i have to cover my bases). Thanks

I noticed that Obsolete setting but wasn't sure what that meant... You're work-around for the obsolete thing worked great! it's just too bad i have to mess with it. I suppose i can live with it since this is basically just for testing. but what happens when in Production we image a machine and maybe a month down the road a user needs to reimage for some odd reason? How do we remedy a situation like that?? The same way? I have a few other questions on things i have ran into, but will create a new post for those so they have their own topics. Thanks for your help

still having issues here... not sure what the deal is, but i'm not happy about this software what so ever here... I created a BRAND NEW advertisement, linked it to my test collection (with only my test machine in it). Still, that machine isn't seeing it because it's exiting the pxe boot... WTF is going on here? I can't believe something like this can be so terribly difficult. I just want to PXE my machine when i tell it to. Why am i having this many problems doing this???? My advertisement is mandatory, set to ALWAYS rerun. This hasn't made any difference.. the ONLY way i can pxe boot and run my reimage jobs more than once is when i delete the computer and re-import it. This isn't acceptable. Any help is greatly appreciated. Remember, i know the very basics about SCCM, but it doesn't really seem that difficult, so i just can't believe i can't get this figured out.

Thanks for the link. I'll check that out over the weekend. Now, I did change the Program Run behavior. I changed it to Always run, i figured since this is a test environment anyway, it woudln't be a big deal as of right now anyways. Well my original image job worked right away but after imaging, i tried to pxe boot again, and i got the same issue. I went back to SCCM and cleared last PXE advertisement on my collection. There was my image advertisment listed. I cleared that and tried again, still no luck.. any other reason why this wouldn't let me reimage a machine. Also while looking at the Clear PXE Advertisement, I noticed it showed the job active for 6 month exactly. Is there a way to change this? I never set an expire time, but it just put that in there. I'm so lost with this thing.. i just don't get how i can't PXE boot more than once to a machine without re-creating the computer account in SCCM.... Thanks

Found the Rerun Program option.. it was set to 'Never Rerun' but it was grey'd out. I found i had to make the advertisement a mandatory one to light up this section. Is there any reprocussions for setting this to 'ALWAYS rerun'??

I have tried the Clear Last PXE. This doesn't seem to work. When I select that on the specific computer, it even pops up and shows me there are no advertisements, but i clear it anyway. Not sure where to find the rerun behavior at? I'll look, but need to know where to look that up at... Thanks

I am a long-time Altiris user and have recently switched companies and working a place that strictly uses SCCM. I've noticed many differences that really drive me nuts about SCCM and here is one of them: I want to PXE boot a machine to test my images more than once. If I advertise a TS to deploy my Windows 7 image, everything's fine, but if i wish to then re-image the same machine, with the same TS Advertisment, it never kicks off and continues to boot to the HD. Is there anyway around this? It seems like i'm just sitting here spinning my wheels and not getting anything done. Now, i have figured out i can delete the computer account in SCCM, and recreate it and it'll work, but this is absolutely not acceptable with over 12000 possible machines. With Altiris, if i issue an image job to a particular machine it just does what you tell it. With SCCM, i issue an image TS, it images, but how do i then reissue it so this same machine can go again. The Advertisement is still active in the collection, so you'd think it'd just work. Can anyone help me... I'm sure i'll have MANY other questions to follow about all aspects of this application. So far i am very un-impressed with it's functionality compared to Altiris. Thanks