anyweb

Step 5. Create a new VM and PXE boot it Create a new virtual machine and PXE boot it, as the virtual machine is New and New to SCCM 2012, it's considered Unknown and therefore we should see whatever deployments we targetted to the All Unknown Computers collection, you should see the following press F12 to PXE boot, and the boot image starts loading we'll get prompted for our PXE password, enter it and click next and our task sequence menu appears, select Deploy Windows 7 Enterprise X64 SP1 and click next and our Deployment begins ! Ths OS installs... our new application Gets installed Create another Virtual Machine and PXE boot it, but this time choose Deploy Windows 7 Enterprise X64 and click next.

Step 4. Deploy the Task Sequence to the All Unknown Computers collection In Software Library, select Task Sequences, select our Deploy Windows 7 Enterprise X64 SP1 Task sequence and right click, choose Deploy (of course you can also select the task sequence and click Deploy from the Ribbon above) for collection, click browse and select All Unknown Computers make sure to select the Vnext Distribution point then click next for Deployment Settings Purpose, make it available (optional) and place a checkmark in Make available to boot media and PXE click next through schedule (don't set anything there), and User experience, for Distribution keep the defaults, click close at the Deployment completion repeat the above for the Deploy Windows 7 X64 Enterprise Task Sequence.

Step 3. Create the Deploy Task Sequence Now that we have added our captured operating system images to Configmgr, and distributed them to our dp's we want to create a Deploy Task sequence to Deploy the image. In Task Sequences, right click and choose Create Task Sequence. This time select the first option, Install an existing image package fill in some details about the image and select the X86 boot image for Image package, click on browse and select our Windows 7 Enterprise X64 Service Pack 1 image for Image click on the drop down and change it from All Images to 1 - 1 and enter a password for the Local Administrator account (good for troubleshooting failed installations), notice there is an already checked Partition and Format the target computer before installing the operating system step enter your Domain Joining credentials and specify an OU if you wish, I didn't. Note: please don't select the Computer Container as that is a container (not an OU). for the configmgr client step, select the configuration manager client package and click next we are not migrating any data at this point so remove the State capture options for Install updates select All Software Updates and for Add applications, we'll add a new app (please add it first using this guide) called Winzip 15 (you can download the MSI file from here, and I want to you specify Install for System, whether or not a user is logged on in the Install for User or System step. click next through the summary... and click close at the confirmation screen Repeat the above process for our Windows 7 RTM image now we have two new Deploy Windows 7 Task Sequences listed

Step 2. Distribute Content We now need to distribute our imported images to our distribution points. Select Our Windows 7 Enterprise Service pack 1 image and in the ribbon above click on Home and then Distribute Content when the Distribute Content wizard appears click next specify our vnext Distribution Point click next, next and review the Wizard Completion click Close and then repeat the above for our other Windows 7 image.

In Part 1. of this series we Installed SCCM 2012, in Part 2 we started to configure it. In Part 3, we configured Beta 2 some more by enabling Active Directory discovery methods, adding some site system roles, configuring the computer client agent and client push settings and finally doing a manual client installation to verify it all worked, in Part 4 we looked at installing an application using Application Management and the Software Catalog and the Software Center features of SCCM 2012, and in Part 5, we added the FSP, SLP, SMP, SUP. In Part 6 we got our SCCM 2012 server ready for Deploying Windows 7 Enterprise SP1 so that we could start deploying some Windows 7 clients to enhance our LAB, then in Part 7 we created a Build and Capture Task Sequence and deployed it to our Build and Capture collection. In Part 8 we created our Network Access Account and captured our Windows 7 SP1 image (and Windows 7 RTM). Now we will deploy that captured image to a new Virtual Machine. Perform the following on your SCCM 2012 beta 2 server as SMSadmin. Step 1. Import the captured images If you havn't already done so repeat the Build and Capture Process so that we have both Windows 7 X64 SP1 and Windows 7 X64 images captured. In the Software Library, Operating Systems section of the Configmgr console, click on Operating System Images, you'll note that it is empty because we havn't imported any images yet. In the ribbon above, click on Home and then Add Operating System Image for data source enter the capture UNC eg: \\vnext\sources\captures and click on browse, select the W7x64SP1.wim file enter the operating system image data click next and next again review the add operating system image Wizard completion message click Close, then repeat the above process for our Windows 7 X64 image (RTM). Both images should now appear

via Ned Pyle, Microsoft. Ned here. We rarely release USMT KB articles, so this post is to spread the word on a scenario that is easy to run into: do not allow calling of the Microsoft-Windows-COM-ComPlus-Setup-DL or Windows-COM-ComPlus-Setup manifests if migrating from x86 to x64. Bad things will happen otherwise, and while fixing it is easy on one machine, fixing it on 10,000 is not. For steps on preventing the issue and remediation, see: USMT 4.0 migration from x86 to x64 results in corrupted COM+ components - http://support.microsoft.com/kb/2481190 This effectively means that CONFIG.XML is now a required option for SCANSTATE, if you are moving from 32-bit to 64-bit OS. If going from 32-bit to 32-bit, or 64-bit to 64-bit, you have nothing to worry about. Until next time. Ned “Com Minus” Pyle via > http://blogs.technet.com/b/askds/archive/2011/08/03/usmt-x86-to-x64-migration-do-not-migrate-com-setup-manifest.aspx

in our production environment at work we have quite complex build and capture task sequences that have evolved over time. start with one change at a time and thoroughly test it until everything is stable, do this in your lab, once it is stable make the changes in production, and continue with your testing (back in the lab) please take a look at this post for some guidance around build and capture of windows 7 any issues you are having we can help with, but as before, keep the changes simple, one at a time and test thoroughly, all too often people add 4 different new steps to a task sequence and one or more of those steps breaks the smooth working process, it's all about testing testing testing cheers niall

just leave it there, it will get used unless of course you dont want a drive used in which case you must place a no_sms_on_drive.sms file on it

task sequences are executed in Local System context, access to packages is done using the network access account, can you try pxe booting again and see if you can press F8 before it reboots, post the smsts.log here please

correct two steps step 1. use toolkit package step 2. xcopy gpo's the toolkit package has several files/folders one folder is called scripts, copy your customscripts folder (and subsequent folders/files) to the scripts folder so the package is now \\server\sources\MDT Toolkit package\scripts\customscripts\group policy then update that package to it's dp's then test the task sequence

ok so you've integrated MDT 2012beta into SCCM 2012 beta 2? does it work without mdt integrated ?

you can do it like so along as you have integrated MDT 2010 update 1 with SCCM 2007. Create a sub folder off of your scripts folder in MDT Toolkit files package, then copy the group policy files from a computer that has had the policies applied, in order to use this you must then have a Use Toolkit Package the actual copy command (Run Command Line) is like so xcopy.exe "%deployroot%\scripts\Customscripts\GroupPolicy" "c:\" /E /C /I /Q /H /R /Y /S and must take place BEFORE the Setup Windows and configmgr Step cheers niall

you said that means DNS is not working correctly, have a read of this and see can you fix it

xcopy doesnt copy those files at all, the copying (backup aka Scanstate) is done entirely by the hardlinking process (re-indexing of files)

fqdn is more like this sccm2012.windows-noob.lab.local try again and try testing nslookup on the vnext/sccm2012 beta 2 computer paste the results here

doesn't matter if the post is old, whats your query ?

are you using virtual machines for this ? if so which type ? if it's hyperV set the NIC to Legacy Network adaptor, if it's vmware i believe you need the e1000 nic drivers added to your boot.wim files. to verify if you have dns issues check nslookup

can you also confirm that the state of that package is Installed (look at package status)

well done, nice find

have you seen this yet ? workaround for AbortPxe.com how to get rid of abortpxe.com

If you’re a Windows watcher, circle this date on your calendar: April 10, 2012. That’s the date when mainstream support for Windows Vista officially ends. And it cannot come soon enough for Microsoft, whose public image was badly damaged by the massively unliked Vista. If the rumors about a possible Windows 8 release in April 2012 are true, it will be an almost perfect changing of the guard. But vanquishing the ghost of Windows Vista is the easy challenge for Microsoft. Windows XP is still hanging around on stage, bumping into scenery and generally interfering with Microsoft’s careful messaging about all the cool and useful stuff it’s doing today. I thought about that date as I watched the keynote addresses from this week’s Microsoft Worldwide Partner Conference in Los Angeles. Some of the people I follow on Twitter were disappointed that Microsoft didn’t divulge more details about Windows 8 or even publicly release a platform preview. That shouldn’t have been surprising. WPC is, after all, a show for partners who are out there selling Microsoft products every day. Yes, they want to know what’s coming up, but they’re far more interested in the present. And for their (mostly business) customers, there are only two Windows choices these days: the 10-year-old XP and the still-new Windows 7. It’s almost like Vista never happened. Consider the words of Chief Operating Officer Kevin Turner, who told a packed audience, “Windows XP, Office 2003, and Internet Explorer 6 deserve a standing ovation. We love those products.” As Turner noted, those products made Microsoft and its partners a lot of money. After a pause for dramatic effect, he added, “But they’re dead.” Oh dear. I guess that means 300 million PCs still powered by Windows XP are zombies, and we all know how hard those are to kill. Which might explain why Corporate Vice President Tami Reller was practically pleading with partners to help them migrate customers away from XP “to a modern OS.” That’s happening, slowly. XP has lost roughly 10 percent of its share over the past year and should be below the 50% mark by the time Vista support ends next year. But the paradox for Microsoft is that businesses—notoriously conservative and slow to adopt new technology—are most likely to embrace Windows 7 when it’s old news. When it comes to Windows, businesses like being on the last version, not the current one. When Windows 8 is released, it will instantly make Windows 7 the safe choice for businesses. Not rational, I know, but that’s how the psychology works. More than anything else, Microsoft is looking forward to shipping Windows 8 so it can finally get back on a regular cadence with its operating system releases: the current one for consumers and early-adopter businesses, the previous one for conservative businesses and cheapskate consumers. With Vista finally out of the mix, that proposition will finally make sense again. via > http://www.zdnet.com/blog/bott/can-windows-8-finally-vanquish-the-ghosts-of-xp-and-vista/3570?tag=content;feature-roto

At long, long last, Windows XP is no longer the number one, end-user operating system. It only took, Microsoft, what? Not quite two years to get desktop users off XP to Windows 7? Well, you could look at it that way, but you’d be wrong. The truth is that users haven’t been moving from XP to 7 of their own free will. They’ve been moving only because their old XP PCs are finally giving up the ghost. Then, and only then, are they getting Windows 7. Or, are they? If you look closer at Net Applications’ latest end-user Web statistics you’ll see that desktop users are Not moving to Windows 7 in droves. While XP has dropped to 49.69%, Windows 7 use is only up to 27.92%. So, where is everyone else? Have they finally moved on to desktop Linux!? Ha. I wish! No, while almost 10% of users are still running Vista-the poor sods-many other people are moving on to Mac OS X. You didn’t need a survey to tell you that though. All you need to do is look around any coffee shop and you can see that for yourself. In one of my own local favorite hangouts-the Dripolator in Asheville, NC–I just did a quick count and there’s eight Mac laptops is use; three Windows PCs, two Windows 7 and one XP; and yours truly with my Samsung Chromebook. What’s far more telling though was the one woman who was using her iPad 2 with a Bluetooth keyboard. Two others were working with older iPads and one was using a Galaxy Tab using just their fingers. Everyone in the place, of course, had a smartphone. The phones were evenly divided between iPhone and Android models with one guy getting ticked off at his Blackberry. It’s the tablet and smartphone users who are really pointing the way to the end-user operating system future. According to a recent IDG global smartphone survey, 69% of users are now using their phones for business. Specifically, “70% browse the Internet regularly and use mobile applications. These devices are no longer limited to calls, email, and text messages as people go online from home, on the move, and in the office. When surfing the web on smartphones, respondents indicated that general and IT news are most popular, followed by social networking access.” In addition, 20% of this group, who were self-selected, tech. savvy users, already own tablets. Half of them are using their tablets for work. They’re using them for “Web browsing (93%), email (84%), mobile apps (72%), watching videos (69%), and reading publications (66%).” The world is leaving fat-client desktops, like Windows, and yes, Mac OS X and desktop Linux behind. The desktop operating system isn’t going to die out, but it’s already becoming less important. In the next few years, more and more of us are going to be using tablets and smartphones for both home use and business. In the long run, the question isn’t going to be “Which desktop operating system is going to be the winner?” No, it’s going to be, “Which mobile operating system will be the winner.” In 2021, we won’t be comparing Windows, Mac OS X and Linux as much as we will be Apple iOS; Google Android; HP webOS; other Linux-based mobile operating system such as MeeGo; and, possibly, Windows 8. “XP? WIndows 7? Those old things?” We’ll say. “I don’t know how the old folks ever coped with them!” via > http://www.zdnet.com/blog/btl/is-xp-finally-dying-or-is-it-the-pcs-its-been-running-on/53797?tag=content;feature-roto

the log reveals why see here <![LOG[Content location request for S020015D:1 failed. (Code 0x80040102)]LOG]!><time="16:04:43.349+-60" date="08-02-2011" component="TSPxe" context="" type="3" thread="1088" file="tspolicy.cpp:1635"> <![LOG[pTSPolicyManager->GetContentLocations( m_sPackageID, m_lSourceVersion, m_dwContentSourceFlags, slistContentLocations, slistHttpContentLocations, slistMulticastContentLocations, m_dwContentPackageFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2330)]LOG]!><time="16:04:43.349+-60" date="08-02-2011" component="TSPxe" context="" type="0" thread="1088" file="tspolicy.cpp:2330"> <![LOG[(*iTSReference)->Resolve( pTSPolicyManager, dwResolveFlags ), HRESULT=80040102 (e:\nts_sms_fre\sms\framework\tscore\tspolicy.cpp,2862)]LOG]!><time="16:04:43.349+-60" date="08-02-2011" component="TSPxe" context="" type="0" thread="1088" file="tspolicy.cpp:2862"> <![LOG[m_pSelectedTaskSequence->Resolve( m_pPolicyManager, TS::Policy::TaskSequence::ResolvePolicy | TS::Policy::TaskSequence::ResolveSource, fpCallbackProc, pv, hCancelEvent), HRESULT=80040102 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1208)]LOG]!><time="16:04:43.359+-60" date="08-02-2011" component="TSPxe" context="" type="0" thread="1088" file="tsmediawizardcontrol.cpp:1208"> <![LOG[Failed to resolve selected task sequence dependencies. Code(0x80040102)] so a couple of questions 1. did you configure the Network access account ? 2. what is this package S020015D:1 and is it distributed to your distribution points (package status should say Installed)

although for Beta 1 this should cover it

if you go into IIS do you see the websites created ? in Configmgr, check your component status, any problems reported ?