As you may be aware I have been very involved with an animal charity. It is called House of Tails (www.houseoftails.org ) and is about taking care of abandoned dogs in Thailand. This is also the reason why the volume of my tech blog posts went down for a while. I will however pick up the pace again, I promise! Lots of ideas here. Because the dog sanctuary has a very hard time to make things happen this has taken a lot of time. We have setup an official Foundation (Stichting in Dutch language) with bank and email and PayPal and so on and we are working on a fresh website.
Yesterday a dear friend Pete Zerger wrote a blog posting about our story and he has taken it upon himself (and his friends and family) to bring a challenge. Any donation given to our House of Tails charity within a 72 hour period (starting last evening, so for the coming 52 hours or so still) will be DOUBLED. So any donation you make will get a double effect for the animal charity and all of it will go to the wellbeing of these dogs!
Please read how you can help too:
Also I will include a link here to the PayPal/Creditcard possibility of the charity Stichting House of Tails.
Take a minute to check it out through that post and through the House of Tails website.
Seeing how my geeky family and my online families are willing to help out a good cause is truely heart warming. It means soo much for us and for the dogs!
a truely gratefull Bob Cornelissen
Just now Microsoft announced the wave of main events of next year. The expected event which brings together several tech events like TechEd and Management Summit and Exchange/Lync/Sharepoint/Project conferences into one big event. Well here it is and it is called Microsoft Ignite. Scheduled May 4 to May 8 in Chicago. Read more about it on this page:
This page also lists some of the other conferences in the year like Convergence, Build and WPC.
This was one highly requested MP that we have been waiting for. The Exchange 2013 Management pack for SCOM is now released. It works on SCOM 2007 R2 and SCOM 2012. The released version today of this management pack is 15.00.0620.030
For those who knew the Exchange 2010 management pack and its special correlation engine: the correlation engine is gone now! (Yes, I am happy with that!!).
A Quote from the post:
“If you are familiar with the Exchange 2010 Management Pack, you know that it had a service called the correlation engine that ran on the Root Management Server. It basically correlated health data from all monitored Exchange components. In the Exchange 2013 Management Pack, the correlation engine is no longer used”
This is the TechNet blog post:
The download can be found here:
The Management pack guide online version can be found here:
Exchange 2013 Management Pack Guide
We will probably write more about this mp later when we had more experience with what it looks like in real life. It looks like they have kept the number of views very low at least.
First of all my apologies to all non-Dutch readers of this blog. A part of this posting will be in Dutch since it’s mainly targeted at the Dutch audience. It’s is all about a new User Group in the Netherlands, Windows Management User Group Nederland (WMUG).
WMUG is founded by Marnix Wolf, Peter Daalmans, Kenneth van Surksum and myself Bob Cornelissen. WMUG is aimed at everything involved with managing IT environments based on Microsoft technology. WMUG will serve as a platform for everyone involved with Microsoft technology. Besides the Microsoft technologies there is also room for other mainstream technologies like VMware and Citrix to name a few. It also creates the possibility not only to attend sessions but also to present sessions on topics people excel in. So WMUG is all about the community and for the community.
With the user group we want to provide a platform for and by people involved with managing the Microsoft Windows platform. Our first session will be held on the 22nd of May this year.
Nieuwe gebruikersgroep ziet het levenslicht
Op 22 mei zal de eerste bijeenkomst van de Windows Management User Group Nederland (WMUG NL) plaatsvinden. De WMUG NL zal zich richten op alles wat met het beheren van Microsoft Windows te maken heeft en wil een platform bieden voor iedereen die zich met het management van Microsoft Windows bezig houdt. Of je nu kennis wilt delen door evenementen bij te wonen of tijdens een evenement een presentatie wil houden, de WMUG NL biedt het platform.
Wat kan je van de WMUG NL verwachten?
Periodiek zal de WMUG NL bijeenkomsten in Nederland organiseren, tijdens deze bijeenkomsten zal het laatste nieuws en specifieke kennis over een product met de aanwezigen gedeeld worden. Natuurlijk zijn de avonden interactief zodat u uw ervaring ook met de aanwezigen kunt delen. Tevens zal de WMUG NL webcasts en een Nederlandstalig forum hosten.
Over wat voor producten wordt gesproken?
De focus van de WMUG NL beperkt zich niet alleen tot Microsoft producten zoals de System Center 2012 suite, de Windows familie en de virtualisatie oplossingen van Microsoft. Wij willen juist ook de combinatie maken met andere producten van bijvoorbeeld VMware en Citrix, denk dan aan VMware ESX of Citrix XenServer als virtualisatie platform ten opzichte van Hyper-V.
Wie of wat is de Windows Management User Group?
WMUG NL ben jij! Opgericht door een viertal actieve community leden, wil je echter meehelpen om dit nieuwe platform tot een succes te maken neem dan gerust contact met ons op, je bent van harte welkom! Want zoals gezegd, de community is er voor iedereen.
Hopelijk zien we je tijdens ons eerste evenement, je kunt je hier inschrijven. Wees er snel bij want de beschikbare plaatsen zijn beperkt. Meer informatie over ons eerste evenement op 22 mei vindt u hier.
Neem contact op via firstname.lastname@example.org
We hopen u tijdens onze eerste bijeenkomst te ontmoeten,
Kenneth van Surksum
This user group is for the community and by the community!
At one of my customers I accidentally came across a machine that was not running its dicovery of the Exchange 2003 role correctly. I was actually looking for something else and had to connect to the mail server and because I did not remember its name I used SCOM to see which one it was Anyway, the view was empty.
So when looking in the OpsMgr event log at the mail server (which I did find through another route ) I saw this Error:
Event ID: 31901
Source: Health Service Modules
Description: The Registry Probe could not connect to the registy of the computer \\server.domain.com
One or more workflows were affected by this:
So at first I thought to just ping that machine name (the fqdn of the machine). And I got another ip address than I expected. Turned out that this machine had two network interfaces (one connecting to storage). So it was using the wrong interface first. I checked by doing an nslookup against the DNS server and that one gave the other ip address.
Now the 0x80070035 actually does point to a Network path not found.
So this can happen more often if the additional network card for storage or backup purposes has some features disabled and is listed first in the binding order.
As this was a Windows 2003 machine I went to Network Connections - Advanced - Advanced Settings and found the following binding order:
So the Storage adapter was set to the first position.
And when looking at the properties of that adapter:
So Client for Microsoft Networks is not enabled.
Because of that combination the discovery could not connect to the registry of the machine using the network adapter listed first in the binding order.
Simply solve by changing the binding order and its all systems GO!
Now back to solving that other issue I was actually investigating at first
Like I said a lot of interesting things are happening and here are a few posts from several blogs (and a few from the You had me at EHLO blog!) that caught my eye for several reasons!
Exchange 2010 SP1 Beta has been released and has been discussed previously by the exchange team covering new features and can be downloaded here.
I actually wonder if the exchange 2010 database reduncancy check script as discussed here has been included in Rollup 4 already.
Nagesh from the exchange team made a posting on a deeper dive into the RPC Client Access Server in Exchange 2010.
And Ross about single item recovery in Exchange 2010.
Something I have not yet used, but has ben around for a few months already is the successor for PFDAVadmin and is called ExFolders. This is to be used with Exchange 2010 as WebDAV has disappeared from that version. Also the PFDAVAdmin tool has gotten an update lately.
A big thank you to David Zazzo for pushing MS to release a tool they have used internally for some time to work with many RDP connections. RDCMan is the name of the tool and can be downloaded here. You can read more about the tool in Davids blog post.
A paper on the advantages of Exchange Unified Messaging features to boost Voicemail can be found here.
The Exchange guys have been creating a video series with Perry Clarke about of course Exchange! You can check out the Ask Perry series with sessions like "Exchange Data Protection" and "More Exchange Data Protection - Beyond Replication" and "Exchange Mailbox Storage Bricks".
Thats about all I quickly saw passing by that I wanted to mention and move back to soon. Last weekend I did an MS update run and it did not pick up the Rollup 4, so I will do that during off hours this week manually Will have to see when to test the SP1, as it includes some nice features as well!
Finally it is time to download the DPM 2010 RC release candidate!
Have been eagerly waiting for it and to test some of the new features.
Get it while its hot!
The other day I was talking to a friend with a problem using Activesync from several devices to a SBS 2003 server. He had gone through several KB articles and could not find the solution.
So full of hope I started out on the server and checking the settings. Hmmmmm, seemed OK. In most cases changing SSL or the permissions settings (like anonymous) are the culprit. Such can be found through:
Whenever somebody synced we could see an error 3005 on the SBS server generated by Server ActiveSync. the error was
Unexpected Exchange mailbox Server error: Server: [bla.bla.local] User: [email@example.com] HTTP status code: . Verify that the Exchange mailbox Server is working correctly.
So I went to the IIS logging and found a few entries each time somebody was trying to sync. This included 401 and 403 status codes and that 409 code.
So it is telling you that the server is not available.
Tried to do the same from an internet explorer from the server and same result. Contact your system administrator
But we are still digging.
While I was doing that I found a great resource for exchange errors relating to activesync and whatever. Big list here
Through what I learned during this troubleshooting there are several things to keep in mind and check.
When installing SBS the install wizard already creates an IIS virtual directory for you with name Exhange-OMA. After you have completed setup you would run the Internet Connection wizard. ALWAYS run the wizards while working with SBS. This wizard does a lot of things actually, but email settings are also set here and setting some stuff on the actuvesync, oma and exchange-oma folders also belong to this.
I tried to re-run the internet connection wizard and run through the email stuff as well with this wizard. Always run IISRESET after this wizard. This did not help. Strange as this should correct most errors you might have made while playing around with the settings to make things work
So back to OMA. As Activesync and OMA are linked I thought this one would be the best to troubleshoot first to get things running.
In the end I found this link to a KB article giving me the solution.
Yes, some of the checkboxes were not correctly set on the Virtual Directory tab of the Exchange-OMA folder in IIS. The link above shows the checkboxes that need to be ticked. Seems somebody played around with this after the installation and before passing the server on into the care of my friend. I am betting these boxes get ticked by the sbs install wizard and not the Internet connectio wizard (as it didn't change after running that second wizard).
Changed the settings and ran an IISRESET.
OMA was accessible! There we go.
The next step was resolving a certificate error we got on the mobile device, but that was just because the intermediate certificate (mail.domain.com) was installed on the mobile device and not the root cert used to sign that one. Took the trusted root cert off the server (of course you do not export the private key!) and installed it on the mobile device.
I really enjoyed the live meeting on managing Exchange 2010 through System Center. Actually I thought the presenters had much more things to tell than they had time for unfortunately. I have to say that time passed by too fast during that small hour. So, even if it has been a few days since the meeting already there are still enough things I can remember from it I guess. The session was hosted by Leslie Kitz (SC product manager for Exchange and system center integration, hope I have this description right). Presenters were also Jon LeCroy who has been working on the Exchange 2010 management pack and Jason all-backed-up-Buffington
The improvements in the SCOM 2010 MP are notable. A lot of improvements have ben made to avoid the alert noise that happens whenever anybody touches an exchange server In order to provide for intelligent alerting towards a root cause the creators of the new MP have put lots of effort into working with the health model to determine root cause alerts and show them first. They are using a new service called the Correlation Engine. Alerts have been reclassified into three categories: Key Health Indicator, Non Service Impacting and Forensic. Also improvements have been made into the reporting field. Notable was that the reports are more of what we were looking for. So report on the service more than the servers, mailflow statistics (in demand by managers) and exchange aware availability modeling.
Next in line was our backup friend Jason Buffington on DPM. Because of the big changes in Exchange the existing DPM 2007 can not backup exchange 2010. The new DPM 2010 however can do that. It fully supports DAG. DPM 2010 is still in the beta stages, but will probably be available in final version around the end of Q1 2010. One interesting remark was that the next RC version will also support machines outside of the domain. This is used to backup a few workgroup and dmz machines for instance. Great feature and much asked for.
On a personal note: Since a few weeks I have a exchange 2010 only implementation and I can say my DPM 2010 beta is performing very well. By the way, it also was doing a great job against the system state, exchange 2007, sharepoint, hyper-v, sql, file shares etc. SO good going with this product Jason and crew!!!
The session went on to give some virtualization advice on exchange virtualization. Some things I can remember are Unified Messaging role not being supported for virutalization. Doesn't mean it won't work, but it will probably give performance issues on larger deployments. Advice to use passthrough disks or fixed VHD files of course. Heavy used servers are best not virtualized.
Probably this session could have been stretched across 3 hours, because there was so much to say. But of course the 1 hour sessions are much easier to schedule for everybody. So solution is to have many sessions on lots of subjects.
The next session will probably be 5 January 2010 and be on virtualization subjects. I can't wait. Thank you very much Leslie Kitz for the exchange and system center session!
Was funny after my last post I discovered what the installer was doing after entering the key. It was removing Outlook
In the end it was just the broken office 2007 underneath it that caused the whole mess.
And removing office 2007 the normal way was not possible. So... I followed the procedure for manually removing the whole office 2007 installation.
This also took care of the 32 bit office programs stuff. SO I cold go for Office 2010 64 bit now.
After installation just start up MS Word. Go for File - Help. There is a link there to change the product key and activate the product. This time this worked! It was just the broken office 2007 that kept everything from working.
Anyway, was happy for the manual removal procedure for the 2007 version to solve all problems.