For those running SharePoint 2007 on Windows Server 2003 / 2003 R2:

cscript c:\windows\system32\iisapp.vbs /a "%SharePointApplicationPool%" /r

where %SharePointApplicationPool% is the application pool that needs to be recycled. Note that iisapp.vbs resides within %systemroot%\system32\

For those running SharePoint 2007 or SharePoint 2010 on Windows Server 2008 / 2008 R2:

appcmd recycle apppool /apppool.name:%SharePointApplicationPool%

where %SharePointApplicationPool% is the application pool that needs to be recycled.  Note that appcmd resides within %systemroot%\system32\inetsrv

The alternative for this of course is just to go in IIS Manager 6 or 7, select the application pool associated with the web application that requires recycling and recycle the pool manually through the UI.

References:

• Recycle an Application Pool on Demand (IIS 6)
• Recycle an Application Pool on Demand (IIS 7)

The best part of the hub in my opinion is the ability to customize it and add additional modules that meet your organization or business unit’s needs to ensure that your implementation is actually serving them from a business perspective rather than just humming away as another file share replacement.

Well, like most technology solutions, there are updates and enhancements.  On 17 January 2011, Microsoft released such an update for the Productivity Hub for SharePoint 2010. So, if you’re looking to just download and implement with the content packs – fear not, it’s simply and easy by just heading over to the Microsoft Download Center at:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=4aaa9862-e420-4331-8bc3-469d7bae0ff1

However, if you’re feeling crafty and are looking to customize this product, it’s available on CodePlex from the team that created it (thanks RedTech!) at:

http://productivityhub.codeplex.com/

The key enhancement to the Productivity hub in this case is that of the customization documentation to provide guidance when crafting the Hub for your implementation’s UX.

They’re available now on the Microsoft Download Center at:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=88e03d22-8f42-4c9d-94ef-d8e48322d677

Just drop them in your My Documents > My Shapes folder and they’ll show up in Visio in My Shapes within the Visio Application.

For the IT Pro Stencils, check out this article for more information:

http://www.sharepointdan.com/2010/11/01/visio-stencil-for-office-it-pros/

In most enterprise settings this is something that you’d find in a global policy object enforcing a particular amount of time that you’re able to be Idle prior to being booted from the server. Also there’s another setting regarding the maximum connection timeout – basically how long until your session gets trashed because you decided after you’d been booted for being idle you weren’t going to log back in.

If you’re searching around for these settings, they can be found through your friendly neighborhood group policy object at:

Console Root\Local Computer Policy\Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session\Session Time Limits

Specifically you’re looking to see what the settings for the following policies are:

• Set time limit for disconnected sessions
• Set time limit for active but idle Remote Desktop Services sessions
• Set time limit for active Remote Desktop Services sessions
• Terminate session when time limits are reached

While they may all seem friendly, upon closer examination you’re likely to find that one of these policies is your culprit (more than like the second and third in conjunction with the fourth).

However, oddly enough some folks still use security templates to tighten the policies on their servers.  In which case, there’s also a Registry edit required and a reboot.  Note you should always backup your registry before you make any changes – not for the squeamish of heart.

You’ll find this information along with other helpful information for allowing and disallowing things like the use of the Clipboard (fDisableClip) in the registry branch of:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services

Note that it’s still called Windows NT and also Terminal Services – I guess that some things never change

Specifically you’re looking for the following registry strings to modify:

• MaxDisconnectionTime
• MaxIdleTime

The decimal values that correspond to these are counted in milliseconds.  For instance, if the MaxDisconnectionTime is set to 300000, this corresponds to 5 minutes (60 seconds/minute x 1000 milliseconds/second x 5 minutes).  If you don’t want to be disconnected or have a max idle time, just set the value to 0 and you’ll be all set.

Happy Implementing!

And if you’re wondering where the title for this blog post came from, check out the Fireside Theater’s “We’re All Bozos On This Bus” radio show. Has something similar where the robot gets unplugged

Epic Fail.

While I understand Google’s intent is to be able to assist users in replacing their Exchange profile with their Google Apps e-mail profile with the sync plugin, there are those of us that will continue to use an Exchange profile and the Google Apps capability is a nice to have to be able to use the Outlook client interface.

At first, I thought perhaps this was an Outlook client issue that had been affected by SP2 or some other cumulative update that was applied, however after doing a little Googling, it seemed that no one else had reported a similar experience.  I also realized that this behaviour only became apparent after installing the Google – Outlook plugin.  So I uninstalled the plugin and wondered, “Will Instant Search work once more?”  Negative, Instant Search was still disabled.

