Skip to content

System.DirectoryServices.Protocols (a.k.a. LDAP is your friend)

I’ve had the displeasure of trying to do some work with LDAP in .NET lately.  The interfaces are all there but the documentation and error handling isn’t.  (Read: The lights are on but no one is home.)  Because of this I was pleased to find there was a book out on the subject The .NET Developers Guide to Directory Services by Joe Kaplan and Ryan Dunn.

I also had the pleasure of sharing an email conversation with Joe.  I initiated a conversation with him slightly before I was able to pickup the book – because of his activity in the newsgroups.  I quickly figured out I needed to pick up the book and did.  I highly recommend it because the information that is contained in it is both unique — because it doesn’t exist elsewhere — and is easy to understand.  LDAP may be common but it’s not something that most developers do every day.  Back to my point, there were some interesting things that came out of that conversation.  I wanted to highlight them in part to document them and in part to thank Joe for his help.

1) System.DirectoryServices vs. System.DirectoryServices.Protocols – What I was trying to do was to develop a high performance LDAP ASP.NET 2.0 Membership Provider for a project.  In order to do that, I was going to be using LDAP to authenticate a large number of users.  One of the issues with System.DirectoryServices is cleaning up all of the connections quick enough in a high load environment.  The net of the conversation with Joe – which I agreed with wholeheartedly as I began to understand the underlying characteristics of System.DirectoryServices – was if you need to control cleanup of connections use System.DirectoryServices.Protocols.  The end I came to was that I think of System.DirectoryServices as a façade over System.DirectoryServices.Protocols.  Façade is a pattern that makes using something easier.

2) SSL is not your friend – There are lots of things to think about when trying to use SSL to encrypt your LDAP communications.  First, if you are using clients all in a domain, add an Enterprise Certification Authority to the domain.  If you do that the domain controllers will enroll themselves and start accepting SSL connections for LDAP – that’s cool.  If you don’t have all internal clients, you can refer to this KB article to add a third party certificate.  Even with it working (and tested via LDP) you may have a problem when you try to set SecureSocketLayer support.  You may receive a less than helpful DirectoryOperationException(“The server cannot handle directory requests.”) what isn’t quite so amusing about this is that it didn’t even try to communicate with the server.  The solution was to add the port number to the server.  So instead of passing “Server” to open the LdapConnection, I passed “server:636”.  By the way, LDAPS is port 636 – rather than the 389 port used by LDAP.

3) Fast Concurrent Bind isn’t really a bind – In LDAP you bind to associate credentials to your connection so that it can use those credentials to validate your operations.  One of the things that S.DS.P supports is the idea of a Fast Concurrent Bind.  Basically, check my credentials to make sure that they’re OK – and don’t do anything else.  I tried using Fast Concurrent Bind (because it is the fastest way to validate a user) to bind to a connection and then do a search.  So I did my bind and then did my search.  When I tried the search I got an exception – DirectoryOperationException(“An operation error occurred”) when I dug into the network capture I found a deeper message: “LdapErr: DSID-0C090627, comment: In order to perform this operation a successful bind must be completed on the connection., data 0, vece”  It was funny because message 5 was a bind with a success response and message ID 6 – the one I got the error on was a search.  The issue at the end of the day I was I was using fast concurrent bind.  So I wasn’t really doing a full bind at all.  I was just authenticating the user.

With Joe’s help I was able to figure out what the issues were … and create a working solution.

Bad Error – Missing User Controls in a Master Page in SharePoint

I had a customer come to me with a problem that they were getting a “File Not Found.” error while trying to move a site collection backup from one system to another.  The client is supposed to deliver their customizations via solutions files.  So I turned off custom errors, turned on the call stack and got this:

Server Error in ‘/’ Application.

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

Of course, that isn’t much help.  After some fun digging with SharePoint Spy and with SharePoint Designer, I discovered that the user control which was referenced in the custom master page (MasterUrl) didn’t exist in the directory it was being referenced from.  It turns out they had delivered the user controls outside of solutions packages to the integration environment.  The master file referenced them from the root of the ControlTemplates directory.  When they were packaged up they got deployed to a subdirectory of ControlTemplates – like they’re supposed to.   The problem is on a new server the controls weren’t in the root which caused the master page not to load which wasn’t well handled by SharePoint.  (Frankly, not that it should have been but an error in one of the logs would have been nice.)

Correct the master page location for the user controls and the problem goes away.

SharePoint and Office Pro Plus

Most of the time, I don’t pay much attention to which specific package of Office that I’m using. I’m not talking version.  I’ve been running Office 2007 for more than a little bit now.  I’m not talking about that.  What I’m talking about is which edition I’m using.  Let me explain.

Microsoft sells the office bundle in Basic, Home & Student, Standard, Small Business, Professional, Professional Plus, Ultimate, and Enterprise versions.  There’s a good grid showing which programs you get with each version on the Microsoft Office Online site at https://www.microsoft.com/en-us/store/b/office.

However, what’s not clear is that you can’t always assume that what you see is what you get – when you want to integrate with SharePoint.  You see there’s “magic” in Professional Plus, Enterprise, and Ultimate.  That “magic” does SharePoint integration “stuff”.  Some of it’s obvious.  Without InfoPath the document information panel (which is really an infoPath form) doesn’t work.

However, one of the issues that I ran into was that there’s some property copying stuff that’s supposed to work to enable SharePoint server based properties to be visible in the Office documents – in my case word.   I had installed Office Professional in my test environment and added InfoPath later.  As a result my Document Information Panel worked – but the properties weren’t getting copied back to the document – only when they were in a content type.

I uninstalled Office Pro and Infopath and resinstalled Office Ultimate to test and the problem went away.

This isn’t conclusive proof that the issue I was facing was due to trying to use Office Professional plus an installation of InfoPath to work with the server, but it’s a strong indication that there’s something missing when this is done.  So from now on if I need Office and SharePoint to have the best friendship … I’m going to be using Professional Plus or better … something that ships with InfoPath in the box.

No more Office Professional and SharePoint for me…  Now if I could just figure out how to get that time back…

Article: Using SharePoint Solutions to Deliver Server-Side Solutions

