anyweb

first verify that the client and sccm box can ping each other and each others FQDN

verify manually by opening an administrator command prompt and doing a DIR in that folder

Hey everyone, recently Michael Niehaus recorded a video demonstration of how to deploy Windows 7 using the Microsoft Deployment Toolkit and System Center Configuration Manager 2007 SP2. I wanted to get you guys the link to the video, it’s about 10 minutes long but well worth the time. http://blogs.technet.com/systemcenter/archive/2009/12/15/deploying-windows-7-with-system-center-and-mdt.aspx

can you show me a screenshot of where in the ts its failing

what does netsetup.log say ? it logs domain join failures, it'll be on the client.This file is located in %windir%\debug

as Peter says, plus you should look at the deploying Firefox guide once you have that working create a brand new Task Sequence in OSD by right clicking and choose New Task Sequence, then choose Create a New Custom Task Sequence called install some applications click next, next, close. Once done, open the task sequence by selecting it and choose Edit. The task sequence will be empty !, click Add, General, Install Software select the Firefox package and the setup program done, repeat for each application you want installed in the Task Sequence and when done, advertise the ts to a collection of computers. cheers niall

look at the sccm logs for windows updates, specifically wuahandler.log and these too: Software Updates Client Computer Log Files * CAS.log - Provides information about the process of downloading software updates to the local cache and cache management. * CIAgent.log - Provides information about processing configuration items, including software updates. * LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client. * PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates. * PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers. * PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates. * RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations. * ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on. * ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients. * SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates. * ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows. * smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on. * SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers. * StateMessage.log - Provides information about when software updates state messages are created and sent to the management point. * UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface. * UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client. * UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle. * WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates. * WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates. Windows Update Agent Log File * WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

great stuff, if you want to share how you resolved it so others may learn then please do so cheers niall

is it a vmware image ? perhaps you need vmware storage drivers included ?

well you'll need to capture a Windows XP/2003 image first to see how, read this post

if you just want to capture it then yes disable the entire BUILD section of the build and capture ts, here's a guide for Capturing Windows 7 cheers niall

wds and pxe, no, do nothing * I also have to change/update my boot images - yup if they have any drivers or customisations added/or they are MDT * Set the new client install upgrade in each task sequence - just upgrade your current client package * reinstall every sccm client to sp2 - use this post

that is your original failure, so did you verify that its actually working ?????????????????

If you were installing SCCM 2007 on Windows Server 2008 R2 and then tried to download and install and configure Webdav as you did with Windows Server 2008, you'd have problems getting WebDav to work with SCCM. Webdav in Server 2008 and Server 2008 R2 are different versions, and need to be dealt with differently. Hopefully this post will clear that up:- In a nutshell: Windows Server 2008 - download and install Webdav 7 Windows Server 2008 R2 - Use Server Manager, Roles as described below to install WebDav 7.5 To install Webdav on Server 2008 R2 In Server Manager, in the IIS Role under Server Manager, Go to Add Role Services and add WebDav Publishing listed under Common HTTP Features. Then follow the steps below to configure the WebDav in IIS. How to Configure Windows Server 2008 for Site Systems [Technet] <or> How can I configure SCCM 2007 SP1 in Windows Server 2008 [windows-noob] Why is this important to me ? All .config files are blocked by default on Server 2008 - see: http://technet.microsoft.com/en-us/library/cc431377.aspx meaning configuring webdav can be problematic. You can still download and install WebDav 7.5 for Server 2008, however the fundamental difference here is that Server 2008 R2 has it built in, 2008 doesnt, and if you download and install Webdav 7.0 on Server 2008 R2 you may get webdav related problems where the SMS_MP_CONTROL_MANAGER reports failures references: 1. http://www.myitforum.com/forums/S_MP_CONTROL_MANAGER-m217303.aspx 2. http://blogs.technet.com/b/configurationmgr/archive/2010/10/26/error-the-webdav-server-extension-is-either-not-installed-or-not-configured-properly-in-configuration-manager-2007.aspx 3. http://technet.microsoft.com/en-us/library/cc431377.aspx I hope this helps cheers niall

verify that the 8th version of that source package is on the dp P0100007:8 <---

find out what this package is hint look at Package Status and make sure to distribute the package to the DP, then try again cheers niall

check your firewall,

so does it get an ip ? can you ping the fqdn of the sccm server ? can you post the rest of the smsts.log file it seems to be missing some of it.... did you try adding windows 7 network drivers to your boot.wim file ?

what does pxeMSI.log say

great work, and thanks for the guidance as well Peter, I have a PKI guide in the works, coming soon, i would like both of you to go through it and offer feedback once published, cheers niall

thanks for sharing this info, hopefully this will help someone

here's a closer look

first of all how did you setup your task sequence for this and is the target computer partitioned with c: and d: drives ?

hi Marko sorry for the delay in replying i think the answer is yes but have you verified here on Microsofts Volume License site ? in addition take a look at this resource on Technet it has videos explaining activation: * Fundamentals of volume activation * Activating Windows ® 7 with MAK * Activating Windows ® 7 with KMS * Understanding activation and validation in Windows ® 7 and Windows Server 2008 R2 cheers niall

Today, I have an update from Kim Griffiths, a product manager on our team focusing on enterprise and government customers. She is a former infrastructure consultant specializing in Active Directory, security, and Microsoft Exchange with more than 15 years of experience working in IT, and will be contributing to our team blog from time to time with information for IT professionals, including podcasts. Kim says: Here’s the scenario: You have the Key Management Service (KMS) hosted on Windows Server 2003 activating your Windows Vista and Windows Server 2008 systems. Now you are ready to start piloting and deploying Windows 7 or Windows Server 2008 R2. Some of your first questions are likely: · Can I use the same KMS to do that? · Do I need to do anything to make that work? The answer to both is yes. The update to the KMS is necessary because of the keys. With each new product edition and release, new keys are provisioned and distributed to our customers. An update is necessary to make the service aware of these new keys in order to activate the new generation of operating systems. There are basically four steps to accomplish this task: 1) apply the update, 2) install the new key, 3) activate the updated host, and 4) check to make sure everything is working properly. It is a simple process that should only take a few minutes to complete. KMS_Podcast Check out this video podcast to see what you need to do and where to get more information. An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 2 (SP2) and for later versions of Windows Server 2003. To learn more, view the KB article (968915). For more information on volume activation, including KMS, visit the Windows Client Tech Center for Volume Activation. It is important to note that there is also an update for KMS hosted on Windows Vista or Windows Server 2008. To learn more, view the KB article (968912). That update is separate from the one described in this blog/podcast, though the process is similar. Not to worry, we’ll cover this one soon. via > http://windowsteamblog.com/blogs/genuinewindows/archive/2009/10/19/updating-kms-on-windows-server-2003-to-support-windows-7-and-windows-server-2008-r2.aspx