anyweb

As this is requested a lot, here's how to make it easier for you to Capture Windows 7. Note that this method is not recommended as you should use the Build and Capture method to capture Windows 7 and the computer should not join the domain, that said, if you still want to capture a domain joined computer and you are willing to deploy that captured image (with registry settings from Domain Joining, gpo's etc...) then read on... Import the following Task Sequence into ConfigMgr by right clicking on the Task Sequences node of Operating System Deployment in ConfigMgr, and choose Import. capture Windows 7 X86.xml Once Imported you will have to supply it with two packages namely your X86 boot image and a new package called AutoLogin_windows7 The Autologin_windows7 packgage contains a registry file and a program the Program is as follows: reg import "autologin_windows7.reg" the properties are as follows: and the autologin_windows7.reg registry file contains the following Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "AutoAdminLogon"="1" "DefaultUserName"="Administrator" "DefaultPassword"="password" replace password above with the local admin password... once done, make sure to edit your task sequence so that it's using your X86 boot image by right clicking on the Task Sequence, select properties and select the correct boot image, then make sure that the Task Sequence is using your new autologin package by right clicking on the Task Sequence and choose Edit, finally advertise it to a capture windows 7 collection and add a computer to that collection using direct membership After you've added the computer to the collection, start it up, login to Windows, open control panel, open the RAP (run advertised programs) and kick off the Capture windows 7 task sequence. Side note: you'll need to create a step in your deploy task sequence to remove the registry autologin values otherwise the deployed image will attempt auto login on first boot.. Further Reading: 1. Auto Login as part of OSD Task Sequence 2. Login Single Domain User for Caching After Imaging via Task Sequence

where is the rest of this log ? can you post it please

International Client Packs (ICPs) contain international-language clients to use with System Center Configuration Manager (SC Config Mgr) 2007 SP2. ICP downloads contain only the Config Mgr client files, not the English-language SC Config Mgr 2007 S2, which is required. ICP1 contains the following languages: * English * French * German * Japanese * Spanish System Requirements * Supported Operating Systems: Windows Server 2003; Windows Server 2003 Service Pack 2; Windows Server 2008; Windows Server 2008 R2; Windows Server 2008 Service Pack 2 * Other Software: System Center Configuration Manager 2007 SP2 - English version Instructions Click the Download button next to the file most appropriate for your needs. * For ICP1 use the file - ConfigMgr07SP2Retail_RTM_ICP1_6487.exe Download > http://www.microsoft.com/downloads/details.aspx?FamilyID=4c8fa7d6-1671-4d76-860b-195b16c214a8&displaylang=en

what error do you get ?

It seems like Microsoft is accepting the outcome of the appeal case yesterday. The company has released an update for OEMs in the United States that strips the infringing feature from the ubiquitous word processor. "The following patch is required for the United States." The patch removes the ability to edit custom XML elements. "After this patch is installed, Word will no longer read the Custom XML elements contained within DOCX, DOCM, or XML files," Microsoft said on its website, "These files will continue to open, but any Custom XML elements will be removed. The ability to handle custom XML markup is typically used in association with automated server based processing of Word documents. Custom XML is not typically used by most end users of Word." This patch has been in the making for a while now, as OEMs were notified of the then-upcoming patch in October of this year. With the release today, OEMs have about three weeks to modify the machines in their channels to comply with the court order. "With respect to Microsoft Word 2007 and Microsoft Office 2007, we have been preparing for this possibility since the District Court issued its injunction in August 2009 and have put the wheels in motion to remove this little-used feature from these products," said Kevin Kutz, the director of public affairs for Microsoft, in an e-mail to ComputerWorld, "Therefore, we expect to have copies of Microsoft Word 2007 and Office 2007, with this feature removed, available for US sale and distribution by the injunction date." Existing copies of Word do not fall under the ruling, and do not have to be modified. via > http://www.osnews.com/story/22651/Microsoft_Strips_Infringing_Feature_from_Word

have you tried using the Windows 7 or Windows Server 2008 R2 DVD instead to create the boot.wim file ?

net share test=c:\test /grant:"NT Authority\WDSServer",Full

if you disable bits on the dp does it work ?

