Use Anonymous Hacker Email With Correct Data Encryption!

Mobile Phone cartoon

In light of recent Internet events that confirm the increasing risk of user data leakage, there is a need for reliable and anonymous services. These services can provide each person with a high guarantee of security and confidentiality of any data transmitted via email. But how do you choose a service that is completely secret … Read more

Exchange 2007 – Change a Shared Mailbox to User Mailbox

5d05eb33135798a962e3199db1fa4a4c

You may have seen our previous post about changing a user mailbox into a shared mailbox in Exchange – but what if you want to do it the other way around and change a shared mailbox into a user mailbox? Well, see below….

There is a simple PowerShell command that you can run within Exchange Management Shell (EMS) to carry this out.

Just open up EMS and use this command:

Set-Mailbox “shared mailbox name” -Type:Regular

where

  • “share mailbox name” – is the name of the user mailbox you want to change to a shared mailbox

Then if you go back into your Exchange Management Console, you should see that this is now a user mailbox.

Feedback

If you have any questions or comments on this post, please feel free to leave us a message below using our comments system.

Mimecast Client for Outlook Version 6 Released

mimecast

Mimecast Logo in blue and greyMimecast have now released version 6 of their Outlook Client. You can download the x64 and x86 versions of the client as well as the editor program from the link below:

Mimecast Client for Outlook Version 6 Released 1

New features

  • Support for Microsoft Click-To-Run installations
  • Support for Office 365 Outlook ProPlus
  • Support for Windows 10 Technical Preview
  • Mimecast for Outlook now uses the main Mimecast API
  • Support for 2-Step Authentication (Coming soon)
  • Support for Revoke Authentication (Coming soon)

Enhancements

  • Log files will now be appended should the service restart unexpectedly
  • Cursor is now automatically focused on the Text field when Search views are opened
  • Support for message sensitivity during Continuity
  • Large File Send messages can now be extended up to the full remaining retention period of the message

Fixes from previous releases

  • Embedded images in the body of a Large File Send email were shown as attachments
  • Calendar appointments were sometimes being de-duplicated incorrectly
  • Improvements to primary mailbox detection
  • Improvements to installation with various Outlook language packs
  • Support for ‘Send As’ with Secure Messaging
  • Resolved an issue relating to permissions when attaching large files from network locations
  • Various performance improvements.

Mimecast Outlook Client 5.4.1263.13520 Released

mimecast

Mimecast Outlook Client 5.4.1263.13520 Released 2Mimecast have now released version 5.4.1263.13520 of their Outlook Client.

This version of the MSO client now supports the following:

  • Support for the new Australian grid
  • Fixes from previous releases
  • Fixed an issue when replying to a message where the address was formatted as “”Smith, Sarah’ (ssmith@domain.com)'”.
  • Fixed an issue where Archive Folders other than those of the primary mailbox were displayed.
We have tested this version with Outlook being open during the install and although we do not recommend doing this, it does seem to work so long as you restart Outlook at some point to enable the new version to load.

To push this out using SCCM or Group Policy, we recommend using the MSI command below:

msiexec.exe /i “MSOInstall.msi” /qb /norestart

What this will do is to firstly run the installer, then the /qb will show a basic user interface without user interaction, but will stop and show the error if, for example, Outlook is still open. The /norestart is fairly simple – this will ensure that your client machine does not automatically restart itself.

To download the latest version 5.4.1263.13520 of the MSO client, you can click the link below:

DOWNLOAD

Mimecast Outlook Client 5.4.1263.13520 Released 3

COMMENTS

If you have any comments on this new release, please use our comments system below.

Shared Mailboxes Sent Items in Outlook

outlook blue logo

If you are using shared mailboxes in Outlook, then you may find that when someone is sending an email from this mailbox, the sent email is going into the users own Sent Items folder rather than the Sent Items folder within the shared mailbox itself.

This is because there is a delegation registry key that needs to be set to allow the sent email to drop into the shared mailbox.

Considerations

