Search the Community

Hi All, Just looking for some advice, has anyone migrated their primary server from one machine to another? Looking at doing this, but wondering if there's any pitfalls I need to look out for. Thanks

I've been tasked with migrating a customer off of server 2008 R2 to Server 2012 R2. All FSMO roles have been transferred to the newly created Server 2012 R2 DC's and replication is taking place. Tomorrow, I would like to migrate dns off of the 2008 boxes. The scopes have replicated to the new dns servers, but how to I make sure the clients get pointed to the 2012 dns servers once I take the 2008 servers offline? I do have dns integrated into AD. I'm stuck at the "ensuring primary dns server" becomes my 2012 DC. Would the below powershell command set this across the domain? Set-dnsclientserveraddress –interfaceindex 15 –serveraddress (“xx.xx.xx.xx”,”xx.xx.xx.xx”) Any advice would be greatly appreciated. Thank to everyone!

Hi, my name is Paul. I'm an employee in a relatively small enterprise (about 700 persons), let's call it Comp-A. My collegue and me are about to make up an SCCM hierarchy for our enterprise. We need to present it next week, which is a bit short, alas. And here are things getting complicated. I'll explain our situation. SCCM will we used to deploy pc's, servers and mobile devices for ourselves. Comp-A consists of three buildings in one city and two sattelites in two other cities. Bandwidth is no problem, we have enough fibers. So Comp-A could do with one primary site and no CAS. BUT. There is also Comp-B, about 1400 employees, this company has her own domain and her own buildings. It is totally independent. But the firewalls between Comp-A and B are wide open, due to policital reasons. We are twins. There is also Comp-C, about 120 employees. It's the same scenario: it's a seperate company but the firewalls are wide open. So we aren't twins, we are three ! Next, we have Comp-D and Comp-E. For those two we deliver pc's and their configurations and updates etc. You get the picture, Comp-A is what you could call a "service provider" for the other companies. We live in some kind of symbiose with them. Now, knowing all this, how would you organise SCCM? CAS/no CAS? SQL remote or local? Primary site in every Comp or not? And what about redundancy and high availability? We do have a huge data center with hundreds of virtual servers, fibers everywhere, a SAN, so resources are no problem.