Level 2 Update Procedures Overview
The Level 2 Update is an advanced support PowerShell process designed to update the entire replication server in a controlled and fully supported manner.
This includes:
- Windows Critical Updates
- Microsoft Office (Microsoft 365 / Outlook)
- Add2Exchange Enterprise Edition
- Required supporting files and modules
At the time of execution, we guarantee compatibility between the current version of Add2Exchange Enterprise Edition and all current critical service packs applied by this process.
Updating the system as a whole ensures the replication server remains fully in-band, stable, and supported for extended periods.
Update Frequency Recommendations
- Quarterly updates are recommended for both Add2Exchange and the replication server.
- Performing all updates together maintains full support alignment (“in band”).
- Critical security updates should always be applied immediately.
- Do not update Microsoft Office independently as part of routine monthly patching without following the required pre- and post-commands.
- Updating MSO without these steps can put the system out of band.
- By default, the system is configured to download and notify Windows updates and disable MSO updates, though centralized patching systems may override this behavior.
Managed Update Systems (RMM Tools)
If the replication server uses managed updates, the required pre- and post-commands must be implemented.
Refer to:
Maintenance Recommendations for RMM Tools – Pre and Post Commands
Starting the Level 2 Update
- Log in to the replication server as the Add2Exchange Sync Service Account.
- Locate DidITBetter Support Menu.ps1 on the desktop.
- Right-click the script and select Run as PowerShell.
Important Notes
- If a standalone “Level 2.ps1” exists on the desktop:
- Do not use it.
- Delete it—it is outdated.
- Always launch Level 2 from the DidITBetter Support Menu.ps1.
Accessing the Level 2 Option
- The Level 2 Update option is located in the bottom-right column of the DidITBetter Support Menu under Tools.
- If the Level 2 option is not present:
- Add2Exchange must be upgraded first.
- From the top-right column, select Upgrade Add2Exchange.
- After triggering the upgrade:
- Close the Support Menu.
- Reopen it so control files refresh.
- When prompted again, select No to upgrading Add2Exchange and proceed with other available options.
What to Expect When Level 2 Starts
Upon launch, significant system activity will begin.
This is normal. Do not interrupt the process.
The Level 2 Control PowerShell is multi-threaded and may open:
- DidITBetter MMC (legacy Event Viewer and service control)
- Task Manager
- Microsoft 365 update thread
- Windows Critical Updates thread
- Exchange Online PowerShell module version correction (if required for scheduled task permissions)
Initial Cleanup and Logging
The Level 2 process first:
- Deletes all temporary PowerShell files created by automatic permission tasks
- Includes files created since the last Level 2 run or earlier
- Calculates reclaimed disk space
- Automatically creates a Support Log documenting the entire session
Add2Exchange Upgrade Prompt
You will be prompted to upgrade Add2Exchange Enterprise Edition.
- The process checks Software Assurance (SA) status:
- If not expired, proceed normally.
- If expired:
- You must renew SA to receive the upgrade.
- After installation, you must submit a license request from the Add2Exchange Console.
Refer to:
License Key Product Activation Instructions
Licensing Notes
- If the Sync Service Account can receive email from diditbetter.com, licensing may auto-complete.
- If immediate syncing is required, contact support for expedited assistance.
Add2Exchange Upgrade Process
During upgrade:
- The Add2Exchange Service is stopped automatically.
- The installer waits for the Add2Exchange Agent to exit memory safely.
- The upgrade package is downloaded, extracted, and installed.
- If a PowerShell window appears paused, press Enter to continue.
- User prompts should not appear on recently updated systems.
Exchange Online Module Validation
- Level 2 verifies the installed Exchange Online PowerShell module.
- If necessary, it will automatically upgrade or downgrade the module to a supported version.
Outlook (Microsoft Office) Update Process
When nearing completion, Level 2 pauses with the prompt:
“When Outlook is done updating, press Enter to continue.”
Outlook Update Thread
- Outlook updates are run in a separate thread.
- Updates are expected, as automatic updates are disabled after completion.
- Do not press Enter until this Outlook update thread has fully completed.
Controlling updates in this manner ensures the system remains fully supported and in band.
Windows Critical Updates Thread
- Windows Critical Updates are checked and installed if allowed by policy.
- You must wait for this thread to finish before continuing.
- If updates are applied, a reboot may be required.
Outlook Profile Optimization
After Outlook updates complete:
- Level 2 runs Setup Outlook Profile.ps1
- This script:
- Resets Microsoft’s default Office update manifest to desired configuration
- Applies required Outlook registry optimizations
- If this step is missed, the script can be run manually from:
- Outlook Tools within the DidITBetter Support Menu
Completion and Reboot Check
After all threads finish:
- Return to the Level 2 window.
- Press Enter to continue.
- Review the automatically generated Support Log.
- Level 2 checks for a pending reboot:
- Any Office update will always require a reboot.
Pre-Reboot Requirements
Before rebooting:
- Open Outlook.
- Answer all prompts.
- Do NOT select “Use the new Outlook.”
- Allow Outlook to send and receive uninterrupted.
- Close Outlook.
Reboot and Post-Update Validation
- Reboot the system.
- The server should automatically log in.
Licensing (If Expired)
- Open the Add2Exchange Console.
- Submit a license request if required.
Relationship Verification
- Review all relationships:
- If alerts are due to licensing, keys are typically issued within 24 hours.
- If alerts are not licensing-related:
- Right-click and select Confirm all alerted relationships
- Approve folder updates when prompted
- For obsolete users:
- Select Empty Trash Always to force deletion
- Remove offboarded users from managed AD or Microsoft 365 distribution lists
- Typically named similar to zpubcontactfoldersync
- Managed distribution lists can be reviewed via:
- Relationship → Relationship Group Manager
- Best practice is to offboard users via AD or Microsoft 365 group membership—not by unchecking lists in the console.
Once the Add2Exchange Service is restarted, offboarded relationships should begin removal within minutes. Onboarding will continue next, then sync all relationships.