28
Apr

Export All SMPT addresses of M365 using Powershell

Exporting all SMTP addresses (emails and their aliases) from Office 365 (now Microsoft 365) can be essential for various reasons, particularly during migration processes, such as transitioning to another domain.

Below PowerShell Query for exporting all aliases in a CSV

You can use the below PowerShell query to export all email addresses and their aliases in a single CSV as a comma-delimited file. You can use Powershell ISE or simple Powershell to run the below cmdlet.

M365 Exchange online module should be installed on your system First then, connect Powershell using the below command and follow the onscreen instructions

Connect-ExchangeOnline

Then, Paste the below Cmdlet

Get-EXORecipient -ResultSize Unlimited | Select-Object PrimarySmtpAddress, DisplayName, RecipientType, RecipientTypeDetails, @{Name=”EmailAddresses”; Expression={($_.EmailAddresses | Where-Object {$_ -like “smtp*”} | ForEach-Object {$_ -replace “smtp:”,””}) -join “,”}} | Sort-Object DisplayName | Export-CSV “C:\Temp\All_user_SMPTys.csv”

Create a folder in drive C named “TEMP” or change the path as per your desire but make sure you have access to the path and path should exist. The below cmdlet will export CSV in Location “C:\Temp\” .

Here’s an elaboration on why it’s crucial:

  1. Migration Planning and Mapping: When migrating from one Microsoft 365 domain to another, or even to a different email platform, having a comprehensive list of all SMTP addresses is crucial. This list serves as a mapping file, ensuring that emails are correctly routed from the source to the destination during and after migration. Without an accurate mapping of SMTP addresses, there’s a risk of emails being lost or misdirected during the transition.
  2. Data Integrity and Continuity: Exporting SMTP addresses helps maintain data integrity and ensures continuity of communication during the migration process. By preserving all email addresses associated with user accounts, you can avoid disruptions in email communication and minimize the impact on productivity.
  3. User Identification and Verification: The exported list of SMTP addresses allows for easy identification and verification of users and their corresponding email addresses. This is particularly useful for large organizations with numerous users, ensuring that no email addresses are overlooked or omitted during the migration process.
  4. Compliance and Audit Purposes: Keeping a record of all SMTP addresses may be necessary for compliance with regulatory requirements or internal audit procedures. Having a documented list of email addresses facilitates compliance audits and ensures that all communication channels are accounted for during regulatory inspections or internal reviews.
  5. Troubleshooting and Support: In the event of migration-related issues or post-migration troubleshooting, having access to a complete list of SMTP addresses simplifies the process of identifying and resolving email-related issues. Support teams can use this information to quickly diagnose and address any email routing or delivery issues that may arise.
  6. Documentation and Documentation: Exporting SMTP addresses serves as documentation of the email infrastructure configuration at a specific point in time. This documentation is valuable for future reference, planning future migrations, or making configuration changes to the email environment.
  7. Risk Mitigation: Exporting SMTP addresses mitigates the risk of data loss or disruption during the migration process. By ensuring that all email addresses are accounted for and properly mapped, organizations can minimize the potential impact of migration-related errors or oversights.

In summary, exporting all SMTP addresses from Office 365 is essential for ensuring a smooth and successful migration process, maintaining data integrity, complying with regulatory requirements, and facilitating efficient troubleshooting and support. It’s a critical step in safeguarding email communication and minimizing disruptions during periods of organizational change.

20
Apr

Search Email using msgid in Gmail/Google Workspace

Sometimes users continuously mention that he/she is not receiving any email from a particular sender/group but his/her colleagues receive the same email.

We need message-id of the same email to search it in the inbox hence below condition should be true to search email using msgid. You need to get the message-id from your colleague.

  1. The affected user should be in the cc/bcc/to of the same email sender from his/her colleague who received the email
  2. Email should delivered via a group (google group/O365 group/distribution list etc)
  3. Or you can get message-id of the email from your administrator from an email log search.

How to Get Message Id from Gmail / Google workspace mailbox

  1. Open the browser, open Gmail.
  2. Open the email you want to find the message id.
  3. Next to Reply, click More. Show original.
    • Search message id
  4. In a new window, the full header shows.
  5. Copy message id, do not copy brackets.




    If you want to download the full message header then
    • click Copy to clipboard and save to the notepad.
    • Or click Download header        

