There’s a gotcha with migrating to Exchange 2007. If your enterprise is still halfway through an Office 2007 rollout (or better yet, if it’s not even begun), you should be aware that users of the delegation features in Outlook are in for trouble.
Specifically, this KB article recommends using Outlook 2007 for “delegates in Outlook 2007 to work correctly.” I can verify that if you’re in a situation where a mailbox is migrated to Exchange 2007 using Outlook 2007, the delegate on Exchange 2003 using Outlook 2003 loses all ability to do the delegated duties.
I recall when setting up RPC over HTTPS for the first time how annoyed I was when I discovered that a Windows 2000 domain controller could not be used by Exchange 2003 SP2 if RPC over HTTPS must function. Outlook clients using RPC over HTTPS would just mysteriously fail to connect without a helpful error message as usual. This was the same situation as using an untrusted certificate for the “S” in HTTPS. After focusing the Exchange 2003 server on a Windows 2003 server, all was well. I consulted with our Microsoft rep at the time and there was indeed some internal knowledge that a mixed domain could cause RPC over HTTPS to fail due to Windows 2000. Why was that? Well, there was some special, undocumented sauce in 2003 that made global catalog lookups function correctly in RPC over HTTPS that Windows 2000 did not have. It appeared that Microsoft only tested the new generation of server products with the new generation of client products because… well, apparently they assume everyone does IT like they do.
It would seem that thought at Microsoft is still pervasive. 2007 products go with 2007 products, period. If you want to avoid mysterious problems that are only discovered by calling support and plunking down some moolah, then use the latest and greatest of everything. That’s the Microsoft world in an enterprise.
6 die from brain-eating amoeba – Infectious Diseases – MSNBC.com
This one is real, folks. There’s a one-celled organism out there that likes to enter through your nostrils, swim up to your brain and feed on the gray matter until you die. That’s not Stephen King or Clive Barker – this one is real. Scary, real life stuff. It’s a good thing I stopped swimming in lakes at around 8 years old!
So I listened to Macbreak Weekly #59 today while walking around the block. A substantial piece of the discussion involved the impending iBrickness, which by now, has either happened to you or not happened to you.
I also caught Leo’s latest rant on the iBrickify rants by Apple. While I agree with him on some points that speak to the desires of freedom, I believe he is addressing the wrong crowd.
Look people – the problem is not with the technology or the company itself. It’s the ability of any company writing any laws they like to maintain whatever death grip they intend to maintain. By using vehicles like a EULA or a cell phone contract, companies in the US market stifle (more like squash) innovation and freedom. You could blame part of it on capitalism, but a lot of it on greed.
I do not believe that Apple wants to brick anyone’s iPhone for any reason. I do believe that AT&T wants to protect its interests like US mobile companies do. Take a trip to Asia and watch how a real free cell market operates and pay particular attention to the amount of government regulation that is required to keep those companies honest and consumer-minded. It’s mind-blowing. While you’re there, put two and two together: Asia is years ahead of the US in technology and innovation.
I’ve said it before here time and time again. The iPhone tragedies just reinforce my opinion on all of that.
I’m reading a lot of backlash today regarding Apple’s announcement that an upcoming firmware update may turn the iPhone into an iBrick.
Most of reactions can be filed under kneejerk, but since that will be the smallest word on the tag cloud (cough cough), let’s analyze this a little bit.
Apple is preemptively warning consumers that some of the publicly available hacks for the iPhone may have caused “damage” of some kind that will either be repaired or turned into an open bleeding wound. The point is not so much that Apple is warning that you may have an iBrick, which is what most people are sticking with. Rather, people feel the point is that Apple is announcing they “intend” to brick you.
Look – the mere fact that Apple is speaking up about this and warning of possible dire consequences proves two things at the very minimum: 1) They have been testing a few of the unlock methods and know there are consequences to the next firmware update and 2) They understand the consumer’s desire to unlock the iPhone and hack away at it, which is why they’re warning you.
Based on this warning, I think many people are getting the mistaken impression that Apple intends to whack your iPhone. I believe this to be false. I would maintain that if Apple was going to intentionally disable this functionality, they would stay quiet about the aftereffects and merely issue the update – then let the customers know how screwed they are when they bring the iPhone in to the shop. Instead, Apple is preemptively warning consumers because they seem to GiveADamn.
Would you rather they just update your firmware and you find out the hard way?
I just don’t understand the mindset of people who call this a customer-unfriendly attitude. Well, actually, I do, but the reason I understand that isn’t kind and… well… I’m going to take someone else’s mother’s advice and not say anything since it’s nothin’ good to say.
This morning I decided that I did not have anything to offer beyond what other Mac sites provide. I grow tired of sites rehashing news from each other or large print magazines and I’m afraid I wouldn’t have much more to offer beyond that.
That being said, the domain leopardcentral.com is up for sale. I’m smart enough to recognize how lucky I was to get that domain, so I’m going to hold on to it for serious bidders – either that or eventually, perhaps I *will* develop a site out of it.
For now though, I’d rather just sell it. Anyone?
Last night I was reminded of why Linux’s failure to launch on the desktop will continue. It still does not survive the grandparent’s test.
In my case, my stepfather wished to view videos and flash on the web. That, of course, doesn’t come naturally with Kubuntu, unless you’re wanting to watch video on with a free/open-source codec that is used by about 0.000001% of the web. If you’d like to use Quicktime or WMV, that offers a bit of a challenge.
He called me up and said, “I researched this and read on the forums on how to do it… open up the terminal, make these directories, type this shit and all that shit, some apt-get somethingorother… and what does sudo mean?”
I offered to come over and help. Regardless, I know that automatix2 is the cheap way out of this situation and potentially borks up the system, but with the little time I had to play with, I didn’t have much choice.
Ultimately, the Linux community still just doesn’t get it. Let me reiterate this for you. Your product – the fruits of your labor or whatever you wish to call it – will not… repeat… NOT… EVER… SUCCEED on the desktop until you find a way to make this stuff easy and work out of the box. Period. Stop expecting that grandpa can open up a terminal session and whack his way through commands on the terminal. Give him an icon to click. Then… and only then… will you start to succeed.
Until that day, you will continue to fail in your quest for larger desktop share.
Hey, maybe you didn’t want a larger desktop share anyway. If that’s the case, that’s fine. Then you’re succeeding. We’ll just continue on fighting those zombie drones that pick up orders from IRC every day. Not a problem.
Update: How ironic that this opinion article just showed up on my feed reader. I did not know there was a heated debate forming on this – but at least this issue is getting recognized by the concerned parties with a stake in the ground.
Globalisation Institute – Brussels’ most popular think tank website – Unbundling Microsoft Windows
…found via Slashdot. I’m not so sure how I feel about this. It’s a ballsy opinion, but usually consumers purchase computers with the expectation of having an operating system on it that is tied to the hardware. Microsoft loves it when the consumer goes to buy a brand new system with the newest operating system (so does Apple, let’s be fair). Without reading the full PDF because it’s 12:12am, I’m hoping that this think tank is only recommending the operating system becoming disengaged from the computer at the business/enterprise level. I don’t see this being a positive recommendation for consumers.
Halloween is one of those holidays that inspires dog owners everywhere to engage in animal cruelty for the benefit of sick bastards like myself who get a big kick out of it. My mother, who is largely responsible for this twisted sense of humor, forwarded a memo to my inbox yesterday. Some of the pictures just had to be shared. Not all of them are included in this post, I just wanted to share some of my favorites.
I have two new websites that I’d like to start. Both of them need the benefits of a content management system. Right now I’m thinking either Joomla or WordPress. Drupal is out because I just don’t have that kind of time. Opinions?