anyweb

Along with the release of the Windows 7 release candidate came new system requirements for Microsoft's next operating system. This updated set of requirements has been declared final, making them the official system requirements for Windows 7 final. Seeing Microsoft's rather... Dubious past dealings with minimum system requirements, let's take a look at Windows 7's. The updated requirements have changed little since the Windows 7 beta, and they are almost identical to those of Windows Vista - but when Windows 7 is released, we will be three years down the road. Without further ado: * 1 GHz processor (32- or 64-bit) * 1 GB of RAM (32-bit); 2 GB of RAM (64-bit) * 16 GB of available disk space (32-bit); 20 GB of available disk space (64-bit) * DirectX 9 graphics device with WDDM 1.0 or higher driver Sadly, I don't own a machine close to these minimum specifications to give you guys a hint as to what that would be like. My AMD Phenom X4 quad-core (4x2.2Ghz), with on-board Radeon HD3200 graphics and 4GB of Geil RAM obviously runs Windows 7 RC (32bit) blazingly fast. My much older, but still relatively powerful Pentium 4 2.8Ghz HT machine with a GeForce 6200 and 2GB of RAM also has no problems whatsoever with the Windows 7RC. The only machine where it could've gotten interesting is my Aspire One netbook, which has the well-known Atom 1.6Ghz processor with an on-board Intel-something video chip and 1.5GB of RAM. Sorry to disappoint some of you, but this netbook has no problems running Windows 7 RC either. Then again, none of these three machines had any troubles running Windows Vista anyway (I never ran Vista on the quad-core though) so to me, there's really no surprise there. I have already accepted that my apartment is a magical Windows-problem-free zone inhabited by fairies who keep my machines tidy and clean at night while taking sips out of my Martini bottles. more > http://blogs.zdnet.com/microsoft/?p=2643 via > http://www.osnews.com/story/21413/Microsof...ements_Official

there are many errors in your log including which sounds like DNS errors, can you test nslookup on the client and see that its finding your domain controller correctly cheers anyweb

you are nearly there !!! access violation simply means that you need to do a Computer Association, to see how that is done, scroll down to the section of this post which reads once you've imported the server to the deploy collection the Access Violation error will disappear cheers niall

hi Dom, if you take things one step at a time you'll get them right. so are you doing a build and capture using PXE boot or some other method, that you need to establish first, secondly, the if you follow the Build and Capture process for Deploy Vista on this forum and substitue the Windows Server 2008 DVD for the Vista one then you'll end up with what you want (a capture of your windows 2008 image...) now, if you want to deploy this captured image via a Custom Install DVD then you need to follow a different process which is detail here please tell me exactly what you are doing and WHY so that I can understand the problems you are seeing cheers anyweb

double check that the boot images are distributed to BOTH distribution points

have you tried redistributing the BOOT images as that is whats failing by the looks of things has it ever worked ?

if DNS is not working then AD will not work properly either, get someone who understands DNS to help you, because without working DNS, SCCM will not work.

please read this, did that help ?

what OS are you trying the mount on ? and what type of user ?

PXE - E53 No Boot Filename received can mean a whole bunch of things, look at the Troubleshooting section for clues... here's a post to give you some ideas http://social.technet.microsoft.com/Forums...2d-c91b5492ba7f

it can't find the file so is the wim called xp.wim and is it in the path you specified ?

what was the file missing from, client or server ?

is the dhcp server on the same box or another machine ? have you created both the X86 and X64 BOOT images and created Distribution points for them and updated the DP's ?

hi, first of all can you tell me why you ended up with 3 WIM images ? are they all part of one master image or 3 separate images ?

you could capture the image using Windows Deployment Services by reading this post once captured, you'll have to copy the install.wim file to your sccm server and create a new task sequence to deploy THAT image cheers anyweb

creating the image is another way of saying 'build and capture' in your case, youve already built the image... so you need to CAPTURE it, you can use WDS to capture it or create a new task sequence yourself which only CAPTURES the image cheers anyweb

sounds like a problem with your sql server, is it running on the same box, have you tried a server restart ?

the SHA (system health agent) and other NAP errors can be safely ignored, your failure is the firefox package so make sure that the firefox package is distributed to a DP, and that the firefox installation string is -ms as in the Firefox install guide.... OR remove firefox from your task sequence OR change the option for Continue on Error = True for the firefox installation cheers anyweb

follow the steps outlined here to get WDS working in Windows Server 2008 cheers anyweb

It's something lots of people here on OSNews have been waiting for. It's something we've talked about, something we've theorised about, and something we've declared as the future for Windows' backwards compatibility - and now it's here, and official. Over a month ago, Microsoft bloggers Rafael Rivera and Paul Thurrott have been briefed by Microsoft on a technology for Windows 7 called Windows XP Mode. Available as a free download for Windows 7 Professional, Enterprise, and Ultimate users, it's a fully integrated and licensed copy of Windows XP SP3 in a VirtualPC-based environment, with full "coherence" support. In other words, it's Microsoft's variant of Apple's Classic environment, and it's coming to Windows 7, for free. Near-instant update: The Windows 7 RC will indeed be available publicly on May 5. TechNet/MSDN will get it April 30. via osnews.com > http://www.osnews.com/story/21372/Windows_...sic_Environment

SMSTS.log file will tell you why it failed, so start reading it, its the only way to find out

programs that require answers are usually installed using switches or a config file, so you'll need to check sites like http://www.appdeploy.com to see what switches are required to silently install an application an example of that is firefox, to install it silently use firefox.exe -ms

if its booting the X64 boot image then the hardware must be x64 capable... thats not a problem, what you need to find out is exactly WHEN it's rebooting, if its happening just after loading windows PE then its most likely a network issue, and you'll need to post a copy of your SMSTS.LOG file here to figure that out this post will help you do that...

Tobie to the rescue ! well done

I agree ! keep things simple and clear, how long will that link be active for example ?