Discover an elegant technique for creating and deploying solutions that provide reusable processes for installing and uninstalling custom code.

If you’ve ever worked on more than the most trivial installation program, you realize that developing installers isn’t for the faint of heart. After spending days or weeks learning about the MSI file format, how to assemble tables, and how to add dialogs, you’re left with a collection of documentation that reaches from the floor to the ceiling, and you can feel just as lost as when you began. Further, the experience doesn’t help much when you need to deliver the software in a silent or automated way. You need to acquire additional knowledge to handle automated setup files.

At first glance you might wonder why there’s a feature in SharePoint Technologies called “Solutions.” The Solutions framework seems to be a direct competitor with the Microsoft Windows Installer technology—and its MSI file format—but it isn’t. Where the Windows installer is targeted toward client-side application installation, the SharePoint Solutions approach is targeted toward delivering complete solutions to SharePoint Servers.

This discussion will walk you through the deployment of a semifictional application, WFInspector, which is a workflow inspector tool. The tool itself is of marginal value because it doesn’t add much functionality beyond what is available out of the box; however, it’s very representative of the kinds of solutions that you may want or need to deploy.

http://www.devx.com/enterprise/Article/34676

Article: Deliver Web Parts with Solutions Packages

SharePoint is the first major application to apply Code Access Security (CAS) in a real way. CAS is a great way to protect your Web application from unauthorized code. However, CAS’s implementation in Windows SharePoint Services 2.0 still left a lot of the heavy lifting to the developers and administrators managing the server. With the introduction of Solutions (a specific feature called Solutions) you have the opportunity to deploy code access security when you deploy Web Parts to the server. This article discusses how to work with Solutions.

http://mssharepoint.advisorguide.com/doc/19010 [Website removed]

Getting an Image thumbnail from WSS 3.0

I recently needed to have thumbnails for some images that we uploaded to SharePoint for display in a thumbnail library.  I couldn’t find any documentation on how to get a thumbnail for an image.  So I fired up Fiddler opened up the script and figured out what the hundreds of lines of JavaScript was doing behind the scenes.

Basically, you take an append _t to the directory, convert the period in the file name to an underscore and append .JPG.  Here are a few examples:

Image URL Thumbnail URL
http://server/site/web/PicLibrary/MyImage.gif http://server/site/web/PicLibrary/_t/MyImage_gif.jpg
http://server/PicLibrary/AnotherImage.jpg http://server/PicLibrary/_t/AnotherImage_jpg.jpg

Using a _w instead of a _t seems to give a slightly larger image.  This might be useful for hover over events.

circuit board

The Fall and Rise of a Server

Some of you may have noticed an extended outage of the server that serves this blog, Hazel Dell Christian Church’s web site (www.hdchristian.org) and some of the ancillary sites that I support.  This outage was caused by a string of problems the likes of which I’ve never seen at any client – but I’m really glad it hit me rather than a client.

Clean Living

I feel compelled to tell you that the server – RENEGADE – has had a clean life.  By that I mean it’s always been in a data center or collocation facility.  As a result it got clean steady power and a temperature and humidity controlled environment.  It’s not one of those servers shoved under my desk, hidden in a closet under a fichus plant, or any other of the strange things clients do to servers.  Despite its clean living it had a series of issues that started May 4th.

Wake Up Call

On Friday morning I woke up away from my office in Danbury, CT.  I noticed that I didn’t get any mail since about 12:45 AM.  Looking down I saw that Exchange was disconnected.  When I investigated further I found that the whole server was offline.  A call to my friends at BlueLock and the server was back up.  I saw that it was at 0x00000077 bug check that brought the server down.  I didn’t bother checking into it much because I was on client site.

Echos of Nightmares

I can’t think of much more disturbing than a server going back down 20 minutes after I brought it up.  That’s what happened to me.  Another break from the client and another call had the guys unracking the server and arranging to transport it to my house – I can’t tell you how grateful I am for the guys at BlueLock.  Not only am I not really on their platform but because of our long friendship they were bending over backwards to make sure that I was taken care of.

But How Late is Late?

So I flew in later that night and set about figuring out what was wrong.  The initial analysis was strange.  The bugcheck is most likely caused by a disk read error while reading the paging file.  That would be odd in and of itself, but even odder when you consider that the server has mirrored drives – a mirror that reported healthy when I looked at it in Disk Manager.  Still new disks are relatively cheap and it’s an excuse to upgrade storage but alas Fry’s isn’t open 24 hours a day yet so at 3 AM I go to bed to go get drives in the morning.

Stupid is as Stupid Does

Here is where I made the critical mistake.  I had an opportunity to start a backup before I went to bed – or before I left for Fry’s in the morning.  I didn’t.  Frankly I didn’t expect any problems.  It would have been a *REALLY* good idea to have taken a backup at this point.

Broken Mirrors

So I get back, install one of the new drives, remove one of the old drives and try to start a mirror … and it fails.  A few more attempts and I break out Ghost 2003.  I try to get Ghost to image the drive across – and get an internal error and decide to give up.  I’ve not had any great luck with Ghost and I had considered trying the upgrade – but when Symantec’s web site told me I couldn’t upgrade I felt like I was not going to get anything from it.  (Certainly didn’t feel like they valued existing customers.)

So I placed the other drive into the system and tried to use it to make a copy to one of the new drives.  That was fun – except for the fact that the drive wouldn’t boot – and after trying to recover the MBR the partition table was unreadable.  It turns out it doesn’t matter anyway because it wouldn’t stay operational for more than a few minutes at a time anyway.  (I’m really confused how the mirror reported healthy at this point.)

Step Back and Punt

I have a backup – it’s a week old but frankly there’s not that much going on in my system that a week is that big a problem.  (Remember above I should have taken another backup.)  So I install the server again with a new name and build the OS.

This seemingly takes an eternity.  I go to restore the system state – a part of my backup – and I find to my dismay that I don’t have a system state backup.  Sure I placed it in the selection list but despite my best efforts, I can’t get the stupid thing out of the backup file.  Of course, that means I have to reload a bunch of software – but I can manage.

Chasing My Tail

