All posts tagged Exchange

Another in our series of Guest posts by Exchange specialists is Glen Knight, aka Demazter. Glen is tackling a tough topic- preparing your environment for a migration- essential for keeping the migration free from additional Costs, Risks and potential Downtime.

Glen Knight is the founder of Demazter IT Services, a UK based IT consulting company which specialises in installation, support and maintenance of secure environments based on VMWare and Microsoft technologies. He has been working in the industry for the past 14 years providing support, installation and consulting services for all sizes of businesses working with all versions of Windows, Microsoft Exchange and Small Business Server, including large scale Active Directory design and maintenance.

Glen also has a blog: http://demazter.wordpress.com and very active in one of the leading technical community sites - Experts-Exchange.

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration.

My first tip Migration Tip #1 – Source Server Health can be found here.

My second tip Migration Tip #2 – The Practice Run can be found here.

So, we now have a healthy source server and you have practiced until the match sticks snap, what next?

My third tip is about making sure you are prepared for the task ahead. Any type of migration needs to be taken seriously, it is a business critical operation you are about to embark on. If you are in any doubt about it at all, now is the time to say so, and if necessary call in help.

If you are happy with the process and confident you are able to complete the steps to achieve your goal then the next thing we need to do is plan a time to do it.

Most migrations are not time limited other than SBS to SBS migrations that have a limit of 21 days where both SBS servers can co-exist at the same time.

Make people aware of what you are doing, involve them, explain that you are expecting to have teething problems but would prefer if they collated them and then passed them to you when you ask for them. The last thing you want is to try trouble shooting whilst trying to complete a migration.

Find out if there is anything business critical happening (a big bid/contract etc that needs to be out just when you take the mail system offline) that could be delayed by the work you are carrying out, and if so, delay your migration. Talk to absolutely every member of staff. Manage Expectations.

In reality, if you get it bang on, the end users shouldn’t even notice and I would say 99% of the migrations I have done this has been the case. But there is always the odd one.

Have a recovery plan, know how to back out of what you are doing if it does go pear shaped. If you need to lock and migrate huge amounts of data then make sure you plan this stage of the migration for when people aren’t going to be using the system as heavily.

Document what you are doing, make notes of which stage you have got to and what action you have just taken.  This might seem like a waste of time, but take it from someone who has picked up a few failed migrations from people, it’s not.  Knowing exactly what stage you are at will help a consultant very quickly get to grips with the situation and this means a faster resolution.

And, most importantly of all, make sure you have backups! Take more than one, take one off-site, and do it different ways. I like to have a backup on either removable storage so I can access it quickly but also on tape just to be sure.

Watch out for tip Migration Tip #4 – The Migration

Add your comment (0)

Cloud Strategist
Mimecast

Article Tags

, , ,

Next in our series of Guest posts by Exchange specialists is Glen Knight, aka Demazter. Glen is tackling a tough topic- preparing your environment for a migration- essential for keeping the migration free from additional Costs, Risks and potential Downtime.

Glen Knight is the founder of Demazter IT Services, a UK based IT consulting company which specialises in installation, support and maintenance of secure environments based on VMWare and Microsoft technologies. He has been working in the industry for the past 14 years providing support, installation and consulting services for all sizes of businesses working with all versions of Windows, Microsoft Exchange and Small Business Server, including large scale Active Directory design and maintenance.

Glen also has a blog: http://demazter.wordpress.com and very active in one of the leading technical community sites - Experts-Exchange.

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration.

My first tip Migration Tip #1 – Source Server Health can be found here.

My second tip is about making sure you are familiar with the technology you are migrating to.

For many people, migrating to a new technology will be the first and only time they perform this task. So, it’s always a good idea to familiarise yourself with the setup process before you do it for real.  With the use of virtualisation technologies we can install and test new products without the need for new hardware and without the possible impact on our live environment.

