Checklist - Moving Existing Servers to Azure

When you’re preparing to move existing workloads to Azure (lift & shift with IaaS), it is important to remember a few things when converting your servers to a compatible format.

Outside of any disk conversions (vmdk to vhd/vhdx to vhd), here are a few other things to keep in mind:

  • Convert existing disks to IDE based disks (no iSCSI)
  • Uninstall any 3rd party guest tools (e.g. VMware Tools)
  • Ensure the any associated disks are less than 1023GB
  • Ensure the server has only one Network Interface
  • Set Network interface to DHCP and remove any static bindings
  • Remove and/or merge existing snapshots
  • Windows Servers
    • Enable Remote Desktop
    • Enable the DHCP Client service
  • Linux Servers

I like to keep this list handy as a quick checklist and reality check whilst converting to avoid any surprises later.

Azure Remote App Hybrid Oddities

Azure RemoteApp can be utilised in Hybrid scenarios where you wish to connect to your on-premises (or even purely Azure-based infrastructure) and leverage on-premises identities.

One interesting thing to note, is that when creating your link between your local domain and Azure, the Organizational Unit (OU) that will optionally host your RemoteApp computer definitions cannot contain a space in the name. The validation logic with the Azure Management Portal will prevent you from adding the necessary details.

The “easy fix” of course is to rename your OU to remove any spaces, and proceed with your Hybrid implementation.

Sorry, we can’t sync this library because it’s hosted on a SharePoint 2010 Server. For more information, please get in touch with your help desk.

Nooooooooooooooo!!!
Sorry, we can’t sync this library because it’s hosted on a SharePoint 2010 Server. For more information, please get in touch with your help desk.

Nooooooooooooooo!!!

SharePoint 2013 Service Pack 1 Pulled

Update

The KB article for SP1 (KB2817429) has been updated with the following:

We have recently uncovered an issue with this Service Pack 1 package that may prevent customers who have Service Pack 1 from deploying future public or cumulative updates. As a precautionary measure, we have deactivated the download page until a new package is published.

SharePoint Server 2013 Service Pack 1 appears to have been pulled from the Microsoft Download Center.

The timing is slightly off, as clients have been requesting this patch lately as its been available for a bit now. I’ve had a few quibbles with Service Pack 1, particularly the poor implementation of registry permissions and general provisioning problems with Service Applications. Its nothing that can’t be overcome, but hopefully the Product Group can clean it up when the patch reappears.

Thanks to Anders Rask for pointing it out and tweeting it up.