anyweb

that error (80004005)could be access denied to the smp folder itself so check folder permissions of the smp, can you access it from explorer on the box you are running the task sequence on ? can you enable verbose logging and then post the scanstate and scanstateprogress.logs pls, scroll down to Testing USMT in this post for help with that

ok what do the logs on your client say ? (look at cas and ccmexec amongst others - see below) The client logs are located in the %WINDIR%\System32\CCM\Logs folder or %WINDIR%\SysWOW64\CCM\Logs (for x64 OS). Client Log Files * CAS - Content Access Service. Maintains the local package cache. * Ccmexec.log - Records activities of the client and the SMS Agent Host service. * CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points. * ClientIDManagerStartup.log - Creates and maintains the client GUID. * ClientLocation.log - Site assignment tasks. * ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages. * DataTransferService.log - Records all BITS communication for policy or package access. * Execmgr.log - Records advertisements that run. * FileBITS.log - Records all SMB package access tasks. * Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection. * InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records. * LocationServices.log - Finds management points and distribution points. * Mifprovider.log - The WMI provider for .MIF files. * Mtrmgr.log - Monitors all software metering processes. * PolicyAgent.log - Requests policies by using the Data Transfer service. * PolicyAgentProvider.log - Records policy changes. * PolicyEvaluator.log - Records new policy settings. * Remctrl.log - Logs when the remote control component (WUSER32) starts. * Scheduler.log - Records schedule tasks for all client operations. * Smscliui.log - Records usage of the Systems Management tool in Control Panel. * StatusAgent.log - Logs status messages that are created by the client components. * SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

what advertisement settings did you select ?

By accident I bumped into this good resource. What it is? A Super Flow is a collection of help files, pictures, diagrams, videos and online resources all combined in one file/application. This particular Super Flow introduces SCOM to people who are new to the product and have to work with it in an Operator User Role. image Much of the information in this Super Flow is based upon the SCOM Documentation. The strength of it is that all is to be found in one place without taking a real deep dive. When people still have questions they can go to the Resources tab which shows them where to get additional information. The Super Flow is to be found here. via > http://thoughtsonopsmgr.blogspot.com/2010/08/scom-operators-basics-superflow.html

