Doug Ortiz's Blog
Architecture and Development blog postings of technologies ranging from Artificial Intelligence, Machine Learning, Large Language Models, PostgreSQL, Cloud, DevOps, Big Data, Data Science, Business Intelligence and Databases
If you have had the chance to download either SharePoint Foundation 2010 or SharePoint 2010 it is most likely that you have attempted to install with a local account on a Single Server Install. Odds are you have probably gotten disappointed because the wizard did not allow the installation with a local account. You were not the only one disappointed, although that disappointment did fuel the need to find a solution.
After some research, I did find a useful blog posting from the field that had the exact solution to my dilemma. The solution consisted in using PowerShell and a script named: “New-SPConfigurationDatabase”; this script is to be executed through the SharePoint 2010 Management Shell.
The step-by-step process would be like this:
1- Open the PowerShell Management Shell
Entering the prompted items:
DatabaseName
DatabaseServer
FarmCredentials
Passphrase
The process will take a while, when completed the cursor will appear in the command line.
2- Open the Configuration Wizard
Click Next Button
3- Restart the Services
Click Yes Button
4- Leave the Do not disconnect from this server setting selected
Click Next Button
5- Continue the normal course of the Configuration Wizard
There you go, now you have a Single Installation Server with a local account, this will work for both SharePoint Foundation 2010 and SharePoint 2010.
I also was very excited as soon as I heard that news to, while it is not set in stone. Some CTP participants for the Office 2010 have received an email that hints to something like that.
If you would like to see more details about that email it can be found at this link:
The details regarding SharePoint 2010 have long been awaited and while many have listed or blogged about it, this a compilation of many of these changes and enhancements.
While it is not in depth, it can be expanded with your comments and suggestions; feel free to leave comments so that we can improve upon this list.
Exclusive for 64 Bit Operating Systems
If you thought that MOSS 2007 was big SharePoint Server 2010 is huge!
No backward compatibility
In case you wanted to use SharePoint Designer 2010 to modify SharePoint 2007 sites; it is not possible
User Interface is Ribbon based
It is all over the place and a major and welcome improvement
Composites
A nice word to describe applications that have been created by the use of InfoPath, Designer, BCS, Web Parts, etc.
Improved and Enhanced Lists and Document Libraries
These can go easily into the millions!
External Lists – residing outside of SharePoint
More Event Receivers!
Editions
MOSS no more - It is SharePoint Server 2010
WSS - Now SharePoint Foundation
Services
PerformancePoint – Improved Business Intelligence
Visio
Project Gemini – An attempt to simplify BI for everyone
Access
Business Connectivity Services – New naming for what Business Data Catalog
Enhancements to the API
Online Services
Standard
Dedicated
Multi-Tenancy
Search
Improved and faster responses
Ability to deploy with FAST Technology
Social Computing Integration
SilverLight Integration
Through out of the box Web Part
SharePoint Designer 2010
Reusable Workflows – Same workflow can be used on multiple Lists in different Sites
Like with any new product there are new naming conventions, terms and concepts that emerge along with the product itself. Yes; there are many of those being brought to the light with the launch of SharePoint 2010.
Does that mean that everything has changed? Yes and No, some concepts and terms have remained the same although they have been improved upon. While others, are completely new and certainly deserve a detailed overview for a good understanding on how they can be applied and used in the real world.
In future blog postings we will be taking a look at all these new functionalities that will be part of the SharePoint 2010 Platform.
Thank you for attending the presentation at the Rocky Mountain SharePoint User Group, as promised enclosed you will find the slides and the sample code.
The blog belongs to an extremely talented SharePoint Architect that has decided to join the blogging world: Joshua Hicks. Personally, I am looking forward to reading his blog posts.
Almost everyone nowadays has or should have an Antivirus on their computer. The available choices usually come in the form of: free or purchased. While most of the time the free versions would not be as great as the purchased ones, a new contender is now available and no longer in Beta from Microsoft, this new product is named: “Microsoft Security Essentials”.
The purpose of Microsoft Security Essentials is to protect against:
Viruses
Spyware
Trojans
Rootkits
So far it is very impressive, quick and simplifies the whole process; not to mention that it even has some nice videos available for: installing, scanning and fixing problems.
Recently, I was asked if I had an idea of how to resolve this problem; the most common and easiest solution to fixing this problem is to add the site to the Trusted Sites in Internet Explorer; while this is the easiest way to fix the problem, some of the users might not like the fact that they will have to do this the first time they access the site.
The second method to fix this problem is more involved and requires the modification of the master page, the steps for achieving this are listed in great detail in the following article:
If your list of blog feeds is growing out of control, try taking a look at Google Labs Fast Flip; it really does make it fast and easy to catch up with the news very quickly.
“How do you update the templates contained in the Document Libraries of the ‘Case Management’ Site Template?”
It is a great and common question, the quick technical answer is:
“Update the document in which the Content Type of the Document Library is derived from”
Instead of keeping the answer technical thought a quick Hands on Lab would easily illustrate and answer much easily, with that in mind what you will need to complete this quick lab is:
Requirements
·A site based on the “CaseManagement.stp”
·Office 2007 as the default Office Suite
·Around fifteen minutes to complete this lab
·For the purposes of this lab we will use:
oDocument Library: Case Documents
oDocument: Expense Report.xls
oContent Type: Expense Report
Steps
1.Ensure enough permissions to modify the Case Documents Document Library, administrator permissions should work fine
2.Navigate to the Case Management Site
3.Navigate to the Case Documents Document Library in which you wish to change the template
4.Click on the Expense Report WorkSheet
5.Select the Edit Radio Button
6.Click the OK Button
7.Modify the Expense Report Worksheet to match your needs
8.Save it to the Desktop or a location of your choice
9.Click the Settings Link of the Document Library
10.Click the Document Library Settings Link from the list of choices of the DropDown
11.Under the Content Types section click the Expense Report Content Type
12.Click the Advanced settings link under the Settings section
13.Select the Upload a new document template Radio Button
14.Click the Browse… Button
15.Locate the recently modified Expense Report Worksheet
16.Click the OK Button
17.Navigate to the Case Documents Library
18.Click the New Link
19.Click the Expense Report Link from the choices in the DropDown
20.Click the OK Button
21.The updated template is now displayed
22.Congratulate yourself, you did a great job!
Conclusion After you complete the lab, you might be wondering:
“Do I have to repeat these steps for all the templates I wish to update?”
The answer is:
“Yes”
You might also end up wondering why so much complexity has been added to a simple process, the reason for this is because it does add tremendous flexibility when sharing this same template across your entire Site Collection.
Imagine that this template will be used all across the entire Site Collection which encompasses 50 Sites and dozens of Document Libraries, making a modification to a centric Site Content Type does simplify the entire process of maintenance. Mostly, because you make the modification and it will replicate across the entire Site Collection. One thing to keep in mind is that it will modify all those new documents based on the recently updated template only, in other words it is not a retroactive process; previously created documents will not updated the change.
In case you are looking into an introduction about how to create workflows and wondering how or where to start; I will save you a few searches and let you know that the following two hyperlinks are great resources for an introduction for building custom workflows and for building one.
It is a two part series from a great blogger: Robert Shelton. Below are the hyperlinks to the postings and materials, they are very complete.
