robintech Posted August 24, 2022 Posted August 24, 2022 (edited) From what I've read it will continue to work but is unsupported from 31st onwards and may stop working at any time Some notes from our upgrade Versions prior to 1.5.42.0 don't have export feature but you can unzip/extract the MigrateSettings.ps1 from the latest msi and run that, it reported success and created the files for me.The Auto Update doesn't work if for example you have added your own custom rules to the configuration Sync seemed to take a few hours to come back to default 30 minute periods PowerShell get-adsync commands like Get-ADSyncScheduler are useful to confirm what settings you have Edited August 24, 2022 by ittech2342323
psydii Posted August 30, 2022 Author Posted August 30, 2022 Probably really my last call about this - deadline is Wednesday this week! That said, I've heard of a couple of installations now that just upgraded themselves after years of being stuck on 1.x
chazzy2501 Posted September 22, 2023 Posted September 22, 2023 Ha! I'm here and missed all this, I'm the guy! Damn it I'm on server 2012r2 as well.... this suckkkks.
colly72 Posted September 22, 2023 Posted September 22, 2023 Ha! I'm here and missed all this, I'm the guy! Damn it I'm on server 2012r2 as well.... this suckkkks. Support for 2012 R2 ends on 10th October - you don't want to be running an unpatched Server after this date. Another reason to get off 2012 R2 ASAP.
chazzy2501 Posted September 22, 2023 Posted September 22, 2023 Support for 2012 R2 ends on 10th October - you don't want to be running an unpatched Server after this date. Another reason to get off 2012 R2 ASAP. ok, double 5hit. many 2012r2 servers (I thought it was next year!) busy week coming up..
3s-gtech Posted September 22, 2023 Posted September 22, 2023 2012 R2 in-place upgrades beautifully IME. As long as you're licensed, don't stress that. If you have an Exchange server on that OS, do stress. Do not update to 2016, skip to 2019 at least. 1
chazzy2501 Posted September 26, 2023 Posted September 26, 2023 I found a 2012 server, had to do the 2016 route... well that took an age! got the credsccp error on RDP now... (on server 2016)
KK20 Posted September 26, 2023 Posted September 26, 2023 credsccp on 2016 was fixed by running latest updates I think. I seem to remember RDP not working immediately afterwards but fine after a few updates. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now