Please note the part of the registry key that is in bold and red “14.0” – this is the version of Outlook that you are using and must be changed for your version.

The different versions of Outlook are:

  • Outlook 2007 – 12.0
  • Outlook 2010 – 14.0
  • Outlook 2013 – 15.0
  • Outlook 2016 – 16.0

Also note that this must be done logged in as the affected user that you want to amend.

Instructions

To do this, simply follow the instructions below:

  • Click Start
  • Click Run
  • Type regedit, and then click OK
  • Locate and then click the following registry subkey:
  • HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Preferences
  • On the Edit menu, point to New, and then click DWORD Value
  • Type DelegateSentItemsStyle, and then press Enter
  • Right-click DelegateSentItemsStyle, and then click Modify
  • In the Value data box, type 1, and then click OK
  • Exit Registry Editor and reboot the machine

Once you have rebooted the machine you should then test sending an email from the shared mailbox and you should now see that the email has gone into the correct folder within the shared mailbox itself.

Feedback

If you have any questions or comments on this, please feel free to use our comments system below.

Outlook Email Signatures Backup and Migration

outlook blue logo

We have recently had to rebuild a number of machines and the main issue that our users bring up is the fact that our first line techs keep forgetting to put users Outlook email signatures back. This, infuriates end users nearly as much as not putting back their 500 desktop shortcuts.

Now, we – as Configuration Manager experts, know that they should be using USMT for such tasks but this does not always happen and sometimes is not always the best course of action depending on the reasons behind the need to rebuild a machine. So how can you quickly and easily backup and restore the users email signatures?

First of all, you have to remember to take a copy of them before the machine is formatted, if you don’t, only tools like GetDataBack can help you now! You should go to the following location:

%APPDATA%\Microsoft\Signatures

In there are all the HTML, RTF and TXT files that you need to copy – ensure that you copy everything within that folder including any sub folders.

Then you can go ahead and rebuild the machine once you are happy that you have a copy on the network or on an external storage device.

Once the machine is rebuilt, ensure that you have created the users Outlook profile first, then you simply go back to the location as stated above and copy and paste the files and folders back into the location where they once came from.

Now, fire up Outlook and you should notice that the users signatures are now there for them to carry on using.

Comments

If you have any questions about the above guide, please feel free to leave a comment and we will try to get back to you as soon as possible.

Mimecast MSO Fix – SMTP in the Credentials Error

mimecast

If you are a Mimecast user and are also using Windows 8.1, you may find that when you have installed the Mimecast client for Outlook (MSO) and try to enter your domain or cloud credentials, the username has SMTP set and cannot be changed and the password part is greyed out. You will then receive the usual error message at the bottom right:

Mimecast MSO Fix - SMTP in the Credentials Error 4

There is a very simple reason for this – Mimecast do not currently support Windows 8.1!

However, there is a fix that you can try, we have test it on Windows 8.1 Enterprise x64 with Office 2013 x64 and it seems to work – we have not tested it on any other setups so you try this purely at your own risk!

Instructions

You need to delete a single registry key on the affected machine. The registry key that you should delete this this one:

HKEY_CLASSES_ROOT\Installer\Products\D8D51FC95CB504D45AB209F36D065B9F

Once you have deleted this registry key, reboot your machine, start up Outlook and see if it has made a difference.

We have also designed a MSI for this fix to distribute to larger amount of machines using ConfigMgr, WDS or Group Policy. You can download this MSI from the link below.

Download

Download Mimecast MSO Fix

If you get an error stating that the install has failed like the one below – then the machine you are running the MSI on does not have the stated registry key on it.

Mimecast MSO Fix - SMTP in the Credentials Error 5

As I’ve stated above, this is not tested on various operating systems and Office versions so you try this at your own risk – however, if you try it and it works, we would like to hear from you as to what setup you have so that we can build up a list of setups that this works with.

Leave a comment below or you use our Help section by pressing the button on the menu bar above and send us an email.

Screenshots

Mimecast MSO Fix - SMTP in the Credentials Error 6