Not many people are aware of this. But “Microsoft Office Communicator hotfixes are not part of Windows Update, so it is important to find and deploy them through other means.” (source)
I’m completely baffled on how this happened. In the Mac Messenger version, the update is handled by the standard office update. Someone on the Windows side completely dropped the ball. And I’m willing to bet that there are a _lot_ of admins out there that don’t know that this is the case.
Having dealt with my fair share of timezone issues while programming, I find leap year issues really funny. Thank you Microsoft for starting off my year with a laugh.
Many Zune owners successfully revived their failed music players Thursday morning, while others were still unable to overcome a leap year-related glitch that caused thousands of the devices to simultaneously stop working on New Year’s Eve.
“Mine is back up and working as of a minute ago!
At work, our corporate network is mainly all Microsoft. Sure there are roles filled by some linux machines and for our ISP services, its almost all unix/linux. But for email, calendaring, document sharing, its Micro$oft all the way.
I’m the black sheep of the office running OSX on a mini. I’m “testing” software, honest =)
Due to the nature of the corporate network, I find it is just easier to run the Microsoft office suite which means working with Entourage on a daily basis.
Mike Nash, one of the VPs in the Windows Product division at Microsoft had a recent blog post announcing the new name of the next generation Windows operating system. Looks like this will be one of the few times that the development code name will be the full release name.
Personally, I’m not sure why I have ever known the internal development name of a product from Microsoft. In reality, it should stay internal if you have good security measures in place as the only people that need to know the name are the developers and engineers working on the project.
At work, I have a project that has been going on for a month or two. It originally started out as replacing our Hosted Exchange 2003 environment with a new fancy Exchange 2007 environment and add on extra features. To provision this, we have decided to abandon our own provisioning system due to various issues with documentation (or lack there of it) from Microsoft. So, we have decided to drink the Kool-Aid and are rolling with their HMC (Hosted Messaging and Collaboration).