Browse by Tags
Sorry, but there are no more tags available to filter with.
-
-
Body: Here’s a short list of companies that provide end user training products or information. Rob Bogue’s Shepherd’s Guide – book and licensable content that you can build into your website. http://www.sharepointshepherd.com/default.aspx BrainStorm Inc’s Quick Reference Cards and Computer Based Training http://www.combined-knowledge.com/EUA/index.html (Also see episode 25 of the http://www.sharepointpodshow.com/ ) http://Office.Microsoft.com of course. http://www.endusersharepoint.com/ - @EUSP on twitter. If there are others, let me know about them. Category: SharePoint – WSS and MOSS Published: 9/10/2009 9:17 PM Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: I just found out about this new website for SharePoint Governance: http://SharePointGovernance.org . I like the idea, and have already submitted 4 comments on how to improve what’s there. The biggest gap I see is that it needs text or a link on the home page that explains what SharePoint Governance is. Here’s my attempt: SharePoint Governance is the policies and procedures an organization puts in place in order to maintain an appropriate level of control over the organization's SharePoint deployment. Every organization that deploys SharePoint should have some sort of governance plan. Such a plan, what we at Magenic call a SharePoint Roadmap, can cover a wide variety of management issues. This isn’t about server monitoring, though a governance plan would say that IT must put a server monitoring plan and process in place. This is about how the organization plans to use SharePoint in the short and long term, and what policies they need to create to support that. This can include how the organization plans to deploy, use, and control the wide variety of SharePoint functionality. This can also include defining where the division of control is: collaboration sites for example may have their adoption stunted if IT chooses to exert...
-
-
Body: I’ve been busy with a deployment of an intranet for a smaller firm, and have accumulated a number of items that I want to share. First off, yesterday and today, I ran into an issue where I had my SSP on port 82 (i.e. http://server:82 ) and want it to make it available on it’s own url, http://ssp.demo.local . I have all of this on one machine since it’s a dev environment – windows server 2008 and IIS7 in a HyperV VM, all 64bit to be exact.. When I extended the SSP’s web app to the new web app, the resulting new site would prompt me for authentication 3 times, and then give me a TOTALLY BLANK page. No access denied from IIS, nor from SharePoint. No error messages in the Application Event Log, nothing in the ULS log. In the Security event log, there was a Logon Failure (which made me think it might be a Kerberos issue, but it wasn’t). In the IIS log, there were a set of 401.1 and 401.2 result codes (access denied.). I had entries in my host file that mapped ssp.demo.local to a local static IP address – not 127.0.0.1 but 192.168.21.20. My friend and coworker Ralph (Twitter:@BigPix2000) pointed me to this KB article: http://support.microsoft.com/kb/896861 Next, I run Windows 2008 Server Enterprise on my laptop so I can use HyperV...
-
-
Body: Although no beta code has been released to the public, and I personally have had no access to it via other channels, we know or can make some intelligent guesses about a few things. First, what we know: 64 Bit! SharePoint Server 2010 will be 64 bit only. That means that the web front ends and application servers will run best on the x64 versions of Windows Server 2008 or 2008 R2 (due out this October). Note that it WILL NOT run on Windows Server 2003, x64. SQL Server has to be 64 bit as well, but either 2005 or 2008. Source: Announcing SharePoint Server 2010 Preliminary System Requirements [MSFT SharePoint Product Team Blog] Todd Klindt and Shane Young , on Episode 18 of the SharePoint Pod Show , advise (and it seems like common sense) that if you are only familiar with Windows Server 2003, now is the time to learn Windows Server 2008. You want to avoid having to learn both Windows Server 2008 AND SharePoint Server 2010 at the same time. Windows Server 2008 is different enough from Windows Server 2003 that you should not underestimate this. In particular, the IIS Admin UI (the IIS 7 MMC) is very different than it was in IIS 6/ Win 2003. For your production farms on physical hardware, your vendor should be telling you what hardware...
-
-
Body: You’ve already installed SharePoint. You want to use SSL to secure Central Admin because it is the Right Thing To Do and it makes those annoying warnings go away. Note that you could not do this during installation because psconfig does not provide a command line option for creating Central Admin with SSL. See http://technet.microsoft.com/en-us/library/cc263093.aspx#section2 . You need a certificate, but you don’t need to buy an official one – after all, the only people using the Central Admin site are the Farm Admin(s), and they can set their web browsers to trust a self signed certificate. In fact, if they always remote desktop into the web front end that runs Central Admin, they only have to set the web browser there to trust the self signed certificate issuer. IIS 7 can make a self signed certificate, but will use the server’s full name (FQDN) instead of just the hostname. The url for Central Admin generally just uses the hostname however. That’s where SelfSSL comes in handy. SelfSSL is an IIS 6 resource kit tool. You get it here: details.aspx-FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en . You MUST run SelfSSL from an ELEVATED command prompt (in other words, RUN AS ADMIN!). Then you can use a command like...
-
-
Body: Virtual Lab: A SharePoint Developer Introduction - Page Branding After completing this lab, you will be better able to work with master pages, work with styles sheets, create themes, and use features and feature stapling. Code Sample: Information Management Policy Deployment Sample for SharePoint Server 2007 This sample code for SharePoint Server 2007 shows how to use feature activation to deploy information management policy to content types, including pre-existing content types and sealed content types. Deploying Information Management Policy Using Feature Activation in SharePoint Server 2007 Learn how to operationally deploy policies through SharePoint Server 2007 by using feature activation event handlers and the SharePoint Server object model. Microsoft Certification Exam Coaching: Preparing for Your Microsoft Windows SharePoint Services 3.0 - Application Development Exam (70-541) April 16, 10:00 A.M. Pacific Time What time is this in my region? New Online Course - SharePoint 2007 for Business Users Both new and experienced users will learn how to get the most from SharePoint 2007 with this new course from AppDev. Expert Dan Wahlin covers many features, including building SharePoint collaboration sites, managing documents...
-
-
Body: Webcasts of my sessions at Microsoft Virtual Tech Days on April 1, 2009 are now available on demand at: Site Provisioning Solutions: https://www506.livemeeting.com/cc/sbsgb3/view?id=RS9WRN&role=attend&pw=2MMg%7DhC (downloadable too) Information Architecture for a MOSS Intranet: https://www506.livemeeting.com/cc/sbsgb3/view?id=FQR5J5&role=attend&pw=jgt%21%247J (Streaming only) Let me know what you think of them! --Michael Category: SharePoint – WSS and MOSS Published: 4/7/2009 9:09 AM Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: Recently, I was involved in deploying two solution packages I had created. The farm administrator had just used the the Solution Management page in Central Admin to deploy the packages globally, and the status was "Deploying" but more than the usual amount of time went by and it was still listed as Deploying. To resolve this, we first ran stsadm -o execadmsvcjobs on the server running Central Admin. No change. We then ran stsadm -o execadmsvcjobs on each member of the farm that had OWS Timer (sptimerv3) on it (everything included Reporting Sevices Servers, but not the database servers used only on the back end). At this point, one solution package completed, but the other still did not. We restarted the OWS Timer Service (sptimerv3) on each member in the farm (again, everything that had OWS Timer on it). At that point, both packages completed their deployment and all was well. --Michael Category: SharePoint – WSS and MOSS Published: 3/23/2009 3:44 PM Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: Every year, the Nielsen Norman Group picks the 10 best intranets of the year, and their latest report (2009) is discussed here http://www.useit.com/alertbox/intranet_design.html (look at the section titled "Technology Platform: Unification Begins". The full report and related info is here: http://www.nngroup.com/reports/intranet/design/ . One of the things that caught my eye in Nielsen's January 5, 2009 Alertbox article was that half of the winners they identified used SharePoint. There's also a nice graph showing the increase in adoption of SharePoint among the winning intranets over time. In 2008, SharePoint was the most used Microsoft product - see "Diverse Technology Platforms" in http://www.useit.com/alertbox/intranet_design_2008.html . --Michael Category: SharePoint – WSS and MOSS Published: 1/5/2009 6:53 AM Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: So I am working in a Windows 2003 server virtual machine that is hosted by my client and is a member of their domain. This VM is my development VM, and it has MOSS installed and uses many of the same service accounts that our production environment uses so that it's a realistic development environment. This morning, I went to do a compile of a workflow solution I am working on. I have build scripts set up, and they do several things including manaully deploying a shared utility DLL to the GAC and restarting the WSS timer service (sptimerv3), because some of my workflows that use this DLL run after a delay, and when they run after a delay activity, they run under the context of the WSS Timer, so to make sure that the timer is seeing the latest version of the DLL, as well as any app config changes that I have put in the app config file I created for the timer, I restarted the timer. Except that this is what I got: The Windows SharePoint Services Timer service is not started. More help is available by typing NET HELPMSG 3521. System error 1069 has occurred. The service did not start due to a logon failure. Well, my timer service is using a domain account, and today is 1/2/2009, I am working from home, and the client's office...
-
-
Body: When you create an alert on a list, you have the option of specifying a view which limits which items would trigger the alert. Note however that the list of views you can choose from is a subset of the views available on the list. In fact, if you don't have any views that are ok to use for alerts, you won't even see the option to select a view. What are the rules that determine which views are available for use? Experimentally, my guesses are: 1) It must have a where clause. All Items views don't show up in the list of views, and it's pointless to use an All Items view because it doesn't filter. 2) It must be a public view, it cannot be a personal view. 3) It cannot involve content approval. To try to substantiate these guesses, I went to the source with .NET Reflector ( http://www.red-gate.com/products/reflector/ ). The page to create a new alert is _layouts/subnew.aspx. Its code-behind is the SubNewPage in the Microsoft.SharePoint.ApplicationPages dll. This is in Inetpub\wwwrooot\wss\virtualDirectories\<dir for the web app>\app_bin. You need to open it in Reflector. Some of the other SharePoint DLL's are in the GAC, so you may need to copy those DLL's out of the GAC into a more accessible place...
-
-
Body: Assuming you require your users to fill out a form to request a new site or site collection, one more thing that you may want to ask them for is one or more distinctive keywords that describe the site content. You could then take these and turn them into Best Bets for Search. I'm thinking of this because I am putting together a search page for a customer that has a lot of team sites beneath one site, and menu navigation is not very usable because you get one menu with all subsites, and it's just too long. So I am creating a search page that lets the user search for the subsite instead. Category: SharePoint – WSS and MOSS Published: 11/21/2008 8:29 AM Del.icio.us | Digg It | Technorati | Blinklist | Furl | reddit | DotNetKicks
-
-
Body: A client of mine is a project manager and wanted to create a view of his SharePoint task list that showed items due in the next 10 days. The problem: The filter options in a view let you compare Due Date to [Today] but not to "[Today] + 10". You can't have a formula in the "right-hand side" (bottom box) of you filter expression. We wanted to say "Due Date is less than ([Today]+10)" but it wouldn't accept the phrase [Today]+10. However, you can create a calculated value column that uses a formula. In other words, we wanted to say: due date < Today + 10 but instead we can say: due date - 10 < Today So we added a Calculated Value column to the Tasks list. I named the column DueDateMinusTen, and gave it the formula of "[Due Date] - 10", and said that it returned a date. No need to add it to any views except for testing purposes. One interesting thing that we saw was that if Due Date was empty, DueDateMinusTen was 12/20/1899. Huh? Yes - because the null value for a date is really 1/1/1900. Now that we have the column, we can filter any of our views by using the filter expression DueDateMinusTen < [Today]. Oops, no time for pictures. Maybe later! --Michael Category: SharePoint...