anyweb

did you select Definition Updates in Classsifications ? you need the ConfigMgr client installed on the computers before you can implement Endpoint Protection, the machines above say 'client =no' so do they have the client installed, or not

you can set the variables in many ways such as via collection variables computer variables HTA sets the variables steps in the task sequence a script glad to hear you got it working

you can simply disable both steps in your task sequence and do a test run, maybe you'll find out before me

if you followed part 5 then why are you running a separate SCEP 2012 install ? when you configured the Software Update Point did you check your wsyncmgr.log as explained in part 2 as described here

please raise one thread per topic, your orginal question was about installing ConfigMgr, now it is installed. Raise a new topic about your Endpoint Protection problem, it keeps things clearer and easier to follow/troubleshoot...

are you setting the SMSTSUdaUsers variable like i do in my example ? http://www.windows-noob.com/forums/index.php?/topic/4522-using-sccm-2012-rc-in-a-lab-part-10-using-prestart-and-extrafiles-to-get-more-out-of-uda/

yes, go to the download page again, here it is. and download this version, click on Show hotfixes for all platforms and languages (3) to see every download... SQL Server 2008 R2 All (Global) x64 SQLServer2008R2_SP1_CU6_2679367_10_50_2811_x64

you are using SQL Server 2008 R2 RTM, ie you are missing the service pack and needed Cumulative Updates. See here for a list of supported versions of SQL Server. Step 10 of using System Center 2012 Configuration Manager - Part 1. Installation - CAS here shows you what to download and install.

that can't be right, can you post the correct error message please ? and the number is the package id of the package in question, add it to your dp and you'll be ok

thanks for posting the resolution ! and good luck with the rest of it

no, SQL Server 2012 is not yet supported so don't use it until it is. The supported versions of SQL Server are listed in my Configuration Manager 2012 RTM guide here.

Configuration Manager client computers can be domain members, or workgroup members however if they are workgroup members you'll need to manage them differently, for example you can't install the client using client push to workgroup computers.

where are you seeing that error ? in the logs or in the setup installation console, can you post the ConfigMgrSetup.log file here please ? did you add the installation account (SMSadmin) as a sysadmin on your sql server as described below ?

is your wds server on the same lan/vlan as the client ?

it's different for every company, however there are scripts for deleting unused updates from packages such as this one here.

is Enable support for unknown computers selected on the PXE tab in your Distribution Point properties ?

what updates were they ?

how do you find the performance of that Dell., is it ok ?

are you saying that the computers are only WORKGROUP joined ?

you can install everything on the one server (Standalone Primary) for that number of clients, no problem, just think about lots of storage, fast discs (for SQL) and lots of RAM. When you say the clients aren't in AD can you elaborate please

it gets the name from the Computer Agent part of the Default Client Settings defined for the hierarchy,

you must install Cu6, your version is Cu4 (you made a typo with 10.51.2796.0 ?) 10.50.2796 SQL Server 2008 R2 SP1 CU4 are you attempting to install CU6 for SQL Server 2008 R2 or CU6 for the regular version of SQL Server 2008 below is the link to download the correct version of CU6, please try again...

it says this in the log " ConnectToProvider: Couldn't connect to the mgmt point (Siteserver.domain.COM): The RPC server is unavailable. " " ### DESCRIPTION: ERROR : Could not connect to WMI on the Management point after 3 attempts " have you set a user/pass in the hp wizard ? have you followed all the advice given in that pdf ?

yup see here using Multiple Task Sequences via PXE, PXE boot to a task sequence menu choice is sometimes a good thing

no you don't, however if you want to be SURE That you are executing the latest changes when pxe booting for example, you can add a version number to the name of the task sequence, that way, if you made changes to Deploy Windows 7 X64 v1.0, increment the version number by one and you should see Deploy Windows 7 X64 v1.1 when you pxe boot. This ensures that your clients have the latests policies for this deployment (sometimes theres a delay depending on hierarchy..) i use versioning a lot when i'm testing task sequences as i want to be sure i'm testing my changes and not the old task sequence