Saturday, March 13, 2010
Google is taking over my life
OSX Server = FAIL
- Create Google mail/cal setup @ domain.com (google apps)
- Add mx records for sub.domain.com
- Rename domain.com -> sub.domain.com on your current mail server
- Create all users @ domain.com (google)
- Adjust domain.com mx to point to the new google apps setup
- Forward all mail from domain.com to sub.domain.com (so the move is transparent. Note there's a window between 4 and 6 where a few emails could come in so watch out. Google doesnt let you add users and forward mail until your MX records point at them)
- Move desired people back from sub.domain.com to domain.com by disabling forwarding and giving them their google passwords
Google Calendar very broken
Sunday, March 7, 2010
iPad?
BluRay and OSX
Tuesday, February 9, 2010
Been quiet, what have I been up to?
Needless to say, there's lots of Mac, Python, backups, storage and other fun things going on with a killer group of people.
Sunday, January 17, 2010
Snow Leopard Server
- Groups don't work as mail distribution lists anymore. Not sure how they broke this, but they did
- Calendar invites from outside your domain do not go to your domain calendar, and if you try to copy/place it on the right calendar you get: The server responded: "HTTP/1.1 403 Forbidden" to operation CalDAVWriteEntityQueueableOperation.
- You still have to hack the server to enable RADIUS for VPN authentication. Apple has it fixed to do wifi auth and didn't think this through
- Mail aliases still are not supported so you still have to sudo vi /etc/aliases in the terminal to manage these. Then you need to deal with any races in it overwriting on its periodic updates as you edit the file
- They have not thought through the whole internal versus external naming/conventions around their web mail/management interface to the point that its almost impossible to make use of
Leopard Server = No Time Machine
OSX DNS issues
Google Voice - not moving?
Where'd I go?
I was at an airport recently for a delayed flight and on the laptop. The thing started cooking my lap. I looked and saw that spotlight was busy indexing my hard drive while I was on battery. This seems like a simple, "if on battery dont update spotlight" decision. Battery life is precious enough, to waste it for spotlight seems like a poor decision. Its a wonder some poor decisions like this last for so long in software.
Tuesday, September 29, 2009
Disqus
(those few that comment!) if it bugs you.
Monday, September 28, 2009
DNS over VPN and Snow Leopard
Thursday, September 24, 2009
Call blocking
spammers and once I identify them from the "missed calls" log (since
no phones ring if they're not in my address book) I can block them so
they get the tone of disconnect. Love it, sweet sweet revenge on the
spammers.
Wednesday, September 23, 2009
iPhone 3.1 woes update
Saturday, September 19, 2009
ScanSnap 510M and Snow Leopard
Monday, September 14, 2009
iPhone 3.1 Woes
Mint and Intuit
Online and I guess Intuit is paying attention. I'm glad to see them
recognizing this and picking up the cool team at Mint.
For the record, Quicken for the Mac STILL has not been updated and
since they don't have an Intel version wont even run on Snow Leopard.
I say fire the group and get some startup to start over, it will be
cheaper and better. Look at Mint.
Saturday, September 12, 2009
Snow Leopard - wait it out
came out. Thanks to some FedEx fiasco's I didnt install until the next
day but I think I still qualify as an early adopter. I have to say i'm
seriously disappointed. The quality and compatibility is poor. Worse
than any other release i've experienced from Apple. Here's some of
what i've seen:
1) Many applications are incompatible and not yet updated. Perhaps you
can blame developers for not being on top of things, but I think not.
I expected PPC apps to have an issue as this is an intel only release,
but I was shocked at the number of apps that broke even though they
had intel support. Here's a short list:
Medialink, EyeTV, Growl, ScanSnap, 1Password, Contribute, and many more
Why did so many apps break? Why didn't apple warn people in advance?
The upgrade from PPC to Intel machines was smoother.
2) I've seen several "black screen of death" events where I must power
cycle the machine. I was perfectly stable before that. For the record
the machine I saw that on I did a complete wipe (disk format) and
fresh install of Snow Leopard and then only installed the latest
versions of apps I needed. Can't blame some less tested upgrade path
for that one.
3) I've had many hangs in Mail and Safari where I have to force quit
the apps. Didn't have those issues before the upgrade. This is a fresh
install, Apples apps and basic ones. Quality Control?
4) We've seen some odd behavior -- VPN to work using Apple's native
VPN to a Cisco firewall worked great before Snow Leopard. After the
upgrade DNS doesnt work. You can connect but you cant resolve anything
on the other end so you end up having to edit /etc/hosts and add
systems by hand. How'd they brake that one? And why? (multiple people
have experienced this)
5) Some vendors, like the Agile folks, makers of 1Password, have
chosen to use this as an opportunity to charge for an upgrade and not
support you unless you upgrade. Considering i'd owned 1Password for
less than 10 months I was shocked to see them require me to pay for an
upgrade. On all other fronts the Agile team is amazing but this
decision is flat out wrong. Others have gone down that route and
you'll be paying for upgrades to apps that worked fine prior to Snow
Leopard. The OS may be cheap ($29) but the time sink and the apps you
have to pay to upgrade are not.
So i've had issues, what about the good stuff? Um, what good stuff?
Frankly I haven't noticed a performance improvement and the
frustrations of a semi-stable OS wipes that out anyway. There are a
few very minor visual improvements, but fundamentally almost nothing
is noticeably different.
Its too late for me now, but I wish I had waited 6 months+ to upgrade.
Not the normal experience with Apple.


