Posted by: kurtsh | May 21, 2008

TOOL: Migrating from Sharepoint 2003 to 2007

Migrating from Sharepoint Portal Server 2003 to Sharepoint Server 2007?  Our Sharepoint Solution Specialist has found several tools that may help in the effort.

  • SharePoint Site Migration Manager from metalogix
    URL: http://www.metalogix.net/products/migrationmanagersp/index.htm
    Summary: Whether you are migrating between SharePoint servers, upgrading from SharePoint 2003 to 2007, or simply re-organizing your SharePoint content, SharePoint Site Migration Manager is an easy to use, convenient way of getting your SharePoint data across. With its familiar copy-and-paste-style user interface, you can quickly migrate all SharePoint sites, libraries, lists, web parts and permissions between servers.
  • Echo for SharePoint 2007
    URL: http://www.echotechnology.com/products/Pages/products.aspx
    Summary: The echo for SharePoint 2007 suite includes the 9 echo managers plus  additional features that allow you to migrate and manage changes on your SharePoint platform through its entire lifecycle and replicate changes and settings to multiple site collections and farms, such as between Development, Staging and Production environments
  • DocAve 4.5 Replicator for SharePoint 2007  by AvePoint
    URL: http://www.avepoint.com/products/sharepoint-administration/sharepoint-replication
    Summary: DocAve Replicator is an essential tool for performing full-fidelity replication, synchronization and management of SharePoint content, configurations and/or securities.

Have you ever been sitting at home, been working on your laptop and suddenly discover through a message emanating from your Systray that, "Hey – you’ve got patches to install."  Or maybe you were watching the Premier broadcasts over Exchange about patches being released and decided, "Hmmm.  I guess I should patch my machine too."

So you went to Control Panel –> Windows Update and attempted to install the updates, only to find it return with as unfriendly and ambiguous red error message saying that your machine couldn’t be updated.  In fact, nothing you do allows you to install Updates/Patches through Windows Update OR download any of the Windows Vista Ultimate Extras.

Whhhhaaaa?  What’s wrong with my machine? 

Nothing’s wrong with your machine.  Windows Vista’s error messages here are just weak sauce. 

WINDOWS IS TRYING TO CONNECT TO AN INTRANET SERVER
What’s happened is that via Group Policy, your workstation was redirected to obtain its Windows Update patches from a Microsoft-Internal installation of Windows Update Services instead of the publicly available UPDATE.MICROSOFT.COM servers.  And since you weren’t VPN’ed in, it was unable to contact the internal SUS server and thus, your patch download/installation failed.  (Heaven forbid Windows Update actually tell you any of this information in its error message.)

