SharePoint Blogs

Body: Well today was certainly a good one with some hands on time building a collaborative solution in SharePoint. While driving though I had a chance to record an additional 5 new podcasts. They include: Silverlight Interface to Media Services in SharePoint Read More......(read more)

Body: After a few months of hard work we are finally making our first release. If you want to download the solution and take it for a spin, go to the release page on codeplex: http://www.codeplex.com/CKS/Release/ProjectReleases.aspx?ReleaseId=7675 The Read More......(read more)

Proper planning is crucial to the successful implementation of any MOSS 2007 Farm.  Below is guide to preparing your server environment by creating the proper accounts and simplifying permissions by making of use of Active Directory groups.

Step 1 – Create Accounts and Admin Group in Active Directory

The following user accounts should be created:

SAMPLE USER ACCOUNTS:

Server Farm Account      =             Domain\SP-ServerFarm
Setup User Account        =             Domain\SP-SetupUser
SQL Service Account       =             Domain\SP-SQLService

SAMPLE DOMAIN GLOBAL GROUP:

AD Global Group              =             Domain\SharePointAccounts

Step 2 – Add Accounts to Administrative Group

Add the three setup accounts created in Step 1 to the Active Directory Global Group created in Step 2.

Step 3 – Add Domain Group to Local Administrators Group on SharePoint Servers

Add the Active Directory Global Group (Domain\SharePointAccounts) to the Local Administrators Group of every Web Front End or Application Server within your SharePoint Farm.

Note: You may also use Active Directory Group Policies to accomplish this.

Step 4 – Add Account to the SQL Server Local Admin Group

Add the SQL Service Account (Domain\SP-SQLService) to the Local Administrator Group of your SQL Server.

Step 5 - Assign SQL Server Roles

Create the following Logins and assign the defined Roles on the SQL Instance to be used for the installation of MOSS 2007:

Logins                                                   Roles

Domain\SP-ServerFarm                 dbcreator, securityadmin
Domain\SP-SetupUser                  dbcreator, securityadmin
Domain\SP-SQLService                 dbcreator, securityadmin, sysadmin

  

---

Posted on SharePoint Blogs

This was a weird one! On one of our site collections for no particular reason the Quick Launch menu disappeared. We're still not sure what happened, but here's how we fixed it. I can't take credit for this as my co-worker, Aldo, figured it out. After a bit of research, he determined it was limited to a specific master page. Once I opened the master page and made a small change and saved it, the Quick Launch reappeared. If you read this and have an idea on the cause, please comment. Mirrored...(read more)

So here is what I came up with related to definitions of Key /folder/sharepoint.htm Business Roles:
/folder/sharepoint.htm Project Manager

• Defines Business Rules for /folder/sharepoint.htm
• Writes requirements specifications for the /folder/sharepoint.htm Developer, Architect, and Designer
• Monitors the /folder/sharepoint.htm Developer, Architect, and Designer's project progress
• Acts as a go between for the customer and /folder/sharepoint.htm Developer, Architect, and Designer
• Re-allocates resources available for /folder/sharepoint.htm Projects based on supply and demand
• Changes project priority as needed

/folder/sharepoint.htm Administrator

• Monitors the Innerworkings of /folder/sharepoint.htm through Central Administration and Server Side Administration
• Maintains backup strategies and scripts
• Maintains Services Related to /folder/sharepoint.htm
• Performs Disaster Recovery
• Sets up services for /folder/sharepoint.htm

/folder/sharepoint.htm Architect

• Creates and maintains the /folder/sharepoint.htm Structure based on user requirements and content needs
• Documents /folder/sharepoint.htm site structure
• Helps the developer find practical solutions for users
• Maintains use case scenarios in UML and other user based diagrams
• Works with the Project Manager to get a better idea of what the users need

/folder/sharepoint.htm Developer

• Writes custom web parts and applications for /folder/sharepoint.htm in Visual Studio 2005, /folder/sharepoint.htm Designer, and Javascript Editors
• Tests, Debugs, and Deploys custom /folder/sharepoint.htm Solutions
• Documents Custom Solutions
• Develops a better strategy for custom solutions

/folder/sharepoint.htm Trainer/Support

• Works with the Architect and Project Manager to train users on /folder/sharepoint.htm Sites and Concepts
• Creates Webex Sessions and hosts them
• Assists users on how to utilize /folder/sharepoint.htm
• Answers user questions via e-mail, in-person, or webex
• Helps the /folder/sharepoint.htm Architect and /folder/sharepoint.htm Developer understand user related issues better
• Creates documentation faq for users, so that they can better understand /folder/sharepoint.htm Functionality

/folder/sharepoint.htm Designer

• Manages all custom visual content in /folder/sharepoint.htm
• Creates custom templates based on Project Requirements from the /folder/sharepoint.htm Project Manager and User Specifications created by the /folder/sharepoint.htm Architect
• Designs and maintains custom default.master pages, so that changes can be made dynamically and easy
• Creates and maintains custom style sheets based on company and user requirements defined by the /folder/sharepoint.htm Project Manager and /folder/sharepoint.htm Architect
• Works with the /folder/sharepoint.htm Architect to get a better feel for the templates based on user requirements

I am not saying this is entirely accurate.  This is just something that I am still working on and would enjoy any comments people out in the community would be willing to give me.

---

Posted on SharePoint Blogs

It is pretty easy to use JavaScript in your WebParts, and people that know me, know I frickin despise JavaScript. I really, really do. I know sometimes I have to use it, but I would prefer if it didn't exist, even though I might start warming up to Read More......(read more)

When using web browser enabled (InfoPath Forms Services) InfoPath templates that have been published to a SharePoint 2007 site, multi-line textboxes will only display with the height that was specified at design time. If the text box contains text that Read More......(read more)

So your company has just implemented SharePoint, and you're going to start using it on a daily basis. That's a good thing, definitely. You've heard about all the things you'll be able to do with it, and how its going to help you and your teammates work, communicate, and collaborate better (yeah, that last "C" word is probably the one you're going to hear the most). But there's a problem: you start investigating what SharePoint is and your head immediately starts...(read more)

I have pulled together a list of items in SharePoint 2007 that may haunt your custom branding if you don't take special note to address it in the interface. Often while branding SharePoint you can get wrapped up with just working with a single web page while changing your design. There is a large application to worry about and this list will hopefully help you avoid bits and pieces of the old SharePoint look popping up on you after you are done branding SharePoint. If there are other elements...(read more)

Please someone define this term for me....  I had a client use this on me, like I don't have to include a specification for this because it is native sharepoint....  What is that?  I believe effective communication is effective communication and if you want a SharePoint list added to a site that has the template of discussion board, you should write into your specification that you want a sharepoint list with a template of discussion board.  Effective, clear communications is all I am asking for...  Any thoughts here, I believe we should set some standards for specifications if we are to be sharepoint developers.

 

---

Posted on SharePoint Blogs