Software: MenuRead Updated

An update to MenuRead, a tool that allows you to easily find where objects are located within the Microsoft Dynamics NAV menu structure, is now available. The latest version includes several enhancements:

  • Added support for 2015 objects (Page, Xmlport)
  • Added option to export menu as XML file

MenuRead is a utility that was designed to make an easier task out of finding where items are located on a Microsoft Dynamics NAV menu.Download MenuRead >>here<<

How to determine the version of PowerShell that is installed?

You can see the version of the PowerShell Engine by using the $PSVersionTable.PSVersion table. If you run Get-Help about_Automatic_Variables and read the contents of the $PSVersionTable you will get the following information:

Contains a read-only hash table that displays details about the version of Windows PowerShell that is running in the current session. The table includes the following items:
CLRVersion: The version of the common language runtime (CLR)
BuildVersion: The build number of the current version
PSVersion: The Windows PowerShell version number
WSManStackVersion: The version number of the WS-Management stack
PSCompatibleVersions: Versions of Windows PowerShell that are compatible with the current version
SerializationVersion: The version of the serialization method
PSRemotingProtocolVersion: The version of the Windows PowerShell remote management protocol

In-place upgrade Windows Server 2008 R2 Standard to Enterprise without Media

If you need to upgrade a server running Windows Server 2008 R2 Standard to either the Enterprise, or Datacenter editions you can use the installation image and choose the Upgrade option or the new command-line utility, introduced in Windows Server 2008 R2, DISM (Deployment Image Servicing and Management). With DSIM it is possible to perform the upgrade online, without the need to reinstall Windows or have the installation image. 

 To perform the upgrade in-place online, without the media image, first open an elevated command prompt (run as administrator) on the server to be upgraded. 

Type the command DISM /Online /Get-CurrentEdition. This will display the current Windows version. 

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

Type the command DISM /Online /Set-Edition: <TargetEdition> (replace <TargetEdition> with the syntax for the desired edition returned by Get-TargetEditions). 

If you receive a message (Error 87) indicating that you need to specify a product key you can include it with the /ProductKey: parameter 

If you receive a message (Error 50) indicating that Setting an Edition is not supported then the machine may be a Domain Controller (DC) and it must be demoted before performing an online upgrade. You do not need to demote it if you are using the installation image. 

As always, be certain that you back up all of your settings and data prior to performing the upgrade.

SQL: How to test a SQL Backup

When reviewing disaster recovery processes I often get asked how a verify / test that a SQL Backup is “good”. Restoring the backup file is a solid and reliable way to verify the backup file, however it may not always be practical due to space and/or time restrictions.

During the backup task, you can check the “Verify backup when finished” reliability option to verify the backup set is complete and readable.

After the backup file has been create you can execute the following commands:

RESTORE VERIFYONLY FROM DISK='<your backup file name.bak>'
This option verifies the backup set is complete and readable, however it does not validate the data structure.

RESTORE HEADERONLY FROM DISK='<your backup file name.bak>'
Retrieve the header information of the backup set.

RESTORE FILELISTONLY FROM DISK='<your backup file name.bak>'
Returns a list of files in the backup set.

There are options available to test the integrity of the backup file, however you should periodically test your disaster recovery / business continuity plan. It is important to verify that the contents of your “backup” contains the pertinent data for a proper recovery.

Installing Windows 2012 Server in Hyper V

In order to become familiar with Windows Server 2012 and ensure application compatibility I decided to install Windows Server 2012 within a Hyper V machine. Virtual Machines are wonderful. The ability to create, snapshot, and restore “machines” without having to having all this hardware is wonderful.

I downloaded the Windows Server 2012 ISO from MSDN and attached it to DVD Drive media of a newly created virtual machine. I booted the machine and started down the road of a Windows Server installation.

Windows Server 2012 Installation Screen

The process started ok, however once I started the installation I received a driver error:

"A media driver your computer needs is missing. This could be a DVD, USB, or Hard disk driver. If you have a CD, DVD, or USB flash drive with the driver on it, please insert it now."

Windows Server 2012 Installation Error

I reviewed all of the settings, hardware configurations and even verified that Windows Server 2012 runs within Hyper V. Everything checked out and I started the install again and received the same error. Needless to say it was a bit frustrating. The physical server is only 5 months old and I have installed several other test servers, from ISO files, running in Hyper V without an issue. I was pretty comfortable with the hardware configurations and even verified the ISO file was valid.

After several failed attempts to load the server from the ISO file I decided to burn the ISO to a DVD. I then loaded the DVD into the server and attached the physical DVD drive media to the virtual machine. This time the installation process started and finished without an issue.

It seems that the installation was not able to process/cache the full tree of files and using a physical disk did the trick.

Reading Stuff

Information in this document subject to change without notice.
All Software source code published is for demonstration and knowledge sharing purposes only. The Code is supplied "as is" without warranty as to result, performance or merchantability. Use at your own risk.
The opinions expressed herein are the opinions of the author and do not reflect those of any other entity.