Don’t forget to modify your Windows Server Power Options

Following a troubleshooting session I’ve had lately, I wanted to share with you an important recommended settings that most folks (myself included) often overlook.

With more and more virtual servers and less and less physical servers being deployed, capabilities like SpeedStep of a CPU were forgotten. Take for example the following “modest” specifications of Intel Xeon E5-2690 v2, with 10 cores @ 3.0 GHz this is a “fare” spec for a high load / CPU intensive profile server.

BUT ! if you forget to select the “High Performance” power option in Windows Server for example, you could end up with:

e5-2690v2 at half speed

Notice that the speed of the CPU is less the half the speed it can run at. now to make things better, just make sure to select the “preferred” settings for your busy server:

e5-2690v2 at full speed

Just a heads up for all you folks out there, the default “Balanced” option caused a performance issue with an Exchange 2013 server that was running on this physical hardware and once the option was changed – all was back to normal ๐Ÿ™‚


Microsoft Exchange Web Services Managed API 1.1 Download

Hi All,

Following a workaround mentioned on – “GetUserOofSettings”, “SetUserOofSettings” and “GetUserAvailability” operations do not support Exchange Impersonation on the Exchange Server 2010 SP1 schema

Seems like the EWS Managed API 1.1 download link does not work anymore, and it’s virtually impossible to get a hold of the files on the WEB, so I’ve uploaded the redistributable package here for anyone looking around for it.

Anyway – grab it here: Microsoft Exchange Web Services Managed API 1.1

Hope this helps.


Exchange Web Service Managed API 1.1, Download – Microsoft ( Non working download links) :

Ammy Admin Error 12007 with Windows 8

Hi again,

I’ve been using Ammyy Admin to support family members and friends for a while now, but since I’ve upgraded to Windows 8, the program seems to fail it’s initial connection to it’s public servers upon start up.

It keeps popping out an error window:

Error {12007} occured while connecting to server “”
Would you like to change proxy settings?

Ammy Admin Error 12007 Windows 8

To solve this, just open the Ammyy Admin setting menu and un-check the “Run under SYSTEM account on Windows Vista/7/2003/2008” check-box.

Uncheck Run under SYSTEM account

hope you find this useful.


Office Suite – Latest Updates

Hey again,

I tend to always spend some time looking up the latest Office / Outlook updates, and found this following link from the office center on TechNet to be much useful.

It has a nice table of the latest Service Pack, Latest Public Update and Latest Cumulative Update for Office 2003 / Office 2007 / Office 2010 – Update Center.

Enjoy !

Microsoft Knowledge Base monitoring

I’d like to share with all of you one of best effective sites I use to “track” hotfixes for Microsoft products..

The nice thing about this website is that it sorts, yeah ! sorts the products and list the updates by date also ๐Ÿ™‚ simply amazing.

For example, the list of KB’s that were written for Exchange 2010 in the year 2010.

Enjoy !

Delete old removed or disconnected device drivers

So you’ve plugged a harddrive / disk-on-key or any other hot plugged device, and oops BSOD ๐Ÿ™

or, you want to install a new driver for a device that you have removed, but windows magic plug-and-play installed the driver automatically…. but you don’t want that do you ?

Anyway there’s an old method that works great.

You open device management, and click , view “show hidden devices”… but you fail to see your disconnected devices…

FIX – Show all disconnected devices, open System Properties, click Environment Variables and click to add a New System Variable.

Configure a New System Variable

After this you will be able to launch Device Manager again and when you’ll click to Show Hidden Devices, you will see all those removed or disconnected device drivers !

Device Manger Before-After

That’s it ! Enjoy

Local operating system boot fails when external storage is attached

Well the topic explains this quite enough..

but I’d like to share little more.

A typical Exchange 2010 deployment based on Server 2008 R2, we used IBM Blade Center HS22 this time with a QLogic HBA to connect to an EMC Symmetrix storage with FC … okay, enough hardware talk. ๐Ÿ™‚

The “symptom” was that after connecting the LUN’s to the and creating the partitions, well the next reboot to the server was .. unsuccessful… shocked as we were, after some quite tryouts: Drivers, Firmware upgrades, disable that and disable that … and when all failed …some searching, we came up with a few links… all seem to be quite “close but no cigar”.

Local operating system boot fails when external storage is attached – IBM System x3550 M2, x3650 M2 and BladeCenter HS22

UEFI-aware OS doesn’t boot after load defaults or deployment – IBM BladeCenter and System x

The system becomes unbootable after you add raw disks to a Windows Server 2008 R2-based computer that has EFI enabled

First real world experiences with IBMโ€™s x3650 M2

The last link includes a comment by “Rudi” , which gave us a good idea. lets try it again…

well, we did ! and guess what ?? IT WORKED.

Quick wrap up:

1) HS22 BladeCenter – Server boots from local raid-1 SAS disks with a GUID Partition Table (GPT) – Server 2008 R2 EFI boot loader.

2) 21 LUN’s attached with FC from a EMC Symmetrix storage (MBR).


3) Make sure you initialize all drives with GPT – Guid Partition Table. that’s it !

Smile ๐Ÿ™‚

** quick notice. to sum all the other links, if you use a non uefi aware OS (basically only server 2008+ is uefi aware) you need to make sure to use the “Legacy Only” method.

Hope this helps, we spent quite some time around this issue.

Where did “newsid” go ? seems mark got the answer

Mark posted a great post about this ancient urban legend, “The Machine SID Duplication Myth”

For the record, just remember that NewSID was never the solution for imaging a computer as a template.
And i’ll quote some of mark’s post and leave you to read the rest on his blog..

On November 3 2009, Sysinternals retired NewSID, a utility that changes a computers machine Security Identifier (machine SID). I wrote NewSID in 1997 (its original name was NTSID) because the only tool available at the time for changing machine SIDs was the Microsoft Sysprep tool, and Sysprep doesnโ€™t support changing the SIDs of computers that have applications installed. A machine SID is a unique identifier generated by Windows Setup that Windows uses as the basis for the SIDs for administrator-defined local accounts and groups. After a user logs on to a system, they are represented by their account and group SIDs with respect to object authorization (permissions checks). If two machines have the same machine SID, then accounts or groups on those systems might have the same SID. Itโ€™s therefore obvious that having multiple computers with the same machine SID on a network poses a security risk, right? At least thatโ€™s been the conventional wisdom.

….I realize that the news that itโ€™s okay to have duplicate machine SIDs comes as a surprise to many, especially since changing SIDs on imaged systems has been a fundamental principle of image deployment since Windows NTโ€™s inception. This blog post debunks the myth with facts by first describing the machine SID, explaining how Windows uses SIDs, and then showing that – with one exception – Windows never exposes a machine SID outside its computer, proving that itโ€™s okay to have systems with the same machine SID. Note that Sysprep resets other machine-specific state that, if duplicated, can cause problems for certain applications like Windows Server Update Services (WSUS), so MIcrosoft’s support policy will still require cloned systems to be made unique with Sysprep.

Enjoy !

Thanks mark for the clarification.