sasavine.blogg.se

1. #Any risks moving pdc to the secondary domain controller upgrade
2. #Any risks moving pdc to the secondary domain controller windows

Do I have different WAN connections on 3 different topologies? Yup. For us, people could work from home at this point. Even if there was a DC on site, nothing would get done past logging in (maybe minesweeper or some other trivial nonsense). Our issue is internet services more than DC authentication.

So, no internet at any site grinds everything to a halt. At my current employer, we have deployed a cloud-hosted ERP, Cloud-hosted VoIP phone system, Cloud-hosted email. While this is is a valid concern, it is the linchpin? Ask yourself a question: How much work will get done without an internet connection? In my last position, this was still a lot. It seems that people are worried about connectivity to cloud-based DCs. I could go on for hours, it's actually comical at this point how everyone thinks cloud will solve all of their problems and they can lay off 75% of their IT department once its done.

#Any risks moving pdc to the secondary domain controller upgrade

O/S's don't upgrade themselves, neither do VDI/RDSH farms.

#Any risks moving pdc to the secondary domain controller windows

And then you still gotta manage Windows the same way we've been doing for 30 years. I would go VMC on AWS in a minute but I'd have to sacrifice my position so the company could afford the $100K per year in hosting fee for 4 hosts, oh and that doesn't include egress traffic costs either or a cloud based backup solution (probably Veeam cloud provider anyways) or a firewall with content filter, IDS/IPS, sandboxing malware, AV, etc, etc. If anything you transfer costs from Capital expenditures to Operational expenditures. But do not move to the cloud thinking you are going to be saving a heap of $$$.

You gain in availability, redundancy and scaling your costs to what you need. When we ran our analysis there was no way that cloud was ever going to be cheaper. We can scale our costs but the brunt of the heavy lifting is still done on prem. Well you wanted to be in the cloud right? We are hybrid and host critical services in Azure as backup. They go all cloud and then executives start asking questions once their monthly spend becomes apparent. If budget is limited that is a different story, but at least then the organization has all the info to make decisions on what it will gain vs lose depending on what they want to spend. Define the features you need first, work backward to what options fill those needs and then the cost of those options. How much control do you need of the directory, what authentication technology do you need (modern auth, NTLM, Kerberos), etc. Where are the objects you are managing (on-prem or remote workstations all over the country), what features does the organization need (heavy workstations management with GPO or just identity/access management only),

I would focus on the functionality you need first, before factoring cost. How can I convince my CTO to go with an on prem DC? I've never been In this position before a DC has always been in place in all my previous roles They both seemed geared towards extending on prem DC rather than replacing one. I have looked at AD directory services hosted by both AWS & Azure both don't have default GPOs that I cant seem to disable or modify and the delegated admin groups are limited since its a managed DC.