HOW TO RESET YOUR MACHINE TO USE THE EXTERNAL WINDOWS UPDATE SERVERS
So, if you want to undo those changes so that you can install said patches, you can override the Group Policy set registry redirection of Windows Update by running as administrator and running the .REG file from this link.  (http://www.evilkoala.org/Documents/FixWindowsUpdate.zip) Don’t worry – the next time you boot up on your corporate Intranet, your machine will have the Group Policy settings for the Internal SUS server re-tattooed onto your box.

For the curious, (or the paranoid that don’t want to download the .REG file)  here’s the content of the REG file in text form:

Windows Registry Editor Version 5.00

[-HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionGroup Policy ObjectsLocalUserSoftwareMicrosoftWindowsCurrentVersionPoliciesWindowsUpdateDisableWindowsUpdateAccess] 

[HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer]
"NoWindowsUpdate"=dword:00000000

[HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer]
"NoWindowsUpdate"=dword:00000000

[HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsWindowsUpdateAU]
"NoAutoUpdate"=dword:00000000
"AUOptions"=dword:00000000

[-HKEY_LOCAL_MACHINESoftwarePoliciesMicrosoftWindowsWindowsUpdate]

[-HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesWindowsUpdate]

[-HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer]
"NoDevMgrUpdate"=dword:00000000

[HKEY_CURRENT_USERSoftwareMicrosoftInternet ExplorerMain]
"NoUpdateCheck"=dword:00000000

[HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesWindowsUpdate]
"DisableWindowsUpdateAccess"=dword:00000000

[HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionPoliciesExplorer]
"NoWindowsUpdate"=dword:00000000

Posted by: kurtsh | May 21, 2008

RELEASE: Virtual PC 2007 Service Pack 1

So Virtual PC 2007 got it’s service pack the other day. 

Why apply Service Pack 1?

  • 64-bit host operating systems (No support for 64-bit guests)
  • Hardware-assisted virtualization (VT, AMD Pacifica)
  • Network-based installation of a guest operating system (PXE boot without a virtual floppy)
  • Running virtual machines on multiple monitors
  • Support for Windows Vista as a host operating system
  • Support for Windows Vista as a guest operating system

And for the typical wort who’s undoubtedly going to throw the old, "I don’t use VPC because it suxorz.  My pirated VMWare Workstation copy rulez!":

  • VPC is free.  No licensing required.
  • VPC uses the .VHD virtual machine file format.  .VHD files are the same files used by Virtual Server 2005 R2 and Windows Server Hyper-V.
  • All Microsoft products are being made available in VPC-compatible .VHD files for ‘testing’ or ‘trial’ to minimize the need for installation time.  For example:

Bits:

Coverage:

image We released a set of useful posters that show the STSADM command line parameters for Microsoft Office Sharepoint Server 2007 and Windows Sharepoint Services 3.0.

Stsadm parameters poster for Microsoft Office SharePoint Server 2007:

Stsadm parameters poster for Windows SharePoint Services 3.0:

imageLINK:  http://blogs.msdn.com/sharepoint/archive/2008/05/12/posters-for-sharepoint-stsadm-command-line-parameters-now-available.aspx

Windows Server 2008 lacks the ability to use Powershell.  It’s entirely Command shell based limiting the ability automate certain functions of the server.  Part of the challenge of this is the fact that .NET Framework 2.0 is not installable by normal conventions, which is a necessary component to get Powershell operational.

(For those of you wondering why .NET Framework isn’t installable, my understanding is that it was not something they made available because of .NET Frameworks current lack of component-ization.)

Well, it turns out that someone’s pieced together a method of getting it to work on Server Core.

<taken from Dmitry Sotnikov’s blog>

Below is a step-by-step instruction on installing Windows PowerShell on Windows Server 2008 in Server Core mode.

Note that these are in no way official or supported by Microsoft. Microsoft is working on official version of .NET and PowerShell for Server Core installations, so eventually you will be able to get this fully supported.

http://dmitrysotnikov.wordpress.com/2008/05/15/powershell-on-server-core/

image Launch on June 3rd, 2008!

This is a virtual event, so you’ll be among the first in the world to get up to speed on Windows Embedded Standard. Kevin Dallas, the General Manager for Windows Embedded Business, will be there to discuss the new technologies and how they further enable next-generation enterprise device scenarios. Plus, you can join from the comforts of your own home – no travel required, and you can even wear your pajamas if you want – what could be better than that?

REGISTER:  http://www.microsoft.com/windows/embedded/standardlaunch/default.mspx

<stolen from http://blogs.technet.com/windowsserver/archive/2008/05/17/windows-hpc-server-2008-beta-2-is-here.aspx>

Whew! Friday at 2:18PM we signed off on Beta 2 of Windows HPC Server 2008. It’s a good thing too since the Redmond team is looking at the first sunny and hot Northwest weekend this year. Mother nature usually gives us these days on weekdays. It’s been a hard push since November when we shipped our last beta. Since then we’ve done test runs on a cluster with over 1000 nodes, fixed over 1000 bugs, coded a bunch of new features, and made a bunch of design changes based on customer feedback. For example, one beta customer was using our new WCF Broker for financial risk modeling but wanted a totally reliable messaging solution. We built a solution leveraging MSMQ that still provides high throughput while allowing for reliable messaging.

Now that Beta 2 is finished our Technology Adoption Partners (TAP) will put this beta into production environments. We’ll carry pagers to help them out if they run into a crit-sit after hours. Actually, we have cell phones. Pagers have gone the way of sock punch cards, teletypes, and sock garters. I suspect there are teenagers wandering around that don’t know what a pager is.

Anyway, there’s a bunch of new stuff in Beta 2.

We checked in high availability for the head node and a new set of diagnostic tests to help people identify and troubleshoot their clusters. The new UI model is really coming together but for users more comfortable with command line interfaces we provide scripting support through COM and PowerShell. Finally, administrators can run administrative scripts in parallel across the cluster using our improved Clusrun feature.

A bunch of humbling (heh) usability testing pushed us to redesign the To Do List. It should be much easier for people to get through setting up a cluster, adding drivers to images, and configuring patching for the cluster (new feature!). The heat map is working so well we’ve thrown out our internal monitoring tools we use on Top500 runs.

After lots of, um, passionate debate we’ve finalized the APIs for job submission. It will continue to be easy for ISVs to integrate directly with our job scheduler while at the same time working with a cluster that may have thousands of jobs in the queue, each job with thousands of tasks.

A lot of people don’t know that we co-chair the HPC Basic Profile working group at the Open Grid Forum. With Beta 2, we ship our support for “HPC Basic Profile,” allowing us to interop with the LSF and PBSPro job schedulers.

We completed a few great Top500 runs in the last few weeks. We can’t talk about the numbers until the International Supercomputing Conference in June but it looks like Beta 2’s new MPI stack and new Network Direct RDMA interface are starting to hum.

Finally, our new programming model based on SOA is getting some nice usage from beta customers. Most of the feedback has come from folks in computational finance but there are also a couple folks in the life sciences industry that are kicking the tires. For example, what if you came up with a new theory about cancer and wanted to search through thousands of medical scans to see if your theory was correct. For Beta 2 we improved scalability, reduced latency and improved session initialization time. Beta 2 supports multiple WCF Brokers, allowing HPC Server 2008 to run really big SOA workloads.

So, we’re done with Beta 2. Lots of new features (whew) and lots of scalability improvements. We’ve posted build 1345, Beta 2, up at http://connect.microsoft.com

We released the IIS7 Administration Pack and Database Manager Customer Technical Preview 2.  This is a collection of IIS 7 Manager plug-ins and extensions which we hope that you will find useful.
LINK:  http://blogs.iis.net/rlucero/archive/2008/05/13/iis7-administration-pack-and-database-manager-technical-preview-2.aspx

So, what’s special about Technical Preview 2?

  • Configuration Editor
    • New locking functionality and visualization of locked items
    • Ability to set configuration settings at any level.  Users can now set application and web site settings within ApplicationHost.config easily.
    • Bug Fixes
  • IIS Reports
    • New Report Types
    • Extensibility Plug-In points.  Users can now write their own custom reports to be shown within IIS Reports.
    • Bug Fixes
  • Database Manager
    • UI Updates
    • Query Support and Execution
    • Extensibility Plug-In points.  Users can now write their own Database Manager Providers and use Database Manager to administer databases.
    • Bug Fixes
  • UI Extensions
    • Bug Fixes

What do users need to know about Administration Pack Tech Preview 2?

  • If you’ve installed Administration Pack technical preview 1, it must be uninstalled prior to installing technical preview 2.

Where do I get Administration Pack Tech Preview 2?

Customizing SharePoint so it doesn’t look like SharePoint is one of the most common tasks site owners get asked by users. While the task may seem daunting, the right tools, a solid understanding of HTML, CSS will take you a long way, and even a little familiarity with ASP.NET master pages technology may help as well. That said, the following resources should help you get started from taking SharePoint out of the box to something that you will be proud of!

Tools
Two essential tools to get started with customizing SharePoint’s look and feel are SharePoint Designer and the Internet Explorer Developer Toolbar.

Office Online
Office Online is a starting point for learning product details for the Office System. SharePoint Designer is a key tool for customizing your SharePoint look and feel.

Samples
Starting with a sample may help you get a master page look and feel together faster than starting from scratch (Though note the expert consensus is to start with a minimalblank master page). Here are some starter samples available for download from Microsoft.

Videos
See SharePoint being customized in action.

WebCasts
MSDN Webcast: Customizing and Branding SharePoint Portal Server and Windows SharePoint Services
http://msevents.microsoft.com/cui/webcasteventdetails.aspx?eventid=1032269755&eventcategory=5&culture=en-us&countrycode=us

MSDN
Microsoft’s Developer Network Site is a great resource for in-depth topics.

Expert Resources
Heather Solomon, Microsoft MVP, Expert on SharePoint Design Techniques

Heather’s Presentations

Examples
Sometimes it’s easier to envision what’s possible when you can see customized sites in action. Here’s a listing of some public facing SharePoint sites.

The site WSS Demo, hosted on SharePoint as well, is also a great reference location that lists all the above sites and more for examples of customized SharePoint sites in action.

PowerGUI – Powershell administration console
Interesting free tool for Powershell users and administrators alike.
http://powergui.org/

(Download PowerPacks – modules to leverage PowerGUI against specific application servers – from the PowerGUI library:  http://www.powergui.org/kbcategory.jspa?categoryID=21)

———————

Example uses:

Frequently Asked Questions:

  1. What is PowerGUI?
    PowerGUI is an extensible graphical administrative console for managing systems based on Windows PowerShell. These include Windows OS (XP, 2003, Vista), Exchange 2007, Operations Manager 2007 and other new systems from Microsoft. The tool allows to use the rich capabilities of Windows PowerShell in a familiar and intuitive GUI console.
  2. How much does it cost and is registration required?
    PowerGUI is a freeware product thanks to the support we are getting from Quest Software. You can download the product and access all information on this site absolutely for free and without any registration or login. You will have to register only if you want to post information to the discussion forums or library, or subscribe to notifications by email (RSS subscription does not require registration.)
  3. What are the system requirement?
    The main system requirement is Windows PowerShell (which in its turn requires .net framework 2.0). If you don’t have this installed on your computer PowerGUI setup will detect that and open a web page from which the system can be downloaded. In terms of operating systems we support Windows XP, 2003, Vista, and Longhorn; both 32- and 64-bit. Particular snapins may add their specific system requirements. For example the Exchange 2007 snapin we ship today naturally requires Exchange 2007 or its administrative tools.
  4. What can I do with PowerGUI?
    Pretty much anything that the underlying system permits. You can browse through the system, filter/sort what you get, select the columns, perform actions on selected objects, change their properties, export data to clipboard, Excel, xml, or just html reports, and much more. And if you don’t believe this is all being done by Windows PowerShell just switch to another tab and you’ll see the PowerShell code behind what you’ve been doing.

    Check out PowerGUI extensions library for the additional features you can download from the community.

  5. How can I customize PowerGUI?
    Yes, if the functionality of the snapins is not enough you can add any nodes (check out our search feature when adding a cmdlet-based node!), actions, or links. You can of course delete any of the ones we ship too, and do basic customization such as changing the set and order of columns the tool displays.

    See demos Documentation in for more information.

  6. What are Links?
    Links provide the ability to get to a set of related objects. For example, if I want to get a list of members of my Managers group, and then find Exchange mailbox stores which have their mailboxes I am effectively following links between the objects to get from the group to its members, then to their mailboxes, and finally to the mailbox stores.

    See demos Documentation in for more information.

  7. What a difference between Actions and Common Actions?
    Actions are specific to an object class. For example, changing user properties only makes sense for user objects. Common Actions work for any object classes. Natural examples here would be reporting and export functions.

    See demos Documentation in for more information.

  8. How can I exchange actions, links, nodes with another PowerGUI users?
    Anything you add can be shared with other PowerGUI users. To share functionality select the export command in the shortcut menu and then share the file by uploading it to the community library. Other users will then be able to download the file and import it into the tool.
  9. What does auto update do?
    Every time you start PowerGUI it tries to connect to the community site to check for latest version. No personal information is transferred during this connection or download. If a newer version is found you’ll be prompted to download and install the version. If your computer is not connected to the internet you need to visit the community site to download and install the latest updates manually.

    You can subscribe to our announcements or blog to get notified when a new version is available.

  10. Where can I get help?
    Check out the flash demos posted on the site in Documentation, and feel free to ask questions on the community forums.

« Newer Posts - Older Posts »

Categories