What you need to do to enable Mailguard Filtering and Officemailguard 365

Login to 365 Portal 

Inbound Filter by IP

This forces all internal mail to only be accepted by 365 from Mailguard IP’s. Spammers start caching DNS records so even though you changed MX records they use old ones!

  • Exchange Administration 
  • Mailflow
  • Connectors

From Partner Organization
To Office 365
How do you want to identify the partner organization? Domain
Specify one or more sender domains: *
Reject email messages if they aren’t sent from within this IP address range ( IP Range from Mailguard )

Outbound Filter forcing SMTP relay

Make sure all Office 365 IP’s http://pastebin.com/6UZZcWPQ are in trusted networks

  • Exchange Administration 
  • Mailflow
  • Connectors

Only when I have a transport rule set up that redirects messages to this connector – Tick
Route email through these smart hosts : filter.riskca-1.mailguard.com.au
Always use Transport Layer Security (TLS) to secure the connection (recommended)

  • Exchange Administration 
  • Mailflow
  • Rules

Name : Relay Outbound through MailGuard
*Apply this rule if… – The Sender is Located … Inside the organization
*Do the following… : Use the following connector Name of Connector Above


Add this include to the TXT record for the outgoing domains


GD Star Rating
GD Star Rating

We can suggest some steps, which may help. Please stop Orion Collector Service and run following query on the Database Manager:

DELETE FROM VIM_SnapshotDiskFileMapping

Start Orion Collector Service. Operation is safe and customer won’t loose any data (next poll will fill tables with correct data)

GD Star Rating
GD Star Rating

veeam_box_ONE[1]After installing Veeam One , login to Veeam One Business View worked , however Veeam One Reporter with the same login details came back with 

The specified username or password is not correct. Provide new credentials and try again.

After Checking the C:\Program Files\Common Files\Veeam\Veeam ONE Settings\VeeamOneSettings.exe and what the service was started as these where all correct.

I was using firefox to login , so I tried with Internet Explorer with the same details and it worked straight away!

***Update if this still doesn’t work

Log onto the server where Veeam ONE is installed.

Open Local Users and groups, ensure that the user in question is added only to the Veeam ONE administrators group.

Log off then log back on and attempt opening the monitor console.



GD Star Rating
GD Star Rating

postgresql_1[1]Unzip your backup dir somewhere convenient where you have full read/write permission as your normal user account.

Assuming that the c:\users\myusername\desktop\postgresql folder contains the folders named bin, data, lib, etc:
Open a cmd shell
cd C:\ManageEngine\OpsManager\postgresql
bin\pg_ctl start -D C:\ManageEngine\OpsManager\postgresql\data
psql -U postgres -h127.0.0.1 -p13306 OpManagerDB
#for other Postgres DB you might not need to list the port/ip ( no -h -p )

If psql connects OK disconnect with the \q command then promptly make a dump of the database:
bin\pg_dump -Fc -U postgres -h127.0.0.1 -p13306 OpManagerDB -f mydb.dbbackup mydb


GD Star Rating
GD Star Rating

clip_image0024[1]When provisioning a new VMware host important things to configure

1) NTP Server
2) IP of Management with DNS Name
3) Portgroup Names
4) Syslog Server
5) SNMP Trap for monitoring
6) Renaming Local Datastore to something with the server name other than datastore1
7) Nic Teaming

Another thing that is also important to setup is the pass selection policy. Depending on the SAN Manufacturer they will tell you the recommended policy e.g. https://vstorage.wordpress.com/2013/03/28/optimising-vsphere-path-selection-for-nimble-storage/

1) Fixed
2) Round Robin
3) Recently used

Most of the time it will be Round Robin

This can be changed via Command Line

esxcli storage nmp satp set -s VMW_SATP_ALUA -P VMW_PSP_RR

or through the VMWare Client

Go to Configuration Tab on Host , go to Storage , Go to Properties of Datastore and click Manage Paths

When changed make sure no VM’s are on the host as this could disrupt them