I rebuilt the system and got it operational with drivers and such.  I go to start putting back services and start running into problems.  I spend several (ok more than that) hours trying to get Exchange to accept the backups and it’s not working.  I place a call to Microsoft product support to get some help but the technician I got was unable to understand the case # I gave him, wasted 30 minutes trying to talk to a technical router, and basically got me so frustrated with him and the team’s service that I decided that I’d deal with it another time.

I did manage to get the server accessible from the outside via terminal services – which is important because I was leaving on Sunday evening to fly to Anaheim to the Advisor Summit on Microsoft SharePoint.  That meant leaving the server down including web sites, mail, etc.  Not something I was looking forward to.

Google isn’t Completely Evil

Before leaving I did one other thing was setup Google for Domains to take care of my mail – including my wife’s mail, my assistant, etc.  I tested it and it was working.  However, rather than setting up DNS like they wanted I took my existing Anti-Spam/Anti-Virus vendor and pointed their output to Google instead of my server – I figured that would minimize the DNS instability time when I came back online.

You’ve never had fun until…

While in Anaheim, between my presentations, I found enough time to start working on the server some more.  I ended up calling back in to Microsoft for a three hour phone call to fix Exchange.  It seems that my online backup that I did was corrupt.  We ended up doing a soft recovery on the off-line backup I took as well (while Exchange was running.)  I managed my own way through a set of issues with the SQL 2005 installer which requires precise folder names if you’re installing from a drive rather than CD media.  (Remember I’m miles away …)  the net effect is that by the time I make it home I’ve got most of the operations working on the server and I should literally not need to do much more than plug it in.

I decide not to move mail over to the server because I’m on a home cable modem and frankly I think every home cable modem is blacklisted for mail.  It’s easier just to wait until the next day to plug things in since the critical thing – email – had a workaround.

Or so I thought…

Well, that’s what I thought until my assistant called and told me she couldn’t log in to Google.  Despite Google continuing to receive mail for the domain they had shut off email for users – without notifying me – because they perceived that I didn’t have email configured correctly.  I managed to “bump” Google and get it convinced to reinstate the email accounts – thanks to the free WiFi at Phoenix SkyHarbor airport.

Back in the Saddle

The next day I put the server back in the rack test operations and find everything working … except for SSL certificates, a few weird web site quirks, and the assorted other issues that I had dealt with over the years but since I lost my system state I needed to redo.

What did I learn from this?

If you’re like most of the folks that I relate this story to you’re saying “What are the odds?”, “How unlucky can you get?”, “You’re pulling my leg, right?”, etc.  My perspective is how I started out – I’m glad it happened to me where the impact is containable rather than to a client.  The lesson is a bit more complicated.  The short is that multiple layers of redundancy WILL fail.  It’s just a matter of when.  Should have all of these things happened at the same time?  No.  Could it happen to you? Yes.  So my question is, how many things have to go wrong before you lose too much data or have a failure you really can’t recover from?

 

disks

List of Features with GUIDs

It turns out I needed to be able to locate a feature by it’s GUID so I wrote a quick tool that dumps out the feature definitions and their associated directory names.  The results from a MOSS 2007 Enterprise server appear below:

