Hello Everyone! I introduced SCCM 2007 R3 to my company's domain a couple of months ago. When I started, I didn't know a thing about it and am teaching myself how to use it more each day. Our company has 4 primary locations. Each is connected by WAN with about 300-500 workstations at each location. I installed the SCCM server at at my location in Tennessee, then created Site System roles at each of the other locations. Here's what I'm trying to do: The San Diego location is the other "big" one. I recently installed the SCCM Console on one of their workstations to show them a few things. During installation, I of course entered in the SCCM server in TN to connect to. When they tried to browse it, it was extremely slow to populate collections as well as refreshing everything else. What should I do? I have already created a new VM in San Diego which will be deicated to SCCM use. Should I make it a secondary site? If so, would that alleviate many of my issues? I had already started installing SQL on it when I stopped as I found that secondary sites use the primary's database. If that's true, I can't see how the browsing and refreshing speed would improve. My primary site has Windows 2008 R2 x64 running SCCM 2007 R3 on a beefed up VM running on ESX. Please advise - Thanks!Ben K.

I would go for a secondary site based on the few information given in the question.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

If you are refering to how slow console access might be across WAN links; here's what we have done. In the same server room (as close as possible, LAN wise) to your central primary site, setup either a Citrix published application, or a Server 2008 TS application. No locally installed ConfigMgr Consoles at all. Your Console users launch the remotely hosted Console application. Here's why that's a good idea. The ConfigMgr console relies on communicating with the "SMS Provider", which is essentially WMI on your primary site server. And crossing WAN links, slow latency, multiple hops; that can make local consoles trying to talk to the remote provider very slow to respond. If the Console instance is 'next to' the server (network wise), the console itself will be fast. Plus, another benefit is it's only 1 console to upgrade when you (for example) have to install R3, or some other console-related updates.Standardize. Simplify. Automate.

Hey Ben, I know that Citrix Published Application works like a charm. Blair Muller

Hey Ben, I know that Citrix Published Application works like a charm. Blair Muller

Hello - I concur with Sheryy if you wanted to use SCCM console through slow WAN. May be, if you have more than 100 users or workstations at the end of slow WAN link then I would rather go with Secondary site option so that you can avoid WAN bandwidth issues through throttling.Anoop C Nair