anyweb

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

your first and most glaring issue is this if wsus can't sync then you can't get any updates, so... do you have internet on the server that WSUS/SUP are installed on ?

Summary: There are more than 300 new features coming in Windows Server 2012. One worth noting is Hyper-V Replica. Here’s why. I’m taking a couple weeks off before the busiest part of Microsoft’s 2012 kicks into full gear. But never fear: The Microsoft watching will go on while I’m gone. I’ve asked a few illustrious members of the worldwide Microsoft community to share their insights via guest posts on a variety of topics — from Windows Phone, to Hyper-V. Today’s entry is all about Hyper-V Replica and is authored by Aidan Finn. Think back to disasters such as the hurricane in New Orleans and the floods in Eastern Australia, where there were business and technology impacts of those disasters. Large datacenters probably had made significant investments to protect against such emergencies. But what about the small/medium enterprise (SME) or the corporate branch office that couldn’t afford these expensive solutions? Did they have somewhere to go? Did those businesses survive? What was the long term cost to their owners and shareholders? The list of new features in Windows Server 2012 Hyper-V is staggering but the new one that stands out to me is Hyper-V Replica (HVR). HVR is built into Hyper-V at no extra cost and is designed specifically for those branch offices and small/mid-size enterprises that cannot afford an expensive SAN-based or host-based replication solution with their required expensive bandwidth. In fact, HVR has been designed to work on commercial broadband with no special hardware. HVR can be configured via PowerShell (there are a lot of native PowerShell cmdlets for Hyper-V in Windows Server 2012) or in the GUI. Users configure each virtual machine (VM) that they want to replicate. VMs are usually just a few files and that makes them easy to replicate. No, you will not be able to use HVR with Passthrough disks, and this is another reason to be excited about 64 TB VHDX files with near physical disk performance. Once enabled, HVR will do light weight logging of changes to the VM’s virtual hard disks. Every five minutes, Hyper-V Replica will attempt to replay that log file, containing the changes only, with compression enabled from the source host to the destination host to reduce bandwidth utilization. If the network connection is not available then HVR will reattempt to replicate for up to 30 minutes before it goes into a state that requires attention. This asynchronous method assumes that the Internet connection to the DR site is unreliable, as commercial broadband usually is. The combination of compression and change only replication is perfect for low cost connections that are the norm for branch offices and SMEs. Microsoft remembered that users might have possibly terabytes of data to replicate during the initial synchronization and gave them a few options. If they have a small amount of data, they can do the first synchronization over the wire, with an additional option to schedule this for out-of-business hours. They can export the data to removable storage, preferably with BitLocker encryption to protect the data during transit. And they can restore the VMs from backup in the DR site, and fix up the differences over the wire. Customers have some additional options when you configure HVR. They can choose to keep multiple snapshots of a VM on the replica host, allowing them to choose a past version of a VM when they start it up in the DR site. (This would be useful if a VM is corrupted and that was the reason for invoking the business continuity plan.) Users can also choose to configure an isolated network for testing the DR replicas. With this enabled, they can start up test copies of the replica VMs in the DR site, and verify that their plans will work during an emergency without impacting on systems on the production network. HVR does not have a heartbeat and does not start up DR VMs automatically. This makes sense because it is designed to replicate across unreliable links and users don’t want accidental invocation of the DR site because the ISP has one of those all-too-frequent brief outages. VMs are manually started, a process which can be sped up by using PowerShell or a System Center 2012 Orchestrator runbook. HVR allows replication of VMs from standalone host to standalone host, from Hyper-V cluster to Hyper-V cluster, and from standalone host to Hyper-V cluster and vice versa. This opens up a lot of options. SMEs are more likely to have standalone virtualization hosts. Many hosting companies choose this option, too, because it allows them to offer very low cost hosting plans. There are a few scenarios where HVR will be used. The SME will find HVR very appealing because it is free and can avail of low cost bandwidth. Those SMEs with two offices might choose to configure each one as the DR site for the other. Managed services partners or public cloud companies can choose to offer hosted DR services, availing of the optional HTTPS authentication and policy mechanisms in HVR, and building on additional add-ons such as remote access and remote backup. Corporations can also look at HVR as a way to provide economic DR replication either to a local DR site or to a central data center. HVR is asynchronous replication. Therefore it won’t be suitable for those organizations that need zero data loss. HVR is also not intended for replicating from massive environments such as a public cloud. In this case, users can expect to find high end storage with built-in replication and plentiful low latency bandwidth that can replicate at the hardware level, which is more suitable for large amounts of data and constant VM change. Hyper-V Replica is a built-in, free, asynchronous virtual machine replication mechanism that can offer something to SMEs, managed service partners, hosting companies, and corporations with branch offices. I think it is a killer feature because it is designed to work well in these environments and can solve problems for SMEs and complex environments, while offering service opportunities for Microsoft partners. Aidan Finn is a Microsoft Valuable Professional (MVP) with an expertise in Virtual Machine. He works for MicroWarehouse Ltd, an Irish Value Added Distributor, as a Technical Sales Lead, working closely with Microsoft and VARs in Ireland. He blogs on aidanfinn.com, tweets as @joe_elway, and has written or contributed to books such as Mastering Hyper-V Deployment (Sybex, 2010) and Microsoft Private Cloud Computing (Sybex, 2012). via > http://www.zdnet.com/blog/microsoft/one-of-windows-server-2012s-secret-weapons-hyper-v-replica/12707?tag=mantle_skin;content