ID  Scope  Name  Installed By
001f4bd7-746d-403b-aa09-a6cc43de7942 Farm PublishingStapling 00000000-0000-0000-0000-000000000000
00bfea71-1c5e-4a24-b310-ba51c3eb7a57 Site BasicWebParts 00000000-0000-0000-0000-000000000000
00bfea71-1e1d-4562-b56a-f05371bb0115 Web XmlFormLibrary 00000000-0000-0000-0000-000000000000
00bfea71-2062-426c-90bf-714c59600103 Web LinksList 00000000-0000-0000-0000-000000000000
00bfea71-2d77-4a75-9fca-76516689e21a Web workflowProcessList 00000000-0000-0000-0000-000000000000
00bfea71-3a1d-41d3-a0ee-651d11570120 Web GridList 00000000-0000-0000-0000-000000000000
00bfea71-4ea5-48d4-a4ad-305cf7030140 Web WorkflowHistoryList 00000000-0000-0000-0000-000000000000
00bfea71-4ea5-48d4-a4ad-7ea5c011abe5 Web TeamCollab 00000000-0000-0000-0000-000000000000
00bfea71-513d-4ca0-96c2-6a47775c0119 Web GanttTasksList 00000000-0000-0000-0000-000000000000
00bfea71-52d4-45b3-b544-b1c71b620109 Web PictureLibrary 00000000-0000-0000-0000-000000000000
00bfea71-5932-4f9c-ad71-1557e5751100 Web IssuesList 00000000-0000-0000-0000-000000000000
00bfea71-6a49-43fa-b535-d15c05500108 Web DiscussionsList 00000000-0000-0000-0000-000000000000
00bfea71-7e6d-4186-9ba8-c047ac750105 Web ContactsList 00000000-0000-0000-0000-000000000000
00bfea71-a83e-497e-9ba0-7a5c597d0107 Web TasksList 00000000-0000-0000-0000-000000000000
00bfea71-c796-4402-9f2f-0eb9a6e71b18 Web WebPageLibrary 00000000-0000-0000-0000-000000000000
00bfea71-d1ce-42de-9c63-a44004ce0104 Web AnnouncementsList 00000000-0000-0000-0000-000000000000
00bfea71-dbd7-4f72-b8cb-da7ac0440130 Web DataConnectionLibrary 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
00bfea71-de22-43b2-a848-c05709900100 Web CustomList 00000000-0000-0000-0000-000000000000
00bfea71-e717-4e80-aa17-d0c71b360101 Web DocumentLibrary 00000000-0000-0000-0000-000000000000
00bfea71-eb8a-40b1-80c7-506be7590102 Web SurveysList 00000000-0000-0000-0000-000000000000
00bfea71-ec85-4903-972d-ebe475780106 Web EventsList 00000000-0000-0000-0000-000000000000
00bfea71-f381-423d-b9d1-da7a54c50110 Web DataSourceLibrary 00000000-0000-0000-0000-000000000000
00bfea71-f600-43f6-a895-40c0de7b0117 Web NoCodeWorkflowLibrary 00000000-0000-0000-0000-000000000000
0125140f-7123-4657-b70a-db9aa1f209e5 Farm FeaturePushdown 00000000-0000-0000-0000-000000000000
02464c6a-9d07-4f30-ba04-e9035cf54392 Site ReviewWorkflows 00000000-0000-0000-0000-000000000000
034947cc-c424-47cd-a8d1-6014f0e36925 Web MySiteQuickLaunch 00000000-0000-0000-0000-000000000000
065c78be-5231-477e-a972-14177cc5b3c7 Web BizAppsListTemplates 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
068f8656-bea6-4d60-a5fa-7f077f8f5c20 Web OsrvLinks 00000000-0000-0000-0000-000000000000
0806d127-06e6-447a-980e-2e90b03101b8 Web PremiumWeb 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
0b4aad40-406f-425c-bdd9-5894c42cffcb Web OsrvTasks 00000000-0000-0000-0000-000000000000
0be49fe9-9bc9-409d-abf9-702753bd878d Web SlideLibrary 00000000-0000-0000-0000-000000000000
0ea1c3b6-6ac0-44aa-9f3f-05e8dbe6d70b WebApplication PremiumWebApplication 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
0f121a23-c6bc-400f-87e4-e6bbddf6916d Farm ContentLightup 00000000-0000-0000-0000-000000000000
0faf7d1b-95b1-4053-b4e2-19fd5c9bbc88 Farm MySiteCleanup 00000000-0000-0000-0000-000000000000
10bdac29-a21a-47d9-9dff-90c7cae1301e Web OssNavigation 00000000-0000-0000-0000-000000000000
11df38ab-5bbb-4304-9da8-221c5c4100b0 Farm SpsSsoLinks 00000000-0000-0000-0000-000000000000
14173c38-5e2d-4887-8134-60f9df889bad WebApplication PageConverters 00000000-0000-0000-0000-000000000000
14aafd3a-fcb9-4bb7-9ad7-d8e36b663bbd Site LocalSiteDirectoryControl 00000000-0000-0000-0000-000000000000
1dbf6063-d809-45ea-9203-d3ba4a64f86d WebApplication SearchAndProcess 00000000-0000-0000-0000-000000000000
1ec2c859-e9cb-4d79-9b2b-ea8df09ede22 Farm DMContentTypeSettings 00000000-0000-0000-0000-000000000000
22a9ef51-737b-4ff2-9346-694633fe4416 Web Publishing 00000000-0000-0000-0000-000000000000
24d7018d-bf48-4813-a28d-dbf3dba173b1 Site PublishingB2TRHop2SiteFilesUpgrade 00000000-0000-0000-0000-000000000000
2510d73f-7109-4ccc-8a1c-314894deeb3a Web ReportListTemplate 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
29d85c25-170c-4df9-a641-12db0b9d4130 Web TransMgmtLib 00000000-0000-0000-0000-000000000000
2ac1da39-c101-475c-8601-122bc36e3d67 WebApplication SPSearchFeature 00000000-0000-0000-0000-000000000000
2ed1c45e-a73b-4779-ae81-1524e4de467a Site WebPartAdderGroups 00000000-0000-0000-0000-000000000000
2fa4db13-4109-4a1d-b47c-c7991d4cc934 Web UpgradeOnlyFile 00000000-0000-0000-0000-000000000000
306936fd-9806-4478-80d1-7e397bfa6474 Web RedirectPageContentTypeBinding 00000000-0000-0000-0000-000000000000
319d8f70-eb3a-4b44-9c79-2087a87799d6 Farm GlobalWebParts 00000000-0000-0000-0000-000000000000
389156cf-498b-41cd-a078-6cb086d2474b Site pwsctypes 538c0384-48ab-483d-90ac-e3a09f755ca5
395702f0-184c-46a2-9bb5-0a64b048738c Farm Analytics 00000000-0000-0000-0000-000000000000
3cb475e7-4e87-45eb-a1f3-db96ad7cf313 Site ExcelServerSite 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
3f59333f-4ce1-406d-8a97-9ecb0ff0337f Web BDR 00000000-0000-0000-0000-000000000000
4248e21f-a816-4c88-8cab-79d82201da7b Site BizAppsSiteTemplates 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
43f41342-1a37-4372-8ca0-b44d881e4434 Site BizAppsCTypes 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
448e1394-5e76-44b4-9e1c-169b7a389a1b Web pwsrisks 538c0384-48ab-483d-90ac-e3a09f755ca5
4750c984-7721-4feb-be61-c660c6190d43 WebApplication OSearchEnhancedFeature 00000000-0000-0000-0000-000000000000
49571cd1-b6a1-43a3-bf75-955acc79c8d8 Site MySiteHost 00000000-0000-0000-0000-000000000000
4d0d9bec-5103-4663-b88d-27cfab1029ff Farm FeaturePushdownTask 00000000-0000-0000-0000-000000000000
4f56f9fa-51a0-420c-b707-63ecbb494db1 WebApplication BaseWebApplication 00000000-0000-0000-0000-000000000000
525dc00c-0745-47c0-8073-221c2ec22f0f Web pwsdoclibs 538c0384-48ab-483d-90ac-e3a09f755ca5
541f5f57-c847-4e16-b59a-b31e90e6f9ea Web NavigationProperties 00000000-0000-0000-0000-000000000000
56dd7fe7-a155-4283-b5e6-6147560601ee Web AnalyticsLinks 00000000-0000-0000-0000-000000000000
5a979115-6b71-45a5-9881-cdc872051a69 Site BizAppsFields 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
5b1e6e3b-83c2-483b-8500-16a025777ed1 Web GradualUpgrade 00000000-0000-0000-0000-000000000000
5f3b0127-2f1d-4cfd-8dd2-85ad1fb00bfc Site PortalLayouts 00000000-0000-0000-0000-000000000000
60d1e34f-0eb3-4e56-9049-85daabfec68c Web pwsissues 538c0384-48ab-483d-90ac-e3a09f755ca5
612d671e-f53d-4701-96da-c3a4ee00fdc5 Farm SpellChecking 00000000-0000-0000-0000-000000000000
65d96c6b-649a-4169-bf1d-b96505c60375 Farm SlideLibraryActivation 00000000-0000-0000-0000-000000000000
6928b0e5-5707-46a1-ae16-d6e52522d52b Site MySiteLayouts 00000000-0000-0000-0000-000000000000
695b6570-a48b-4a8e-8ea5-26ea7fc1d162 Site CTypes 00000000-0000-0000-0000-000000000000
69cc9662-d373-47fc-9449-f18d11ff732c Farm MySite 00000000-0000-0000-0000-000000000000
6adff05c-d581-4c05-a6b9-920f15ec6fd9 Web MySiteNavigation 00000000-0000-0000-0000-000000000000
6c09612b-46af-4b2f-8dfc-59185c962a29 Site SignaturesWorkflow 00000000-0000-0000-0000-000000000000
6d127338-5e7d-4391-8f62-a11e43b1d404 Farm RecordsManagement 00000000-0000-0000-0000-000000000000
6e53dd27-98f2-4ae5-85a0-e9a8ef4aa6df Web LegacyDocumentLibrary 00000000-0000-0000-0000-000000000000
7094bd89-2cfe-490a-8c7e-fbace37b4a34 Site Reporting 00000000-0000-0000-0000-000000000000
713a65a1-2bc7-4e62-9446-1d0b56a8bf7f Farm SPSDisco 00000000-0000-0000-0000-000000000000
750b8e49-5213-4816-9fa2-082900c0201a Web IPFSAdminWeb 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
75a0fea7-0017-4993-85fe-c37971507bbc Web ProjMilestones 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-02cb-4f87-bb11-1ffde748a953 Web HelpDeskModules 3d7fb834-5d7d-48e9-b66f-194fde445c0c
75a0fea7-040e-4abb-b94b-32f1e7572840 Web AVMAbsencesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-056a-445f-9a78-db1b38bb0b74 Web AVMListInstances d9d569e3-ec65-4e38-a1b0-b3b3ff1aef8e
75a0fea7-07c7-453d-866c-979c401d0105 Web DocumentReviewModules 5e33b0a9-1aaa-4509-8b2d-0e60abefdbca
75a0fea7-08d9-4a8f-b1cd-953d4f15467f Web ResourceTypesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-0cb9-4862-8e76-9f5e149236f5 Web CallCenterCustomer 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-0e55-4249-b117-4757adfcc704 Web CompProcListInstances 8b9300af-e90f-4b49-9309-ebafb126a7bf
75a0fea7-12fa-4e77-a477-d75778ef90e9 Web ProjModules 25d59dca-500c-41c0-bc5d-1894b9bb1e11
75a0fea7-12fe-4cad-a1b2-525fa776c07e Web KnowledgeBaseKeywordsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-1651-4b91-8cdf-3f24e57526ed Web ProjChangeCRList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-1757-461b-8997-6c3a4afd86c9 Web RecruitingModules 0ebcf2cc-6297-4354-bf55-2962f423a386
75a0fea7-1906-4f0d-8e04-96eaefb60294 Web CompProcModules 8b9300af-e90f-4b49-9309-ebafb126a7bf
75a0fea7-24d7-4907-81ec-2d71dd3dfde9 Web DRProvisioningFeature 5e33b0a9-1aaa-4509-8b2d-0e60abefdbca
75a0fea7-2791-45a2-896f-e538f91032d8 Web ProjProjects 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-2812-45ce-aa8a-b0a8e7c70151 Web ERModules c430946f-ca17-4925-bdc6-868a47f7877f
75a0fea7-2d1e-451a-b445-16bc346d7d8e Web BugList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-30ba-45d8-bf12-3c0855491ad1 Web LendingLibraryTransactionsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-3737-40a1-b908-c325e30d77de Web InventoryTrackingModules f9dbe862-60d5-4de5-92f1-1544f51647d3
75a0fea7-377d-4b4f-b864-984379ed0f42 Web ResourcesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-37d2-484b-b362-dcff1538e2a4 Web BugTrackingListInstances 0e2f7540-e92f-4eb2-b916-cb2364c3941c
75a0fea7-3a7f-40c2-bf9c-503f36caca93 Web InventoryTrackingListInstances f9dbe862-60d5-4de5-92f1-1544f51647d3
75a0fea7-3b2a-4838-8a0c-57ba864feed3 Web HelpDeskTasks 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-3cc9-4c20-bf74-9bfa9fd5d614 Web DocumentReviewDiscussionList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-42e8-4527-8313-f63c4c49a7e6 Web BugCategoriesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-4d56-4479-a469-230a0eb68184 Web SalesOpportunitiesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-518a-485e-841d-ababd2145e27 Web RecruitingCandidatesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-51e8-4065-a3ef-a2b24f209dca Web ITTeamWorkflows bed8bd64-d0ac-469a-96fc-cb867001368a
75a0fea7-5797-48cd-958d-805cbf270087 Web CompProcCompReg 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-57fb-44e4-ac79-48513cac5416 Web ReservationsListInstances 1df107e5-6d9b-4490-bf91-28cb419748c7
75a0fea7-585d-4862-b7e8-2fdef3ccc537 Web CallCenterModules 08ec3335-c9b0-458b-a848-6d739b6a74e5
75a0fea7-5871-41eb-bac0-5ecedf198c44 Web RecruitingListInstances 0ebcf2cc-6297-4354-bf55-2962f423a386
75a0fea7-5dd8-40af-b960-12af3053f5ec Web LendingLibraryList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-5f52-4bb0-aef8-bd4135d19e5e Web SalesTeamListInstances 964e2241-baa9-49d4-8ae8-aef77d4a07d6
75a0fea7-5f69-4282-83ae-22808c0fbfd9 Web ContactManagementModules 96555d19-e225-44f9-92e7-5efc880bc8c4
75a0fea7-625d-4b31-be9e-24cee53d0d72 Web AssetTrackingAssetsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-6667-4a63-9224-5108aca1c5de Web LendingLibraryListInstances 1a76aee6-bad7-4934-b8d7-5cc4d933db21
75a0fea7-6e3f-4d4a-8f78-245bda567b60 Web RecruitingCandidateFeedbackList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-70e3-40b1-b395-c06f85d0d158 Web HelpDeskSupportFaqList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-7370-403f-a48c-fd5e141ea776 Web ITProvisioningFeature f9dbe862-60d5-4de5-92f1-1544f51647d3
75a0fea7-7478-44e1-8b39-d600e3f4f53f Web EPPersonalEvents 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-76e5-47c4-931a-a90da71c69b7 Web AssetTrackingListInstances 8ed0be87-c777-421e-88cf-024a5a76dbc5
75a0fea7-775b-4ae1-bbc6-ad5ef0d22413 Web DocumentReviewDocsForReviewList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-7851-4350-a082-3b2476621a57 Web AVMModules d9d569e3-ec65-4e38-a1b0-b3b3ff1aef8e
75a0fea7-7afc-4a13-b91a-7dc661f04785 Web RecruitingRequisitionsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-7c51-4a75-92c1-cbaccb371622 Web KnowledgeBaseListInstances 975d6932-0820-41e3-82fe-bb4f8889d935
75a0fea7-7ce3-4ba1-84b7-4bd9da4c9468 Web AssetTrackingProposalsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-7f1b-4b63-a41c-2a2a55fa2709 Web SalesAccountsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-8464-4a6e-9d51-f370bb34ee9c Web CallCenterServiceRequestsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-84d9-447d-b9ec-bc49570874db Web KBProvisioningFeature 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-85b8-4e88-8a0b-3a04a572e20c Web KnowledgeBaseModules 975d6932-0820-41e3-82fe-bb4f8889d935
75a0fea7-86b0-4778-b957-7d6953160dbd Web EPModules c5932b68-e0b1-4879-aa4a-c3099d183297
75a0fea7-8b9f-489a-a971-497418e43698 Web ProjChangeModules 6ec9e585-6d56-4d2b-911e-2e3b99948e35
75a0fea7-8d3c-455d-89d3-4ece8739402d Web AVMAbsenceTypeList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-90ea-4d39-9749-bacfe713d4bb Web AssetTrackingModules 8ed0be87-c777-421e-88cf-024a5a76dbc5
75a0fea7-92c2-4fdf-9b21-8cfbb6d3b240 Web AssetTrackingCategoriesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-9454-48ab-883d-ede5b98710d6 Web ProjIssues 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-9507-49c7-a473-0ce55c18ef89 Web ERExpenseFormsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-97c5-4487-88e4-70fde8f79b25 Web HelpDeskListInstances 3d7fb834-5d7d-48e9-b66f-194fde445c0c
75a0fea7-9c7f-4881-b7f1-7d0271a1ea16 Web ERListInstances c430946f-ca17-4925-bdc6-868a47f7877f
75a0fea7-9d96-4f02-a800-a3512154efcd Web BugTrackingModules 0e2f7540-e92f-4eb2-b916-cb2364c3941c
75a0fea7-9f82-4120-96a3-6a3f93272a97 Web ReservationsModules 1df107e5-6d9b-4490-bf91-28cb419748c7
75a0fea7-a4ce-4a83-867d-f6be0ffdd867 Web ContactManagementListInstances 96555d19-e225-44f9-92e7-5efc880bc8c4
75a0fea7-a64d-4dfa-a39f-d0076127771e Web InventoryTrackingInventoryList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ada5-4d30-a123-330bff54d0be Web CompProcTasks 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ada9-4441-893d-39ec3b945c91 Web InventoryTrackingTransactionsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-b0ef-434e-90d6-ce997d970564 Web PostProvisioningFeature 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-b4c2-46ca-b4b1-819331cf2e4b Web EPPeopleList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-b5a0-47d5-90e6-4b3205b02278 Web AVMResponsibilityAdoptionList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-bbb4-488d-bfc6-79da8ff3ed21 Web SalesTeamModules 964e2241-baa9-49d4-8ae8-aef77d4a07d6
75a0fea7-bfc1-42fe-b08b-ae44bca6a536 Web ProjChangeRisksList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-c1cd-40f9-9f5d-88b7b0c7fc00 Web ProjListInstances 25d59dca-500c-41c0-bc5d-1894b9bb1e11
75a0fea7-c256-49cb-bf7f-de124ca9bf13 Web ProjTasks 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-c285-4c09-839e-0b5e1453e387 Web ITTeamListInstances bed8bd64-d0ac-469a-96fc-cb867001368a
75a0fea7-c54f-46b9-86b1-2e103a8fedba Web TSAimage 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-c671-4696-ac6f-5decfca3173e Web DocumentReviewListInstances 5e33b0a9-1aaa-4509-8b2d-0e60abefdbca
75a0fea7-c966-4e74-b74e-8f77e7bae175 Web EPEventsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ca3c-4d71-9d2c-5efc8e68a5a8 Web SalesLeadsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-caef-4454-be97-4bf0e784650a Web ProjChangeListInstances 6ec9e585-6d56-4d2b-911e-2e3b99948e35
75a0fea7-cbdd-4360-90cb-12aed8c69f43 Web EPListInstances c5932b68-e0b1-4879-aa4a-c3099d183297
75a0fea7-cd50-401e-af0e-782f3662a299 Site TSATypes 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-d01e-48b3-ba36-8cbbdfeef1d6 Web ProjChangeRequestStatusList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-d27d-4319-af1c-9f2d26486cb8 Web CallCenterListInstances 08ec3335-c9b0-458b-a848-6d739b6a74e5
75a0fea7-d31d-491a-9177-f0e461a81e3f Web KnowledgeBaseKnowledgeBaseList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-d6d3-47bc-95be-1b26b5927180 Web HelpDeskInIssuesList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-e632-4b1f-bfa4-a77c0adcdf41 Web ITTeamModules bed8bd64-d0ac-469a-96fc-cb867001368a
75a0fea7-e63b-4059-8f5a-ce9cbbadad2a Web HelpDeskExpertsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ebe9-4501-8897-74c984588afa Web EPAnnouncementsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ee78-4bca-9d7c-9c2fd2593798 Web LendingLibraryModules 1a76aee6-bad7-4934-b8d7-5cc4d933db21
75a0fea7-f13a-4670-8b69-97e90d05f7c8 Web RecruitingInterviewCalendarList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-f780-458c-b53d-441b33a9ac32 Web ITTeamBugList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-fe65-41c3-a965-c5df83fb098b Web ListPropertyFeature 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-fe9d-4119-9615-2c2ef22d6fdb Web HelpDeskServiceRequestsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ff19-4b2e-953b-bea234eba14a Web ReservationsList 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ff47-418f-8bfc-9498b0bc1a85 Web CompProcProjects 0273f170-f34b-4f05-9973-494e875dee24
75a0fea7-ffa9-4c2d-8b20-88401290692e Web CompProcIssues 0273f170-f34b-4f05-9973-494e875dee24
7ac8cc56-d28e-41f5-ad04-d95109eb987a Site OSSSearchSearchCenterUrlSiteFeature 00000000-0000-0000-0000-000000000000
7acfcb9d-8e8f-4979-af7e-8aed7e95245e Web OSSSearchSearchCenterUrlFeature 00000000-0000-0000-0000-000000000000
7c637b23-06c4-472d-9a9a-7c175762c5c4 Site ViewFormPagesLockDown 00000000-0000-0000-0000-000000000000
7fe16263-b3fd-454f-a3e8-ed05fdf2adb6 Web MigrationLinks 00000000-0000-0000-0000-000000000000
8156ee99-ddfb-47bb-8835-7ae42d40d9b9 Site ReportCenterCreation 00000000-0000-0000-0000-000000000000
81ebc0d6-8fb2-4e3f-b2f8-062640037398 Farm EnhancedHtmlEditing 00000000-0000-0000-0000-000000000000
82e2ea42-39e2-4b27-8631-ed54c1cfc491 Farm TransMgmtFunc 00000000-0000-0000-0000-000000000000
8581a8a7-cf16-4770-ac54-260265ddb0b2 Site PremiumSite 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
863da2ac-3873-4930-8498-752886210911 Site MySiteBlog 00000000-0000-0000-0000-000000000000
89e0306d-453b-4ec5-8d68-42067cdbf98e Site Navigation 00000000-0000-0000-0000-000000000000
8a663fe0-9d9c-45c7-8297-66365ad50427 Farm MasterSiteDirectoryControl 00000000-0000-0000-0000-000000000000
8c6a6980-c3d9-440e-944c-77f93bc65a7e Web WikiWelcome 00000000-0000-0000-0000-000000000000
8f15b342-80b1-4508-8641-0751e2b55ca6 Web LocalSiteDirectoryMetaData 00000000-0000-0000-0000-000000000000
90014905-433f-4a06-8a61-fd153a27a2b5 Web pws 538c0384-48ab-483d-90ac-e3a09f755ca5
937f97e9-d7b4-473d-af17-b03951b2c66b Farm SkuUpgradeLinks 00000000-0000-0000-0000-000000000000
94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb Web PublishingWeb 00000000-0000-0000-0000-000000000000
97a2485f-ef4b-401f-9167-fa4fe177c6f6 Farm BaseSiteStapling 00000000-0000-0000-0000-000000000000
99ee0928-7342-4739-865d-35b61ea4eaf0 Farm BDCAdminUILinks 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
99fe402e-89a0-45aa-9163-85342e865dc8 Web BaseWeb 00000000-0000-0000-0000-000000000000
9e56487c-795a-4077-9425-54a1ecb84282 Web Hold 00000000-0000-0000-0000-000000000000
a0e5a010-1329-49d4-9e09-f280cdbed37d Web IPFSWebFeatures 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
a10b6aa4-135d-4598-88d1-8d4ff5691d13 Farm ipfsAdminLinks 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
a311bf68-c990-4da3-89b3-88989a3d7721 Web SitesList 00000000-0000-0000-0000-000000000000
a392da98-270b-4e85-9769-04c0fde267aa Site PublishingPrerequisites 00000000-0000-0000-0000-000000000000
a573867a-37ca-49dc-86b0-7d033a7ed2c8 Farm PremiumSiteStapling 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
aebc918d-b20f-4a11-a1db-9ed84d79c87e Site PublishingResources 00000000-0000-0000-0000-000000000000
aeef8777-70c0-429f-8a13-f12db47a6d47 Farm BulkWorkflow 00000000-0000-0000-0000-000000000000
af847aa9-beb6-41d4-8306-78e41af9ce25 Farm ProfileSynch 00000000-0000-0000-0000-000000000000
b21b090c-c796-4b0f-ac0f-7ef1659c20ae Site BaseSite 00000000-0000-0000-0000-000000000000
bc29e863-ae07-4674-bd83-2c6d0aa5623f WebApplication OSearchBasicFeature 00000000-0000-0000-0000-000000000000
c43a587e-195b-4d29-aba8-ebb22b48eb1a Farm SRPProfileAdmin 00000000-0000-0000-0000-000000000000
c5d947d6-b0a2-4e07-9929-8e54f5a9fff9 Web ReportCenterSampleData 00000000-0000-0000-0000-000000000000
c6561405-ea03-40a9-a57f-f25472942a22 Site TranslationWorkflow 00000000-0000-0000-0000-000000000000
c85e5759-f323-4efb-b548-443d2216efb5 Site ExpirationWorkflow 00000000-0000-0000-0000-000000000000
c88c4ff1-dbf5-4649-ad9f-c6c426ebcbf5 Site IPFSSiteFeatures 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
c922c106-7d0a-4377-a668-7f13d52cb80f Farm OSearchCentralAdminLinks 00000000-0000-0000-0000-000000000000
c9c9515d-e4e2-4001-9050-74f980f93160 Site OffWFCommon 00000000-0000-0000-0000-000000000000
ca2543e6-29a1-40c1-bba9-bd8510a4c17b Web DeploymentLinks 00000000-0000-0000-0000-000000000000
ca7bd552-10b1-4563-85b9-5ed1d39c962a Site Fields 00000000-0000-0000-0000-000000000000
cdfa39c6-6413-4508-bccf-bf30368472b3 Farm DataConnectionLibraryStapling 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
d250636f-0a26-4019-8425-a5232d592c09 Web AddDashboard 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
d3f51be2-38a8-4e44-ba84-940d35be1566 Site PublishingLayouts 00000000-0000-0000-0000-000000000000
d8d8df90-7b1f-49c1-b170-6f46a94f8c3c Web pwscommitments 538c0384-48ab-483d-90ac-e3a09f755ca5
d992aeca-3802-483a-ab40-6c9376300b61 WebApplication BulkWorkflowTimerJob 00000000-0000-0000-0000-000000000000
e15ed6d2-4af1-4361-89d3-2acf8cd485de WebApplication ExcelServerWebApplication 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
e4e6a041-bc5b-45cb-beab-885a27079f74 Farm ExcelServer 7ed6cd55-b479-4eb7-a529-e99a24c10bd3
e8734bb6-be8e-48a1-b036-5a40ff0b8a81 Web RelatedLinksScopeSettingsLink 00000000-0000-0000-0000-000000000000
e978b1a6-8de7-49d0-8600-09a250354e14 Site LocalSiteDirectorySettingsLink 00000000-0000-0000-0000-000000000000
eaf6a128-0482-4f71-9a2f-b1c650680e77 Site SearchWebParts 00000000-0000-0000-0000-000000000000
edf48246-e4ee-4638-9eed-ef3d0aee7597 Farm OSearchPortalAdminLinks 00000000-0000-0000-0000-000000000000
ee21b29b-b0d0-42c6-baff-c97fd91786e6 Farm StapledWorkflows 00000000-0000-0000-0000-000000000000
f0deabbb-b0f6-46ba-8e16-ff3b44461aeb Farm UserMigrator 00000000-0000-0000-0000-000000000000
f324259d-393d-4305-aa48-36e8d9a7a0d6 Farm SharedServices 00000000-0000-0000-0000-000000000000
f386a1b6-b0f4-46d2-a122-b3a1e56eeb16 Site pwsfields 538c0384-48ab-483d-90ac-e3a09f755ca5
f41cc668-37e5-4743-b4a8-74d1db3fd8a4 Web MobilityRedirect 00000000-0000-0000-0000-000000000000
f6924d36-2fa8-4f0b-b16d-06b7250180fa Site PublishingSite 00000000-0000-0000-0000-000000000000
fc33ba3b-7919-4d7e-b791-c6aeccf8f851 Farm ListTargeting 00000000-0000-0000-0000-000000000000
fcd4c704-ed7a-42fb-ab30-2bb0ab6494c8 Farm OSearchSRPAdminLinks 00000000-0000-0000-0000-000000000000
fd3dd145-e35e-4871-9a6d-bf17f28a1c19 Site PublishingB2TRSiteFilesUpgrade 00000000-0000-0000-0000-000000000000
fde5d850-671e-4143-950a-87b473922dc7 Site IssueTrackingWorkflow 00000000-0000-0000-0000-000000000000
fead7313-4b9e-4632-80a2-98a2a2d83297 Farm SiteSettings 00000000-0000-0000-0000-000000000000
fead7313-4b9e-4632-80a2-ff00a2d83297 Farm ContentTypeSettings 00000000-0000-0000-0000-000000000000
fead7313-ae6d-45dd-8260-13b563cb4c71 Web AdminLinks 00000000-0000-0000-0000-000000000000

