anyweb

thanks for updating us with the solution, and for future reference, you should not do any configuring in the WSUS console ever, it should always be managed via SCCM's sup, this is probably why you had the problem in the first place cheers niall

what error did you get ? I will do up a topic on this very shortly as I have a working solution now, albeit a slight hack

don't manually delete the packages, do that within sccm and wait for the changes to propogate, check your system status component logs and the package status logs to verify any problems.

I would kep them separate, easier to manage see below

checkout site management, site settings, Certificates, Boot Media if no certicates appear there then have you ever added or configured the PSP role in SCCM ? doing so will allow you to create a self signed certificate (on the database Tab of the configMgr PXE Service Point properties)

is the configmgr client installed on this reference computer ?

odd problem. can you explain this line please

if you search for Article ID 936929 do you see any results ?

try a refresh does it show up then ?

ok interesting, after you do a sync, can you verify from the system Status component logs that the sync was successful and see does it appear then ?

check your classifications in the software update point components, are service packs selected ?

if it is marked as obsolete then it is still known.

is your All Windows XP updates search folder criteria setup like this ?

a machine that is unknown to sccm is one that isnt in sccm's database the machines mac address, guid or computername can be present in the sccm database, and you need at least two of those components to (for example) import a computer into sccms database and make it known

InfoWorld's J. Peter Bruzzese takes an admin look the key decisions and options you'll have to address to ensure a successful migration to Windows 7. Bruzzese's guide -- which includes a hands-on video tour of Windows 7 and a deep-dive PDF report that provides Windows 7 benchmarks -- examines hardware and software compatibility issues, addresses the licensing question, and lends insight for those Windows shops considering the virtualized desktop route. via > http://www.osnews.com/story/22286/Admin_s_Guide_to_Deploying_Windows_7

please raise a new topic in the correct section, this topic is for how to install SCCM 2007 SP1 in Windows Server 2008..

its not that hard to do when you think about it, all unknown computers (unknown to sccm) can be deployed via a task sequence advertised to the unknown computers collection... (windows 7 for example) whereas all known computers can be added to deploy XP.... does that make sense, or not ?

its easy i use collections and drop computers into collections based on what I want to do with them so if I want to deploy Windows 7 to a new computer I drop the computer into a collection called Deploy windows 7 if I want to deploy XP I can do the same for the XP computers, I have my task sequences advertised to the respective collections and they are mandatory unless of course I want a list of task sequences does that make sense ?

find out what this package is and distribute it to the DP and try again (GEO00009)

i believe ghost does multicasting which by the sounds of things is what you want to do is it ?

"Thanks to everyone's feedback, we're happy to announce that Windows XP Mode has RTM'd today. We expect to make the final release of Windows XP Mode available via the Microsoft Download Center on October 22nd. OEMs will be able to offer Windows XP Mode on their PCs based on their manufacturing schedules." via http://www.osnews.com/story/22272/XP_Mode_Hits_RTM_Status

can you elaborate ?

the regional and language settings are used as follows create a blank (or edit existing) sysprep.inf file with the following lines in it then create a sysprep package of the above file and add it to your task sequence, if you use MDT integration in SCCm you can use ztigather and zticonfigure scripts in the TS and they will poke the correct values you set on the collection variables into your sysprep.inf during deployment try it and post your results here

initiate a Data Discovery Cycle on the client and then refresh the collection in configmgr 10 minutes later any change ?

Windows 7 will be released October 22, and the pricing information for both the full and upgrade versions have been known for a while. However, as most of us geeks will know, there's a third variant you can buy, apart from upgrades and full versions: OEM or system builder releases. NewEgg has leaked the pricing information for these releases too. In stores in the western world, you'll be confronted with three Windows versions: Home Premium, Professional, and Ultimate (although that last version might be hard to come by). NewEgg has published the pricing information for all OEM variants of those three versions. Putting all the three price variants together for the three versions (get it?), results in the following table (as far as I can tell, these prices go for both the 32bit and 64bit versions): more > http://www.osnews.com/story/22265/Windows_7_OEM_Prices_Revealed