Jump to content

cishandfhips

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by cishandfhips

  1. So IPv6 has been unticked on our existing DCs since they were installed some 12 and 8 years ago. It is unticked across the network and all computers (running windows 11) are operating fine. Also Smoothwall (which we use) only uses IPv4. I have a 2016 DC and a 2012r2 DC (Yes I know! that's why I'm doing this!) I want add a 2019 DC as it will be covered for updates for a few more years. (2016 updates end Jan 27) and when its up and happy, I want to retire the 2012r2 DC (Obviously! 😬) My point is if everything is ticking along nicely now and i don't have any issues, why would i need to tick the IPv6 box in my "new" 2019 dc? (When i set it up)
  2. Thanks for the reply One drive has (or will have) Server 2022 on it I looked into storages spaces and both drives have to be blank in order to create the mirror
  3. Hi Back when schools had money we purchased a few HP Microservers. One was never used and has been sat in storage for 5 years. I want to use it as a Server 2022 VM Host for a DC. It only has 8gb of ram but its perfectly fine for a 4gb DC as it wont be doing a lot. Its out and up and tested to make sure its still good. BUT With the cost of enterprise SSDs going through the roof, as well as school budgets being tight, I bought a couple of 250gb EVO 870, with the intention of putting them into RAID1. Like I say all this server will be doing is hosting a 2022 DC. They are brand new (dated 2026) But then I read that the Marvell Controller in the Gen10 Microserver doesn't play nice with SSD's (Especially the EVOs) The Server is (or will be) plugged into a good APC UPS with a new battery. I only have two of these 870 EVO drives, Do I risk it and use the Marvell controller? Or do I just use (Old School) Disk management and mirror the drives from there? I cant use storage spaces because both drives need to blank in the first place. I don't know best the option? Or do i just beg finance to let me buy another and use that as boot drive (Obviously wouldn't have any redundancy) Thanks
  4. Thanks for the replies. It's already unchecked on the 2 DC's that are running and it has been since they were setup some 8 years ago? That's what's confusing me. Everything I read says don't disable ipv6 on DC's but it always has been disabled as far as I'm aware and it hasn't caused any obvious issues. In fact I've noticed both schools I work at have the same setup with 2 virtual 2016 DC's that have ipv6 disabled? I didn't set any of these up, this is my first time adding an addition DC, and it's only because of the physical age of the existing setup.
  5. I have 2016 DC doing my DNS DHCP I have an ancient 2012r2 DC DNS which is still going strong but needs to come out for obvious reasons I have spun up a new 2019 VM on hyper v and want to make it into another DC so that I can remove the 2012r2 one IPv6 isn't enabled on any DC but they have both been doing a stellar job for 8+ years with no issues (I inherited this network a few years ago and only now am I able to do anything with it) However will I have any issues if I don't tick the IPV6 box? I kind of don't want to cos it's all been working fine without? It's only when I was researching that I found out that IPv6 should be enabled on DCs other wise it can cause all sorts if issues when you try to add another?? Any advice greatly received!
×
×
  • Create New...