iPhone Detected, site running in minimal mode.
Home     Tags/Archives     Tweets     About Kevin

I recently read an analogy that Robert Scobble used to describe why Microsoft failed to jump on the Web 2.0 bandwagon back in 2004-05 when things were starting to heat up.  I'm stealing the premise here to ask a slightly different question (he probably stole it from somewhere else anyway).
 
So the question is, which would you rather have... a penny that doubles it's value every day for 30 days or $100,000?  Obviously, if you do the math, your penny would end up being worth over 100x as much, but not until far into its cycle (see below):
 
day 10: $10
day 15: $328
day 24: $167,772
day 30: $10,737,418
 
So perhaps the choice is obvious, but let's put some real world variables into the scenario.  What if there was an increasing chance each day that your penny would stop doubling... maybe this starts low, but by, say day 23 it was at 50%?  Or what if each day represented a larger timescale... perhaps day 30 was the last day of your life?
 
Think about how you make opportunity risk decisions- what other factors or variables might weigh into your decision? [stop reading for a second and think about the last question]
 
If we could ever know all of these variables we could just analyze each one and make the most sensible decisions, but this is rarely the case and so most of us have developed part of our personality to make these decisions from an emotional or gut level.  If you believe Malcolm Gladwell's book Blink we might be much better at this than we think.
 
*I* think by understanding our own personalities in these ways we can actually be content in life, free from regrets, and believing that we truly want what we have instead of always wishing we had what we want.  Then again, I'm a pretty optomistic person that also has written about failing fast, the journey of learning, and the importance of being wrong occasionally.


If you want to create/use a site template (STP) to create subwebs (sites) within a site collection you just put it in the template gallery which can be accessed in site settings.
 
However, if you want to use a site template to create a root site of a site collection (normally done either in central admin, or through scsignup.aspx), then you need to use STSADM to "install" the template, otherwise you won't see it when picking the templates during a site collection creation.
 
Here's the syntax:
 
stsadm -o addtemplate -filename pathtotemplate.stp -title NameOfTemplate
 
After you do this, you will need to do an iisreset before the template will appear under the Custom tab in the template selector when creating a new site collection.  Other related stsadm commands you might need to use are:
 
stsadm -o enumtemplates
stsadm -o deletetemplate -title NameOfTemplate
 
I guess it would have been too easy for MS to create a site gallery in central admin for this purpose.


Point 1: You should always install MOSS while logged in as the account that will ultimately be used as the service account.  This is because during the install whoever you are logged in as by default get's admin access to just about everything.
 
Point 2: If you need to later go back and create another "Super Admin" user account, there are a number of places you need to do this... here they are in case you forget (most important required ones are in red):
1) Farm Administrators - add from the operations page of central admin (security configuration)
2) (optional) Site Collection Administrators for CA - add in the site settings from central admin. 
3) Site Collection Admins for your SSP - add in the site settings area from your SSP site.
4) Shared Service Rights - Add all manage rights in the "Personalization Services Permissions" section of the SSP
5) Make sure account is in the owners group on all Applications (done in the People and Groups area of each root level web of each site collection)
6) (optional) Add user as either primary or secondary site collection administrator for all the web app site collections (don't mess with the MySites though other than the root).  Do this in "Site Collection Administrators" on the Application Management section of Central Admin.
7) (optional) Set up full control policies for the web applications.  Do this in the "Policy for Web Application" under the Application Management section of Central Admin.  Make sure you don't check the box "Treat account as System" when doing this unless that's really what you want.  This will make sure the account can access/modify anything and everything that gets created in the entire web application.
 
Hope this helps someone.

 










RSS FeedBack to the HomepageMy Twitter Feed and More!Video Chat Now!

Tags

Hide Low Frequency Tags

Archives

Recent Posts