TomWhi

Thanks Garth! That's good advice and you're right; there are a lot of components to a domain that probably need to be investigated. I cannot find any references from Microsoft that says if empty sites are supported, but the fact you can create them possibly means that it is...? As long as the subnets and costs are in order then the clients should still be able to find the closest DC and that site information can be used in other "site aware" applications. I did find this link which highlights that "empty sites" are controversial but do have their purpose; http://www.myitforum.com/articles/1/view.asp?id=11919so might be useful reading. Now I'm off to kick our AD team with that list and make sure stuff is in order ;-)

Hi, I ran into the same problem / question on our SCCM 2012 R2 site. It's my understanding that you need this folder on your primary because that's where the content generated to and copied from. Even though the clients won't download content from it, the folder is still required on the primary for your remote DP's to work. This previous post confirms it: http://www.windows-noob.com/forums/index.php?/topic/11234-sccmcontentlib-on-primary-server/ Hope it helps (even though it's not what you want to hear) Cheers Tom

I am willing to bet that this isn't the answer MadMacs77 was looking for. I must admit I have been following this thread because the topic is interesting to me. The question was "Do you make a Site in S&S if there's a physical location, but no Domain Controller local to that location, or do you assign the subnets for that location to a Site that has a Domain Controller (and has a direct route)?". I assume why he wants to cleanup his AD S&S is because it's good practise to learn how his new employers AD is setup so he can better support it - I know that's the first thing I did when I was managing my company's AD, but that's not important - that wasn't the original question. So if we can look at the question again - is it best practise to create a site for each physical site in your organisation even if there is no DC on the physical location, or do you attach the subnet to a site which does have a DC even though computers are not actually on that physical site. The reason why I want to know (maybe for similar reasons as MadMacs77) is because our large SCCM environment uses AD Sites for the boundaries and we also want to look in to creating group policies based on AD Sites (for printers and drive mappings) which for small sites with no DC might benefit from having an AD Site created - it also helps our first line support team know where the users are when they are looking in logs rather than assuming they are on a large site. It'd be great to get your opinion on this Gareth (and others) because I have followed a few of your posts and I know that you've got a wealth of experience and knowledge. Cheers Tom