Do you know how much money your company could save moving to Windows 7? Thinking about deploying Windows 7? Need to crunch the numbers to show your boss the reduced TCO and quick ROI that Windows 7 will have for you’re company? The Windows 7 Return on Investment (ROI) Tool, powered by Alinean, can help you evaluate your current PC total cost of ownership (TCO) and identify the potential benefits of deploying the Windows 7 operating system to help lower costs, improve service levels, and increase productivity. This new tool can quantify the tangible value of Windows 7, estimate migration costs, and calculate the financial metrics necessary for your a project review and approval. To check out the the Windows 7 ROI Calculator visit the Pilot and Deploy area of Springboard or just click here. via > http://windowsteamblog.com/blogs/springboard/archive/2009/12/21/do-you-know-how-much-money-your-company-could-save-moving-to-windows-7.aspx#comments

check the Prerequisites for out of band management here on Technet and I quote: below that it includes a table of what system types offer what type of support within SCCM, does this help ? cheers niall

Problem: If you attempt to do a Capture User State on Windows XP SP3 with ConfigMgr Client with version 6221 (SP1) and USMT will fail with an error similar to the following :- The workaround is to create a USMT 4 package pointing to the X86 USMT 4 bits. To resolve the problem, install the SP2 configMgr client on your XP client before attempting to run USMT 4. thanks to Peter and the kind folks on Technet for helping me debug this issue. cheers niall references:> * USMT problem on a specific pc * User State Migration Fails 0x80070714

hi all, we are all visiting here, reading, learning, working, sharing, and also helping each other now lets see who the others are show your face and tell us a bit about yourself, here's me for starters... that's me in work, October 2010, now it's your turn ! cheers niall

we need more details of your setup, like is sup local or remote, and has sup ever worked ? can you include some logs from a failing client is it sccm 2007 sp2 or sp1

How to properly set up a Task Sequence to deploy Windows 7 images captured via an SCCM 2007 Capture CD When a Task Sequence is created via the "Create New Task Sequence Wizard", the Task Sequence may fail if the Windows OS being deployed is Windows 7 and the reference Windows 7 WIM image being deployed was manually created and then captured using the SCCM 2007 Capture CD. Here's how to fix it: http://blogs.technet.com/configurationmgr/archive/2009/12/17/how-to-properly-set-up-a-task-sequence-to-deploy-windows-7-images-captured-via-an-sccm-2007-capture-cd.aspx J.C. Hornbeck | Microsoft via > http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/d292690f-a2be-4c71-b4e9-72b993c8175d

The distribution manager (distmgr, the component that is responsible for distributing the packages to the distribution point) seems to be not quite working as one would expect with SP2. Don't panic, this seems to affect only the way DistMgr fails to distribute a package to a DP, see below. It relates to the "Number of retries" - and "Delay before retrying" settings: The "Number of retries" and "delay" are ignored (after reaching the maximum it is started again from scratch and does not wait the configured time, but only 10 seconds). Another MVP has confirmed this behaviour too. I have already sent a mail to Seattle. As soon as there is news, I'll provide an update! translated into English using google via > http://www.mssccmfaq.de/2009/11/06/sp2-distribution-manager/ (in German)

Now the ConfigMgr Management Packfor OpMgr 2007 R2 supports ConfigMgr SP2 ... http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a8443173-46c2-4581-b3b8-ce67160f627b&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MicrosoftDownloadCenter+(Microsoft+Download+Center) Read the complete post at http://wmug.co.uk/blogs/r0b/archive/2009/12/17/configmgr-2007-sp2-mp-for-opmgr-2007-r2.aspx via > http://myitforum.com/cs2/blogs/robm/archive/2009/12/17/configmgr-2007-sp2-mp-for-opmgr-2007-r2.aspx from Twitter

no problems and in case it isn't clear yet, you can move applications installation order up or down by 1. selecting a Task Sequence Step 2. press the appropriate button (move up, move down) by using the buttons at the top of the task sequence (applies to any task sequence step as long as there is more than one) see this pic for details as this topic is asked a lot I will pin it.

and make sure that allow users to interact with this program is NOT SELECTED otherwise it won't appear in the drop down menu, same goes for Disabled programs, they won't show up either

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.