anyweb

sorry, where are there contrary reports ?

you need to specify NAME and MAC ADDRESS or NAME and SMSBIO GUID, you must have at least two

sounds like you deployed an OS to the All Systems collection did you ?

can you post of a screenshot of what values you entered

thanks, people still do want to do client push though, even if it's the manual option. I will certaintly consider adding this as a step in the next iteration of these guides, thanks ! As regards getting the client on the computers i've simplified it even more using Microsoft's best practise method which i describe in detail in Part 5 of this series (linked below). using System Center 2012 Configuration Manager - Part 5. Adding WSUS, Adding the SUP role, deploying the Configuration Manager Client Agent Part 5. Adding WSUS, Adding the SUP role, deploying the Configuration Manager Client Agent [June 3rd, 2012]

have you tested running the script as the local system account, you can test this using a tool called psexec from sysinternals. start a command prompt as system psexec.exe -s cmd.exe and then run your script from within that SYSTEM command prompt.

nice, and thanks for posting the solution !

do you mean Visual Studio 2008 or Visual Studio 2010 or something else ?

have you deployed any antimalware policy to a collection ? are your computers a member of that collection ?

box A can share the internet using internet connection sharing, have you tried that ? you'd have to disable the dhcp server (if any) on your wrt 54G as the computers would get their ip address from box A

well the failure is logged as Setting wizard error: An error occurred while starting the task sequence (0x8007000E). For more information, contact your system administrator or helpdesk operator. which sounds very like you have too many updates targetted to this machine - see this post for details of that. http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/53f84517-0f84-438b-bf07-c828c5f2109b

well it depends on how far you've gone, for example does this site have permissions delegated in AD for the system management container ? probably the best thing to do would be to uninstall the site (control panel, select Configuration Manager... in Programs/features and uninstall it...) wait for it to completely uninstall before rebooting, then start again.

unconfigure it and try again

looks like you have a gpo configured at the domain level for WSUS (software updates), check this and either get it disabled or rethink your Configuration Manager 2012 SUP strategy.

it's a pretty confusing diagram, ever tried MS Paint ;-) why don't you just setup a NAT of some sort and do it that way

hi Gary. please do post the smsts.log file from a machine where this problem has occurred

from your ConfigMgrSetup.log is the logged on user a domain user and a local administrator of this computer ?

are your clients XP or Windows 7 ? why did you think it was a windows installer problem ?

i wouldn't install them on the same server, not sure if it's even supported. as regards can you install a primary site without a CAS, of course, but then it will be a standalone primary site with a maximum support of up to 100,000 clients.

have you reviewed part 5 yet ?

did you add a role for Mobile Devices ? (Enrollment Point) ?

have you configured Ip helpers for your switch/router that sits between your computer and the configuration manager server that is on the other lan ?

you need to install the PSP role on the secondary site if you want to image computers at that site using PXE boot. The PSP role requires WDS to be installed (but not configured)

have you made sure to distribute content for this content to a dp ?

my comments in RED below:- 1. Install EP Role on SCCM - you must do this on the Top most site server (CAS or a Primary in the case of a standalone primary) 2. Enable management but set install to FALSE in the default Policy, do NOT change the default client device settings, create Custom client device settings and deploy them to the collections you want targetted. 3. Setup a new policy to manage deployment for groups of users in a controlled way. you can only deploy Endpoint Protection to Computers, not users. 4. I can also do a backwards, package install so FEP is available, ready to go before the user even logs into the machine by creating a package for FEP, and running as follows: scepinstall.exe /s /q as a package, and deploying in the task sequence not following your train of thought here.. you havn't mentioned how you've defined your SUP, your ADR's for definition updates ? i would test everything in a lab first (use my guides) and then when you have confidence push it out to production starting one collection at a time. (phased rollout)