Last year at this time, Microsoft was in the final stages of preparing Windows 7 for its worldwide launch. The new OS was finally available to the public—well, at least that segment of the public with a TechNet or MSDN subscription. Those early adopters had to wait a few weeks after the official release to manufacturing date but still got a head start on the general public. Those demanding and skeptical Windows users have now had a full year to stress-test Windows 7 and decide whether it’s good enough to replace Windows XP. The verdict? Windows 7 has been a quiet success, maybe even a phenomenon. Last spring, a Microsoft executive told me that the company had sold 100 million Windows 7 licenses. As part of its quarterly earnings call in July, Microsoft announced that that number had risen to 175 million, and the company has projected that a total of 350 million Windows 7 licenses will have been sold by the end of this year. That’s a run rate of roughly 30 million copies per month worldwide, and it represents a lot of Windows 7-powered PCs. Despite the big numbers, Microsoft has been almost eerily silent about its success. I didn’t hear a lot of bragging in advance of the Windows 7 launch, nor has there been much chest-thumping since. The competition has been muted as well. When was the last time you saw one of Apple’s infamous “Get a Mac” ads? Hint: the last three ads in Apple’s campaign were released on October 23, 2009, the day after Windows 7 was launched to the public. With titles like Broken Promises and PC News, Apple’s marketing executives were hoping for a Vista-style wave of complaints, but they were as disappointed as Windows 7 upgraders were relieved. And then John Hodgman and Justin Long went off to spend more time with their families. Meanwhile, Windows 7 keeps selling and XP usage is dropping. That’s certainly true at this site [zdnet], where Windows 7 visitors now outnumber those using Windows XP and Vista usage has plunged in the past year. Here’s a graphic representation of how Windows 7 usage has increased among visitors to this site since its first beta release back in January 2009. Data source: Google Analytics data for all pages at Ed Bott’s Microsoft Report. Samples cover 30-day periods ending in December 2008, August 2009, December 2009, and August 2010. Each sample consists of a minimum of 100,000 unique visitors. I asked ZDNet’s editors to check sitewide stats for me. They report similar trends. Windows 7 usage increased from 22.2% in December 2009 (exactly the same as Windows Vista) to 35.6% in August 2010. Over the same period of time, XP usage among ZDNet visitors fell below the 50% mark, dropping 7 points to 46.6%. At that rate, Windows 7 will surpass XP among all ZDNet visitors well before the end of this year. Vista users were clearly eager to upgrade, judging by these results, even to a beta release of Windows 7. But XP users are also converting at a steady clip, with XP diehards now under the 40% level here. These numbers include only Windows users, but I also found interesting results when I looked at the percentage of visitors using Mac OS X. As of this month, that number has returned to its December 2008 levels (slightly over 5%) after peaking above 8% a year ago this month, just before the launch of Windows 7. So what’s really going on? You can summarize the entire story in one simple sentence: Windows 7 is the anti-Vista. Reviews have been overwhelmingly positive. Every couple of months, some blogger or reporter tries to stir up a Windows 7-related controversy (remember the “Black Screen of Death” scare stories?), but nothing seems to stick. Most of the obvious annoyances of Vista are fixed—especially the misunderstood User Account Control feature—and there hasn’t been a scandalous security or privacy issue or a killer bug. Word of mouth has been solid, too. In fact, it’s good enough to finally dislodge XP’s stranglehold on corporate computing. Not overnight, but certainly by XP’s end-of-life date in April 2014. That’s the conclusion I draw from a review of data covering Windows 7 adoption rates in corporations, which are notoriously conservative when it comes to OS upgrades. Although the rates of adoption are far slower than among consumers, there’s evidence to suggest that corporations are migrating to Windows 7 at a much faster pace than they did for either XP in 2002-2003 or Vista in 2007-2008. According to a Forrester Research study, Windows 7 was “already powering approximately 7.4% of corporate PCs” in April 2010, six months after its release. Although that number might sound small, it represents about a 1.25% increase in Windows 7 usage per month—an impressive number considering how slowly most corporations move. It’s also more than twice the adoption rate of Windows Vista at the same point in its release cycle (Vista usage in enterprises topped off at 12.6% after three years), and it’s 50% greater than Windows XP after a similar period. As Forrester analyst Benjamin Gray explained: Today, roughly 70-75% of corporate desktops are still running Windows XP. If enterprise adoption rates for Windows 7 continue at the seemingly slow pace of 1.5% per month, Windows 7 will probably overtake XP in corporate installations by the end of 2011. If that rate picks up even slightly, as it appears to be doing, then there’s a good chance that XP will hold a single-digit share of corporate desktops when it’s officially retired in 2014. Last year around this time, I looked at some bullish projections of Windows 7 adoption rates. One was from IDC analyst Al Gillen, who predicted that Windows 7 would account for 75% of units shipped in 2011 and nearly 90% of all Windows desktops sold in 2012. This week, I asked Gillen whether his outlook for Windows 7 was still optimistic, based on the last year’s data. There’s “no change” in that level of optimism, he told me. “We are still expecting Windows 7 to be very successful.” You can take that to the bank. via > http://www.zdnet.com/blog/bott/its-official-windows-7-is-a-hit-and-xp-is-finally-in-decline/2324?tag=content;feature-roto

have you verified that the network access account works (perhaps locked ?)

hi Ray, if you cannot pxe boot due to network issues (what issues are they ?) did you know that you can create standalone media (cd) to handle that part of the boot process and the rest will be performed as normal ? the suggestions i offer are only one way of doing things, you could of course do it differently and use some HTA frontend which links to variables in your task sequence which in turn decides what gets migrated and when hth cheers niall

this is a good way (there are many) http://www.windows-noob.com/forums/index.php?/topic/1166-fully-automated-application-groups/

updated the link, thanks !

