Search the Community

Ladies and Gentlemen, I am in a quandary and am in need of some guidance. We are in the process of deploying a post image task sequence to the "All Client Systems" and I am reluctant to pull the trigger due to the new program notification pop up that will come with it. I was suppressed all program notifications in my packages, remove any sort of reminders and count downs from my advert. However, I am still getting the new program pop up on the client machines. Any ideas on how to remove the pop up for just this specific task sequence advert? I have figured out how to disable the pop ups using a global setting but want to make sure there are no other options prior to making such a broad change. Let me know if more information is needed. Thanks in advance cb Edit: The task sequence needs to be ran via Run Advertised Programs after the image is completed and the SCCM client has done its thing. We are using SCCM 2007.

I just set off my manage Distribution points for my newly created Captured image. I loaded and put it in to the Operating System Images. Is it normal to take down the rest of my PXE Booting ability till that is done? I have noticed this is the current case. I also can do no work in SCCM since it is slow\locked right now. How often do I need to update Distribution Points? What dictates this and why? My environment is existing but I am only a week in. The person that created it is no longer with us and was the SCCM expert, so I am learn on the fly. School starts for us in 3 weeks and I have to have these images up and tested by Aug 8th. I can go through the process I do if any one would like to review to see if I am missing anything or if there is a better way. Cheers, Les

I have been able to start an image I I have created. I get the F12 then PXE boot F12. I then Log in and select the new image I have created. The image kicks off fine but then I get a red X and the error: Task Sequence: (Image name) has failed with the error code (0x80070570). For more information, please contact your system administrator or helpdesk operator. I also then can not redo F12 and restart the process for testing. need some help.

A few questions on maintenance windows for SCCM 2007 collections. I have created a Parent collection that finds all of the servers I need to work with. I then have created child collections that feed off of the parent and split them based on other selections like so. Servers I Manage - (Parent) Domain Controllers - (Child)Windows 2008 - (Child)Windows 2003 - (Child)SQL Servers - (Child)Misc Servers - (Child) Now, if I set a maintenance window on the Parent Collection (Servers I Manager) and then deploy a package or update to the Child Collection (Windows 2008). The server that resides in both collections should not see the maintenance window from the parent collection as I am deploying to the child which has no maintenance window. I have read that "Maintenance windows are not inherited by subcollections." and the above would be true as there is no inheritance, but I've seen some discussion in that because the server itself resides in both collections, it will take the maintenance window from the Parent (Servers I Manage). Is this True? Thank you for any and all of your thoughts Regards, Yarrokon