Looking within the Search Interface, Windows Desktop Search was telling me that Indexing Outlook had been disabled by the System Administrator.  Doing a bit of digging around, it became apparent that I hadn’t disabled WDS, and the mail admins hadn’t done so either, so it was back to square one of looking through the registry to see what had been tweaked.  Where else to begin but Microsoft’s documentation pertaining to Group Policy settings and Windows Desktop Search which can be found at:

http://technet.microsoft.com/en-us/library/cc732491(WS.10).aspx

A registry key had been created at:

Computer\HKLM\Software\Policies\Microsoft\Windows\Windows Search

with a registry key named “PreventIndexingOutlook” set to a value of “1″, telling WDS not to search Outlook under any means.  Simply changing this value to “0″ and restarting the Outlook client and WDS and Instant Search were back up and running properly across all profiles.

Uninstalling and reinstalling the Google Sync plugin quickly reverted the registry key back to “1″, preventing WDS from indexing Outlook.  Even upon uninstalling the plugin, the registry key remained.  This seems like a bit of configuration management that should be corrected so as to ensure that users are not limited by Google’s plugin should they decide not to use it without hindering their search capabilities.

Bottom line, this is a registry change that is unexpected that is caused by the Google Sync Plugin.  Am I happy to see Google integration with the Outlook client, sure, but not at the cost of Search.

So the first part to the madness that should be understood is that IIS 7 (standard for Windows Server 2008) is a lot more granular in nature than IIS 6 which is the standard web publishing application on Windows Server 2003.  From even when you’re starting your installation of the Web Server role to installing the individual components, it’s far more granular and modular, and probably confusing to some administrators that are used to just clicking “IIS” from Add/Remove Program in Server 2003.

So where to begin, well, once you’ve got your Windows Server 2008 box up, operational, patched, service packed, sysprepped (if you’re using Virtuals, you end up requiring that you have different SIDs and computer names right?), IP’d and joined to a domain, the fun begins in installing just the framework prior to SharePoint.

Step 1 – Open up the Server Manager, this typically appears when you power on the server, but if not, you should be able to find it fairly easily from the start menu.  Select and expand the roles label from the tree in the left pane, then select “Add Roles” from the right pane.

Step 2 –   If this is your first time installing a role, this would probably be helpful to read “Before You Begin”.  Definitely read through it at least once, after that, feel free to click the check box to skip it in all future instances.  Click on Next.

Step 3 – Select the Web Server role from the list of server roles. Note that you will be prompted to select additional features for the Web Server role to operate properly.  Select “Add Required Features” else turn and back away, and perhaps reconsider what you’re looking to do.

Step 4 – Once you’ve accepted the need for additional “required” features to be installed, you should see something like the below stating that you have selected the “Web Server (IIS)”.  Click on Next.

Step 5 – The role installation wizard presents an overview of the Web Server (IIS) role which again is fairly useful for an administrator to read through the first time.  Click Next.

Step 6 – Select the individual server roles that you require for your SharePoint installation.  I’ve found that the basic role services that are installed with IIS 7 are barebones, which from a security posture is fairly helpful so as to not have to remove several roles, but it will make you stop and think through what roles you do indeed to make the system operational.

Step 7 – The first thing to select of course to make your platform usable by SharePoint is the ASP.NET development platform.  Once you’ve selected this, you will be prompted to add additional roles that are required for ASP.NET.  Select the “Add Required Role Services” else, much like before, be prepared to have a difficult time installing SharePoint services on your server.

Step 8 – Select the additional roles that will assist in your SharePoint implementation, in my case this also includes “Logging Tools” to diagnose issues that may come up.

9 – Select the appropriate authentication providers that you wish to be able to utilize.  For me, I’m going with a fairly vanilla SharePoint installation and configuration, so I’ll select “Windows Authentication”.

10 – Additionally, so as to not bother with going back and installing later, I’ve selected the “IIS Management Scripts and Tools”.

11 – Lastly, the “Management Service” to be able to better manage the IIS 7 instance on the server from the server or remotely.

12 – After selecting the roles that are appropriate to support your SharePoint services installation, click on Next, which then will bring you to a page that lists all of the components that you are looking to install.  Do a quick read through to ensure that you’ve got the components, roles and features that you require and click on Install.

13 – Observe the installation process as can be seen here:

14 – After a few minutes, the installation progress bar will complete and an installation results page similar to this will be presented.  Click on Close after you’ve observed that your installation results were successful.

15 – After you’ve completed your IIS 7 installation, you’ll see that there are 24 installed role services related to IIS running and operational on the server through the Service Manager roles summary.

Next on Tap:

• SharePoint on Windows Server 2008 – Installing and Configuring SQL Server 2005 on a single node
• SharePoint on Windows Server 2008 – Installing and Configuring Microsoft Office SharePoint Server 2007 Standard Edition
• SharePoint on Windows Server 2008 – Configuring Kerberos based Windows Integrated Authentication