There are a number of virtualisation products that will allow you to do this on your desktop/laptop computer. You need to consider that most new products (if not all) will be based on x64 bit architecture. This does limit the virtualisation technologies that you can use on the desktop. Some of my favourites are listed below.

  • VMWare Workstation, this is a paid product but worth its weight in gold
  • VMWare Server, this is free for use and technically should only be used on a Server Operating System, but it does work on Desktop OS for testing purposes.
  • Virtual Box

Whichever technology you use, virtualisation will allow you to install the new software in a test environment, and keep installing it until you are happy with the process. Run through it 2, 3 even 4 times. Make sure you are familiar with the screens and what answers you are going to provide to the wizards. Take notes, even write a step-by-step of what you encountered and when you encountered it. Remember, the more you do now when you are in a safe “sandbox” environment, the easier and less pressurised the real thing will be. Don’t pay too much attention to the actual data you are entering as some of this will change when you do a migration as opposed to a new installation.

For the actual Migration Pick a migration guide for your technologies, it’s always best to use one that’s recommended by others and they have had good success with.  You will find my migration guides here. I use my guides in my own migrations and update them with any changes as often as possible.  Read the guide thoroughly before you start the migration.   It’s easier to get answers when you are not under pressure to fix things.

If you have the time and the inclination I would also suggest that you convert your physical source server to a virtual one. This will allow you to do a test migration with your actual source server. There are many tools for performing the capture and they depend on the virtualisation technology you are using and whether you want a free or paid product. Some examples of methods that can be used to convert physical machines to virtual ones can be found here.

Doing a virtual migration with a virtual copy of your actual source server is a great way to identify any problems you may encounter during the real live migration. You then have the opportunity to rectify these issues and then try the migration again. Once you are happy the migration has worked you are then in a position to do the live backup. I would be doing 3 to 4 virtual migrations just to be absolutely sure.

Watch out for tip Migration Tip #3 – Preparing for Live Migration in the next day or two.

Add your comment (0)

Cloud Strategist
Mimecast

Fifth in our series of Guest posts by Exchange specialists is Glen Knight, aka Demazter. Glen is tackling a tough topic- preparing your environment for a migration- essential for keeping the migration free from additional Costs, Risks and potential Downtime.

Glen Knight is the founder of Demazter IT Services, a UK based IT consulting company which specialises in installation, support and maintenance of secure environments based on VMWare and Microsoft technologies. He has been working in the industry for the past 14 years providing support, installation and consulting services for all sizes of businesses working with all versions of Windows, Microsoft Exchange and Small Business Server, including large scale Active Directory design and maintenance.

Glen also has a blog: http://demazter.wordpress.com and very active in one of the leading technical community sites - Experts-Exchange.

Welcome to my series of short tips on migrations. Whilst based on Microsoft migrations the same principles can be applied to any type of migration.

My first tip is around source server preparation.

No migration is an easy migration, there is always potential for something to go wrong. All we can do is try to minimize this risk.

The biggest risk comes from the system we already have in place, the integrity of this system is paramount in ensuring a successful migration.

Making sure your source system is healthy and configured correctly will go a long way to ensuring you have a smooth migration.

Use analyzers and health check tools that are available from the vendor. Microsoft, for example, have a number of best practice analyzer tools. These can be used to identify any problems the system may have and provide advice on how to resolve them. Some of the ones I use regularly are listed below:

In a Microsoft migration I will use tools like DCDIAG, NETDIAG, REPLMON and REPADMIN to check for errors, even if it’s a single server. You would be surprised how easy it is to misconfigure a single server. Further details on the usage of these tools can be found here:

Make sure the source system is up-to-date. All updates, service packs etc need to be applied. This may seem like a waste of time on a system that you are soon to be migrating out of your network but really it isn’t. New products from the same vendor normally rely on the source system being up-to-date. I have been known to spend hours installing service packs and updates on a source server.

It’s worth spending the time getting this part of the migration perfect. There are no timescales in play here you can take your time, once you start migrating there are pressures at play that will make the slightest hiccup seem like your whole world is imploding. I would consider this part of the migration process the most important, and therefore if you are not comfortable with this process, hire someone who is. Buying in consulting services to make sure the server is healthy can save you a lot of money.

