anyweb

if you are going to deploy Vista then you don't need mixed mode functionality

after clicking on Member of, choose Object Types and make sure that Groups or Built-in security principals is selected, in your screenshot you've only selected Groups....

the above tells you that you should have setup RIS first, otherwise you'll end up in native mode with no possibility of doing ris or legacy installs so maybe its time to uninstall WDS and start again by reading this WDS topic

what type of user are you logged in as when attempting to do this ?

what are you doing exactly in this screenshot, i need to know where in the guide you are exactly...

try pointing it to d:\sources

Domain Admins is present (it has to be) so you must be doing something wrong, try leaving it blank instead and click on check names and you need to do this as a user wit Domain Administrative permissions

hi there its there too, you need to look harder, I'm using sql 2005 sp3 on my home SCCM lab (windows 2008 sp1 x64) don't install the 32 bit version of SQL, get the x64 bit version instead i've just checked technet and its there and

take a look at this post then please

bring up the properties of the Security group called SMS Admins, and click on the Member Of tab, Click Add and type Domain Admins thats it

file not found means it cannot find a file to read or boot from verify that you have a boot image in windows deployment services if you do, is the WDS server running on the same pc as the DHCP server or a different one ?

use Active Directory Users and Computers right click on Users, choose New etc

you could probably write a small script to copy the contents manually to a folder and then once done install the application have you tried that ?

hi and welcome you can create it by doing this

ok in a production environment where you should have SCCM and AD on different servers do it like this make a global security group in Active directory Users and Computers and call it SMS Admins now, make two (or more) new Domain Users called SMSadmin and SMSread once done, log on to the SCCM server and startup Server Manager, Configuration, Local Users and Groups and select Groups double click on Administrators and add the SMS Admins Global Security Group as a member. (this gives the SMSadmin user local admin rights on the sccm server) in your lab do as follows: *if you have both SCCM and AD on the same server* create the two Domain Users in Active Directory Users and Computers called SMSadmin and SMSread create the SMS Admins Global Security Group and add the SMS Admins group as a member of Domain Admins.

read this part http://www.windows-noob.com/forums/index.p...post&p=1442 that's where those accounts were configured

you've pretty much answered your own question, and in this case you should probably install the os+drivers first, then after the os is installed send out the Intel Proset software by utilising the cache feaure

its not required for SCCM cheers

you can still reimage quickly using sccm with Media (usb key or cd/dvd) you'll learn more about that here

well spotted, i've amended that part, please refresh it to see the change. cheers anyweb

have you read this guide yet ?

With virtualised workloads, data backup and recovery becomes even more critical. Whilst large companies can use products such as System Center Data Protection Manager to back up multiple servers, that may not always be appropriate for and, in this video, Mark Wilson takes a look at backing up a Hyper-V deployment using the Windows Server Backup utility provided with Windows Server 2008. Presented by Mark Wilson http://www.markwilson.co.uk/blog/ Length: 11 minutes 29 seconds Watch the video (requires Silverlight 2)

The Windows Server Hyper-V Management Pack for System Center Operations Manager 2007 supports monitoring of Windows Server Hyper-V systems. This includes monitoring coverage of Hyper-V host servers, including critical services and disks, and Hyper-V virtual machines, including virtual components and virtual hardware. Overview This management pack supports monitoring of Windows Server Hyper-V systems. This includes monitoring coverage of Hyper-V host servers, including critical services and disks, and Hyper-V virtual machines, including virtual components and virtual hardware. Feature Summary This management pack provides the following functionality: Management of critical Hyper-V services that affect virtual machines and host server functionality Management of host server logical disks that affect virtual machine health Full representation of virtualization in a single Hyper-V host server, including virtual networks, virtual machines, and guest computers Monitoring of virtual machine hardware components that affect availability Release History 6/19/2009 - Original release of the English version, version 6.0.6633.0 Top of page System Requirements Supported Operating Systems: Windows Server 2008 Other Software - System Center Operations Manager 2007 (SP1 or R2) Important Note: This MP takes following dependencies: System.Virtualization.Library MP v.6.1.7221.0, included in this MP download package System.Hardware.Library MP v.6.1.7221.0, included in this MP download package Windows Server Operating System 2008 management pack, v.6.0.6321.5. Top of page download > http://www.microsoft.com/downloads/details...;displaylang=en

take a look at this http://social.technet.microsoft.com/Forums...8b-b0b1611ae519

Microsoft released a new version of ACT, version 5.5. This version changed the database schema which prevents configuring the ACT database from the ACT Connector administrator console. If you upgrade an existing ACT installation to 5.5 which has already been configured in the ACT connector, no additional steps are required. Using this documented workaround ACT 5.5 is supported by Microsoft with the System Center Configuration Manager 2007 ACT Connector. Symptoms You will see the following error when attempting to configure your ACT database: Cannot connect to SERVERNAME. [-2146232060] Invalid object name ‘ACT_Databases’. An update will not be released to fix this issue at this time, but the following workaround is available: more > http://blogs.technet.com/configurationmgr/...-connector.aspx