Chris Nackers

There is absolutely no reason for a 5k organization to have a CAS, not a single valid reason. Separating the server teams and desktop teams is done via RBA, multiple primary sites will not give you separation as the data is global, it will be replicated between the sites. You also should not have any load issues with a 5k client environment if the server is configured properly. You can easily run all the roles including the database on a single primary site as long as it is configured properly. Here is a webcast i did on RBA, i would recommend watching it to learn how to seperate desktops/server teams. http://www.chrisnackers.com/2013/10/27/role-based-administration-tipstricks-replay-is-up/

It's stored in the XML in DB, it's encrypted. The task sequence is located under OSD - Task Sequences node.

You can simply use the existing WSUS server to install updates during a ConfigMgr TS. http://myitforum.com/cs2/blogs/cnackers/archive/2011/04/28/using-ztiwindowsupdate-wsf-to-install-updates-in-a-system-center-configuration-manager-task-sequence.aspx

have you imported the R3 reports? that is a manual step that needs to be completed.

what does the software distribution look like? what do the logs say? is the client receiving the policy?

when you distribute the boot image you should have a PXESHARE$ option, that is the PSP, needs to be there to boot it over PXE...

Did you add the boot image to the PXE Service Point? The log should be in x:\windows if memory serves

ok, then it's probably not the correct driver... if you look at the winpeinit.log you should be able to see the hardwareid of the NIC, you can use that to track down the correct driver

Are you referring to the R3 package that is created during the install? Did you remember to distribute that package to the distribution points?

drivers should be added/removed from within the configmgr console (boot image properties) if you are using WAIk to add drivers, then they need to be added to the winpe.wim file, not hte winpexxxxxx.wim file. If MDT has been integrated into your console, you will have a new option under the right-click menu for boot media and for task seqeuences called "Microsoft deployment...", MDT extensions are a PER-console basis.

Windows PE is based upon windows 7, so you need t inject the appropriate windows 7 drivers... then you will also need the appropriate drivers in your driver store for the OS you are working with (XP, Vista, Windows7). These would be installed via apply driver package or auto apply driver step. Again, for winpe to have a correct IP, you need the correct windows 7 driver added to the appropriate boot image. ConfigMgr SP2 is WAIK 2.0 which is windows 7 based WAIK 2.1 is windows 7 sp1 ConfigMGr SP1 is WAIK 1.0 which is Vista MDT 2010 uses WAIK 2.0 (win7) MDT 2008 uses WAIK 1.0 (vista)

Linked shares have their own customsettings.ini and bootstrap.ini, so you need to add the appropriate queries to those files just like you have for your primary share. Remember that any change to bootstrap.ini requires an update to the boot media for that share.

I haven't been able to sucessfully get it to work. I typically just copy the stock files and modify as needed. The issue is always the path and ensuring that path works for all scenarios, which is next to impossible.

I could mistaken on if it's possible, but off the top of my head, i don't think it is. not 100% though. I know you can do it without the SMP but with the way the SMP works, it doesn't surprise me that it's not working for you.

So your main issue is really a result of the disk encryption. Typically you would simply refresh the existing box in-place. This isn't possible do to your encryption, so you almost have to treat it like a replace scenario, old hardware to new hardware. When you PXE boot the machine, it's basically a new item, there is no associaton, that's where you're getting into a bind. It's not designed to do what you are trying to do with it. It's seeing the MAC is the same, so it's creating a new record, and thus the in-place assocation doesn't work. You would have to create an assocation to a new object just like new hardware, but since it uses the MAC, that's an issue. Another option would to not use the SMP and simply dump the user data to a network share.