Sims and other MIS Timetables into Exchange and Office 365 Calendars

Using the timetable data from your MIS, whether it is Sims, Progresso, Facility CMIS, iSAMS or any other MIS, Salamander Active Directory can update staff and pupils’ Exchange calendars with their timetable. These calendars are updated each time Salamander runs, allowing the calendars to remain up to date with any changes to an individual’s timetable. This works with any version of Exchange both on premise in the school, or Exchange Online including Office 365.

This example is for a staff member so the subject is configured to be the name of the teaching group as a staff member will likely teach multiple classes for the same subject. For pupils it would usually be configured as the subject name as they typically only have one teaching group for each subject.



An example of an event.



Appointment Categorisation


Events can be categorised to suit your needs. Here we have events which are categorised by Subject, but this could equally be the Year of the group or the Room.


Cover Timetables

The cover timetables can also be synchronised, allowing users to easily see what cover has been assigned to them day to day.

Other Timetables


Salamander Active Directory can also synchronize other types of timetables from Sims and other MIS including:

· Sims Diary

· Room timetables

· Class timetables

· Sims Homework

· Behaviour timetable

· Exam timetable

Read More

Exchange 2010 Management Console Error – Initialization Failed

Today I had a strange error when trying to connect to a remote Exchange 2010 using the Exchange Management Console.


The text of the error is:

Initialization failed.

The following error occurred while configuring Help links:

The operation couldn’t be completed because a change occurred in the remote forest.

Please complete any operations that are in progress, restart the Exchange Management Console, and follow the help instructions to obtain a compatible upgrade.

Needless to say, neither clicking here to retry or restarting the console helped.

It turned out that the version of the management console on this machine was different to the server version. If you manually connect to Exchange you get the correct message. To manually connect:

  1. Right Click on Microsoft Exchange in the left pane and select Add Exchange Forest.AddForest
  2. Type in the name of your Exchange server and click OK. You’ll probably need to give your login details.ForestName
  3. The new forest, with the friendly name given in step 2, will now appear in the left pane. Now click on this and you will get the real error.
  4. ExchangeAfter

Here you can see that the server is on Update Rollup 2 for Exchange Server 2010 SP1 while the client machine is on Microsoft Exchange Server 2010 SP1.

There’s a list of Exchange version numbers on TechNet.

Read More