anyweb

where do you have the install software updates step ? is the computer in the domain ?

first of all what version of sccm are you running ? secondly the only drivers you should add to your boot.wim files are Network drivers (sometimes storage too, but rarely) and the network drivers are based on the version of SCCM and not on the os you are deploying eg: if you are running SCCM 2007 sp1, use Windows vista based network drivers if you are running SCCM 2007 sp2, use Windows 7 based network drivers the drivers used by the os you are deploying (windows 7 or windows xp or whatever) are applied during the Apply Driver Package stage of the Task Sequence, your failure, baseed on the logs provided seems to be here <![LOG[Failed to locate the local data path. The files needed to resume the task sequence are missing. This could be because the task sequence finished while in Windows PE. Please check the largest available partition for SMSTSLog\smsts.log file for more information. The system cannot find the file specified. (Error: 80070002; Source: Windows)]LOG]!><time="11:17:02.912+240" date="08-30-2010" component="TSManager" context="" type="3" thread="7444" file="tsmanager.cpp:1106"> <![LOG[Task Sequence Manager could not initialize Task Sequence Environment. code 80070002] so can you tell me a bit about how you set up your task sequence, how are you executing it etc.. cheers niall

it will probably fail (feel free to verify please and report back) as the back end WSF file (CUSTOM_AppInstall.wsf) isn't expecting that input, you'll have to talk to your scripter(s) and ask them to rewrite the back end script to take account of multiple dc's and once you have it working, post it here cheers niall

hi there, in your ccm/logs folder do you see any other SMSTS*.log file ? if so does it list the actual failure as i don't see one mentioned in your log

first of all how did you set the software metering rule and did you wait until the clients reported back ?

We already know quite a few details about Internet Explorer 9, Microsoft's upcoming attempt to retain - or grow - its market share in the browser world. Standards and speed are the main focus of IE9, and if a video of the upcoming beta release is anything to go by, they're doing pretty well. Just... Did they just manage to make the interface even less appealing? Microsoft has fed us a number of builds for Internet Explorer 9, and while theyshowed off the speed improvements as well as the much more modern standards support (95 on Acid3), Microsoft remained tight-lipped on what, exactly, it was planning to do about that abomination they dare to call a "UI" used by the previous two Internet Explorer releases. With the beta release only a few days away, leaks are bound to occur. A website called IEBest.com (I wish I was making this stuff up) claims to be in possession of the beta release, and has the video material to prove it. Of course, it's hard to assess how genuine this stuff is, but if it is, the IE9 user interface team deserves a spanking. Assuming this is real, the interface doesn't look particularly polished; the tabs feel bolted on, as if they're not part of the actual program. If it were a screenshot, I'd call Photoshop on that one. Everything does look a lot tidier than previous releases, but one massive problem stands out like a major cringe-inducing eye-sore. While I'm this close to proposing to Chrome's UI so I can give her babies, Chrome does have one major problem: lack of tab overflow. If you open boatloads of windows in Chrome, the tabs become ever smaller and less readable, until you're finally just staring at a white mountain range. However, at least Chrome will give you the full width of the window to play with. In this supposed IE9 user interface, you're given just half of the window for the tab bar, because the stupid address bar is in the way! This monumental oversight alone makes me think we're looking at a fake. This just can't be real. If it turns out this is, in fact, real, I'm going to do a massive facepalm. via > http://www.osnews.com/story/23771/Internet_Explorer_9_UI_Video_Leaked

My post late last week about unplanned downtime for Microsoft’s Business Productivity Online Suite (BPOS) seemingly has opened the floodgates for more similar reports. On September 7, I began receiving notes from several customers of Microsoft’s hosted Online Services — which include Exchange Online, SharePoint Online, Communications Online, Live Meeting and the BPOS bundle of these services — of yet more access problems. Today’s outage, which several users have told me is still ongoing (at 6:30 p.m. ET) after at least three hours, seems to be related to Exchange Online, Microsoft’s hosted version of Exchange Server. “We are currently experiencing an Exchange online outage. It started around 3:30PM EST today and as of this moment is still on going,” said one IT user who contacted me and requested anonymity. This user said his organization switched to BPOS three months ago and have experienced three outages since signing up. (One of these was in late August, one in early September and one today.) the customer added. I’ve asked Microsoft what’s causing the recent spate of Online Services outages and was told late last week that an unspecified network issue was at fault. I asked again today for further details and have received no information so far. Microsoft officials notified North American customers on September 7 that the company was experiencing possible limited service for its Microsoft-hosted services earlier today, but said problems were resolved as of 1 p.m. (not sure which time zone). At 4:30, Microsoft sent customers another note telling them the same services had been restored. Update: Not too many more details, but this just in from a Microsoft spokesperson: Microsoft has scheduled maintenance for Exchange Online and SharePoint Online in North America this coming Saturday, September 11. The planned maintenance period begins at 4 a.m. GMT and may last through 10 p.m. GMT, company officials have told customers. One of my readers who has helped his customers with Microsoft’s Online Services claims that the late August outage may have been due to someone at Microsoft misconfiguring a switch. The reader said the early September outage was caused by “a misconfiguration of the switch fabric for Exchange,” which is the crux of a number of Microsoft’s other cloud pieces, he added. “The idea of a cloud architecture being unreliable is both (a) contradictory and ( common,” noted that reader, who asked not to be identified. As I noted late last week, I, too, know cloud services outages are common — and not just in Microsoft’s case. Because this blog is “All About Microsoft,” I am focusing on Microsoft’s infrastructure and how it affects its customers. Anyone else hit by the latest Microsoft cloud-service outage and hearing any possible explanations as to what’s going on? via > http://www.zdnet.com/blog/microsoft/microsoft-exchange-online-users-reporting-more-cloud-access-problems/7314?tag=content;feature-roto

nice, please post the registry file here (remove password) so that others can benefit

first option, but why do this when you can troubleshoot the failure, do you logs reveal anything else ?

odd, ok tell me at what point it fails because your log didn't reveal anything interesting, however i'll take another look to be sure are you sure you have the configmgr SP2 client installed on the client ?

as above, plus you can test it using psexec in System Context you can autologin using the method described here http://www.windows-noob.com/forums/index.php?/topic/1543-how-can-i-capture-windows-7/

In Part 1. of this series we Installed vNext. In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext. Now we will install the Reporting Point Role along with some additional roles and configure them. Perform the following on the vNext server as SMSadmin Step 1. Install the Fallback Status Point, Reporting Point and Software Catalog Roles Click on Administration in the Wunderbar, Site Operations, Site Roles and select our vNext server (V01). The current roles are listed. In the Tasks Pane to the right, click on Create Roles When the New Site Role wizard appears click on Browse and select our vNext server, click next Select the following roles from the list: Fallback Status Point Reporting Point Software Catalog Web Service Point Software Catalog Web Site Point click next, and then Accept the defaults for the Fallback Status Point, if you want clients to report their State Messages faster you could set the Throttle Interval to 300 as long as it's only in your LAB but in Production leave the suggested value. for the Reporting Point Services role, click on Verify to verify your SQL instance, then In the credentials box, select Credentials stored securely in the report server from the drop down menu and use the ReportsUser we created in Part 1, select Use as Windows credentials when connecting to the data source and then Next Accept the defaults for Software Catalog Web Service Point Leave the defaults for DM click Next again review the summary, and click next... click Close when done.

should work, have you tried it ? just disable the un-needed steps

the task sequence was for X86 so you'll have to check that in the XML file as your's is for X64... edit your xml file in notepad or whatever and verify/replace the x86 bits with amd64 bits instead, once you have it working please post your sample X6 capture windows 7 Task Sequence here and i'll add it to the first post.

updated with details about the Event Welcome to yet another meeting in the Danish System Center User Group. We are very excited to offer you the opportunity to come and meet with fellow System Center administrators and influencers. During this event you can expect to see some live demos of the next version of Configuration Manager aka vNext and the latest release of Microsoft Deployment Toolkit 2010 Update 1. Agenda 09:00 – 09:45 Breakfast and Registration 09:45 – 10:00 Welcome and introduction to SCUG.DK 10:00 – 11:00 Session 1 : Microsoft Deployment Toolkit 2010 Update 1 (Johan Arwidmark) 11:00 – 11:15 Break 11:15 – 12:15 Session 2: ConfigMgr v.Next (Wally Mead) 12:15 – 13:00 Break and Lunch 13:00 – 14:00 Session 3: ConfigMgr v.Next (Wally Mead) 14:00 – 14:15 Break 14:15 – 15:15 Session 4: ConfigMgr v.Next (Wally Mead) 15:15 – 15:45 Q&A, prize drawings, softdrinks and beers. Practical information Date: 5th. of November 2010. Time: The event will start 09:45 and end 15:45. Doors will be open from 09:00. Please show up for registration 15 minutes before the event begin. Address: Teknologisk Institut, entrance 1 (Main building), Gregersensvej, 2630 Taastrup. Refreshments: Breakfast, Coffee, Tea, Water, Soft drinks and Sandwiches. Audience: IT Professionals and Administrators.

I can’t believe that’s it’s almost a year since Windows 7 was released! Many customers are already beginning deployment projects or are about to. Of course before the product released last year we at Microsoft had a goal to be running on the OS before launch and our internal Microsoft IT folks were challenged with this huge task. Well they have recently released details on how they went about it using System Centre Configuration Manager 2007 and the Operating System Deployment feature which is part of SCCM. Check out all the details below as it makes for a good reference to consider for your own deployment projects. Deploying Windows 7 Using System Center Configuration Manager 2007 and OSD Microsoft is the first enterprise organization to use Windows 7 on a large scale, and that includes deployments using the System Center Configuration Manager 2007 Operating System Deployment (OSD) feature. OSD provides administrators with a tool to create images that can be deployed to managed and unmanaged computers. The OSD user interface, and features such as driver management and the User State Migration Tool (USMT), have been significantly enhanced. Join subject matter experts from Microsoft IT as they share best practices. These include complex scenarios such as using OSD with Network Access Protection (NAP). Technical Case Study | IT Pro Webcast via > http://blogs.technet.com/b/jeffa36/archive/2010/09/06/deploying-windows-7-with-sccm-2007-how-microsoft-it-deployed.aspx

Step 3. Configuring Discovery Methods in vNext Now that we've configured our Boundary, we need to configure Discovery methods. In the Administration node, expand Site Operations, and sites, select our Windows Noob site and at the bottom of the screen you'll see Discovery Methods. Click on Discovery Methods to see what discovery methods are configured, by default, only Heartbeat Discovery is configured (enabled). Right click on Active Directory System Discovery and choose Properties. Place a checkmark in Enable Active Directory System Discovery and then click on the yellow star When the New Active Directory Container window appears, click on Browse and for the purpose of this lab it's ok to leave the root of the domain as selected, click ok. review the selections made and click ok, if required you can change your polling schedule by clicking on that tab, but for now let's leave it as it is then right click on Active Directory System Discovery and choose Run Now Answer Yes to the discovery question After a few minutes have passed you can verify that the discovery has run by looking at the All Systems collection (in the WunderBar, click on Assets and Compliance, then select the All Systems Collection, then right click and select Update Collection Membership)

post your smsts.log file here and i'll take a look

Step 2. Configure vNext to use the New AD Site as a boundary. Perform the following on the vNext server as SMSadmin By now you'll know that the Admin Console has changed in vNext (it looks similar to SCOM 2007) and these changes are not just graphical. The following is taken from the Microsoft vNext Server InfraStructure Document supplied with the download of the beta. Changes to the Administrator Console Ok great, let's start configuring it. Open the console and in the left lower pane select Administration. Expand Site Hierarchy and then click on Boundaries. As we havn't added any yet, it will appear blank. So let's add one by right-clicking and choose Create Boundary In the description pane, enter AD Site Boundary, for Type, click on the drop down menu and choose Active Directory Site, then click on Browse and select our WindowsNoobSite that we created above. For Network Connection select Fast (Lan) and click Apply. Press F5 to refresh the console and you should see your new Boundary listed.

yep that shows you how to point the Deployment Management Task to a specific collection, you should probably create two Deployment Management Tasks, point one to your Deployment Collection and the other to the Unknown Computers Collection

don't add lines to your sysprep file it wont work that way, read this post to see the correct way to add the Mass Storage Drivers http://www.windows-noob.com/forums/index.php?/topic/2428-how-to-create-a-driver-package/

yes it's possible, just advertise a new deployment management task (or tasks) containing the updates (both windows 7 and office updates) to the collection(s) that the computers are in

here's a list direct from Microsoft http://technet.microsoft.com/en-us/library/bb632442.aspx

good work Terry, and thanks for sharing, Offline mode in WinPE rocks doesn't it

In Part 1. of this series we Installed vNext, now we will configure it. If you have used Configuration Manager 2007 before you'll know that we need to use Boundaries. You need boundaries or the clients will not find the nearest Distribution Point when they make a Client Location Request. The boundaries help them find the content at the nearest Distribution Point. Before we can configure the boundary in vNext we will create a new Active Directory Site based on our Ip subnet. Step 1. Add new Active Directory Site We will begin our Configuration by adding an Active Directory Site. Perform the following on the Active Directory Domain Controller as a Domain Administrator Open Active Directory Sites and Services, Click on Sites, New site. Give your new site a name like WindowsNoobSite and click the DEFAULTIPSITELINK and click ok. click Ok again Now right click on Subnets, and choose New Subnet Enter your Prefix in the box provided (I'm using 192.168.3.x so I entered 192.168.3.0/24) and select the WindowsNoobSite then click ok. Now we are going to Move our Active Directory server (AD1) from the Default-First-Site-Name to our new site, WindowsNoobSite, so expand it as below and right click on AD1 and choose Move. Select our WindowsNoobSite and click ok. The AD1 server is moved to our new site !