First off, if you have not downloaded the beta or seen some of the exciting information on Configuration Manager v.Next, Check out these links: * System Center Configuration Manager Site * System Center Configuration Manager: vNext Beta Site * Configuration Manager v.Next Beta Download on Connect * The System Center Team Blog * Configuration Manager v.Next VHD Test Drive Hierarchy wide Bootable or Prestaged media. One of the most requested features/capabilities around operating system deployment in Configuration Manager 2007 is the ability to have bootable media that is not tied to a specific site. A large portion was restrictions within the Configuration Manger 2007. In Configuration Manager v.Next we have spent time modernizing the infrastructure. The new hierarchy (based on SQL replication), is flatter, shares more data across sites and requires less infrastructure. As part of the hierarchy redesign, we focused on ways to update Bootable media to be dynamic and not require a specific disc per site. Let’s go over some of the details. How it works today: * In ConfigMgr 2007, an admin creates Bootable media. * During the creation, the media is generated with information specific to the site. * The computer is booted to media and contacts the default site Management Point for information about Optional and Mandatory Advertisements. How it works in v.Next: What needs to be setup: * A v.Next Hierarchy containing: o A Central Administration Site o Two or more primary sites (No need for hierarchy wide media if there is just one site =) * Boundaries defined for the Primary sites * Distribute the Boot Image that is needed for the media to one or more Distribution Points Steps to Create Task Sequence Media: * Select Create Task Sequence Media. * Select Bootable Media (or Prestaged media) * A this point you now have an option for Dynamic Media or Site Based Media. o Dynamic Media gives you the option to use one piece of media for the entire hierarchy. It will redirect the client based on its current location. o Site based Media keeps the parity with ConfigMgr 2007. It remains tied to a specific site. * When you select Dynamic Media, you now receive fields to select a Management Point. You can specify several Management Points for the media. This gives you a fallback if the first Management Point in the list is not available. When specifying the Management Points, keep in mind all clients using the media will contact the Management Points in the order specified for the initial request. The initial request is only a couple KB. How does it all work? * Client boots to the Bootable Media and the Management point you selected for the media is used for an initial request. * The client send the Management Point a request takes networking information about the client. * The Management Point performs a server side look up based on defined boundaries to determine the correct site for the client. * The Management Point returns the default Management Point of the correct site for the client. * The client contacts the default Management Point for the correct site for available or required deployments (formerly Advertisements). * The client processes all further communication with the correct site to process its deployments. John Vintzel Microsoft Corporation | Program Manager | System Center Configuration Manager | twitter: jvintzel via > http://blogs.technet.com/b/inside_osd/archive/2010/08/18/v-next-beta-1-feature-hierarchy-wide-bootable-media.aspx?utm_source=windows-noob.com&utm_medium=twitter

yes it will re-appear as soon as the discovery kicks in, did you Delete or Delete Special ?

maybe the files themselves are blocked (exe's) to unblock them right click and choose unblock or copy all the drivers to a FAT file system then back to the drivers folder and then repackage them. there is one other option, in the Apply Drivers package step, select 'Do unattended installation of unsigned drivers on Versions of Windows where this is allowed@ but at least you are getting somewhere,

i dont see any pictures, just mht files...

did you have to change any perms on the xml file ?

did you see that ^

hmm i simply used the IRRT step (instead of both) and it installed all drivers perfectly on a Dell E4200 here device manager i didn't do Jason's step but it may help you, i don't have the same hardware as you so cannot test that model. during the install a c:\_SMSTasksequence folder is created as normal and in there was drivers, along with several other folders number 1 to 31 or so, in addition there was a TEXTMODE folder with some iastor drivers *inf sys etc* and a TextSetup.OEM file which contained the following text

did you create a package from definition for the client package ? did you define a network access account with full local administrative permissions on those clients ?

Hello everyone, we wanted to get this information to you as soon as possible. We now have released a fully configured virtual machine for ConfigMgr v.Next Beta 1. Based on a Windows Server 2008 R2 x64 OS, this is a fully built virtual machine ready to import into your Hyper-V environments. This is something the ConfigMgr team has done for a few major releases, starting back at the ConfigMgr 2007 RTM timeframes. We are really excited to get you guys this type of access, to help you evaluate the latest and greatest ConfigMgr v.Next release. We are also in the process of uploading the hands on labs for ConfigMgr v.Next as well, look for that announcement soon. Some resources for you: * VHD Test Drive - System Center Configuration Manager v.Next on Windows Server 2008 R2 – link * VHD Test Drive - System Center Configuration Manager 2007 R2 - link * Configuration Manager vNext Beta 1 evaluation download – link via > http://blogs.technet.com/b/systemcenter/archive/2010/08/18/configuration-manager-v-next-beta-1-now-on-vhd-test-drive-program.aspx?utm_source=windows-noob.com&utm_medium=twitter

in the system management container in AD, do you see that it has populated with site info ?

can you post the smsts*.log files please ?

ok assuming you have added ALL those drivers into the package as per the link (had to re-read your post, sorry) do you see the drivers listed anywhere on c:\drivers\? i'll try and do a test here in my lab but it may be tomorrow before I post a result

well you could pull the capture task out of a build and capture task sequence, that is essentially taking a wim backup of a system

you could script a full backup (to wim file), not hard to do but requires a lot of storage for the wim file and/or network speed. You should be able to deploy sp3 without having to do this though so why do you think it will fail ?

interesting result and thanks for confirming

check in c:\windows\temp