Welcome to all of my loyal (and occasional too) readers to the new home of the blog. After 4+ years of running the blog on various versions of blogging servers on my own hardware, I am simplifying my life by letting someone else do the heavy lifting. In this case, Blogger.

For those of you who have migrated over to the feed link, this shouldn’t even hurt a bit, as your reader will just swap over to the new feed. If you have any hard links to old articles, unfortunately those will no longer work.

Thanks for tagging along in the change. I’ve got a bunch of things planed for 2008, so stay tuned.

SP1 for Windows SharePoint Services 3.0 and Office SharePoint Server 2007 have arrived. You can get the download, read installation instructions, and find out more at the SharePoint Team Blog and the official SP1 Site.

The impacts of email can be devastating to careers and can be long-standing with the permanent nature of the communication. A recent article on law.com highlights the think before you send mentality that needs to be ingrained into company cultures far and wide.

E-mails, text messages, BlackBerry communications all are potential time bombs if not worded thoughtfully and with discipline. "It just creates the potential for a permanent record for all this type of stuff," Clarke said. "People don’t realize that to some degree, if it’s in an e-mail, it’s analogous to etching it in stone."

Read the entire article here.

Yep, available now.

• Download link
• Release Notes

Improvements in Exchange Server 2007 SP1 include:
Anywhere Access
• Integrated Exchange Unified Messaging functionality with Microsoft Office Communicator 2007 and Microsoft Office Communications Server 2007.
• Outlook Web Access additions, including public folder access, S/MIME support, personal distribution lists, and mailbox rules editor.
• Webready document viewer supports Microsoft Office 2007 documents in addition to Microsoft Office 2003 documents.
• Extended language support in Outlook Web Access with Arabic and Korean spell checking.
Operational Efficiency
• Support for Windows Server 2008 deployments, including benefits in flexible clustering, native virtualization, advanced networking, and simplified management.
• Additional tools in the Exchange Management Console, including public folder management and configuration options for clustering and POP/IMAP access.
• Improvements to the Exchange Management Shell syntax and import-export PST in the move-mailbox command.
• Wider variety of web services for application development, including public folder access, delegate management, and folder level permissions.
Built-in Protection
• Addition of Standby Continuous Replication (SCR) for site resilient high availability deployments.
• Extended Exchange ActiveSync policies for mobile policy enforcement.
• Information rights management pre-licensing by the Hub Transport role.
• Secure Real Time Protocol (SRTP) support in the Unified Messaging role.
• Support for IPv6 when using Windows Server 2008.

I’m on day three of my new position and have been diligently getting my new computer set up to operate in a way that I need it to run to do my job. Part of that setup included installing PowerShell. PowerShell (both 1.0 and 2.0) rely on the .NET 2.0 Framework, which came pre-installed and configured on my company-built notebook computer.

When I attempted to run PowerShell, the application would crash with no apparent errors, other than a non-descriptive Windows Error Reporting dialog with no details.

I did the natural thing, and jumped into the event log. First stop was the PowerShell event log which showed nothing special about the startup and then the shutdown of the PowerShell providers. The system log did not show anything out of place either. However, the application log had this error entry:

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Description:
.NET Runtime version 2.0.50727.1433 – Absolute path information is required.

Curious, I did the natural thing and searched Google while ran a repair on the .NET 2.0 install. All my searching yielded not a snippet of help. I did notice though that my home directory had been redirected to a shared drive on the personal storage SAN while working in Word. I wondered if that had something to do with my error, and sure enough, it did.

Upon further examination, the redirection for "My Documents" (Windows XP) was set to "Z:". A quick change of this to "Z:\" (note the trailing backslash?) corrected the issue. How to change this quickly? Right click on the "My Documents" folder on your desktop or Start Menu. From that properties dialog, you can change the storage location for that special folder.

Problem solved, back to writing scripts.

Oh, and work here is fun. The company treats its employees like people, which is a kind change from most corporations. We’re still in the honeymoon period and working on grand new ideas on how to revitalize the IT juices around here. Exciting times lay ahead.