anyweb

sounds like you need Distributed File System - Distributed File System (DFS) Namespaces and DFS Replication offer simplified, highly-available access to files, load sharing, and WAN-friendly replication. In the Windows Server® 2003 R2 operating system, Microsoft revised and renamed DFS Namespaces (formerly called DFS), replaced the Distributed File System snap-in with the DFS Management snap-in, and introduced the new DFS Replication feature. In the Windows Server® 2008 operating system, Microsoft added the Windows Server 2008 mode of domain-based namespaces and added a number of usability and performance improvements. What does Distributed File System (DFS) do? The Distributed File System (DFS) technologies offer wide area network (WAN)-friendly replication as well as simplified, highly-available access to geographically dispersed files. The two technologies in DFS are the following: DFS Namespaces. Enables you to group shared folders that are located on different servers into one or more logically structured namespaces. Each namespace appears to users as a single shared folder with a series of subfolders. This structure increases availability and automatically connects users to shared folders in the same Active Directory Domain Services site, when available, instead of routing them over WAN connections. DFS Replication. DFS Replication is an efficient, multiple-master replication engine that you can use to keep folders synchronized between servers across limited bandwidth network connections. It replaces the File Replication Service (FRS) as the replication engine for DFS Namespaces, as well as for replicating the AD DS SYSVOL folder in domains that use the Windows Server 2008 domain functional level. here's a step by step guide - http://technet.microsoft.com/en-us/library/cc732863%28WS.10%29.aspx

why are you deploying FEP 2012 clients when SCCM 2012 RC has the Endpoint Protection role and SCEP clients built in ? am I missing something here ?

are you using Pure SCCM 2012 RC or with MDT integrated ?

If I get time in the future to convert these docs to pdf format then i'll do so, but not right now sorry

what do you mean all or nothing ? if you don't want the SCEP agent installed then configure the Default client agent settings and your heirarchy will get no SCEP agent, if you want 10% of your computers to get it then configure custom client settings for that collection and they'll get the SCEP agent, you can then configure custom antimalware policies for those 10%

ok then, if you are sure you followed the guide exactly as i explained it then check your component status logs, is there anything obvious wrong in there ?

did you configure your boundaries ?

can you clarify, does your SCCM server have access to the internet ? what happens when you trigger a sync does that work ?

if you've got 100 laptops to build this week then use the Build and Capture Windows method, that way you wil control the process from start to finish, you didn't say what OS it was but I presume it's windows 7, here's the guide, follow it and you'll be Golden. Using SCCM 2007 Sp2 to deploy Windows 7 Deploy 7 (4 parts)

if you follow what I did above then real time protection will be ON and your virus definitions will be up to date assuming you are checking on a Windows 7 client in the All Windows 7 computers collection as that's where we targetted the deployments can you please double check ?

post your smsts.log here and the appenfore and appdiscovery logs

check your boundary group(s), and the references tab, in there have you a site assigned ?

i'm sorry you had to do this but i'm happy you are moving to the current release, please keep it up !

thanks for the thanks are you testing with the Release Candidate version ?

well the new and current version is SCCM 2012 Release Candidate - see here, i've already done a bunch of guides for it, my advice, forget about beta 2 and move to the new version, sorry !

one thing i must point out, are you testing this with Beta 2 (the old version) or the current release (Release Candidate) ?

what does ccmsetup.log say about that ?

simply remove the values we added in the registry hack and all is good.

you could script it sure, but what is stopping you from using SCCM, have you considered MDT also ?

are you referring to EP as from being installed above or purely talking about FEP 2012 on a different version of SCCM ? please clarify

did you login as Domain Admin and try again

have you tried SCCM 2012 RC yet ? in case you didn't know i'm running a series of guides all about it, so join in and see what is new and exciting with ConfigMgr 2012 Release Candidate

nope unless you want to, but do it to the x86 boot image at least

hi there ! have you looked here yet ?

there is more than one LOGS folder, double check that you are looking in the right place, if in doubt use explorer to SEARCH your disc partitions for the file