Search email in Mailbox using message id

  1. Open Browser, and go to Gmail.
  2. Click on the “search in the mail” in the search bar.
  3. Past the below string, with message-id copied from the above steps
    1. rfc822msgid:msgeid

For eg

rfc822msgid:1933222678.349555394.1713231481987@sjmktmail-batch1f.marketo.org

4. Press enter

30
Jul

Notification issue while Migrating O365 RoomMailbox to Google Calendars

Issue

When migrating Roommailbox bookings to Google Calendars, the migration Tool (GWS) sends RSVP notices to participants’ mailboxes which will cause a lot of confusion and Users keep receiving mailbox notifications for resource Booking.

To Fix this problem A content compliance rule can be set up in the Google Workspace admin console to quarantine such mail notifications.

Solution

Follow the below steps

  1. Open Google admin console, URL www.admin.google.com
  2. Go to Menu “”and then”” Apps > Google Workspace > Gmail > Compliance.
  3. Select the Root OU (Domain name = Root OU)
  4. Scroll to the Content compliance setting in the Compliance section, and Click Add another Rule.
  1. Content compliance = Give a name for the rule, eg. Block resource calendar notification.
  2. Select Messages to affect – Inbound and Internal -Receiving
  3. Add expressions that describe the content you want to search for in each message
    • If all of the following match the message, and click ADD
    • Location: Full headers
      Contains text: @resource.calendar.google.com
    • Location: Full headers
      Contains text: ILARL

5.  If the above expressions match, do the following
Quarantine message = Default. (you can create your a quarantine space for different types of emails, refer article on how to create quarantine)

6. Save.

31
Oct

Add Aliases in O365 using Powershell

Add users aliases in O365 (Powershell)

Things to Remember while adding aliases to MS O365 via PowerShell while running our CMD-lets

  • Prepare a user list for adding aliases in CSV format.
  • First Column will have primary email address and second will have aliases.
  • In the CSV, create header for primary email address as Mailbox and Alias email header will be named as NewEmailAddress
  • Create folder in C drive and name it as temp.
  • We are saving csv as aliases.csv
  • Connect the Exchnage powershell and Run below command. Click here to setup and connect Online powershell.

Adding aliases we can achieve by running the command in two ways but both will have the same result. The difference is working with PowerShell script and running it into Powershell ISE and another is via using Powershell CMD

First Method

By Importing everything from CSV to Variable named $user and then process our request. Also, you can save it as a PowerShell script like aliases.ps and then run it using windows Powershell ISE Or copy/paste the below code to the PowerShell console. Click here how to setup PowerShell for using O365.

Copy and past below CMD to Powershell or Copy/past it into notepad, save it as “Alias.ps” then open it in Powershell ISE. Click here how to connect PowerShell ISE for using O365.

$users = Import-csv ‘C:\temp\aliases.csv’
foreach($user in $users)
{
Set-Mailbox “$($user.Mailbox)” -EmailAddresses @{add=”$($user.NewEmailAddress)”}
}

Second Method

Below CMD will use to direct apply changes without using any variable. Copy the below command and past it to Powershell CMD. Connect power with exchange online (EXO) before past the below command.

Import-csv ‘C:\temp\aliases.csv’
foreach{
Set-Mailbox $_.Mailbox -EmailAddresses @{add=”$_.NewEmailAddress”}
}

Please share and Like if it helps you or Reply in comment if something issue missing.

26
Oct

How do I access a shared mailbox via Outlook Web Access (OWA/Webmail)?

Method 1

  1. Go to https://outlook.office.com/mail/username@domain.com, where username@domain.com is the username or email address of the account you wish to access

  2. Login with your own credentials.

Method 2

  1. Login to Outlook Web App.
  2. Select your name in the top right corner then select Open another Mailbox. See below screenshot:
Steps to Open Shared mailbox

3. Enter the name, username or email address of the mailbox you want to access, select the account from the list provided and select Open. (as below screenshot)

