anyweb

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)

did you follow my guide exactly ? is it in a boundary that is already assigned to your SCCM 2007 clients ?

for a primary you shouldn't be using "SQL server 2008 Express" try SQL server 2005 or 2008 and see what happens

task sequences themselves are just a bunch of instructions defined by policies, when you for example pxe boot a computer and select a task sequence it pulls down the policies (instructions) that it needs to carry out from it's management point. if you want to be sure that you are using the modified task sequence simply change it's name for example, if the task sequence is called "deploy windows 7 x64" change it to "deploy windows 7 x64 v1.0" then pxe boot your computer, and which task sequence do you see ? you do not need to re-advertise the task sequence after changing steps in it

try re-installing it on http instead, and post the log here.

can you please explain how you are manually enabling the client ? and why ? are you talking about during OSD deployment ?

although for configuration manager 2007, this should work fine, have you tried it ? How can I password Protect a Task Sequence ? Password Protecting a Task Sequence

take a look at the previous part (Part 17) here, it covers adding those two applications

what does your smsts.log file reveal ? how are you defining the variables and how are you running the Run Command Line step ?