UPDATE: Spence posted a great comment pointing out some issues with this post. Richard then restored our Community Server DB to a point in time before the post, so it’s been wiped. Post again, Spence, please, as I didn’t get chance to copy the text of the comment, I’m afraid.
I finally bit the bullet and decided to upgrade our SharePoint farm yesterday. I’d been holding off for a while because of time constraints and because of a known issue with Project Server, also part of our farm.
I’ve been meaning to write this up for a while, simply because it’s not quite as straightforward as with Server 2005.
To configure incoming email on SharePoint when running on Server 2008 you’ll need to run through the following steps:
NOTE: We use a wildcard SSL certificate which makes our life much easier when dealing with multiple hostnames. I have not tested this approach with multiple SSL certificates for specific sites.
One of the most useful elements of the Virtual Windows XP feature in Windows 7 is that the VPC is easily replicated and you can have multiple virtual machines all publishing applications which run in their own sandboxes.
The title says it all. I’m currently building a virtual lab to test DirectAccess and every time I run newsid on windows server 2008 R2 the system bluescreens irrevocably on reboot. I’ve now switched to using sysprep to change the SID. Here’s hoping the sysinternals guys update what is undoubtedly one of the most useful tools around!
I’ve been using Windows 7 for a while now, but I’ve never needed to install the System Center Capacity Planner (Andy usually handles that side of our SharePoint engagements). He now has taken the plunge with Microsoft’s shiny OS and hit a problem: SCCP refused to install with an error message saying it was only supported on Windows XP (!)
You may remember that I ended my previous post with about 1.6Gb free on the 8Gb SSD of the Mini 9 after installing Windows 7.
I still needed to install Office 2007, or at the very least Word and Excel for the ‘book to be useful. I therefore rummaged out another 16Gb SD card and revisited my earlier vista post about installing apps to an SD card. This time I simply let the card allocate a drive letter and installed Office to d:\Program Files instead.
In my previous post about getting Windows 7 onto the fantastic Dell Mini 9 I talked about solving things like the driver issues and antivirus. This time I’m going to cover how I installed Windows 7 onto the 8Gb SSD version of the Mini 9.
The steps in this article were figured out with Windows 7. However, they should work just fine with Vista for anybody having the same issues. Note that whilst this is written for ATI hardware, it may be the case that NVidia gear suffers from the same problem and this solution should help.
One of the things I am most impressed about with Windows 7 is the latest Media Center. As a result, I wanted to install the build 7000 beta release onto our media PC at home. However, I already have that working nicely with Windows Vista and, frankly, I didn’t want to have to repeatedly reinstall if the beta caused problems.
Having just spent a long time examining the state of a new farm we’ve been working on for demonstrations, I would like to issue a warning…
The Problem: None of the ‘New…’ menu items in our document libraries would work – we were seeing the error message:
I’m using the Mini9 quite a lot lately, at least in part to fiddle with Windows 7. I decided it would be nice to be able to access our Hyper-V servers so I went looking for the management tools…
I’m still trying new things with the Mini 9. I now have an image file that I can restore to the Mini which has my base install after running sysprep. The problem I have is storage space – the SSD isn’t quite big enough.
Flush with my success earlier in getting apps installed on the SD card now mounted as ‘c:\SD Program Files’ I installed a few things. I then hit a snag.
When you install apps using an MSI, the installation files get cached by Windows Installer. Steadily, c:\windows\installer gets bigger and bigger, so whilst my apps were no longer taking up space, the install files were (and some of those are quite large).
As you may remember from my earlier post and subsequent follow-up, we have been seeing an issue related to workflows and the Workflow History list in SharePoint 2007. As I’ve already mentioned, the case is with Microsoft and I also said that I would post updates as new information arrived. Today, more detail has emerged and, as promised, I am sharing.
As part of a customer project I needed to create a Netware environment for testing. It’s been a little while since I did any netware management and I quite enjoyed it. I did, however, encounter a couple of gotchas which I thought I’d write up for the greater good.
Sometime ago we noticed an issue with My Tasks in Project Server. Certain users were unable to access My Tasks at all - they simply got a SharePoint error page.
I find myself drawing the same diagram over and over again in meetings to explain how SharePoint sites relate to IIS web sites, how managed paths and alternate access mappings fit and why you need to extend the SharePoint web application if you want more than one authentication provider.
I’m not certain how many of you will find this useful, but I had a question about configuring the Touch Diamond to talk to Exchange which I regrettably failed to notice.