12
May

Correction in Google+ DOB restricted for admins

Google+ date of birth correction option removed from the admin console. The admins are restricted to correct DOB of the suspended user due to a wrong update of DOB in Google+ by a user.

Day by day Google has improved visual for users and admins to work smoother on Google platform. But sometimes its very annoying when Google deprecates any important feature because of the new interface.

Recently, Google has introduced a new way of viewing user account in the admin console but there are many things are missing from the new interface. Google internal Engineering ticket that explains this behavior and discloses that the new UI doesn’t support at this moment the Age-rename.

It is impossible to correct the DOB of any user from admin console as there is an option available. Let see what was the issue, why it happened and how it was resolved and how now we can resolve this.

Issue Description:
Some user has reported that they are no longer accessible to the mailbox as the mailbox has been disabled. Users did some changes in Google+ profile while they create a new profile or edit old profile. After saving settings suddenly they no longer able to access the mailbox.

Cause: Why users are not able to access mailboxes.
The account only locked via Google+ profile if the users have put their age below 13 years. And as per the Google standards, the person not allowed to use Google services if they are below 13 years. There are many reasons user have put the wrong DOB.

Like, Users put the wrong DOB unintentionally by mistake, In a hurry and thought they can change it next time, You colleague put the wrong DOB if you forget to lock your system, there are many reasons. Even, as the warning message, the account will be deleted in 30 days if the DOB will not be corrected by the user. Refer below screenshot.

Solution:
In old interface there was an option to reset the user’s google DOB from admin console admin console>User’s profile> account>Google+ profile> Correct DOB. The admins were able to correct the DOB to get the account active instantly.

But, now in the new interface, there is no option like that and admin can not correct the DOB or any user. The Google’s proposed solution is not as per the business standards and user-friendly

As per Google Article below is the option to recover the user’s account.

If you use an account through your work, school, or another group, you should go to myaccount.google.com in order to re-enable your account. We currently offer two ways to confirm your age:

  1. Uploading an electronic copy of your current, government-issued ID showing your date of birth, or
  2. Performing a small transaction ($0.30 USD) on a valid credit card.

Continue reading

17
May

Microsoft fix for Wannacrypt Ransomware

Protect yourself from “Wannacrypt Ransomware”. You are affected or not by the recent cyber attack but you should ready to deal with this kind of situation, Below is the list of windows patches released by Microsoft.

  1. Windows XP SP3http://download.windowsupdate.com/d/csa/csa/secu/2017/02/windowsxp-kb4012598-x86-custom-enu_eceb7d5023bbb23c0dc633e46b9c2f14fa6ee9dd.exe
  2. Windows Vista x86http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.0-kb4012598-x86_13e9b3d77ba5599764c296075a796c16a85c745c.msu
  3. Windows Vista x64
    http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.0-kb4012598-x64_6a186ba2b2b98b2144b50f88baf33a5fa53b5d76.msu
  4. Windows 7 x64
    http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.1-kb4012212-x64_2decefaa02e2058dcd965702509a992d8c4e92b3.msu
  5. Windows 7 x86
    http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.1-kb4012212-x86_6bb04d3971bb58ae4bac44219e7169812914df3f.msu
  6. Windows 8
    http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/05/windows8-rt-kb4012598-x64_f05841d2e94197c2dca4457f1b895e8f632b7f8e.msu
  7. Windows 8.1
    http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/02/windows8.1-kb4012213-x64_5b24b9ca5a123a844ed793e0f2be974148520349.msu
  8.  Windows 10
    http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/03/windows10.0-kb4012606-x64_e805b81ee08c3bb0a8ab2c5ce6be5b35127f8773.msu
  9. Windows 2003 x86
    http://download.windowsupdate.com/c/csa/csa/secu/2017/02/windowsserver2003-kb4012598-x86-custom-enu_f617caf6e7ee6f43abe4b386cb1d26b3318693cf.exe
  10. Windows 2003 x64
    http://download.windowsupdate.com/d/csa/csa/secu/2017/02/windowsserver2003-kb4012598-x64-custom-enu_f24d8723f246145524b9030e4752c96430981211.exe
  11. Windows 2008
    http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.0-kb4012598-x64_6a186ba2b2b98b2144b50f88baf33a5fa53b5d76.msu
  12. Windows 2008R2
    http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows6.1-kb4012212-x64_2decefaa02e2058dcd965702509a992d8c4e92b3.msu
  13. Windows 2012
    http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/02/windows8-rt-kb4012214-x64_b14951d29cb4fd880948f5204d54721e64c9942b.msu
  14. Windows 2012R2
    http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/02/windows8.1-kb4012213-x64_5b24b9ca5a123a844ed793e0f2be974148520349.msu
  15. Windows 2016
    http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/03/windows10.0-kb4013429-x64_ddc8596f88577ab739cade1d365956a74598e710.msu

 

