anyweb

ok first things first, did you read the README that comes with sp2 beta ?

did you install mdt 2010 beta as well ? are you testing this with real hardware or in virtual machines

ah well we use SCCM here, hence the SMS in the filename, but glad it's working now

can you remove the advertisement of that program for that machine ?

ok you must have missed that in the guide then http://www.windows-noob.com/forums/index.php?showtopic=491 glad to hear it's working now though

ok then try pushing a new advertisement to it, eg: firefox make sure the firewall is disabled on the client for the test

ok build and capture done, don't use Sysprep 2, you must use the version that comes with Windows 7. now, after it was built i logged in as local administrator the pc was removed from the domain already) i then opened a CMD prompt with Administrator Permissions and browsed to c:\windows\system32\sysprep\ and then executed sysprep.exe /quiet /generalize /shutdown /oobe and got this error is it the same one as you get ? anyway, try this kill this process wmpnscfg.exe or wmpnetwk.exe and do it again should work then kudos to http://www.swishertech.com/blog5.php/2009/...-trying-to-sy-7

ok i'm doing a build and capture of Windows 7 now, and hope to test sysprep on it shortly can you tell me what service pack level on sccm have you installed, what version of mdt and what sp level on server 2008 cheers

try setting Option 67 to \boot\x64\wdsnbp.com instead, does it work ?

now that DNS is working can you tell me if your client is showing up in the all systems collection with Client = Yes and Approved = Yes status

sorry, i assumed that when you said 'not part of SCCM' that you didn't want any SCCM functionality (including r2 support which is where unknown computer support comes from) thanks for clarifying it

here's a Video explaining the changes in 7 relating to activation and it goes into some details about * Your KMS host * KMS keys * MAK keys In summary: Windows 7 volume licensing customers have two options of licensing, KMS and MAK, by default, all customers will get a KMS key. * you can activate Windows 7 using KMS as long as you have 25 machines (same as Vista requirements) however now that total can be made up of virtual machines as well as real machines * you can activate using your existing KMS host as long as it has been patched with a patch for Windows 7 and the Windows 7 kms key added * or you can setup a separate KMS host for activating Windows 7 *or you can use MAK keys (similar to retail keys except they can be used multiple times). MAK keys can be activated over the internet or via proxy (no internet) using the VAMT tool which is available on the new WAIK. here's the full video > http://edge.technet.com/Media/Volume-Activ...s-in-Windows-7/ and for details about volume activation check here http://www.technet.com/volumeactivation

We are close, but have not yet signed off on Windows 7. When we RTM you will most certainly hear it here. As we’ve said all along, we will RTM Windows 7 when it’s ready. As previously stated, we expect Windows 7 to RTM in the 2nd half of July. Windows 7 will be available in many languages from around the world. For us to consider RTM “done”, it requires that all languages be completely finished. So there is a lot of work that needs to take place for us to finalize all languages of Windows 7. We also need to get to a point of “global readiness” with our partners. Our partners being ready for Windows 7 is extremely important to RTM. As Steven Sinofsky mentions in this blog post in May, RTM isn’t a single point in time. It’s the beginning of the next “process” for Windows 7. At RTM our partners begin their final preparations for Windows 7, including testing and building images for new PCs. RTM is essentially the final “stage” of engineering for Windows 7 before it hits the market at General Availability (GA). As Steven notes, engineering continues on Windows 7 from RTM until GA on October 22nd. more > http://windowsteamblog.com/blogs/windows7/...dows-7-rtm.aspx

there's a new version available for deploying Windows 7 and Windows Server 2008 R2, it's still in beta and here is the download

You can now download the Microsoft Deployment Toolkit 2010 Beta 2. MDT 2010 will support deployment of Windows 7 and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP. For details on the MDT 2010 Beta 2, see the Microsoft Assessment and Planning Toolkit Team Blog. http://blogs.technet.com/mapblog/archive/2...-available.aspx

first things first, if you removed the dc and dns role then what is providing that ? can you do a simple nslookup test on the sccm server to see that IT is correctly using DNS type nslookup and paste the results here

try REMINST/SMSBoot/x86/pxeboot.com

which version of 7 is this and where are you running sysprep from ?

is DNS functioning correctly on the WDS server do an nslookup to test it

how are you setting it currently

is wsus running on the same server as sccm ?

ok have a read of this article on MSDN regarding Synchronizing from Microsoft Update or an Upstream Server and from your last post it does do this, and you just have to accept it i guess I set my search folders up as follows, this way i get to see/pick whatever updates I want, for example, if i want the service packs i can take them from the OS All Updates search, and so on does this help ? and finally, from the SCCM help file: The Sync Source tab contains the following elements: Synchronize from Microsoft Update Specifies that the software update point synchronizes with Microsoft Update. This setting should be selected for only the software update point that is highest in the Configuration Manager 2007 hierarchy. Synchronize from an upstream update server Specifies that the software update point synchronizes with an upstream update server. The software update point at the parent Configuration Manager 2007 site is automatically configured to be the upstream update server. Do not synchronize from Microsoft Update or an upstream update server. Specifies that the software update point does not synchronize with any server. Select this option if using the WSUS export/import function to obtain software update definitions. For more information, see How to Synchronize Updates Using Export and Import.

on the containers, right click and choose properties,

nope, click on the Member Of tab to find out what Active Directory Security Groups the user is a member of

what Active Directory Security Groups is your SMSAdmin user a Member of ?