anyweb

welcome dave and thanks !

keep it up Jaoibh, good work ! one thing though, when taking the screenshots if you hold down ALT when clicking on a window you can get just teh window so we don't see all the other stuff in the background cheers anyweb

here's the reason why (straight from your LOG) It is not supported to deploy an x86 architecture OS from a amd64 boot image use Trace32 to examine your logs, it makes your SCCM life much easier troubleshooting info > http://www.windows-noob.com/forums/index.php?showtopic=546 cheers anyweb

wow good catch Dom and thanks ! I never noticed that after all this time.. I've updated the post with the distribution details, thanks again ! cheers anyweb

use sysprep to configure all those settings in your image before capturing it ie: place a file called sysprep.inf with your chosen settings into your Sysprep package for XP, this sysprep package will be used as part of the build and capture process

can you explain your sccm server environment (virtual or real) and how you set it up ? did you try rebooting it ?

what problem are you having tom ?

to properly test DNS do a nslookup, paste the results of that here cheers anyweb

from within the Capture section of the smsts_20090504_163719.log file looks like DNS issues or network issues, which might explain why it's failing to capture the WIM file to the network

A little earlier than expected, Microsoft has already released the Windows 7 release candidate to the general public. The Redmond company had already put the RC up for download on TechNet and MSDN, but from now on, everyone can download it. I've already updated all my Windows machines to the RC, so let's take a quick look at what I found. Note: The Windows XP Mode beta is also set to arrive today, but has not yet been made available. We'll update this item accordingly once it's released. Update: The Windows XP Mode beta is also available. Get it now! First of all, Microsoft asks you to not perform an upgrade from the Windows 7 beta to the new release candidate. It's technically possible, but it's a scenario the company has not tested, and as such, it may result in bugs and other unexpected behaviour. They advise you to do a clean installation of the release candidate, but if you want to help Microsoft make the upgrade experience smoother, you can also opt to install Vista first, and then choose the upgrade option. The gathered telemetry could help in improving the upgrade process in the final release. more > http://www.osnews.com/story/21434/Windows_...eased_to_Public

verify that client=Yes on the computer in question in the collection the software is advertised to, if client=no then no software will install cheers anyweb

restart the WDS servive and the DHCP service then try again

thanks for the update Dom

if you click on the network card icon what error does it say ?

you need to use the image created in the CAPTURE process as your new image for deploying Vista with and edit your Deploy Windows Vista task sequence to join the domain, please understand that the Build And Capture Windows Vista Task Sequence is only used to create a NEW image to be used for deploying vista using an entirely NEW task sequence and the new task sequence is the one which you must enter your domain joining details.... so you will have two task sequences, one for Build and Capture, and one for Deploying Windows Vista using the captured image.... cheers anyweb

hi, I hope you are aware that BDD has now been replaced by MDT 2008 (microsoft deployment toolkit) I havnt used RIS for quite some time now, but I'll try and answer the below from memory (i could be wrong, you'll find out soon enough) 1. Can I install BDD on my RIS server and just create a new deployment share along side MY RIS share yes you can 2. Can I still use my RIS images and RIS server while I start to create my new images in BDD like you can with WDS in mixed mode. yes 3. Can I convert my RIS images to use within BDD yes cheers 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 ?