15
May

“WannaCrypt” Ransmware Attack

“WannaCrypt” Ransomeware, What it is and how it does work?

After a big cyber attack by the hacker on Friday 12 May, 2017 in the form of “WannaCrypt” Ransomeware”. The attacker might have come back soon after making some changes in the code. According to Microsoft, they released a patch on 15 March 2017 to protect their customer from this “WannaCrypt” Ransmware” after United States reported earlier about the stolen of the code from the National Security Agency, or NSA. So basically, it is not a virus it’s a data encrypting/decrypting software.

First, this attack covers the United Kingdom and Spain, then malicious “WannaCrypt” software attack globally, blocking users to access their data and demand to pay a ransom using Bitcoin. Attackers demanding $300 dollar to decrypt your data but interestingly there is not guaranty that they will be able to decrypt your data. This kind of code which is currently used by many companies in many forms to protect their data while sending from one place to another over the internet. Let see How this work.

Let say you have some important data that you want to send to you colleague, the with help of encryption software you can encrypt your data and send via mail, if anybody get you data by phishing hacking then they won’t be able to read file because of the encryption but you colleague can because he has the decryption on their system. There number of software available (you can google it) to encrypt your data.

According to the experts, nobody should pay to them for decrypting the data as result it encourages them to do it again but a slight change in code and as you contacted them earlier, hence you would be the soft target for them to hit you again. There are also strong chances that the attackers do have code to decrypt data as the stole code from the NSA United States and paying will give you nothing.

There are high chances that you receive “WannaCrypt” Ransomware (code) via mail and after downloading it will ask you to give access to your file and when you grant the access, it will encrypt you hard drive data in seconds. So, you need to keep below points in mind to avoid this attack.

  1. Try to use less internet for some days, use it when you really need it.
  2. Do to click any link in the mail which is not familiar to you, call/chat your buddy and ask if he/she really send that mail or not.
  3. Do download free software’s and cracks, especially cracks which you should never user as they are completely virus.
  4. Turn on your windows update or install the update manually from Microsoft website here.
  5. Do not accept any authentication for any file you downloaded from the internet and from email. Keep check the URL while downloading any document, the URL should be trusted, provider.
  6. Install good antivirus, it always helps you to protect unwanted virus and online attacks.

Google and Microsoft world top leading companies of email provider are trying to keep their customer safe, to get these mail delivered.The “WannaCrypt” Ransomware mostly reach to the user via mail but users should keep this in mind that most important percussion is to patch your window and do not download anything from the internet/mail to your system.

17
Apr

Gsuite account does not sync due to Mobile Device policy (android devices)

Mobile device Sync issue

Issue: Mobile device does not sync with Gsuit account if the user has update mobile device OS to Android 7 (Nougat) and mobile device policy has enabled for your domain.

Solution: Becuase of the new feature in android 7 where the user must have enabled mobile device startup password and as per the mobile device policies of Gsuite user account it must. this is done because of security reasons.

Users need to enable the secure startup option to require a password to start the device to re-enable the G Suite account sync. This setting requires the lock screen password to be entered before the phone powers on, and is also known as ‘require a password to start device’.

– Open the Settings app
– Select ‘Lock Screen and Security’, then ‘Secure startup’
– Choose ‘Require password when device powers on’ and then OK

Once this setting is enabled, opening the Device Policy app and touching ‘Sync Now’ will re-enable G Suite data synchronization.