anyweb

ah ok, see below (taken from my SCCM 2007 setup but you should get the idea) :-

are you saying you cannot see the attachments or what ?

I would certaintly separate the roles (isa/sccm) but.. I have never installed sccm on an ISA server so cannot comment, but common sense would tell me not to do it... so, try a fresh install using only SMSadmin to do the install/configuration and all, the SMSadmin account should be a domain user who has local administrative privaledges on the computer running SCCM

The official stance from Microsoft has always been that Windows 7 would be released three years after Vista, which would put its release date somewhere in January 2010. However, various rumours already indicated a release ahead of that schedule, and if the beta and RC are anything to go by, they could release it today and get away with it. Microsoft seems to have realised this, as it has now said it will release Windows 7 in time for the 2009 holiday season. It was Bill Veghte, senior vice president of the Windows Business at Microsoft, who was the one to break the news during Microsoft TechEd North America 2009. Both Windows 7 and Windows Server 2008 R2 will be released onto the world in time for the 2009 holiday season, which puts its release in December at the latest. Microsoft did not mention a specific date of release. Apart from moving the release date forward about a month, this also means that Windows Server 2008 R2 will arrive alongside Windows 7, while the company previously stated that Server 2008 R2 would arrive some time after Windows 7. more > http://arstechnica.com/microsoft/news/2009...oliday-2009.ars via > http://www.osnews.com/story/21470/Microsof...Before_Holidays

it's normal that you create the account yourself, once created, always log in with that account for the entire installation of SCCM from start to finish. do you have any other errors in sccm ?

before running sysprep, logon as Administrator then remove any un-needed accounts, then run sysprep

if the server will be a DC and SCCM all in one, then you can make the SCCM admin user (SMSAdmin) a member of the Domain Admins group, this would be ok for a LAB but it would be far better to separate the roles out onto different servers,

hi, does the user you are installing SCCM with have local administrator permissions on the server ?

content location failed, which means it can't find the content, make sure to distribute your package to a distribution point (update distribution point if unsure)

much better ! thanks Dave and keep up the good work

is your sccm server in mixed or native mode

if client= no then nothing will install, you must install the client properly.... if the ConfigMgr client appears to be installed on the client then you'll need to initiate a Data Discovery Cycle on the client, open the configMgr client, click on Actions, and click on Data Discovery.... cheers anyweb

Windows Deployment Services supports 3 main methods of deploying clients, manual, unattended and multicast. If you want to do unattended installs then you'll need to configure WDS to support this by doing as follows:- Unattended Deployment. This method automates the Windows Deployment Services client and the latter stages of Windows Setup. For instructions, see Using unattend files in the "Windows Deployment Services Role Step-by-Step Guide". For examples, see "Sample Unattended Files" in the unattended installation chapter at http://go.microsoft.com/fwlink/?LinkId=88439 . This two-stage approach is accomplished by using two different unattend files: a. Windows Deployment Services client unattend file: This file uses the Unattend.xml format and is stored on the Windows Deployment Services server in the \WDSClientUnattend folder. It is used to automate the Windows Deployment Services client user interface screens (such as entering credentials, choosing an install image, and configuring the disk). b. Image unattend file: This file uses the Unattend.xml or Sysprep.inf format, depending upon the version of the operating system in the image. It is stored in a subfolder (either $OEM$ structure or \Unattend) in the per-image folder. It is used to automate the remaining phases of setup (for example, offline servicing, Sysprep specialize, and mini-setup). get your sample unattend.xml file from here >>>>> http://technet.microsoft.com/en-us/library...80.aspx#client1

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