anyweb

try it in <settings pass="specialize"> cheers anyweb

as a test point it to the X64 boot file could be that the bios is reporting 64bit capable...

the built-in Administrator account is disabled by default but by adding the following command to your AutoUnattend.xml answer file using Windows System Image Manager (Windows SIM) or any text editor we should be able to enable it. <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <AutoLogon> <Password> <Value>windows-noob</Value> <PlainText> true</PlainText> </Password> <Username> Administrator</Username> <Enabled> true</Enabled> <LogonCount> 5</LogonCount> </AutoLogon> <UserAccounts> <AdministratorPassword> <Value>windows-noob</Value> <PlainText> true</PlainText> </AdministratorPassword> </UserAccounts> </component>

is option 66 pointing to the ip of the WDS server ? have you tried setting option 67 to boot\x86\wdsnbp.com instead of your current value =?

its easy to do but you need to first decide if you want to deploy software to USERS or COMPUTERS the recommended way is to deploy software to COMPUTERS otherwise things can get messy (think one user using multiple computers...) you will also have to enable Active Directory Discovery using the following two Discovery Methods in SCCM Active Directory System Group Discovery Active Directory Security Group Discovery once done... in Active directory you need to setup a structure for this, You will need to create some Active Directory Security Groups, and then create an OU in Active Directory and call it Applications Group now, you need to create your corresponding Collections in SCCM, so lets create three new collections Office 2003 Computers in the Office 2003 Security Group Users in the Office 2003 Security Group The two sub collections will have separate queries to determine their contents: The query for Computers in the Office 2003 Security Group shall be select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM .SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemGroupName = "SCCM2007\\Office 2003 Users" so from the above, SCCM2007=your domain and Office 2003 Users is the Active Directory Sercurity Group you added Computer Objects to. Note: To define collection queries please read this post The query for Users in the Office 2003 Security Group shall be select SMS_R_USER.ResourceID,SMS_R_USER.ResourceType,SMS_R_USER.Name,SMS_R_USER.UniqueU serName,SMS_R_USER.WindowsNTDomain from SMS_R_User where UserGroupName = "sccm2007\\Office 2003 Users" Now you can target these sub collections with software to install, so in this case you would target the collections above with an advertisement to install Microsoft Office 2003. once done, you can start adding computer or user objects to the respective Active Directory Group in active directory, and based on your Discovery Methods schedule they will appear within the correct Collection and based on the collection they are in they will receive the correct advertisement, as this is a common question, I have renamed the topic, and pinned it. Related steps: How can I deploy an application using SCCM 2007 SP1 ? How can I target an application to specific hardware using SCCM 2007 SP1 ? how can I deploy Windows Vista SP1 using SCCM 2007 SP1 ? how can I deploy Windows XP SP3 using SCCM 2007 SP1 ? how can I deploy Windows Server 2008 using SCCM 2007 SP1 ? cheers anyweb

sccm can handle all this and utilise Wake up on lan also, so are you utilising SCCM or SMS =?

zero touch means no one has to touch the machine getting imaged. light touch means someone does have to touch it, so what are you referring to exaclty ?

is there a switch of any sort in between the server and client ? if so try removing it to rule out the switch... secondly is the client also virtual or is it real, if it's real is it 32bit or 64bit ?

normally if you are installing a server OS you would install it on hardware that is sold to be a server, have you tried installing the Windows VISTA chipset and network drivers for this HP ? the vista drivers should work just fine....

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