Yes, I have just finished figuring out that it was an issue with the database permissions on my production server (I must say that it would have been nice to have a database error kick with that information.)
Regardless, the default timezone should be set. :)