If I have a remote site that I want to start out with just a Branch DP installed on a 2K8 server, and later if we find a need to upgrade to a Full Secondary Site with a real DP is there any issue I need to be aware of? Since the clients will all still use the primary site code in both instances I should be ok there correct? The reason I ask is because this location has some IT staff, however they are untrained on SCCM. They are also not sure that they want much more then software updates and software distribution. So as suggested by my Microsoft SE I want to use the K.I.S.S. principles. In the future if they decide they want to use OSD I guess I would then think about making them a Secondary Site.

You should look at the technical (dis)advantages instead of the local IT staff... mainly because both can't be managed localy... So take a look at this article to make a good pick: http://technet.microsoft.com/en-us/library/bb693570.aspxMy Blog: http://www.petervanderwoude.nl/ Follow me on twitter: pvanderwoude

Honestly, if you already have a server there, a secondary site is the simpler approach. BDPs do things differently that add complexity and possible overhead particularily when something goes wrong. They are also more flexible without any real extra overhead.Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys

If you have a server, do not go for a BDP. Install a secondary site server, it will save you time troubleshooting and give you more options (site systems).Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund