Archive for category: Knowledge base

Learn how to automate daily reboots or shutdowns at specific times using the command line or command prompt in Windows 10/11.

Below is an example of scheduling a computer shutdown daily at 6 PM:

schtasks /create /sc daily /tn ShutdownAt6PM /tr "shutdown -s -f -t 2" /st 18:00 /NP

schtasks: Command used to schedule tasks. The deprecated AT command from earlier Windows versions is no longer supported.

/create: Creates a new task.

/sc: Sets the frequency of the task, such as once or daily.

/tn: Specifies the name of the task, serving as its description.

/tr: Defines the command to execute, like “shutdown -s -f -t 2“. Here, -s initiates shutdown, -f forces shutdown, and -t 2 introduces a 2-second delay. Replace -s with -r to reboot instead of shutting down.

/st: Indicates the time to execute the command.

/NP: Ensures the scheduled task runs on Windows computers irrespective of user logins.

By using this command, you can streamline and automate regular shutdowns or reboots for enhanced system management.

The following are the outgoing IP addresses and networks of Microsft Office 365 SMTP/Email in case you need to know to white-list in your antispam or firewalls:

52.100.0.0/14
40.92.0.0/15
40.107.0.0/16
104.47.0.0/17
2a01:111:f403::/48
2a01:111:f400::/48

Office 365 Mailbox Migration Status Stuck Syncing

We had a mailbox that wouldn’t complete migrating from a hybrid setup with on-premise Microsoft Exchange 2013 Server to Office 365. We’ve cancelled the migration several time and restarted it but it always got hung up at the end without completing, with status Syncing or InProgress… left it even for days and wouldn’t complete

We’ve found out that some corruption in the calendar ACLs that was causing the issue… Office 365 portal wouldn’t show any message about corruption or skipped items….

We connected to Office 365 through PowerShell and issued the following commands which would approved skipped items (that we never prompted to approve in the migration using the browser which was odd, then the 2nd command would complete it)

Set-MigrationBatch  -Identity  TypeNameOfTheBatchHere  -ApproveSkippedItems
Complete-MigrationBatch  -Identity  TypeNameOfTheBatchHere

In Office 365 two factor authentication (2FA), App Password is used for older versions of Microsoft Outlook or for non Microsoft email clients on devices like MACs or smart phones.

After enforcing 2FA in Office 365 and if you are trying to configure Outlook 2016 for email, and Outlook keeps rejecting the password that you have been using and that works with OWA, while if you try the App Password it works in Outlook, then you might want to add a registry key to enable and enforce Modern Authentication.

Make sure Modern Authentication is turned on on the Office 365 Portal.  Login as admin, expand Settings, click Org Settings, Select Modern Authentication and turn it on.

• Outlook 2010 doesn’t support Modern Authentication

• Outlook 2013 supports Modern Authentication but you need to add the following two registry keys.  DWORD and set to 1.

HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\EnableADAL

HKCU\SOFTWARE\Microsoft\Office\15.0\Common\Identity\Version

The following key will enforce it.

HKEY_CURRENT_USER\Software\Microsoft\Exchange\AlwaysUseMSOAuthForAutoDiscover

• Outlook 2016 supports modern authentication and it is ON by default but we’ve had to enforce it in some instances because Outlook kept prompting for a password and wouldn’t take the password that worked with OWA but Outlook worked with App Password.  Enforcing Modern Authentication made Outlook 2016 accept the regular office 365 password (that worked OWA password).   Add the following DWORD and set to 1

HKEY_CURRENT_USER\Software\Microsoft\Exchange\AlwaysUseMSOAuthForAutoDiscover

Note: registry changes might result in problems and serious issues with computers and software.  Do it at your own risk.