Watch out for tip Migration Tip #2 – The Practice Run in the next day or two.

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

, ,

First in our series of Guest posts by Exchange MVP’s is Kevin Ball, exploring a new approach to on-premise Exchange hardware. My interest in appliances was piqued at WPC last year, with the launch of the Azure appliance and if you wanted to retain some Exchange on-premise, but without the all the complexity of managing hardware this seems like a sensible approach. Matched with Cloud Services could Exchange appliances be the future of Exchange on-premise?

Kevin Ball is a Senior Mail Support Consultant, working within the Enterprise Infrastructure Services group at Hewlett-Packard. He has been working with Exchange since Version 4.0 Release Candidate 2, back in 1996, and he has received a Most Valuable Professional (MVP) award in Exchange Server from Microsoft every year since 2007. Follow him on Twitter for random observations on life including the occasional Exchange-related tweet: @zbnet.

Appliances are wonderful things. It’s great having a white box in the kitchen that cools and freezes stuff with just a numbered dial to adjust – I get to stop my food decaying without having to become a refrigeration engineer and build a cooling plant and know about the safe handling procedures for tetrafluoroethane*.

Exchange 2010 is a great product – arguably the best-ever version of Microsoft’s now very mature enterprise email server. Exchange 2010 has more disk storage options than ever, and can be utilised in vastly varied configurations, which makes it extremely flexible and adaptable to a wide variety of email needs. But every coin has two sides, and variety of configuration options means that setting it up correctly for any given situation needs care, and often expertise. How many IOPS should you allow per mailbox? Will the bus bandwidth of a particular disk controller be fast enough? Are your disks performance-bound or capacity-bound? These and a hundred other questions need answers before you can be sure your hardware spec is up to the task of serving your particular user community with no fear of resource shortage.

