Category: Microsoft

Convert Windows Server Evaluation to Server Standard

There are time when you install a Windows Server using the evaluation version and decided to buy the license. Microsoft has set that the product key must match the Edition of the server. For Example, StandardEval and ServerStand is 2 different SKU.

To solves this, you will need to convert the edition using the DISM command. Make sure you run this from elevated command prompt

DISM /online /Set-Edition:ServerStandard /ProductKey:XXXXX-XXXXX-XXXXX-XXXXX-XXXXX /AcceptEula

Exchange 2013: Exchange Admin Center (EAC) blank

Recently we have extra servers in our environment idling for quite sometime and since I’m also have some extra time that I can squeeze out of my day, I decided to test Exchange 2013. Sadly, after almost 18 months it was released I’m able to test it fully.

The installation is a breeze since Microsoft have simplified the Exchange 2013 server roles as in Exchange 5.5 – 2003 with only 2 roles, CAS & Mailbox. Anyway, installation part will be in another post.

One of the major changes in Exchange 2013 is that there is no more EMC (Exchange Management Console) and that’s really a good news for me as I have always hated using EMC due to the time it takes to present the information and lack of filtering feature as well as details information. It has been replaced with Exchange Admin Center or EAC.

I believe the most common issue for someone who testing Exchange 2013 is, you don’t know how to access EAC and when you have the address you are getting a blank screen.

How to access EAC

Https://servername.fqdn/ecp

Capture

if you are getting a blank screen

open your Exchange Management Shell (EMS) and run this command

Get-EcpVirtualDirectory | FL *URL*

Capture

Look for the InternalURL and copy and paste into your browser. Viola! You will get the the interface as in the 1st screenshot!

Hope this helps people who have the same problem like mine.

-Lokman-

Change Scope in Exchange Management Shell (EMS)

If you are an Exchange admin in a large organization where you have multiple domain in a forest and you just want to see all the Exchange object in the forest, you can use the following cmdlet

Capture

Set-AdServerSettings -ViewEntireForest $True

to change back, just change from $true to $false
Set-AdServerSettings -ViewEntireForest $false

Note:

In this mode, be careful when you ran any cmdlet as it will display all the related object in the environment if you are not careful with it. Eg. Get-Mailbox will list out all the mailbox in the forest. Imaging 20,000 mailboxes.
And to top it, Get-Mailbox -Database DBNAME | New-MoveRequest -TargetDatabase TARGETDBNAME. If you are not careful, you might move some other domain mailbox to yours. ahaha!

Remote Desktop IP Virtualization doesn’t work

Remote Desktop IP Virtualization

Remote Desktop IP Virtualization is a new feature introduce in Windows Server 2008 R2  which provides administrator the ability to assign unique IP to a session or a program which requires it.

By default, IP Virtualization requires a functional DHCP to be use as an address pool source but we can also define a static IP address range as the IP Pool (http://technet.microsoft.com/en-us/library/ee382306(WS.10).aspx)

Issue

During my Desktop Virtualization project, we had an application which can’t run on a multi-session environment and we would like to test whether by enabling IP virtualization can help to solves the issue. We have enabled and configured IP Virtulization based on the article in technet (http://technet.microsoft.com/en-us/library/dd759263.aspx) and after perform a testing, we can’t see the leased IP.

The expected result should show a multiple IP on a single interface as the screenshot below.

Root Cause

A case has been open to Microsoft, and it seems like it was caused by the 32bit version of Sophos Antivirus Client. Uninstall it and the problem goes away. 🙂

Applicable to:

  • Windows Server 2008
  • Windows Server 2008 R2
  • XenApp 6.5

Additional Reference


  1. http://www.windowsitpro.com/article/virtualization2/q-what-s-remote-desktop-services-ip-virtualization-and-why-would-i-want-it-

Unable to launch Excel from Sharepoint

If you getting the below error when trying open an excel from a sharepoint library, the the issue might be because you don have the Sharepoint OpenDocument class as you add-on. These can be caused by either you are using 64bit version of the IE or the add-on is not there.

Solution – just use 32bit version of IE or repair your outlook. If your share point is running on version 2010, it is better to install a Microsoft Office 2010 for better experience. 😉

The document could not be opened for editing. A Microsoft SharePoint Foundation compatible application could not be found to edit the document

MS Exchange Dirty Shutdown: Explained and Troubleshooting

I’ve been using Microsoft Exchange 2003 and playing with it for almost 4 years and during these 4 years, I have encounter many kind of issues involving this product. And the father of all this “issues” is exchange database “Dirty Shutdown”. This is by far the worst and most common issues that I’ve heard or experience.

So what is exchange “Dirty Shutdown”?

As the name suggest, “Dirty Shutdown” is when the MS Exchange shutdown dirtily, whatever that means. All jokes aside, it’s actually really bad even disastrous. A “Dirty Shutdown” happens whenever the Information Stores have not been closed in a properly manner. This might be due to power outage or power surges or any other action that might caused the server to be inproperly shutdown.

Most people usually think of dirty shutdown as the indication of damaged database. But that’s not the case at all. It’s just that Exchange database has not been shut normally and therefore it becomes our area of concern as it leads to corruptions in Exchange database .EDB and .STM files.

From TechNet

A Dirty Shutdown state does not indicate the database is corrupted or damaged. A Dirty Shutdown state indicates only that the database files were not detached from the log stream correctly. Therefore, before you can start the database again, you must first recover the database files.

The next time that the database is mounted, this recovery is run automatically. If automatic recovery fails, you can use the Microsoft Exchange Server Disaster Recovery Analyzer Tool to analyze the reasons for failure. After analysis, the Exchange Server Disaster Recovery Analyzer will provide recommendations for manually recovering the database files.

So how to check for Dirty Shutdown?

Login to you Exchange Server that you want to run the check and follow these steps.

  1. Click Start, and then click Run.
  2. In the Open box, type CMD, and then click OK.
  3. Switch to the C:\Program Files\ExchSrvr\Bin folder, type one of the following commands (as appropriate to your situation), and then press ENTER:
  4. type in eseutil /mh <My_Database_Name.edb>
    eseutil /mh "c:\program files\exchsrvr\mdbdata\priv1.edb"

    dirtyshutdown
    Find State: when you have “Dirty Shutdown”  it will say “State:Dirty Shutdown”.

Continue reading