Nebuchadnezzar

I am also experiencing similar symptoms and could really use some feedback on this as well. My environment is SCCM SP2 R3 on Server 2008 R2 x64. My WSUS is Version 3.0 SP2 is on the primary site using the default SQL Embedded DB, and the SUP Role is also on the Priary site. WSUS was installed without configuring (configuring was handled by SCCM). What I'm seeing is that my SCCM isn't displaying certain updates which have been inventoried by WSUS. They are visible within the WSUS console but not within SCCM (for instance Bulletin IDs MS08-003 and MS08-006). I've tried re-installing both SUP and WSUS with the same results. The SUP-WSUS Sync completes successfuly and there are no errors within WCM.log, WSYNCMGR.log, or WSUSCtrl.log. One thing I DO notice is that there are these errors within the WindowsUpdate.log file but I don't know whether they're related to the patches that aren't being displayed, but there seem to be more patches ot being displayed in SCCM that I see for these errors: 2011-04-29 11:20:59:175 896 12c4 DnldMgr Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update 37B06CAD-1544-4484-ACB7-CCFE6BD3BE74 is "Priority" regulated and can NOT download. Sequence 4968 vs AcceptRate 0. 2011-04-29 11:20:59:175 896 12c4 DnldMgr Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update 15943B40-3D54-494A-B6AB-E0C49DD3D427 is "Priority" regulated and can NOT download. Sequence 4968 vs AcceptRate 0. 2011-04-29 11:20:59:175 896 12c4 DnldMgr Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update 8D75381D-A3D2-452F-A13E-67FF59E2081B is "Priority" regulated and can NOT download. Sequence 4968 vs AcceptRate 0. 2011-04-29 11:20:59:175 896 12c4 DnldMgr Regulation: {9482F4B4-E343-43B6-B170-9A65BC822C77} - Update 617ED1AE-0CB8-4409-9C96-FCDE01F15E16 is "Priority" regulated and can NOT download. Sequence 4968 vs AcceptRate 0. Also I've read that some updates are not displayed within SCCM if they require user intervention or if they have been superceeded. The Microsoft Updates catalogue displays properties like these and I've used it to view properties of these and a couple other updates and I do not see anything that indicates either of these to be true for the patches i've looked at. Also I have a Central Site (in a separate hierarchy) which is exhibiting the same symptom with the same patches. Is there something about these certain patches which proves this is normal behavior? UPDATE: It appears that the updates inquestion here in my case have been superceeded, which explains their non-existence within my SCCM console.

Great post, this has been helpful!! I want to find out if anyone has had any success with creating a custom Task Sequence that renames a computer?? For instance, I'm working on a TS that will prompt for a new name, unjoin the machine from the domain to a workgroup, then rejoin with a new name. Thus far I am able to prompt for and obtain the new name either when the TS is launched from PXE by using a TS Variable, or when launched from the Run Advertised Programs control panel applet by using a script to prompt for the name. The point I am at a stall at is when it comes to applying the new name. From what I know the only time the variable for OSDComputerName is paid attention to is during the "Applying Windows Settings" task. However, since this isn't a full OSD TS there seems to be an issue with using this step in my custom TS. There is a Task Sequence error that references this, it's small but I won't paste it in this entry however, I will attach the error to this posting as a text file if anyone is curious. This thread has been active on and off so I hope there are still members out there paying attention who might have some ideas on how to get around this or on another method to use. Thanks in advance! UPDATE: My Apologies, everyone. I thought I scanned through this entire article but it appears I did not! There is a posting by AnyWeb on Feb 23rd that provides an option to perform just what I'm trying to do by using a third party name changing tool. These forums are extremely helpful. Thanks again! TaskSequenceError.txt