WebCast: Chilling Changes in the Computer Room

On Wednesday, April 25, 2007 at 2PM EDT,  I’ll be copresenting a web cast “Chilling Changes in the Computer Room” with my buddy Pat O’Day.  The presentation abstract is:

The more your organization depends upon the network and your servers, the more heat they produce and the more power they consume. Learn about technological and data center changes that are driving your cooling bills through the roof, forcing you to drag in even more power to your server room that’s already resonating at 60 Hz. Learn what you can do to stave off higher cooling bills and power costs – at least for now.

If you’re interested in attending the live webcast (or the prerecorded version) the URL to sign up is: http://cp.jupiterweb.com/index.php/3351_default/1953f7bee0d0bd7f8f743d8343a8fd8c?js=1

Linked: How Everything is Connected to Everything Else and What It Means for Business, Science, and Everyday Life

Book Review-Linked

Some things come easy to me.  I see patterns.  I make connections that not everyone makes.  However, there are many more things that are more difficult.  I struggle to understand the idea of social networking, blogging, wikis, and forums.  They mystify me.  That doesn’t mean that I don’t try my hand at it to learn, it just means it doesn’t make that much sense.  I keep trying new things, new approaches, and start new conversations all seeking to figure out how it all works together.

So while I’m still reading software development titles because the journey that I’m on to be a better software developer – despite a decreasing amount of my time being spent that way – is a never ending journey.  However, I’m also beginning to inject social networking, long-tail marketing, and similar topics in an attempt, no matter how feeble to GROK it.

