anyweb

sccm will take care of the WDS configuration as long as WDS is actually functional, so is the WDS service started or not ?

yes you can, you can add and remove roles at will, what iis page were you trying to show me, i didnt see any link cheers

This tip will show you how to let your local I.T. guy see a Task Sequence menu after PXE booting the computer. first of all create a new collection (in your Deploy collection) called MultiTask. from your list of available Task Sequences that you have already made, choose one, and right click and select Advertise. advertise it to your Multitask collection, make sure PXE boot is enabled and choose next make sure that you do not set any mandatory options (in other words, it is now voluntary) and click next set your distribution point settings and leave interaction as default and click next until complete through security and summary. repeat the above steps with at least one more Task Sequence, after this, you can verify that the task sequences are advertised to the MultiTask collection by looking at the collection properties and clicking on the Advertisements tab Now using Computer Association, import a computer (or create a direct membership) into the MultiTask collection and pxe boot it, you should see the following do as it says and press F12 it will start loading Windows PE If however, you see some of your Windows Deployment Services menus (like capture or deploy) then you will need to reconfigure the WDS server properties and set the PXE respone time to more than than PXE response time set in SCCM, and then restart the WDS service. If that doesn't help then verify that the computer you imported is not obsolete in SCCM. followed by this, just click next, if you want it to prompt for a password then configure the PXE Service Point role with a password then you'll see your list of Task Sequences, select one and you are done ! Note: if you want the password and choice menu removed via a script then checkout this post

if the smsadmin user account you mention here has domain admin permissions (which you should only do in a lab environment) then that user will automatically have local administrative permissions on any computer joined to the domain,

yes basically you can, but if you do you cannot deploy operating systems using the PXE service point role (PSP) as the WDS role is required by PSP more info about that here http://technet.microsoft.com/en-us/library/bb693934.aspx and here http://technet.microsoft.com/en-us/library/bb680753.aspx

they arent really empty, look at them closely (double click), plus as you add more sites, more entries will be added

try restarting the WDS service

doesn't your user exist in the All Users collection ? if that's not sufficient try this post or adapt the All Users collection query to suit your needs

is this happening with all clients that pxe boot to the server, what messages if any do they see before this ? any errors on your SCCM server in site status/component status ?

the container will populate itself if you followed the guide correctly, give it some time to do so. the container is needed to store info in AD about where sccm site servers are located here's some more info Four actions need to be taken in order to successfully enable Configuration Manager Clients to query Active Directory Domain Services to locate site resources: * Extend the Active Directory schema. * Create the System Management container. * Set security permissions on the System Management container. * Enable Active Directory publishing for the Configuration Manager site.

what domain account have you configured as the Client Push Installation Account =? this user must have local administrative access to the computer that you are trying to install the client on

i do believe the last post in my setup sccm2007 guide covers this in detail. cheers

"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