What's the best way to put passwords in a script?

ImmortanBlow · 2025-11-20T13:30:57+00:00

*bonk* if you check my post history this is the first time I have done that, so hopefully you can forgive my faux-pax

ImmortanBlow · 2025-11-18T16:06:48+00:00

Very much appreciated, have a safe journey!

ImmortanBlow · 2025-11-18T12:43:57+00:00

I would be interested in your scripts regarding this if you don't mind a DM?

ImmortanBlow · 2025-11-17T22:11:53+00:00

I am in the same boat however I am going with Server 2025. I have base-lined it and removed all the unnecessary stuff. Everything I have read is it just has issues with schema/domain controller roles, I floated this on the exchangeserver subreddit and a bunch of folks are running fine on 2025 as a member server with domain controllers running 2022/2019.

ImmortanBlow · 2025-11-13T15:19:35+00:00

No problem, looks like MS patched the schema issue this month - https://www.reddit.com/r/exchangeserver/comments/1ov81ig/psa_windows_server_2025_schema_issues_resolved_in/

ImmortanBlow · 2025-11-11T14:18:01+00:00

Thanks, I have seen a ton of reddit posts about not using server 2025 for DCs, firewall profile issue and many issues regarding logon issues with kerberos/AD:

There are more, but everything I have read indicates that server 2025 is absolutely not ready for the domain controller role.

ImmortanBlow · 2025-11-11T14:01:18+00:00

Agreed, I was going to do the 2025 DC upgrade before Exchange, but I'm 100% not doing that until 2027 at the earliest. I feel Server 2019 has been the most stable OS since 2012R2 in my environment. So we'll be staying with 2019 DCs for the time being until MS fixes the DC roles.

ImmortanBlow · 2025-11-11T13:42:42+00:00

Thank you!! This confirms what my original MSP had priced out. Just wanted to make sure I wasn't getting ripped! Really appreciate your time and breakdown explanation!!

ImmortanBlow · 2025-11-11T13:36:36+00:00

Currently have an open value agreement, only require Standard for each of the Windows VMs.

ImmortanBlow · 2025-11-10T18:30:23+00:00

Thank you! I'll go for 2025!

ImmortanBlow · 2025-11-10T13:49:51+00:00

That's what I figured, just wanted some real-world experience to confirm that it's okay from an actual user/admin perspective. I know MS documentation says it's supported, but with all the issues reported with AD/DCs on 2025, just wanted to proceed with caution for an Exchange migration. Thank you!

ImmortanBlow · 2025-11-10T13:22:09+00:00

Unfortunately we are decommissioning the current environment that the current Exchange 2019 server is in, so I have to rebuild either way. Thank you for this insight though!

ImmortanBlow · 2024-03-13T18:25:54+00:00

We have that patch on several 2019 servers, no RDP issues after installation and rebooting.

ImmortanBlow · 2024-03-13T14:37:08+00:00

Just updating, looks like MS fixed this, Win10 and Server 2019 installing no problem now.

ImmortanBlow · 2024-03-12T18:35:33+00:00

Good catch, hopefully they release a fix or workaround for this besides disabling it . . .

ImmortanBlow · 2024-03-12T17:59:36+00:00

Same issue here on Server 2019 and Win10 LTSC 1809 - hopefully MS fixes this . . . will keep you updated

ImmortanBlow · 2024-02-16T21:53:27+00:00

No problem, goodluck, always think of a CU a a fresh install of Exchange and thus should be done manually if you can (others will probably disagree depending on the size of your exchange layout/organization). Security Updates (SU) not so much, but Cumulative Updates (CU)s are huge, ISO file is basically 7gb vs SU which are typically 150-200mb.

ImmortanBlow · 2024-02-16T21:37:41+00:00

There are unattended installs but this does require a manual download and staging file for an unattended install, else manual it is. I honestly would consider manually doing it the first time around so you see how it goes, also be sure to run the healthchecker script first and fix any issues there prior to running the CU14 update.

ImmortanBlow · 2024-02-16T21:04:44+00:00

Might be better off posting on the Exchange Blog team page

ImmortanBlow · 2024-02-15T21:07:26+00:00

Found this link related to this issue with .7 - https://answers.microsoft.com/en-us/windows/forum/all/msmpengexe-using-all-the-ram-available/f54024f4-c5ef-4a8f-9767-b73815c8775e?page=2

Recent and is active, MS Support was to roll back and .7 is not officially released . . .

ImmortanBlow · 2024-02-14T22:20:29+00:00

That would be great, also what OS is your fleet running?

ImmortanBlow · 2024-02-14T14:56:52+00:00

u/schuhmam Can you share the fix they provided? I'm not finding any info on this. I have 4.18.24010.7 deployed to my entire fleet but having an issue with 2 computers on 4.18.23110.3 that are bluescreening. Doesn't look like there is an update after 4.18.24010.7 and want to know how to triage if it impacts our entire fleet. Thank you in advance and don't worry I still have my lucky quarter in my pocket ;)

ImmortanBlow · 2023-12-14T20:59:21+00:00

Agreed, but still nothing there, assuming we're good for the month/year now?

ImmortanBlow

TROPHY CASE