anyweb

"One Microsoft Way is reporting that Microsoft has significantly incremented the build number of both Windows 7 and Windows Server 2008 R2: 'Reports across the Web are pointing to a build 7600 for both Windows 7 and Windows Server 2008 R2. This is significant because the bump in the build number would suggest that Microsoft has christened this build as the Release to Manufacturing (RTM) build. The RTM is expected to be given out to Microsoft partners sometime later this month and launched on October 22, 2009, the day of General Availability (GA). The build string is "7600.16384.090710-1945," which indicates that it was compiled just a few days ago: July 10, 2009, at 7:45pm. Microsoft only increments the build number when it reaches a significant goal, and the only one left is the RTM milestone. The last builds that were leaking were all 72xx builds, so such a large bump is suspicious but at the same time it is something Microsoft would do to signify that this is the final build.'" via slashdot

you can add boot images to WDS after manually configuring it. I've done it and had both SCCM and WDS happily co-existing. The location of WDS is not important aside from the fact that your DHCP server will need to have options set to tell the pxe requests where to look, once youve configured wds you'll be able to PXE boot to it, press F12 then to see the normal Windows Deployment Services boot menu (capture-deploy-discover whatever...=)

you should always be using the Windows Vista network drivers when updating boot.wim files as boot.wim is windows PE which is based upon windows vista cheers anyweb

in the SCCM All Systems collection, right click the CLIENT and choose Install Client, select all the checkboxes and click next the sccm client should now install on the client computer, refresh it after 10 minutes in the collection (right click on the all systems collection, choose update collection membership) then refresh in the collection, does the client say Client=Yes now ?

please have a look at the Capture and Deploy guides right here then

are you using wds or sccm now ?

try it and see what happens

not to the account, but to the computer the user is logged onto... i did it so that you can see how to target users with a query both methods work but the preferable method is to target the Computer

sure there is, but you'll need to add images to WDS first (boot images and install images) if they are not in sccms database they should then try to boot to wds

hi Scotts, what you are probably referring to is the Lite Touch menu's you see with MDT, you can get a similar effect by using HTA's within SCCM, read about that here

have a read of this

this might give you some ideas http://www.myitforum.com/forums/m_194863/m...y/tm.htm#194863 but you should test this in a lab first before doing anything in production

pm me when you are ready to try this

on the SCCM server, you have to check if the client appears in the All Systems Collection does it ?

try disabling it, does it work then

hi kingskawn sorry i just posted that screenshot for another post on technet, it wasnt directed at you. are you software updates working ok or not ?

look at this post and welcome to windows-noob !

see here

firewall enabled or disabled ?

below is a screenshot of Offline Updates (via MDT integration in the Task Sequence)

if it\s missing, then create it as per the adsiedit guide, then once permissions are correct, it will populate with info cheers

heh, good work

cool, glad to have helped

I'll see if i have time to test this,

you can deploy XP using WDS in mixed mode or using RIS (the old fashioned way). To deploy XP using WDS without a PXE enabled network card you would use what is called a discover (deploy) boot image, you should only be using the boot.wim file from a Windows Server 2008 or Windows Vista SP1 DVD for these jobs, i'd advise you to go through the capture and deploy WDS guides here for starters, they work just fine for XP too