The question:
**Should GUIDs be the primary key for every table in every system as a blanket policy??**
would depend on the reason for the policy. It would not make much sense to require guids as primary keys in a system that uses Access as adatabase engine.
But if the reason they are required in every table is to maintain consistency through out the table structure of a system, that would be reasonable.
One may argue the fact that they are bigger and harder to read that auto-incrementing numbers, but in real life a primary key should not do anything other than uniquely identify a record in a table. So there should not be the need to read it. You should never have to type it in and the user should never see it.
And as far as being bigger, that is very true. The are 4 times as big as an int and create bigger indexes as well.
One reason to use a guid, as you mentioned, is to create GLOBALLY unique keys. Specifically for distributed databases. And one might argue'we will never need to distribute this database over multiple servers'. I would question, why limit yourself. NASDAQ.com certianly didnt expect the demand they got. Had they been short sighted and said 'we will never need to have more than one server' what would have happened to them?
But it also comes down to a development style. If you just dont like them - lets face it - they are pretty ugly, then you will not want to use them.
Should it be a blanket policy? If you wish to create a standard interface to your tables and the primary key type is a guid then yes - it should be a blanket standard. But if you do not care about creating and dealing with those standards then no - it should not be.
One must make the best choice possible based on the business you are in, the types of projects you are doing and where you see the trends going in the future.