anyweb

Today marks an important milestone in the Windows 8 project. The Windows 8 team is proud to share with you that a short while ago we started releasing Windows 8 to PC OEM and manufacturing partners. This means our next milestone will be the availability of exciting new models of PCs loaded with Windows 8 and online availability of Windows 8 on October 26, 2012. Back when we first demonstrated Windows 8 in May 2011, we described it as “reimagining Windows, from the chipset to the experience,” and that is what Windows 8 (and Windows RT) represents for both Microsoft and partners. The collective work: from the silicon, to the user experience, to new apps, has been an incredibly collaborative effort. Together we are bringing to customers a new PC experience that readies Windows PCs for a new world of scenarios and experiences, while also preserving an industry-wide 25-year investment in Windows software. We continue to be sincerely humbled by the breadth of participation in our pre-release testing. The previews of Windows 8 (Developer, Consumer, Release) have been the most widely and deeply used test releases of any product we have ever done. Over 16 million PCs actively participated in these programs, including approximately 7 million on the Release Preview that started 8 weeks ago. The depth and breadth of testing validate the readiness of Windows 8 for the market. The openness of the previews presents a unique perspective on product development, and we’re deeply committed to the transparency of the preview process. No product used by so many people in so many different ways is developed “out in the open” like Windows 8 has been. This blog, the forums, and the preview releases form an important part of the development process. Major changes have been made at each milestone and as we promised, the final release (build 9200, for those tracking) contains many promised refinements. We are humbled by the responsibility of meeting the needs of such a diverse set of customers and enthused by the deep level of participation in the pre-release process. While we have reached our RTM milestone, no software project is ever really “done.” We will continue to monitor and act on your real world experiences with Windows 8—we’ve used the preview process to test out our servicing and we have every intent of doing a great job on this next important phase of the product. Hardware partners will continue to provide new devices and improve support for existing devices. PC makers no doubt have quite a bit in store for all of us as they begin to show off PCs specifically designed for Windows 8. With improvements in fundamentals, enhanced storage and connectivity, newly architected subsystems, the “fast and fluid” user experience, and the WinRT platform (to name a few), Windows 8 has literally thousands of new features. We did a record number of blogs posts (and videos) and did not even come close to covering the full breadth of Windows 8. There’s much left to learn about and discover in the product. Some of the most exciting innovations with Windows 8 are yet to come—the innovations from developers building apps on the new WinRT platform. Today, the Store is open for business and we’ll rapidly expand to over 200 markets around the world. The opportunity for developers around the world to deliver innovative (and profitable) apps is unique with Windows 8. We’re excited to see the work developers will be bringing to Windows 8. We’ll also have a chance to talk more about the Windows 8 platform at the next BUILD conference recently announced. We know there are lots of questions about how to get Windows 8 and when, and of course more questions to come about exploring and using the full set of thousands of Windows 8 features. Our Windows Team Blog today has posted a lot of new information and gathered up some important details that we hope will answer your questions. Please check our blog and stay in touch on the in-market developments of Windows 8 there. On behalf of the Windows 8 engineering team, we want to thank you very much for your contributions throughout development and your contributions yet to come to Windows 8. THANK YOU! Next stop, October 26, 2012 and General Availability! --The Windows 8 team via MSDN > http://blogs.msdn.co...ust-1-2012.aspx

Howdy! Today is the day we’ve all been waiting for. I’m proud to announce that Windows Server 2012 has been released to manufacturing. That means the final code is complete and we are delivering it to our hardware and software vendor partners this week. We will also make the software available to our volume licensing customers in the next couple of weeks. Get out your calendars and free up some time on September 4. That’s when Windows Server 2012 will be generally available for evaluation and purchase by all customers around the world. On that day we will also host an online launch event where our executives, engineers, customers and partners will share more about how Windows Server 2012 can help organizations of all sizes realize the benefits of what we call the Cloud OS. You will be able to learn more about the features and capabilities and connect with experts and peers. You’ll also be able to collect points along the way for the chance to win some amazing prizes. You don’t want to miss it. Visit this site to save the date for the launch event. On behalf of the Windows Server engineering team, I can tell you it has been a thrill and honor for us to deliver this product. Most importantly, we thank the many thousands of you who have provided your input and guidance throughout the process of designing and building it. So far the hands-on feedback on the product from you, industry analysts and press has been phenomenally positive. I attribute that to the fact that, from the outset, we committed ourselves to building Windows Server 2012 around the needs and goals of our customers and partners. It feels great to ship software that so squarely addresses customer objectives, both in the here and now and in the future. Cheers! Jeffrey via Technet > http://blogs.technet...ufacturing.aspx

