Tristan Watkins on IT Infrastructure
Technical guidance for Microsoft security technologies, Windows, SharePoint, and other generally useful findings
SharePoint 2010 ULS logging adds a very useful new column called the Correlation ID. The ID tracks a request and greatly simplifies finding detailed error logging in SharePoint trace logs. Additionally, Mattias Karlson points out that there’s a new CodePlex project called ULSViewer which parses SharePoint 2010 logs in a friendly view.
The correlation ID in a SharePoint 2010 error message:
The Trace logs in ULS Viewer, filtered by the Correlation ID:
It’s now a week on from Mark Russinovich’s NewSID retirement announcement and I’ve been watching the feedback since. To give a brief overview, it’s long been a tenant of machine cloning processes that a new machine SID should be generated for each clone in order to prevent conflicts. Mark Russinovich wrote the original NewSID tool for Windows NT and as a Microsoft Technical Fellow today, he supposed that it might not be needed anymore and investigated the implications of retiring it. Obviously, if you haven’t read it yet and you work with machine cloning, you should read the article, but if you haven’t found the time to sift through the 168 comments (and counting), this summary might help clarify things:
Continue reading “NewSID myth implications for SharePoint development”
Taking a quick break from the SharePoint development series (I hope to finish part IV tonight), Matt Groves has a fix for a slightly more perturbing version of the DCOM IIS WAMREG 10016 error with SharePoint 2010 on Windows Server 2008 R2. His fix works a treat, but I’d recommend granting rights to the WSS_WPG and WSS_ADMIN_WPG local groups in order to make this a permanent fix.
Having agreed the project objectives and designed the system, I turned my attention to the Hyper-V host image build. This is a high-level build guide with start-up time and baseline memory consumption benchmarks at key milestones. These benchmark figures were taken from the Windows Server 2008 R2 Release Candidate build and are admittedly a bit imprecise. However, they do provide an overall indication of system performance as things were added to and removed from the installation. Although I do not have precise figures on RTM improvements, I spot-checked a few of these benchmarks when I rebuilt the system on RTM. Start-up times improved slightly at each milestone. In fact, the final benchmarks came in at 100MB less idle memory used in the RTM release. Continue reading “Building a SharePoint 2007/2010 development environment — Part III: Host image build and performance benchmarks”
In the first part of this series, I introduced the pros and cons of various SharePoint development approaches and the objectives of this system redesign. In this part I will focus on design choices and conclusions, starting with the core technology.
There are broadly five decisive factors: performance, management features (like snapshots), cost, 64-bit OS support and a full host OS (not just a virtualisation administration console): Continue reading “Building a SharePoint 2007/2010 development environment — Part II: Design”
As I’ve alluded to a few times in this blog, over the last few months I’ve led the consultancy and system design for a SharePoint 2007/2010 development environment built on Hyper-V in Windows Server 2008 R2. This series of six posts will reveal the key decisions and will consolidate recommendations from a broad range of research and guidance. This first post offers a technology-agnostic introduction to the problem, pros and cons of alternative approaches and what we hoped to achieve with the new approach. The design decisions will be covered in more detail in the second post, followed by a deeper look at detailed build guidance. Continue reading “Building a SharePoint 2007/2010 development environment — Part I: Introduction and Objectives”
This is the final post in a six-part series on SharePoint 2007 administrative commands. So far I’ve covered:
In this post I will review Site-scoped administrative functions. Continue reading “SharePoint 2007 administration part VI: Site administration”
It’s now nearly 180 days since the MOSS 2007 SP2 product expiration problem was discovered. Any systems that are running with the original version of SP2 will expire 180 days after it was installed. There are some quite simple solutions to this problem, but it’s worth assessing the state of your systems to make sure they aren’t at risk.
If the original version of SP2 has been installed on any systems, this can be fixed by re-entering the original product key or by applying this hotfix. If the service pack installer was downloaded after 29/7/09, this fix is included. Any questions should be answered by the original post’s Q&A.
This is the fifth post in a six-part series on SharePoint 2007 administrative commands. So far I’ve covered:
In this post I will review Site Collection-scoped administrative functions. Continue reading “SharePoint 2007 administration part V: Site Collection administration”
This is the fourth post in a six-part series on SharePoint 2007 administrative commands. The first part was an overview, the second covered Farm administration, the third covered web application administration, and this post is devoted to Shared Service Provider (SSP) administration. The bulk of this post only applies to MOSS, as there is no SSP for WSS. Continue reading “SharePoint 2007 administration part IV: SSP administration”
You must be logged in to post a comment.