Tag Archives: microsoft

Grep-ing in Microsoft windows powershell

How you find all maiboxes which starts with a certain string in tons of mailboxes in your Office 365 (Microsoft Exchange Server)? In Linux is quite simple... you use grep, but how about Microsoft Windows Powershell?

You have to remember the findstr command:

[codesyntax lang="powershell"]

PS C:\> findstr /?
Searches for strings in files.

FINDSTR [/B] [/E] [/L] [/R] [/S] [/I] [/X] [/V] [/N] [/M] [/O] [/P] [/F:file]
        [/C:string] [/G:file] [/D:dir list] [/A:color attributes] [/OFF[LINE]]
        strings [[drive:][path]filename[ ...]]

  /B         Matches pattern if at the beginning of a line.
  /E         Matches pattern if at the end of a line.
  /L         Uses search strings literally.
  /R         Uses search strings as regular expressions.
  /S         Searches for matching files in the current directory and all
             subdirectories.
  /I         Specifies that the search is not to be case-sensitive.
  /X         Prints lines that match exactly.
  /V         Prints only lines that do not contain a match.
  /N         Prints the line number before each line that matches.
  /M         Prints only the filename if a file contains a match.
  /O         Prints character offset before each matching line.
  /P         Skip files with non-printable characters.
  /OFF[LINE] Do not skip files with offline attribute set.
  /A:attr    Specifies color attribute with two hex digits. See "color /?"
  /F:file    Reads file list from the specified file(/ stands for console).
  /C:string  Uses specified string as a literal search string.
  /G:file    Gets search strings from the specified file(/ stands for console).
  /D:dir     Search a semicolon delimited list of directories
  strings    Text to be searched for.
  [drive:][path]filename
             Specifies a file or files to search.

Use spaces to separate multiple search strings unless the argument is prefixed
with /C.  For example, 'FINDSTR "hello there" x.y' searches for "hello" or
"there" in file x.y.  'FINDSTR /C:"hello there" x.y' searches for
"hello there" in file x.y.

Regular expression quick reference:
  .        Wildcard: any character
  *        Repeat: zero or more occurrences of previous character or class
  ^        Line position: beginning of line
  $        Line position: end of line
  [class]  Character class: any one character in set
  [^class] Inverse class: any one character not in set
  [x-y]    Range: any characters within the specified range
  \x       Escape: literal use of metacharacter x
  \<xyz    Word position: beginning of word
  xyz\>    Word position: end of word

For full information on FINDSTR regular expressions refer to the online Command
Reference.
PS C:\>

[/codesyntax]

That being said, here is an example:

[codesyntax lang="powershell"]

PS C:\> Get-Mailbox | findstr test
test                      test                 amspr06mb197     49.5 GB (53,150,220,288 bytes)
PS C:\>

[/codesyntax]

 

How to create an organization calendar in Office 365

Recently I migrated company's email to Microsoft Office 365. Because I haven't worked before with Office 365 the process wasn't so easy as I expected initially, but after passing all challenges, I got it done. Next challenge was to create a company calendar so every user can use it. There are few posts on the web that teaches you how to accomplish this task, but none of them was complete as I intend this post to be.

Note: You will need a Windows machine... (I know this sucks, but there is nothing you can do about this).

Well, let's get to work.

First thing to do is to download someĀ  packages that we will going to use to get this task done!

1. Connect to Office 365

2. Create a new mailbox called "Organization Calendar" (you can choose whatever name you like, of course):
[codesyntax lang="powershell"]

New-Mailbox -Name "Organization Calendar" -Alias OrganizationCalendar -Shared
Add-MailboxFolderPermission OrganizationCalendar@organization.com:\Calendar -User user@organization.com -AccessRights Author

[/codesyntax]

3. Go to the Calendar view

01. Calendar view

4. Right click on OTHER CALENDARS and choose open calendar

02. Open the Organization Calendar

5. In the From Directory field search for Organization Calendar created above and click Open.

03. Open the Organization Calendar

That's it!

Migrate your IMAP account to Microsoft Office 365

What will you do if your organization decided to move email, calendar and so on into the cloud and they choose Microsoft Office 365 and your task is to move all emails from your current server into cloud. How do you do to complete this task? First of all you search on the web (as I did) and you will find that there are some tools and documents. For me choosing a tool was the difficult part, but at the end I decided that imapsync is the best tool for this kind of tasks.

Ok, let's finish this small talk and let's get to work.

1. Get imapsync

[codesyntax lang="bash"]

git clone https://github.com/imapsync/imapsync

[/codesyntax]

2. Installing required packages

[codesyntax lang="bash"]

apt-get install libmail-imapclient-perl libterm-readkey-perl

[/codesyntax]

3. Checking dependencies

[codesyntax lang="bash"]

cd imapsync
perl -c imapsync

[/codesyntax]

And if nothing is missing then you will see a message like this:

imapsync syntax OK

4. Create the password files

[codesyntax lang="bash"]

echo "secret_password1" > ~/secret1
echo "secret_password2" > ~/secret2
chmod 600 ~/secret1
chmod 600 ~/secret2

[/codesyntax]

5. Do the migration

[codesyntax lang="bash"]

./imapsync --nocheckmessageexists --syncinternaldates --usecache --useuid --host1 example.com --user1 "user@example.com" --passfile ~/secret1 --ssl1 --host2 pod51011.outlook.com --user2 'user@example.com' --passfile ~/secret2 --ssl2

[/codesyntax]

example.com - is the host from where you want to pull the mails
pod51011.outlook.com - is the microsoft server where you want to push the mails

Note: if you already executed the above command before then you should use --maxage n parameter so imapsync to check and pull and push only mail no more older than n days