Sunday, August 7, 2016

Acrobat Reader 11: Fix “There was an error opening this document ..

An error may appear that says “There was an error opening this document. Access denied.”
  1. From Acrobat Reader, select “Edit” > “Preferences“.
  2. Select “Security (Enhanced)” on the left pane.
  3. Uncheck the “Enable Protected Mode at startup” box.
  4. Select “Yes” to the prompt about being sure about making this change.
  5. Click “OK“.

Saturday, August 6, 2016

Group Policy Error: "The RPC server is unavailable."

RPC uses port 135.
  • Open the Group Policy Object Editor snap-in to edit the Group Policy object (GPO) that is used to manage Windows Firewall settings in your organization
  • Open Computer Configuration, open Administrative Templates, open Network, open Network Connections, open Windows Firewall, and then open Domain Profile.
  • In the details pane, double-click Windows Firewall: Allow remote administration exception.
  • In the Windows Firewall: Allow remote administration exception properties dialog box, on the Settings tab, click Enabled or Disabled

http://technet.microsoft.com/en-us/library/cc738900(v=ws.10).aspx

How to configure GFI Archiver to work with Microsoft Office 365

GFI Archiver can be configured to work with a Microsoft Office 365 environment.

This article lists basic steps required to setup Office 365 and GFI Archiver from a high level point of view. For more detailed steps, please refer to the GFI Archiver and Office 365 Deployment Guide.

Setup 1: Setting up Microsoft Office 365 and GFI Archiver integration

Step 1 - Set up a mailbox
Set up a journaling mailbox in Microsoft Office 365. This mailbox will collect a copy of all emails exchanged between your users.

Step 2 - Create Forwarding rule Create a Forwarding / BCC rule in Microsoft Office 365. By creating this rule, you make sure that a copy of every email sent by your users is copied to the journaling mailbox that was set up in Step 1.

Step 3 - Identify server connection information
In Microsoft Office 365, locate the connection settings and take a note of them. These settings are required by GFI Archiver for Exchange Online setup.

Step 4 - Verify directory service details
Verify that directory service details are set up correctly according to the following article: http://go.gfi.com/?pageid=mar_directoryservicesettings

Step 5 - Configure GFI Archiver
Configure a new Mail server to archive with EWS connection in GFI Archiver. Here you specify the connection settings identified in Step 3.

Step 6 - Test your setup
Test the integration of GFI Archiver with Microsoft Office 365.

Setup 2: Setting up Microsoft Office 365 and GFI Archiver integration using a 3rd Party Journaling Mailbox

Step 1 - Setting up a 3rd Party Journaling Mailbox
Set up a 3rd party email account as a Journaling Mailbox in Microsoft Office 365. All emails exchanged between your users will be forwarded to this mailbox.

Step 2 - Configuring Forwarding Rule for an External Mailbox
Create a journaling rule in Exchange Online that will forward a copy of all emails to the 3rd party journaling mailbox configured in Step 1.

Step 3 - Verify directory service details
Verify that directory service details are set up correctly according to the following article: http://go.gfi.com/?pageid=mar_directoryservicesettings

Step 4 - Configuring a new Mail Server to Archive using an external mailbox Configure a new Mail server to archive in GFI Archiver. Using this connection, GFI Archiver will archive any emails forwarded to the external journal mailbox.

Step 5 - Testing setup
Test the integration of GFI Archiver with Microsoft Office 365.     

Azure AD Connect 1.1: Forcing a Synchronization

When a new Azure Active Directory synchronization tool or a new version of an existing tool is released, there´s also a good chance the synchronization interval scheduling method changes, which again means that the way in which force a synchronization changes as well.

Guess what? This is no different for the recently released version 1.1 of the Azure AD Connect (AAD Connect) tool, which by the way brings several significant changes and improvement with it as you can read in the blog post, I link to.

With AAD Connect 1.1, we no longer have a Windows scheduled task running every 3 hour. Now the tool has a built-in scheduler, which by default performs a delta sync every 30 minutes. You can change this interval schedule, however bear in mind that 30 minutes is the lowest interval supported.

Although a synchronization now runs every 30 minutes, there may be occasions, where you still want to force a sync. To do so, you launch Windows PowerShell on the respective server on which AAD Connect has been installed and type the following to import the AAD Connect PowerShell module:

Import-Module ADSync

You check the current settings for the new scheduler, you can use the new Get-ADSyncScheduler as shown below.



To force a delta sync, you the following PowerShell command:

Start-ADSyncSyncCycle -PolicyType Delta



If you want to force an initial (full) sync, use this command:

Start-ADSyncSyncCycle -PolicyType Initial