Is Your Edge Bleeding?
I guess it has been a while since I have been on the "bleeding edge". When everything installs using the standard configuration and you don't need technical support then you probably aren't out on the bleeding edge. I was reminded of this recently when I purchased a 16GB Windows 7 64-bit machine and tried to add it to my Windows Server 2003 domain and install SharePoint 2010 Server on that laptop. Everything was so far from a custom installation; my edge was hemorrhaging.
By hook or crook, no less than a dozen MS support guys, and eight nights-sometimes fourteen hour stints-could not get that laptop to join the domain, Outlook 2010 find my exchange server, or permit the SharePoint server to be installed on that laptop. I am not exaggerating.
First, joining a domain is a 30 second process usually, not with a Windows 7 64-bit laptop. Registering Outlook 2010 with an Exchange server is about a two minute process, provide the exchange server name and a user account and you are in, not with a Windows 7 Ultimate 64-bit machine. And, configuring SharePoint 2010 Server to run on a laptop, well that takes a long time too.
The odyssey began with adding the 64-bit Windows laptop to the domain. I received RPC failure errors, trust relationship errors, and the Active Directory computer account was just wrong. I had to use ADSIEDIT and configure the computer record by adding the servicePrincipalName attribute to contain the HOST and TERMSRV values with the computer name and FQDN-fully qualified domain name. (Adding and removing the computer to the domain using Active Directory still doesn't work, whether I preconfigure it on the AD server or use a change name on the laptop.)
Fixing the AD record manually permitted the laptop to log into the domain. The Microsoft techs tried disabling the firewall, turning off IPv6-Internet Protocol 6 with its longer IP address schemes-and close to fifty hours of other changes, none of which worked.
Microsoft Office 2010 64-bit never installed and recognized the MS Exchange server. I had to uninstall Office 2010 64-bit, install Office 2007 32-bit, register that (Outlook) with the exchange server, and then upgrade to Office 2010 32-bit. (Kind of a bummer.) Keep in mind this was no simple choice for me. I had worked more than 50 hours with Microsoft technical support over 8 days-including Office, Exchange, Active Directory, Networking, and ISA (Internet Security and Acceleration/firewall) folks before throwing in the towel on Office 64-bit. These guys tried everything, including changing global policy, opening ports, running diagnostics, and running a dozen knowledge base patches to no avail. Their efforts were valiant but I got the distinct impression they were guessing too.
Finally, just tonight-one day before Thanksgiving in the US-I got the SharePoint Server 2010 to install, but this took a lot of finagling and no less than a half dozen attempts. This article helped--http://msdn.microsoft.com/en-us/library/ee554869.aspx-but itself is incomplete.
To install SharePoint Server 2010 64-bit on a Windows Ultimate 7 64-bit machine follow the steps in this article carefully, very carefully but Step 3, item 6, which runs psconfgui.exe is going to fail a couple of times and you will need to make some changes and re-run it too. To get the products and configuration wizard to complete successfully you will need read the diagnostics log, Google each error and make the necessary changes. This blog--http://vinaybhatia.blogspot.com/2010_01_01_archive.html-had all of the answers for each error and almost all of them needed to be made.
For this error "Microsoft.SharePoint.SPException: User cannot be found" make sure you are connected to a domain controller.
For this error: "System.Security.Cryptography.CryptographicException: The data is invalid" back up the registry and delete the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure\FarmAdmin", although since I selected a standalone installation I am not sure why this key was present.
For this error "Failed to create sample data": apply the hotfix KB976462.
And, finally, the configuration wizard fails on step 8 of 10 with "SharePoint Products and Technologies Configuration Wizard Error : Failed to create sample" you can apply the fix at http://social.technet.microsoft.com/Forums/en/sharepointadmin/thread/4747863c-ab4f-4dda-9a79-519a8afc32a6 and run the configuration wizard one last time. (Note: even the steps at the aforementioned TechNet article aren't correct for Windows 7 Ultimate. Listed as 1. Click Start, point to Administrative Tools, and then click Component Services. 2. In the left pane of the Component Services snap-in, expand Component Services, and then expand Computers. 3. Right-click My Computer and then click Properties. 4. Click the MSDTC tab, and then click Security Configuration under Transaction Configuration. 5. Under Security Settings, click to select the Network DTC Access check box, if it is not already selected. Then, click to select the Allow Remote Clients check box 6. Click OK. 7. When you receive the message that states that the DTC service will be stopped and restarted, click Yes to confirm that you want to continue. 8. Click OK when you receive the message that the DTC service was restarted. 9. Click OK.
Follow these steps instead: 1. Click Start and in the Run field start typing component services and run Component Services 2. Expand Component Services|Computers|My Computer|Distributed Transaction Coordinator 3. Right click on Local DTC and select properties 4. In the Local DTC Properties dialog click Security 5. Check Network DTC Access and under Client and Administration check Allow Remote Clients 6. Click OK and let the DTC restart 7. Close the Component Services console and re-run the SharePoint configuration tool
Sometimes I wonder why big companies don't immediately upgrade to the latest and greatest product releases. Over the last two weeks I was humbly reminded. Upgrading on the bleeding edge can be a big time suck, a huge productivity risk, and even the blogs and tech support haven't got the configuration issues worked out very well.
The bleeding edge can be a lot of fun, but if you have real work to do it can be a huge pain in the butsky. If I had to do it over again the new-new laptop and 64-bit OS could wait six more months at least.I am a software architect and developer by day. I adminsitrate an enterprise network configuration with a PDC, Active Directory, ISA Server, SQL Server, DNS, DHCP, a second server and wired and wireless networks in my home office by night. Sometimes installing the latest and greatest software and upgrades is a huge, time consuming challenge. Adding a Windows 7 64-bit laptop with Office 2010 64-bit, and SharePoint Server 2010 was just that. Right now it may not be for the meek. The solution is in bits and pieces all over the net and you might be on your own even with technical support present, at least for a while yet.