Linked is one of those books that I picked up upon the recommendation of a trusted colleague.  The book’s primary focus is networked thinking.  In other words, there is not one answer that drives everything.  It’s a series of complex interactions between all of the players that creates the play.  As someone who does a lot of IT work I’ve gotten quite familiar with a binary view of the world.  The code is either right or wrong.  The answer is either yes or no.  The hypothesis is either true or false.

However, the binary world of ones and zeros isn’t enough to explain the group dynamics of a user group.  Nor can it illuminate the reasons why a community thrives when another doesn’t.  It doesn’t well expose the single cause for success – probably because there isn’t one.

One of the great things about Linked was that it provides a great deal of information about a wide variety of subjects and pulls it all back to a central theme that many things are networks where one change impacts every other.  From eco-systems where animals are returned to a state of balance, to cancer, and to other far flung ideas a model emerges that things are connected to one another.

As an author and editor, I’ve read and written more than my fair share of material.  However, to be honest I’ve never liked reading academic papers.  I felt like the objective was to make the information harder to understand – to prove that the author is smarter than the reader.  The sacrifice I’ve made in this is that sometimes information that is quite good and relevant never makes it to me because I can’t coerce myself into reading the academic papers that the information is buried in.

This too was an interesting thing about Linked.  There were lots of very critical and strangely useful details buried in its pages and in very few occasions did I feel like it got to be too academic. (This is high praise if anyone’s trying to sort out what I mean.)  I felt like the author repeated his points from different angles without being overly repetitive.  He exposed some fairly advanced mathematical topics without wandering off into places that the reader couldn’t follow.

The short is that Linked helps you to understand how things are connected in every discipline, in every country, and in our every day.  If you’re struggling to understand how marketing works, how large systems function, or how coincidences happen, it’s definitely worth a read.

Recent Posts

Public Speaking