Upgrade

In Place Upgrade Of Windows Server 2008 R2 Standard

If you have a need to upgrade a server running Windows Server 2008 R2 Standard to either the Enterprise, or Datacenter edition, it’s possible to do so online, without re-installing Windows. This not only a simple process, it saves you time.

Open an elevated command prompt and type DISM /Online /Get-CurrentEdition. This returns the current Windows version.

Type DISM /Online /Get-TargetEditions to list the Windows editions to which this server can be upgraded to.

Type DISM /Online /Set-Edition:ServerDataCenter /ProductKey:xxxxxx will upgrade the operating system. All that’s required to complete the upgrade is a reboot.

Done!

Ref Info:

DISM Windows Edition-Servicing Command-Line Options – https://technet.microsoft.com/en-us/library/hh825157.aspx

KMS Client Setup Keys – Link

VMware: vCenter Server Appliance 6.0 Update 1

That time has come, when you upgrade vCenter 6.0.  Here are some quick simple steps to see this done.

As always, its a good idea to have a backup before proceeding.  In my case I used a snapshot of my appliance. This was done by me connecting directly to the ESXi and creating a snapshot.

And here are the steps to start this process:

  1. Download the VCSA 6.0 Update 1 from  the VMware Patch Download Website. File-name: VMware-vCenter-Server-Appliance-6.0.0.10000-3018521-patch-FP.iso
  2. Mount the VCSA 6.0 Update 1 Patch ISO to your VCSA 6.x appliance. I attached the ISO by logging into the ESXi and then attaching to the guest appliance
  3. Next is to be logged into the VCSA 6.x appliance via SSH – note this must be an admin account.  I used the local root user and password
  4. Run the following command to begin the installation process: software-packages install –iso –acceptEulas

  5. When completed issue the reboot command: shutdown reboot -r “Updated, thanks to my buddy jermsmit”

     

Congrats you have upgraded.

Info sources:

VMware KB – for additional info

William Lam – who’s tweet informed me of this release, thanks dude

 

I hope you enjoyed this post, thanks for visiting – jermal

Tech Short: Upgrade To Windows 10 by force

So you are running Windows 7 or 8 or 8.1 and you don’t see any indication of an upgrade to Windows 10 option. Here is something which can assist you in getting upgraded in a jiffy.  All you need is the

You still reading this? Why? Head over and grab the tool and upgrade. Its simple

Download the tool

  1. Find the media creation tool on the Software download page.

  2. There are two versions of the tool, one for a “32-bit operating system” and one for a “64-bit operating system.” To find out which you have, go to Start, type Control panel, select System and security, and then, under System, look at the value for System type:.

  3. If your PC is a 32-bit operating system, on the Software download page, select Download tool now (32-bit version). If your PC is a 64-bit operating system, select Download tool now (64-bit version).

  4. When you’re asked, select Run (or choose to Save the tool if you don’t want to run it now).

Run the tool

  1. Run the tool, if you didn’t already select Run above. (You need to be an Administrator on the PC to run it.)

  2. If you’re upgrading this PC, select Upgrade this PC now, and then follow the rest of the instructions to finish the upgrade.

  3. If you want to create media for a different PC, select Create installation media for another PC. Use this table to choose the edition of Windows 10 that you want to create media for.

Link: http://windows.microsoft.com/en-us/windows-10/media-creation-tool-install

HowTo Upgrade OpenMediaVault

Here are some quick and simple steps to upgrade your OpenMediaVault (OMV) to the latest version; OMV 1.0  (Kralizec).

SSH into your OpenMediaVault server; in my case I am running OMV 0.5 and run the following command:

apt-get update && apt-get dist-upgrade && omv-update

Then type the following command:

omv-release-upgrade

Once completed you can either restart the web services or reboot the system and your all set.

 

SharePoint 2010 to SharePoint 2013, Content Database Upgrade

I have been working on upgrading SharePoint 2010 to SharePoint 2013.  Here are some notes on steps taken to update a content database for your default web application.

Please note:  

  1. A backup of your default (primary) SharePoint 2010 content database is needed.
  2. These steps are for those who have already installed SharePoint and have a functioning central administration site working.

Step 1 – Backup of content database.

In order to upgrade and mount your SharePoint 2010 content database in SharePoint 2013 you will need to create a backup of the content database and restore this onto the database server chosen to server as your SharePoint 2013 database. While a new server is not required (space permitting) you may do this on the same database by restoring with a different name.

Step 2 – Create new (in my case) default application site

To attach the restored SharePoint 2010 database to the SharePoint 2013 installation, we need to create a new application site.

  • Open Central Administration
  • In Central Administration, select Application Management then select Manage Web Applications 
  • One under the Manage Web Applications, click  New to create a new web application
  • This bring you to the ‘Create New Application setup model.  There are many options here. In my case I am setting up just a new SharePoint site.
  • Create a new IIS website – For my setup I am keeping the default name. If the site runs on port 80 no need to change this. I am keeping the default site path, and being that this is part of an upgrade of a SharePoint 2010 database I am calling the database WSS_Content_delete_me as a reminded to delete later.
    Click OK and you will see the following popup
  • Followed by a message indicating that your application has been created.
  • We now want to make our way to Central Administration > Application Management and select, Manage content database 
  • Selecting the database we created above: ‘WSS_Content_delete_me’ we choose the option to remove the content database from the newly created application
  •  Click ‘ok’ to complete this action