Microsoft helps, of course – there’s the famous Mailbox Server Role Requirements Calculator spreadsheet (http://blogs.technet.com/b/exchange/archive/2010/02/17/3409348.aspx), which can be used to specify the required disks, memory and processors for a certain number and a certain type of users. But even with all the great tools and TechNet, planning Exchange servers can be daunting for the small- or medium-sized enterprise who lack a tame Exchange expert, or who can’t afford the time and cost of specialised training.

Another option is to hire in a consultant, or outsource to a services company. That works for some, but can tend to be costly. Not everyone needs nor wants to spend money on the luxury of a custom-designed bespoke Exchange configuration. Wouldn’t it be great if we could buy our Exchange servers like we buy our refrigerators – according to their storage capacity, and with just a simple numbered dial to control them? When will the age of the email appliance be born?

Welcome to the stage the E5000 from HP. One fruit of a $250 million collaboration between HP and Microsoft, the E5000 family of appliances (there are 5 different models) are a new venture for both companies in the partnership.

What You Get

An E5000 email appliance is basically a DAG-in-a-box (a Database Availability Group, or DAG, is a group of between 2 and 16 Exchange mailbox servers that can replicate database copies between them to provide highly-available access to Exchange mailboxes). The E5000 chassis contains two blade servers each of which is essentially a ProLiant BL460c G6, with a set of internal and chassis-housed disks (the type and capacity vary slightly according to the model number), a custom disk controller, an on-disk Exchange install kit (this is the first time any server kit has been sold with Exchange binaries included), and a newly-developed wizard that helps you set up the appliance. Also included in the price is a 3-year support contract for both the hardware and the software, that gets you help and replacement bits within 4 hours in the event of a problem or a component failure.

Because the disks are already fitted, you don’t have to worry about IOPS calculations, and bus bandwidth, and disk controller set-up. Each of the two DAG servers has its own RAIDedfault-tolerant array of disks, as the minimum number of servers in a DAG to support JBOD storage is three. Also, as the appliance comes with a wizard, you don’t need to be a certified Exchange professional to ensure the installation is set up optimally – the wizard steps you through a series of questions, prompts you for the information it needs, and then does its magic behind the scenes to deliver you an optimally-configured Email solution.

Does all that sound too good to be true? Is it really ‘plug and go’ Exchange in a box? Well, not exactly; the day of ‘refrigerator-style’ email isn’t quite here yet. There are some things that aren’t included in the box that you’re going to want to get before your new email appliance can serve mailboxes for users. First on the shopping list is a pair of Exchange 2010 server licences (and don’t forget your Exchange CALs whilst you’re in licence-shopping mode). You’re also going to need to buy some kind of hardware load-balancer (or a virtual version), because the Exchange 2010 servers in the E5000 are multi-role servers (each running a Mailbox, Client Access and Hub Transport server role), which means Windows Network Load Balancing (the ‘free’, software equivalent to an external load balancer) can’t be used – it’s incompatible with the Windows Failover Cluster component that the DAG servers need to run.

Is the need to buy an external hardware load-balancer an issue? It might have been 12 months ago, but not in 2011 – the marketplace has responded to the growing need for Exchange solutions to use such devices, and now a number are available that will meet your needs, and are fully certified for and come with install and configuration documents for Exchange 2010 use, so you don’t need to fret. See here for a full list. If you’re at the lower end of the capacity of the E5000′s capabilities, one (or two if you’re committed to a full highly-available configuration) of Kemp’s LoadMasters will suit you well.

So it’s not quite yet ‘plug and go’ email-in-a-box. You need extra bits and pieces, and you’ll need to have some idea how to answer the questions the wizard asks you if you’re going to get the most out of your E5000. It’s maybe not quite an appliance as it stands today, but don’t lose heart. This is V1. Be certain that both Microsoft and HP are aware of the short- comings, and both partners are working hard at developing and refining the concept. Who knows what levels of refinement and automation will be built into future versions of the E5000 appliances? Those who know aren’t telling, but things will definitely improve. Nevertheless, the E5000 isn’t value-less – it’s a bold first step into simplifying the complexity around implementing Exchange, and it’s a great initial effort. It brings an ease of configuration and a level of pre-supplied compatible hardware config to a newly accessible ‘appliance-style’ product, and in doing so begins a revolution that has the potential to help many small- and medium-sized enterprises implement the best-ever version of Exchange with the least amount of hassle and lost sleep – and that is a great step forward for Exchange, and for your users. Refrigerators and E5000s – they’re both pretty cool!

To learn more about the E5000 range, go to www.hp.com/go/E5000

*an inert gas used as a refrigerant in domestic refrigerators. It is denser than air in gas form, so if you breathe it you might die; and when evaporating from liquid to gas it absorbs copious quantities of thermal energy, so if you spill some on your hand you’ll likely get severe frostbite. So probably not a great idea to make your own refrigerator!

Add your comment (0)

Cloud Strategist
Mimecast

Article Tags

, ,

In Part 1 of this series, we made the audacious claim that you could use SATA disks without RAID to run Exchange! Here’s how you can achieve it.

Exchange 2010 introduces the concept of Database Availability Groups, or DAG for short. It’s a High Availability model that uses the best bits from Exchange 2007, known then as CCR, and uses the same technology to ship the database logs to as many members of the DAG as you may have configured. Since you’re shipping logs around and NOT the database as you did previously with your replicated SAN that means that now each copy of the database on each of the DAG members is a clean copy of the live database.

If any of the copies of the database has a minor glitch because the disks you’re using develops a bad sector, then each server is able to reach out to any other copy and request the page which has corrupted and receive a known good clean copy to patch itself with automatically.

Does that mean that Exchange can’t use SAN’s anymore? Of course it doesn’t. Exchange 2010 is able to use virtually any kind of disk you allocate to it. SAN volumes, DAS (Direct Attached Storage) shelves or JBOD (Just a Bunch Of Disks). Irrespective of the disk you give Exchange, you’re able to build a highly available distributed unit of high availability.

Using lots of relatively cheap and large SATA disks means you’re able to deploy lots of cheap Exchange servers with large mailboxes, which are highly available and mostly self-repairing. Using your SAN means you’re provisioning finitely sized mailboxes and expensive storage which is now potentially overrated for the task required.  As you may know, redundancy in your SAN isn’t cheap either, and mirroring your SAN to an offsite location can be desperately expensive.  In short, the use of SATA allows high availability to be achieved by distributing Exchange databases across cheap storage as opposed to one massive SAN which is mirrored somewhere else.

CAN Exchange benefit from your SAN? Of course it can, but you may find that the performance you get using low cost SATA based storage option with Exchange built in high availability through DAG’s will service your organization better than your SAN will. In fact, if you hand your high cost SAN back to your SQL teams for their use and step away from SAN infrastructure for your email, your company will win on two counts and you will become a hero outside of your own team!

 

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

, ,

Exchange 2010 promises to dramatically cheapen the cost of mail storage to the point where it no longer requires SAN based storage to achieve its goals of storing mail in a secure and highly available manner.

Exchange 2010 is able to use virtually any storage you give it, the only criteria being that it supports the IOPS requirement for the workload demanded. Due to the efficiencies in the current version of the storage engine, that means that databases can now be stored on SATA disks, SAS disks, RAID volumes on DAS Shelves, or the holy grail of storage – Tier 1, the SAN.

You may think that SATA is great when it comes to storing videos of the kids on holiday, old emails, documents and your music collection, and we agree. SATA has been the last thing we would have thought of in the modern datacentre, OR that mail server you hide under the desks or in the closet in your small branch office.

So how has SATA become the new rising star of storage, after previously only influencing the desktop sector?

There are two kinds of SATA we need to consider here, desktop or consumer SATA and enterprise SATA. The difference comes in the construction and the firmware of the disks. Enterprise SATA disks have more rigidity, more extra bits in the chassis and firmware that take into account that each disk may be housed in a shelf with a number of other disks which vibrate, spin and potentially influence each other.

Consumer SATA disks on the other hand have a much lower cost construction and are not designed with any of the additional heat or vibration considerations in mind.

So that makes sense – enterprise SATA disks can live amicably in a datacentre – but they’re still SATA. They’re still slow – literally slow. They rotate as slow as 5400 RPM, as opposed to the 10 000 or 15 000 RPM you’d expect from a traditional enterprise disk. Random seek times are what you’d expect, randomly slow. So how on earth do they become good candidates for the most important commodity in your digital life – your companies email?

The Exchange 2010 version of ESE – the Extensible Storage Engine, which is the database that Exchange uses, has a bit of secret sauce, actually it’s a rewrite from the ground up, which makes it 90% faster than Exchange 2003. That’s right, 90%, no typo there. But wait there’s more – it’s also optimised for sequential read and writes, in fact the entire database is logically laid out to accommodate long reads and long writes, exactly the kind of thing SATA disks are good for.

So let’s talk about the trust issues you may have with SATA – it’s STILL SATA, it’s still just a single disk, and just to top things, Microsoft are asking you to throw your RAID controller away as well. Is that still a real world expectation?

In part 2 we’ll have to have a quick look at how Exchange 2010 does High Availability for the database.

CC Image via univrsltransl8r on Flickr

Add your comment (0)

Enterprise Consultant
Mimecast

Article Tags

, ,

In my last post I talked a little about Microsoft and their increased activity in the cloud and how that made me feel- very proud as it happens.

In this post I wanted to talk a little about how I think potential customers might feel about the Microsoft Business Productivity Online Services Suite (BPOS) offering.

You see, with so many of us telling IT managers and staff that the cloud is such a perfect panacea to many of their ails and consumers using online services for just about everything, it is no wonder that Microsoft created the BPOS cloud offering.

This is a service that delivers Microsoft Exchange, Microsoft Office and Microsoft SharePoint from the cloud. All of Microsoft’s core communications products, their crown jewels – outside of the OS space – delivered via the cloud.

The next evolution in this offering is nearly upon us and there is a significant facelift in the works, with a move to Exchange and Office 2010, an upgrade to SharePoint 2010 and the addition of Microsoft’s much talked about Lync communications server. Welcome to Office 365!

The Office 365 beta is already out there in production and details are starting to emerge about the transition. This got me thinking with my Sysadmin hat on- if I were thinking about buying BPOS, should I buy it now or wait until Office 365 is released?

It turns out quite an interesting strategic issue and one that needs actioning quickly if you are to take advantage of a number of things. The reason for that is new customers will get Office 365 when it’s released first and existing customers will wait before it’s released and then have up to a year to move- which is totally under their control.

So why would you want to go to Office 365? Here are some reasons:

  • Exchange 2010 back end with significantly improved management features (a lot more control for admins)
  • Sharepoint 2010 with extended customisation
  • Office 2010 available as a web app and as an installed desktop application on a subscription
  • Lync for presence, IM, video, voice

So why would you want to sign up to BPOS now?

  • You want to stay on Exchange 2007- e.g. because Office 365 doesn’t support Office 2003
  • You want to control your migration timescales

Even still, if you are waiting for Office 365 or going to BPOS, now is the perfect time to think about your migration strategy. Orlando posted on Monday about Migrations, but I can’t help but agree with esteemed Exchange MVP Nic Blank when he says “Archive before you migrate” and that’ll make your transition to the cloud quicker and easier. Even if you can have 25GB mailboxes- migrating them is a not a pleasant (or quick) task.

Personally, I would wait for Office 365 because we’re on Office 2007 and soon to be 2010, so there are no client side issues. Plus we’re already on Exchange 2010 and it wouldn’t make sense to go back to 2007. Especially considering the clever things you can do with routing thanks to the CAS role in 2010 and Office 365. But that’s another post.

Add your comment (0)

Cloud Strategist
Mimecast

Why BPOS is making me feel smug.

Microsoft has been doing some of their most prolific promoting in recent history about the fact that they are “all in” for the cloud.

They are offering services like Azure to provide application hosting platforms and BPOS to provide email systems and even SharePoint online!

This excites me no end as it’s no secret that over the past few years Mimecast has been pushing the value that “driving tin” into the cloud offers customers. Fewer servers to manage, fewer specialized non-core skills needed internally and less time spent on the never ending parade of vendors and systems integrators eating up your valuable time while they try to flog their wares.

So what does this have to do with Microsoft and Mimecast? When the largest software company in the world manages to adjust its strategy to begin delivering services in a way that we have been recommending for a very long time, it brings with it a certain amount of pride, personal validation, for me at least.

What does it mean for customers?

It means it’s no longer just hype- it’s real and is definitely a firm fixture for not only our future, but the present too.

So what exactly is it that is causing us to consider these things, especially in light of the fact that so many people I speak to are worried about the impacts that cloud computing could have on their jobs?

There are a few simple facts.

  1. Email is seldom a directly revenue generating service for organizations. While email is a critical application, and one that is tightly woven into many business processes, it is seldom the mail system that is responsible for driving growth, unless the organization’s business is providing email services.
  2. Email is a relatively standard and doesn’t differentiate you against your competition. Let’s face it, managing email systems seems pretty mundane to most tech folk, a system that can be run with eyes closed. The problem with this perception is that while the core mail server itself may be fairly standard, the conditions that evolve around email systems are far from it and fluctuate regularly making this seemingly mundane system a real nightmare to get right and keep on getting right.
  3. Email can be used anywhere. Users should be able to access it from the office, home, on the road from a variety of different devices, operating systems and mail clients.

In these changing times- we need to ask ourselves questions:

First off, should we dedicate so much of our staff’s time to a system that does not generate revenue? Surely the answer is no, we shouldn’t have to, remembering there is not a one size-fits-all policy for email. We cannot however ignore the fact that we have to run email systems and that they have to run well.

Secondly, does working on email systems interest the sysadmins and add value to the organisation? Retaining talent is hard in IT and in some sectors email systems are considered “boring” and “don’t move the needle”. So there could be a temptation to delegate email management to more junior staff who end up scared of this complicated beast where any slip means an unhappy incident that is almost always visible to every single user.

Thirdly, do your users don’t care where their email systems reside? Surely most only care that they are able to connect to those systems when they want to, and it works, Data Sovereignty aside.

So, one of the new found choices in an IT admin’s arsenal of tools for messaging is Microsoft BPOS. There is not a one size fits all policy when it comes to what you do with messaging, but if you don’t want to run your Exchange Servers in house- BPOS might be top of the list. Less infrastructure work for you to do, so you can focus on adding more value to your organization. A winner all round.

And now with Mimecast support for BPOS- you can get extended availability and a third party Cloud archive. Welcome to the Cloud everybody!

Add your comment (2)

Enterprise Consultant
Mimecast

On the 17th of September, Microsoft  released Microsoft Security Advisory (2416728) which detailed an information disclosure vulnerability in ASP.NET.

All versions of Microsoft Exchange since 2003 use ASP.NET in a way in which the vulnerability could exist and the MS Exchange Team told administrators to look out for warnings in the application log that looked similar to: -

Event code: 3005 Event message: An unhandled exception has occurred. Event time: 11/11/1111 11:11:11 AM Event time (UTC): 11/11/1111 11:11:11 AM Event ID: 1309 Event sequence: 133482 Event occurrence: 44273 Event detail code: 0 Application information: Application domain: c1db5830-1-129291000036654651 Trust level: Full Application Virtual Path: / Application Path: C:\foo\TargetWebApplication\ Machine name: FOO Process information: Process ID: 3784 Process name: WebDev.WebServer40.exe Account name: foo Exception information: Exception type: CryptographicException Exception message: Padding is invalid and cannot be removed.

Even this is not a clear indicator that a system was under attack as it could exist for many legitimate reasons. They simply asked that if you see inexplicable versions of this and increased quantities of it that you investigate a bit deeper.

Thankfully today Microsoft announced the release of a security patch that will fix this vulnerability!

The Exchange Team say:

“The Exchange Server team has completed validation of this fix against Microsoft Exchange Server 2010, 2007 and 2003 and we are pleased to report that we have not identified any issues related to the application of this patch on an Exchange Server.

We recommend that Exchange customers consider applying this fix to all of their Exchange Servers which have an affected version of ASP.NET installed on the underlying Operating System in a timely manner to help protect against any attempts to exploit this vulnerability within their environment.”

So if you are a company that applies hotfixes and security patches only after serious testing, you better get on with it as this vulnerability is fixable so you have no excuses if you get exploited through it.

Good one Microsoft. Turning around a vulnerability from announcement on the 17th to repair on the 28th. That is a record 11 days!

Add your comment (0)

Enterprise Consultant
Mimecast

Last month, Google announced the integration of Google Voice into Gmail. Gmail users can now make calls right from within their email.

Google Voice in Gmail

Many analysts are citing this as a direct attack on Skype- but I think they’re wrong- I think it’s a direct attack on Microsoft, Telcos and PBX manufacturers. Skype has had similar functionality for a number of years, but it’s business adoption isn’t large enough for this to be an attack IMHO. Yes you can now call from your PC, but phones have long been the bane of businesses- especially smaller ones. They’re expensive and never function as you would really like them to. And although this is currently on Gmail only and not available today for businesses on Apps- it’s coming soon.

To PBX manufacturers and Telcos this represents a serious threat- why would you kit out your company with phone lines and extensions when you can have this for free on your PC? Or if you’re not at your PC, have your calls follow you on your mobile phone. That’s a serious amount of cost reduction- especially when you add in free in country calls and low cost foreign calls, and an improvement in functionality.

When it becomes available on Apps to businesses, it’s going to make a very compelling ROI case to use Apps.

Microsoft has had similar functionality available in Office Communication Server (OCS), but it’s been a separately installed and licensed application. To respond- I think Microsoft needs to put a more compelling value proposition around OCS- should they bundle it free with Exchange and BPOS? What about bundling free calls?

This is classic disruptive innovation- create a product that’s good enough for a small segment of the market and grow that into the mainstream. Google will soon be putting within reach of businesses a very powerful unified communications tool- and Microsoft needs to respond.

Add your comment (0)

Cloud Strategist
Mimecast

Article Tags

, , ,