GD Star Rating
GD Star Rating
The benefits of this upgrade for the client are as follows:
·         Performance improvements in vCenter Server and vSphere Web Client http://www.vmware.com/files/pdf/techpaper/Whats-New-Perf-vSphere6.pdf
·         Better support of Microsoft Clustering (including vMotion of clustered VMs)http://kb.vmware.com/kb/1037959
·         Different security enhancements (host security, certificate management through centralized CA, etc.)https://www.vmware.com/files/pdf/vsphere/VMW-WP-vSPHR-Whats-New-6-0-PLTFRM.pdf
I would also highly recommend considering Enterprise Plus edition of vSphere for the client in the future, as it brings features that can further standardize and automate the system as follows:
·         Storage I/O control (SIOC) and IOPS reservationhttps://blogs.vmware.com/vsphere/2015/07/sioc-io-distribution-with-reservations-limits-part1.html
·         Cross-vCenter vMotion and Long Distance vMotionhttps://www.vmware.com/files/pdf/vsphere/VMW-WP-vSPHR-Whats-New-6-0-PLTFRM.pdf.
The process of upgrading to vSphere 6.0 consists of the following subsequent steps:
1.       Upgrading vCenter Server (3 days):
a.       Preparing vCenter 5.5 for upgrade
b.      Upgrading vSphere and vCenter licenses (requires access to the MyVMware portal)
c.       Migrating from SSO to PSC
d.      Upgrading vCenter
e.      Upgrading vSphere Update Manager
f.        Testing the new vCenter
2.       Installing ESXi on new hosts (3 days):
a.       Checking / configuring remote access to the servers (iLO)
b.      Updating firmware and BIOS to the latest versions
c.       Setting up the BIOS settings on the hosts
d.      Preparing image for auto-installation
e.      Performing installation
f.        Configuring the management network
3.       Configuring the hosts (2 days):
a.       Configuring networking on the hosts (best practices!)
b.      Configuring hosts for storage and attaching datastores (best practices!)
c.       Migrating VMs
4.       Upgrading VMs (work time depends on the company’s policy for the planned system outages):
a.       Scheduling VMware Tools upgrade
b.      Scheduling VM hardware upgrade
c.       Optimizing VMs according to the running applications and the best practices.
GD Star Rating
GD Star Rating

Recently we had a task to update all the Finished folders in Olympus to remove old items old than 2 months. I tried to use the Group function of this software to deploy the settings however they weren’t taking. Instead of editing the individual users I wrote the following powershell to Edit each users XML configuration

$Files = Get-ChildItem \folderlocation
ForEach($file in $files) {
$xml = [pastacode provider="manual" lang="markup" manual=""](Get-Content $file.FullName)
$xml2 = $xml.Profile.TranscriptionInformation.FolderDesign.FolderList.Folder | Where-Object { $_.parent -eq '101' -and $_.type -eq '115'}
$xml2.Actions.Cleaning.fixed = [io.path]::GetFileNameWithoutExtension($file.Name)
$xml2.Actions.Cleaning.Enabled = '1'
$xml2.Actions.Cleaning.Period = '2'
$xml2.Actions.Cleaning.Unit = '1'
$xml2.Actions.Cleaning.Option = '2'
GD Star Rating
GD Star Rating

2014-06-17_16h26_59[1]Recently during a Veeam backup HA kicked in due to a problem with VCenter and marked two machines as Invalid

  •  Veeam started backup and created snapshot on affected VMs
  • HA kicked in after VCenter Server failure
  • Vcenter tried to move the machines after the HA event but they were locked by the snapshot Veeam had (the hypervisor has a lock because of the snapshot)
  • Machine couldn’t move but Vmware removed them from inventory and tried to register them to another host, without success
  • Machines marked as Invalid, Removing machines from Inventory and registering the machines manually did not work
  • The machines are locked however still powered on and response

Fix to get VM’s registered on VCenter

  • Stop any tasks (i.e. Veeam) that might trigger a snapshot on affected machines
  • Temporarily disable DRS in the cluster (when we power up the machine we don’t want Vsphere to power it up on another host otherwise the lock will persists)
  • Power affected VMs off gracefully from within the OS.
  • Login to vcenter and select Host which failed and . Unregister “unkown” VM’s listed (these should be the actual Vms). Unregistering should remove the lock.
  • Register the virtual machines using the vmx files in the datastore
  • Check no snapshots are present, if yes delete or consolidate
  • Power on Vm
  • Re-enable DRS
GD Star Rating
GD Star Rating