in the Administration workspace, Servers and Site System Roles, select your server hosting the SUP role, click on software update point, done.

you can follow the same guide and you'll see it links to a 'standalone' server installation, that's what you require (a standalone primary, no CAS), just make sure your versions of SQL match whats listed in the Part 1. Installation guide. As regards Q2, I'm not sure i've not used it, but i would do so prior to setting this up.

did you try forcing the machine policy ? is the client functional ?

you have the same error as before, have you looked into using /lac ?

the smsts.log file will reveal why it failed to capture your image, look in c:\windows\ccm\logs\ you can post it here if you wish

first things first, when you setup the SUP on your primary how did you install it ?

are you using Configuration Manager 2012 or 2007 ? please raise NEW topics when you have problems instead of posting little or not info at the end of an unrelated thread.

first things first, create your Windows 7 master image using the step by step guide here. Secondly post your log files so that we can see what is wrong and explain what you expected to happen and what actually happened.

I have to ask, did you open loadstate.log in notepad or Trace32 ? if you did you would have seen this error (search for the word failed)

look for the loadstate.log file in this location, it's listed clearly in your smsts-.... log file (did you look at the contents of that log file?) C:\Windows\SysWOW64\CCM\Logs\SMSTSLog\loadstate.log post that loadstate.log file here and we'll help you.

why did the installation fail ? can you provide the logs from the client please

just make sure it's in a collection targetted with custom client settings that enable installation of the SCEP client.

are you sure you followed my guides step by step, if so you wouldnt have any firewall PORT issues for sql, i can remote into your box tomorrow and take a look if you want.

please raise a separate post for that question, you are mixing up two entirely different problems, it's confusing to readers. Moving this topic to Configuration Manager 2007 forums.

and if you still want more content there are the videos from MMS 2012 - http://www.niallbrady.com/2012/04/23/mms-2012-videos-wouldnt-it-be-nice-to-be-able-to-download-them-all-automagically/

are those file permissions set on the software folder in your screenshot, or somewhere else ? don't do a site reset, fix your permissions, are you logged on with the same account that you installed Configuration Manager with ?

attach your smsts.log file from the attempt and we'll check it out, my guess is you didn't add any network drivers for your specific hardware to your boot.wim file and got no ip address which then meant the task sequence failed and it rebooted eventually to a blank harddisc or you are missing the network driver in the apply driver package step, but to be sure we need the smsts.log file, pressing F8 after enabling command prompt support in your boot images will help this.

i dont see any scanstate or loadstate log files atttached above... however from the small bit of smsts.log file you posted theres the following error which means that a file (or files) are still on the hard disc (probably somewhere in the old users profile) that could not be deleted prior to applying the new os, therefore the installation failed, you'll need to examine the logs to find out what files are causing the issue.

as per my post above

great stuff :-)

are you saying that you had permission issues on a destination share causing the error above ? if so what share (was it the capture directory ?) and what permissions did you change ? i still think based on the screenshot above that it was ip address/dns related so would like more info about your troubleshooting

as Peter says, the only way to find out what is working or not with your migration is to examine the scanstate.log and loadstate.log files generated by USMT

maybe you only put the drivers in one of the boot images and not the other, i'd recommend you only add the drivers you NEED to the boot images you are using, to find out which driver you need see this post please http://www.niallbrady.com/2011/08/31/missing-nic-driver-in-winpe-boot-image-no-problem/