Testing Vagrant Azure provider

Last weekend I tried Vagrant-Azure, it is still a little bit unstable.
First of all, I did some tests with Vagrant and Virtualbox on Windows, following this URL, in this first test everything went fine, no problems.

Later, I wanted to use a Azure as provider and I had to install Vagrant-Azure Plugin https://github.com/MSOpenTech/Vagrant-Azure

VPN from CISCO ASA 5530 8.3(2) to Azure resets every 1 minute

We are working in a hybrid cloud solution, the first step is setting up the communications between our on premise servers and Azure.

We have at least one dozen of different network ranges in on premise network behind the ASA. 

We started the communication between on premise and Azure with one full /24 network and it worked fine, no problems at this point. So we added an extra HOST of different network and the problems began, we saw these messages in the ASA device log:

Lessons learned with a migration to Office 365

Today we are going to write about Office 365 and the recent migration of one of our clients.

Scenario:

• The client want to migrate their mailboxes from on premise Exchange servers to Office 365
• The client requieres password synchronisation (just an active directory sync, not federation or SSO)
• The client has Exchange 2003 and Office 2007
• The Exchange 2003 in our client's implementation is not standard
• The client wants a gradual migration to have time window to deploy Office 2013 on their computers in multiple stages.

Limit bandwidth between on premise and Azure with Cisco ASA

Here is a new recipe. We are working into a new hybrid cloud with Microsoft Azure and our offices. One of the requirements was the limitation of the bandwidth, between on premise servers and services in Azure servers, because we only have a  link of 20Mbps and this link has to provide access to clients and to our infrastructures in Azure. So we decided to limit the bandwidth to 8Mbps, between both sites. Here is the configuration example.

SCOM 2012 SP1 UR5 Failed

Today we have to update our management server from SCOM 2012 SP1 UR4 to SCOM 2012 SP1 UR5.

We have installed the KB 2904680 in the management server and after rebooting it, the Microsoft System Center Data Access Service started and died ten seconds later, generating the following errors in the event viewer under de Operations Manager log:

Powershell DSC (Desired State Configuration) Summary

Before writing about DSC, I want to recommend a video. Few days ago I saw this video about Visio Powershell, it is really cool how this guy uses Powershell to manage their Visio diagrams, it is a must watch.

Last month was the month of the DSC (Desired State Configuration), there are a lot of posts and discussions about this topic, especially after the Technet America 2014 and I am going to make a little selection of these posts and videos.

Monitoring memory and CPU based on process command line match

The title of this posts looks fairly uncommon, but sometimes it is necessary to monitor some system parameters based on the command's line, for example, it is useful to monitor IIS application pools.

Our client needed this type of monitoring to do reports based on this data, so we did these SCOM RULES based on scripts.

One little notice before we start with the scripts: some people ask us what "Call oAPI.LogScriptEvent" does. The answer is that this call writes an event with number 2000 in the agent machine and it is useful for debugging.

If you don´t know or you don´t remember how to associate a script to SCOM RULE here is an old post talking about this topic.

Here are the scripts, I hope they will be as useful to you as they were to us.