Step 3 – Upgrade and Mount (attach) Database

The next steps require us to use SharePoint 2013’s Management Shell to mount the SharePoint 2010 database and in doing so upgrade it to function with SharePoint 2013.

We run the following command syntax to mount  the database:

To mount: Mount-SPContentDatabase -Name <database_name> -WebApplication http://<sharepoint_server_application>

To test: Test-SPContentDatabase -Name <database_name> -WebApplication http://<sharepoint_server_application>

Depending on the size of the content database, you may have to wait for a short period of time for the upgrade to complete.

* note * you may encounter error messages at the end of the upgrade once completed indicating customization’s that are not supported in SharePoint 2013.

Do not upgrade virtual hardware of ESXi 5.5 guest

I updated my ESXi 5.1 server to the latest ESXi 5.5 release. The process with smooth as it has always been in the past. After updating the tools for my guests I thought it was only practical to update the hardware level of my machines… I thought wrong.

The moment I upgraded the ability to edit a guest vm’s configuration using the vSphere client. When you make an attempt a message box opens with the following: “You cannot use  the vSphere Client to edit the settings of virtual machines of version 10 or higher…” And in forms you that you need to use the VMware vSphere Web Client

link” http://www.ivobeerens.nl/2013/10/01/watch-out-with-hardware-version-10-in-vmware-esxi-5-5/

I was able to correct this after the fact by creating a new configuration and attaching the the disk of the machine I recently applied the update to. Now I am back in business.

Exchange 2010 SP3 Upgrade Error

I just got finished with upgrading my Exchange 2010 Server to SP3 in preparation for next weeks online of Exchange 2013. During the service pack upgrade I encountered a few issues:

  1. After the prerequisite test the upgrade failed due to my antivirus software
  2. Upgrade failed due to the Exchange MMC being open by other users session
  3. Upgrade in a bad state after the two failures above

During the upgrade some of the roles had updated and my install was failing on the mailbox role. Exchange would not continue the upgrade process. To fix this I needed to delete an entry from the registry.

These are the steps I had taken:

  1. Opened regedit (Start > Run)
  2. Browsed the the following key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftExchangeServerv14
  3. Listed here are each role; Hub Transport, Client Access, Mailbox – I looked for the the following: action and watermark entries and deleted them. In my case they only existed under the Mailbox role.
  4. Rebooted Server
  5. Started the Exchange 2010 SP3 Upgrade

This completed with success. After the completion of the upgrade I gave my server a restart and once online and all services running tested via my Outlook Client, Outlook Web Access, and via Mobile Devices to ensure Exchange was running as expected.

I hope this saves you some time if you are attempting this or looking for a solution.

Windows 8.1 Preview ISO files now available

When the announcement of the preview was made the bits were not yet available for download; They are now. Head over to http://windows.microsoft.com/en-us/windows-8/preview-iso and grab yourself a copy.

Product Key: NTTX3-RV7VB-T7X7F-WQYYY-9Y92F
Important: Windows 8.1 Preview isn’t currently supported on some tablets and PCs with newer 32-bit Atom processors. Get the details here

The Windows 8.1 Preview is here!

There has been some buzz about it and it seems as if its finally Windows 8.1 is here as an preview. Now you can take a first-hand look at many of the new features and improvements with the Windows 8.1 Preview.


For a more complete look at all the features in Windows 8.1, check out the Product Guide.

Before you install the Windows 8.1 Preview, it is also highly recommended you backup any files you have on your PC or tablet first. Please see the Windows 8.1 Preview FAQ before installing, which includes information on how to go back to Windows 8 if you need to. There are certain cases in which you will not be able to go back to Windows 8 after installing the Windows 8.1 Preview so please read the FAQ before proceeding.

So head over to the Windows 8.1 Preview page on Windows.com. The Windows 8.1 Preview will be installed through the Windows Store. Please see the Windows 8.1 Preview FAQ for the minimum requirements needed to install the Windows 8.1 Preview.

Here is the Download Preview Page: http://windows.microsoft.com/en-us/windows-8/download-preview

ISO file Download (no yet available **** Its aviable now): http://windows.microsoft.com/en-us/windows-8/iso-preview

 

Update available message after installing update

Recently I updated my Ubuntu Server 12.04.2 to Ubuntu 13.04 when I noticed that the message of the day (MOTD) displaying in my console was telling me that an update was available and to Run ‘do-release-upgrade’

It seems the cause of this was /usr/lib/ubuntu-release-upgrader/release-upgrade-motd which is called by /etc/update-motd.d/91-release-upgrade which checks for the existence of the release-upgrade-motd file.

Removing this with rm /var/lib/ubuntu-release-upgrader/release-upgrade-available and rebooted and logged in again and the MOTD was normal as expected.

Steps to take:

  1. cd /var/lib/ubuntu-release-upgrader/
  2. rm release-upgrade-available