Adventures of an IT Pro

How to install Update Rollup 4-v2 for Exchange Server 2010 SP1 Faster

noreply@blogger.com (Ilker Aydin) — Mon, 19 Sep 2011 18:13:00 +0000

This post is purely based on my recent experiences in installing the Update Rollup 4-v2 on a number of Exchange 2010 servers with my team. With default settings and via regular Windows Update interface, it takes about 45 minutes to 70 minutes to install this 30MB hotfix on decent (12 cores and 64GB RAM) physical boxes. On the other hand we found that if the update is downloaded as a separate package from MS download site (http://www.microsoft.com/download/en/details.aspx?id=26910) and run in an elevated command prompt (cmd.exe, runas administrator) it only takes about 10 minutes to finish the installation. We also found that temporarily disabling UAC reduced the installation duration to 10 minutes, even via the regular Windows Update interface.

I also "googled" this issue and our resolution but could not find anything so far. Therefore I cannot explain why running the update in an elevated command prompt or disabling UAC speeds up the process.

Finally if you experience the same thing with this Update Rollup (or any other update) please share your experience here using the comment link.

Vmware Vcenter 4.1 Upgrade and Search Bug

noreply@blogger.com (İlkay Aygün) — Fri, 27 Aug 2010 11:13:00 +0000

We have upgraded our virtual center from 4.0 update2 to 4.1 on the 4th of August. After a period of time, we have realized that the search function did not find new vms that we have created since the upgrade.
Made a little bit troubleshooting and diagnosed the problem's cause. It was Tomcat's VcCache-default-0.XhiveDatabase.DB cache database, not working properly. We decided to open a call to vmware and learned that this is accepted as a bug waiting to be fixed soon. And desperately began to wait for the solution.
Today by chance, I made a search in google about the problem again and found the solution!
It was solved on the 25th of August in another case declared to vmware again.
The bug is solved by raising the memory dedicated to tomcat java application. In our case it is solved by raising up to 2 GB.
Here is the link that I found.
I suppose also an official article would be available soon about the bug.

http://communities.vmware.com/thread/282117

Vmware Tools Automatic Upgrade

noreply@blogger.com (İlkay Aygün) — Wed, 18 Aug 2010 08:21:00 +0000

We have been facing a problem in our environment to upgrade the vmware tools of our guests.
The problem is that some of the guests never automatically upgrades vmware tools even if you have enabled "Check and upgrade tools during power cycling" or selected "Upgrade Tools" within vmware tools tray.
Basically the guest does nothing after you trigger upgrade or power cycle.
After searching for a while we have found an article which has no relation with our case but somehow true and solved the problem.
The problem was caused by a prior vmware tools installation file "vmwaretoolsupgrader.exe" in C:\windows\temp directory to be deleted before triggering the upgrade. After deleting the file, everything works seamless. here is i link to the kb;

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1023459

Tips for a Successful Vmware Converter Operation

noreply@blogger.com (İlkay Aygün) — Tue, 08 Dec 2009 08:15:00 +0000

For the ones making P2V operations using Vmware Converter plug-in, sometimes it is a nightmare to troubleshoot why the agent fails to proceed. I've tried to compile my experiences on the Vmware Converter plug-in for a successful import without facing any errors.

First of all make sure you read and open the ports necessary if there is firewall(s) between vc, hosts and guests. you can find the official link to the article below;
http://kb.vmware.com/kb/1010056/
Before you launch the plug-in, make sure the guest resolves both the vc and host with their fqdn. If necessary, enter the fqdns in the host file.
Always reboot the guest after the agent is installed (even the vmware says a reboot is not necessary)
Make sure the admin$ of the guest is reachable from vc (in order to install agent).
And finally if all of the above are true and you still see face an error while importing, you can find a verbose log named vmware-converter-agent-0.log (increments if a file size threshold exceeds) under the client's below directory;

%allusersprofile%\Application Data\VMware\VMware Converter Enterprise\Logs

Exchange 2010 RC is Ready

noreply@blogger.com (Ilker Aydin) — Fri, 21 Aug 2009 05:01:00 +0000

Exchange Server 2010 Release Candidate (RC) is available for download at the following link:

http://technet.microsoft.com/en-us/evalcenter/dd185495.aspx

Largest Exchange Mailbox?

noreply@blogger.com (Ilker Aydin) — Wed, 29 Jul 2009 20:07:00 +0000

I have been working with Microsoft Exchange Server since v5.0. During all those years and versions, I have seen mailboxes of all sizes. I have seen users with a couple of 4GB pst files. The largest mailbox I have ever seen on a system was around 8GB, and I used to think it was huge... until recently. I was performing a "site assessment" for a client and was collecting information about their Exchange Server 2003 environment. Since the disk space was a non-issue for the client, there were no quotas defined at the mailbox size level. I opened up the Mailboxes view in ESM and sorted the mailboxes by size to see the top 10 mailboxes and I got perplexed. I looked at the screen again, and asked the IT Manager if I was seeing right. Here's what I saw:

(The names of the users have been blurred to protect the innocent.)

So now the largest single mailbox I have ever seen is 27GB. How about you? What is the largest mailbox size you have ever witnessed? Please share your experiences and thoughts using the "Comments" link below.

Windows 7 on Dell Latitude D810

noreply@blogger.com (Ilker Aydin) — Mon, 27 Jul 2009 06:38:00 +0000

This may not be my most technical post, but I would like to share my recent experience with Windows 7 on my company provided Dell Latitude D810 laptop. It has a 1.73 Ghz Intel Pentium M Processor, 2GB of RAM and a 60 GB harddisk.I have been using this laptop since the day I joined the company, second week of December 2006.

I have always been amazed by the fact that this laptop was capable of running Windows Vista. Although I have been working on this laptop since December 2006, the laptop was actually purchased in June 2005. Because Vista OS was brand new when I started to work for BVA, I started right away with Vista. My first few months (OK I admit, my first year till the SP1 was released) was not so pleasant. I had performance issues, intermittent VPN connectivity problems and wireless network issues of all kinds. I used to think my problems were caused by due to the fact that Dell did not provide any Vista drivers for this model. However, after the SP1 install, all of my problems disappeared. Since then, my experience with the laptop and Vista has been quite good despite all the negative hype created around this version of Windows. Please keep in mind that this laptop is not officially "Built for Vista" or even "Vista Ready". The only label it has on reads: "Designed for Microsoft Windows XP".

So when Microsoft announced the next version of the Windows Operating System, I got curious. When I read comments and reviews like "Windows 7 runs much better than Vista", "Windows 7 can run on any hardware which supports XP", I thought I could give it a try. When my coworkers started to install and test out the RC code with their relatively newer generation laptops, I decided that it was time.

Because I was too lazy for a backup and restore operation, I initially decided to perform an "in-place upgrade". To avoid conflicts during the upgrade process, I uninstalled my VMware Server, Cisco VPN Client and virus scanning software. Upgrade process ran about an hour or so with no problems. At the end of the process the laptop rebooted for the last time, and I got the infamous "blue screen of death" (BSOD). Following the BSOD, the installer ran again and rolled back the upgrade process. Within 20 minutes of the BSOD, I got my Vista OS back, like nothing's happened. This first unsuccessful attempt was about six weeks ago.

Following this unsuccessful attempt, I had no choice but to perform a "wipe and install" operation. Because of time constraints, I was not able to perform this operation until last weekend.

I had considerable amout of data, but I did not want to perform any "System Transfer" (or Files and Settings Migration). In addition, in case of a second failure, I needed a tool that can perform image based backups and restores. So I used the free DriveImage XML tool (http://www.runtime.org/driveimage-xml.htm) for this purpose. The tool let me create an image based backup of my full drive, and gave me the option to perform file and folder level restores using this backup set. You can use the tool to create online backups (i.e. you can backup your computer while the operating system is running), or you can use it with WinPE and create offline backups. I used the online backup method.

Following the backup, I started the Windows 7 RC installation. I wiped out the existing partition and Windows 7 created a new hidden system partition, plus a new boot partition. Intallation was quick like Windows 2008 installations.

After the installation I found myself with some non-working devices. My network card was there, but wireless card (Intel(R) PRO/Wireless 2200BG Network Connection) was not recognized by the installer. In addition, I had an "PCI Simple Communications Controller" device with no drivers. Finally, my video card was recognized as "Standard VGA". First I had to find the Wireless driver to gain access to the Internet. Then after a brief Google research, I found that the "PCI Simple Communications Controller" actually was listed as "Texas Instruments PCI 6515 Cardbus" at Dell's web site. Finally, I was able to install the "ATI Mobility RADEON X600" driver with no issues. Please keep in mind that all these drivers from Dell were actually created for Windows XP. After the drivers, I updated the OS, and installed my favorite virus protection tool. Finally, I installed Driveimage XML, and only restored Downloads and Documents folders from the backup set. I installed MS Office 2007 quickly and started to test and see the differences between Vista SP2 and Windows 7 RC. First impression, Windows 7 boots and comes back from hibernation faster than Vista. With Latitude D810, my "Windows Experience Index" is 1.0, because of poor 3-D graphics support. I searched for an updated driver for ATI X600, but so far I have been unsuccessful. Most importantly, Windows 7 has a smaller footprint than its predecessor: right after the boot, it's using roughly 700MB of RAM while Vista was consuming almost 1GB. No need to say, any program looks (or feels) faster in Windows 7 as well.

Finally, my biggest challenge with Windows 7 was to install Cisco VPN client. I heard and read bad experiences and BSOD horror stories about Cisco VPN Client on Windows 7. However, I really needed Cisco VPN Client on my laptop, so I asked Google. I was lucky enough to find not only one but two alternative solutions to the problem.

1. Following the instructions at http://weblogs.asp.net/bhouse/archive/2009/01/15/how-to-successfully-install-cisco-vpn-client-on-windows-7.aspx, I first installed Citrix DNE Update, then installed Cisco VPN Client v5.0.05.0290 with no problems. I have tested a number of different connections, and it works great.

2. Dell Latitude 810 does not support this option, because it requires a CPU with Intel Hardware Virtualization support. This option is called "Windows XP mode for Windows 7". Microsoft presents this option to break the incompatibility barrier between the older applications and the new OS. According to Microsoft, any application compatible with Windows XP should work in this mode. However, because of hardware constraints, it is not for everybody. As the first prerequisite, you need a CPU with hardware virtualization (Intel-VT or AMD-V) support. Even though the newer CPUs support this feature, you have to explicitly enable it at the BIOS level. Then, you can follow the instructions here (http://www.microsoft.com/windows/virtual-pc/download.aspx). As a final step, you can install Cisco VPN Client in the XP virtual PC. This is a great feature and provides a very well integration with the host operating system (i.e. Windows 7). One of my co-workers was able to complete this process with his Latitude 820 and got Cisco VPN Client working without the Citrix DNE update.

My overall experience with Windows 7 on my 4-year-old laptop so far has been great. Next step is to get my hands on the RTM code and upgrade the OS one more time. I will try to post about this experience as well. How about your experience/thoughts about Windows 7? Please us the "Comments" link to provide feedback about this post or share your experience about Windows 7.

Update to the post (Nov 09):

After I had used the RC code for a couple of months, I finally found the available time slot to perform a transition to Windows 7 RTM. As some of you have already mentioned, all I needed was to download and install the Windows XP graphics and the audio drivers from Dell's Web site. All other devices were automatically recognized by Windows 7. For the wireless network card drivers, I had to run Windows updates.

In addition, Cisco released an updated version of their VPN client software. Right now I am running Cisco VPN Client v 5.0.06.0100 on Windows 7, and it is really fast.

Unable to Mail Enable Public Folders

noreply@blogger.com (Ilker Aydin) — Thu, 23 Jul 2009 22:38:00 +0000

One of my clients had a recent issue. He wanted to create and "Mail Enable" a new public folder in their Exchange 2007 infrastructure. He used the UI (not the Exchange Shell commands) for the purpose. He did not receive any error messages when he right clicked the folder and selected "Mail Enable" from the context menu. However, then he wanted to verify the operation and tried to open up the properties of the folder. At this step, he received the following error:

The Active Directory proxy object for the public folder '\Root Folder\Sub Folder' is being generated. Please try again later. It was running command 'get-mailpublicfolder -Server 'ServerFQDN' -Identity "\Root Folder\Sub Folder".

We checked almost everything including the "msExchOwningPFTreeBL" attribute. Even if we created a top level folder, the behavior was the same. Mail Enable was running with no problems, but when we checked the properties of the public folders, we were getting the exact same error message.

Because we had retired the Exchange 2003 servers recently, I even thought this issue might be related. However I was not able to find anything to prove this.

My long Google search did not return much results either. Then, in Technet Forums, I found a post which was about a similar problem. In their case, they were working on the RTM version and they noticed that the "System Attendant " service had been shutting itself down intermittently. Their solution was to make sure that the "System Attendant" was running. After reading this post, we immediately checked and verified that the service was already "up and running". Then we thought, since we have nothing to lose, we could try restarting the service. After "System Attendant" restart, we "Mail Disabled" then "Mail Enabled" the public folder. Finally, when we checked the properties of the public folder, we got no errors and were able to verify the new e-mail address of the folder.

I really don't know what was wrong in the first place, but apparently "System Attendant" was not performing properly. Then the service restart fixed the problem. Since the other services do not depend on the "System Attendant" anymore, the service restart did not require us to take all the other Exchange Server services down.

We spent a couple of hours on this "interesting" problem, and with this post I am hoping to save you same time if you run into the same issue.

Windows 7 and Windows Server 2008 R2 RTM'd

noreply@blogger.com (Ilker Aydin) — Thu, 23 Jul 2009 04:12:00 +0000

Microsoft announced today that the new version of the Windows operating system has been released to manufacturing.

http://www.microsoft.com/Presspass/press/2009/jul09/07-22Windows7RTMPR.mspx

Microsoft resources also announced the availability of the new version with the following blog post.

http://windowsteamblog.com/blogs/windows7/archive/2009/07/21/when-will-you-get-windows-7-rtm.aspx

Windows 7 Tips & Tricks

noreply@blogger.com (İlkay Aygün) — Fri, 29 May 2009 07:00:00 +0000

Attached document contains very useful tips for managing Windows 7 features easily, as we already know some of them from Vista.
Taken from Microsoft Partnering Site

Download Tips&Tricks for Windows 7

Update Rollup 7 for Exchange Server 2007 Service Pack 1 Can Kill OWA and Web Based Services

noreply@blogger.com (Ilker Aydin) — Wed, 06 May 2009 06:05:00 +0000

No matter how careful you are with your network, you cannot avoid getting bitten by patches or fixes occasionally. I have seen this exact same behavior with three different networks, so I think there's some sort of pattern going on.

Here's what's been happening: Right after you install "Update Rollup 7 for Exchange Server 2007 Service Pack 1" successfully in your environment, OWA and ActiveSync may not work at all. I want to repeat this one more time: the installation might run without any errors or warnings, but you may still end up with a non-functional OWA.

Uninstalling Rollup 7 might solve the problem, but I have found a better solution: Simply repeat the installation of the "Update Rollup 7 for Exchange Server 2007 Service Pack 1" package one more time. This second install will take care of OWA and Web Based Services problems for good. Only in one instance, the installation process failed to re-enable the Exchange services at the end of the installation. Simply re-enabling Exchange Services and restarting the server solved the problem.

I am not sure under what circumstances this issue occurs, but I hope this simple yet effective tip can save you from frustration.

How to Install Operations Manager 2007 R2 on Windows 2008

noreply@blogger.com (İlkay Aygün) — Tue, 21 Apr 2009 12:15:00 +0000

It is a little tricky path (espacially reporting) to install OpsMgr 2007 wSP1 or OpsMgr 2007 R2 on a Windows 2008 system.
I tried to explain the steps to take before every component installation for a successful OpsMgr installation.

Download Document

Terminal Server 2008 - Issues and Solutions - Part 1

noreply@blogger.com (Ilker Aydin) — Sat, 07 Feb 2009 19:42:00 +0000

I have been working on a project where we setup a TS 2008 farm (made up of three virtual servers) on a three node VMware Infrastructure 3 environment. During the implementation of the systems, we had to tackle a number of problems and discrepancies. Some of the problems were related to Windows 2008 compatibility, and some of them were direct results of feature set changes in the new OS.

1. Windows 2008 on VMWare ESX and Painfully Slow Performance

Our Session Broker Load Balanced farm included three virtual Windows 2008 Terminal Services servers. Along with them we had two seperate file servers. One of them was designated for roaming terminal services profiles, the second one was for shared MS Office files and users' home folders. All systems were running on Windows 2008, except one single Windows 2003 domain controller for another which was used for domain migration. ESX hosts were running on 16GB of RAM and Quad Core 2.5GHz CPUs, while guest TS servers were configured with 4GB of RAM and 4 CPUs.

Right after the installation and data migration, we invited some pilot users to test the environment. They were supposed to test standard Microsoft Office Applications, along with their third party Business Management Software. All pilot users agreed on one point: systems were "painfully slow". Logons were taking extremely long, sometimes up to 5-6 minutes. Opening a 40KB Excel file was taking a minute on average and sometimes users had to wait forever for a small file to open. Furthermore, working in their Business Software was almost impossible.

The environment described in that article was very similar to ours with one exception: while we were running Symantec Corporate Edition 10.2, their problems were caused by Symantec EndPoint Protection Server 11.0. Knowing that both security solutions share the same roots and just to see the effects, we removed SAV Corporate Edition from the file servers. After the reboot, performance returned back to normal.

Removing the SAV Corporate Edition from the Terminal Servers helped reaching the normal perfomance values. We were able to open any Excel file with no latency. As described in the article above, instead of Symantec Corporate Edition 10.2, we upgraded the systems to Symantec EndPoint Protection 11 MR3. Installing Symantec EndPoint 11 MR3 did not affect the performance, so I hope the problem has been resolved with this release. We have also installed a number of OS patches to the systems after this, so far the systems are still running properly, I assume Symantec had adressed and resolved the problem with MR3. At the time of this writing, I can see that the latest release for Symantec Endpoint Protection is MR4. We are planning to implement this soon, I will also update the post if it affects the performance.

2. Terminal Services 2008 and Adobe Reader Problem

Some users were not able to run Adobe Reader on the Terminal Servers. After every failure, they were getting "Adobe Reader has stopped working" error message. With each failure, the following message was logged in the Application log:

Log Name:      Application

Source:        Application Error

Date:          12/16/2008 1:53:03 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      TS01.domain.local

Description:

Faulting application AcroRd32.exe, version 9.0.0.332, time stamp 0x4850f0a3, faulting module Annots.api, version 9.0.0.332, time stamp 0x4850e57f, exception code 0xc0000005, fault offset 0x001bd9e0, process id 0x2e1c, application start time 0x01c95fc0491c84c1.

Since the error points out to "Annots.api" file, my initial response was to locate the file in Plug_ins (C:\Program Files\Adobe\Reader 9.0\Reader\plug_ins) folder and rename it to "annots1.api". However this did not help. The user received the exact same ""Adobe Reader has stopped working" error, and in the application log complained about "annots1.api" this time.

My second action was to move the file out of plug_ins folder. After the move the problem disappeared. However, I was sure that this is not a wise solution. So as a final test, I moved the file back to the plug_ins folder then enabled Compatibility mode and set it to "Windows XP SP2" on "Acrord32.exe" file. I was able to verify that this action resolved the problem for good. No problems were encountered after this change. I also had to repeat this action two other Terminal Servers.

3. Terminal Services 2008 and Session Broker Problem

To be able to distribute the load among three Terminal Servers, we have configured Terminal Services Session Broker service and Session Broker Load Balancing. I will not go through all the configuration steps, you can easily find detailed configuration information from many different resources in the web. However, I would like to mention about a discrepancy in Session Broker configuration. One of the steps during configuration is to supply each Terminal Server with the name of the Session Broker Server. This can be achieved by two different methods:

i. You can specify the name manually on each server's Terminal Services Configuration

ii. You can specify the name in a GPO and assign this GPO to all Terminal Servers

Regardless of the configuration method, as per Microsoft, the name you need to specify can be either in host name, IP address of FQDN form. In GPO Editor, if you examine the "Explain" section of the group policy setting (Computer Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\TS Session Broker\Configure TS Session Broker server name), it reads:

"If you enable this policy setting, you must specify the TS Session Broker server, using either its host name, IP address, or fully qualified domain name. If you specify a name or IP address for the TS Session Broker server that is not valid, an error message is logged in Event Viewer on the terminal server."

Unfortunately, I found that above statement is only partially correct. If you select to use FQDN, you will eventually see the following errors on each Terminal Server's event log:

Log Name: System
Source: Microsoft-Windows-TerminalServices-SessionBroker-Client
Date: 12/6/2008 9:36:19 PM
Event ID: 1014
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: TS01.domain.local
Description:
The server failed to retrieve the security identifier (SID) of the TS Session Broker server.
Win32 error code: 0x6FC.

You will find that Session Broker functionality intermittently stops (the service stays running but terminal servers fail to join) when you use FQDN in this configuration. To get rid of this warning and intermittent failures, you need to specify host name (i.e. NetBIOS name) of the Session Broker server. After changing it to the host name, the warning does not show up anymore. Somehow, FQDN does not work properly. I did not get a chance to test out the effect of using straight IP address for this setting, if you have similar experience and if you are using the IP address, please let me know if it works.

Exchange 2007 Multi Node Single Copy Cluster and Additional MTA Issue

noreply@blogger.com (Murat Akın Irmak) — Tue, 09 Dec 2008 15:32:00 +0000

Based on my experience , there is no need for addinational MTA on Exchange 2003 Multi Node Cluster. If you have an MTA resource on first Exchange 2003 node, you don’t need additional MTA resource at other Exchange Nodes.

But If you install multi-node single copy Exchange 2007 Cluster, you have to create additional MTA in Active Directory (by using AdsiEdit) for every additional Exchange 2007 nodes. If you don’t do that you cannot create a mailbox on these Exchange nodes.

You receive the following error in Exchange Management Console: “A proxy generator DLL on server FQDN.serverName could not be found or failed to initialize. Proxy addresses for the current recipient cannot be calculated. Please ensure that all proxy address generator DLLs have been installed on the target server”

Additionally, the following event may be logged:
Event Type: Error Event Source: MSExchangeIS Event Category: General Event ID: 1201 Description: Error -2147221233 reading/decrypting the msExchResponsibleMTAServer attribute on the Server object in the Active Directory. For more information, see Help and Support Center at Data: 0000: 5b 44 49 41 47 5f 43 54 [DIAG_CT 0008: 58 5d 00 00 26 00 00 00 X]..&... 0010: ff f0 0d 00 00 00 00 00 ÿð...... 0018: 00 02 18 00 00 00 cd 4a ......ÍJ 0020: 20 10 00 00 00 00 bd 5f .....½_ 0028: 20 10 00 00 00 00 bd 5f .....½_ 0030: 20 10 00 00 00 00 .....

Move Mailbox operations doesn’t care about additional MTA on every Exchange2007 Server on cluster. You can successfully move mailboxes to these Exchange servers. But these clients cannot logon via Outlook Web Access or MAPI (Outlook).

You can find additional information at http://support.microsoft.com/kb/928811 Microsoft support article.

802.1X NAP and Certificate Issue

noreply@blogger.com (Murat Akın Irmak) — Tue, 09 Dec 2008 14:56:00 +0000

At this posting , I want to talk about 802.1x NAP and Certificate related problems. According to my experience , you have to use a certificate from Enterprise CA at Network Policy Server’s certificate. StandAlone CA’s certificate is not working properly at NPS. Another issue about certificate is Client Machine certificate. According to my experience also, you have to use computer certificate and machine authentication at 802.1x NAP. If you don’t use computer certificate and also computer authentication on 802.1x NAP clients, there would be authentication failure at Pre-Logon stage. This problem causes cached logons on client computers, clients wouldn’t get either group policy or password expiration notifications.

Microsoft Office Communications Server 2007 using Direct SIP to Cisco Unified Communications Manager Simultaneous Ringer 7.0(1) Feature

noreply@blogger.com (Murat Akın Irmak) — Tue, 09 Dec 2008 13:13:00 +0000

Hi Everyone
This time , I want to talk about OCS 2007 and Cisco Call Manager Integration. Upon my OCS 2007 telephony experience , Cisco Call Manager has only direct integration with OCS . İf you want to remote call control , you need to Cisco Unified Presence Server. But Cisco Unified Communications Manager‘s mobility feature allows you simultaneous ringing (not Dual Forking) , cisco ip phones or Cisco IP Communicators and OCS MOC clients or Microsoft Phone Editions at the same time. You can find related howto solution at http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns728/ns784/716742.pdf. Also you can test this feature at virtual test environment. Because Unified Call Manager 6.x or above can be intalled at WmwareWorkstation or ESX for testing purposes. If you use Dual forking and Remote Call Control you will have "in a call" status even when you are using the phone. It's only Nortel that supports Dual forking and Remote Call Control right now. Here is the Supported IP-PBXs for Microsoft Office Communications Server 2007 link :http://technet.microsoft.com/en-us/office/bb735838.aspx#ippbx2

Vista SP2 Beta and Windows 2008 SP2 Beta Available

noreply@blogger.com (Ilker Aydin) — Sat, 06 Dec 2008 05:39:00 +0000

Microsoft has released Windows 2008 SP2 Beta with some interesting changes. For me, most important news is that same installer can be used for both Windows 2008 SP2 and Vista SP2. As many of you already know, Windows 2008 was released with SP1 code included. Essentially Windows 2008 RTM and SP1 are the same code. That's why the first downloadable service pack for Windows 2008 is SP2.

If you want to test out the new SP2 Beta, check out the following link:

http://technet.microsoft.com/en-us/windowsserver/dd262148.aspx

You can also find the detailed information here:

http://technet.microsoft.com/en-us/library/dd351466.aspx

Useless hiberfil.sys file on Windows 2008

noreply@blogger.com (İlkay Aygün) — Tue, 02 Dec 2008 10:10:00 +0000

Hibernation is disabled by default when you first install Windows 2008. However, a hidden file called hiberfil.sys is created as big as the amount of physical memory on the system partition of the disk (not more than 4 GB). As using hibernation is not reasonable on production servers, you can delete this file and gain space by simply running "powercfg.exe /h off" command without quotations.
There is also a support article http://support.microsoft.com/kb/920730/en-us

Check State & Start Specific Service Script

noreply@blogger.com (İlkay Aygün) — Mon, 01 Dec 2008 12:57:00 +0000

The below script checks the state of the DHCP Server service and tries to start it if stopped.

Download Script

A User Deleted Emails by Mistake? No Need to Restore from Backup!

noreply@blogger.com (Ilker Aydin) — Mon, 01 Dec 2008 04:13:00 +0000

Before I start, I have to admit that the title of this post can be found little bit misleading. This statement is only true under certain circumstances. However, to my experience most Outlook users usually are quick to realize their own mistakes and they usually inform IT Department about accidental deletions within a week. So if your "Deleted Item Retention Period" value is set to a number larger than 7 (or still at default value of 14) days, and if the user comes with a restore request within this period, there really is no need for a restore from backup. Although this is feature has been around for a long time, I recently realized that it's not well known among most IT Generalists.

Last week, for two occasions I was asked for assistance in restoring lost emails from backups. In the first case, one of my clients was trying to restore emails with Symantec Backup Exec 12. In the second case, another client needed step by step guidance with MS Data Protection Manager (DPM) 2007 to restore an accidentally deleted folder within "Inbox". Surprisingly, they both had users who accidentally deleted a bunch of emails and email folders from their Exchange Server mailboxes. For both cases, it took a little investigation to find out that the deletions took place within the last 7 days. So when I recommended them to use "Recover Deleted Items" feature in Outlook instead of tape restores, both of my clients were surprised.

Both of these clients are sharp and intelligent IT Generalists. They manage mid-sized networks with a bunch of business applications along with their Exchange Servers. So Exchange Server management is not their only (or primary) responsibility. I think that most of the IT Generalists might be missing the fact that you can recover any deleted mail item within the limits of "Deleted Item Retention Period". So this post is for you, the IT Generalist who missed this powerful Exchange Server and Outlook feature. If you're an Exchange Server Admin (I mean, if Exchange Server is your primary responsibility), I assume you're already aware of this really neat feature.

You can find plenty of online blog posts and articles on this topic. Microsoft KB Article 246153 explains the required registry key change for Outlook 2003 and older versions. MSExchange.org has an excellent article which describes all the basic information in detail along with OWA restore method. However, because these resources are relatively older, they fail to mention that Outlook 2007 does not require a registry trick to enable this feature. In other words, with Outlook 2007, you don't need to add the "DumpsterAlwaysOn" registry value to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\Options key, because it's already there by default. For the Outlook versions prior to 2007, you have to add the registry value manually as described in MS KB Article, then restart Outlook. Alternatively, if you are still on Exchange 2003, you can use the OWA method described at MSExchange.org. However, Exchange 2007 OWA does not provide a similar functionality. You can only recover deleted items at the "Deleted Items" folder in OWA 2007 SP1.

With Recover Deleted Items feature, you can recover individual mail items, folders along with their contents, even if they were deleted using "Shift + Delete". If the deleted folder is one of the top level folders (like Inbox, Sent Items, Junk Email, etc.), you need to select the "Mailbox" at the Navigation Pane, then select Tools and Recover Deleted Items to reach the list of deleted folder(s). With this method you can also recover items that are deleted with "Mailbox Management" process.

Finally, I want to mention about a great MSDN blog post by Doug Gowan, which discusses the necessity of backups in Exchange 2007 environments and outlines the scenarios when "Recover Deleted Items" feature can be used.

Limitations of Branch Distribution Points in SCCM

noreply@blogger.com (İlkay Aygün) — Fri, 28 Nov 2008 15:24:00 +0000

If you are going to implement the branch office scenario in SCCM and deploy branch distribution points on workstations, be sure to read the article "Clarifying: Retry Behavior for Distribution Points" which is not officially documented in TechNet and posted by SMS Writing Team.
It is about the 10 concurrent TCP connections limitation in client operating systems.

Install XP Guest on ESX Systems

noreply@blogger.com (İlkay Aygün) — Fri, 28 Nov 2008 07:38:00 +0000

As ESX does not support IDE disk controllers, it will be tricky to install an XP guest on the ESX host. You will either need LSI or Bus Logic SCSI drivers in FLP image format.
So it is a question where to find or how to create these floppy images.
Here is a link to download official BusLogic floppy image (also can be found in VmWare site but I could not find it easily in my second attempt...)

Download Floppy Image

Windows Firewall and SCOM Agent

noreply@blogger.com (İlkay Aygün) — Thu, 27 Nov 2008 12:03:00 +0000

When windows firewall is enabled by group policy on clients and you want to install SCOM agent using discovery in SCOM console, you get a message saying "RPC server is unavailable" at the end of discovery and agent install fails.

The below powershell script reads computer accounts from AgentList.txt and uses .net to stop windows firewall service on the remote host (as powershell does not support remote shell at the moment) and then uses discovery to install SCOM agent. After finishing, it starts the Windows Firewall service again.

Download PowerShell Script

Desired Configuration Management in Configuration Manager

noreply@blogger.com (İlkay Aygün) — Thu, 27 Nov 2008 07:09:00 +0000

Desired Configuration Management is a a new and useful fetaure in Configuration Manager. I tried to explain the basic steps to configure and interpret the reports of DCM.

Download Article

Script to Audit Disk Usage

noreply@blogger.com (Ilker Aydin) — Fri, 21 Nov 2008 07:57:00 +0000

This is a very basic script, which connects each server in a given list, then collects and reports the disk usage information for the fixed disks on each system. Script displays the drive letter, disk size, used and available disk space information on the screen and writes to a tab separated text file. I selected the tab separated file format for portability: You can easily copy and paste the contents to an Excel sheet. Script uses WMI to connect to the servers and collect the data, so please be aware that you will either need to shutdown Windows Firewall or add a "file and printer sharing exception" on the target systems.

I have tested the script on Windows XP, Windows Vista, Windows 2003 and Windows 2008. I hope the script will be very handy for easily creating disk usage reports on multiple servers and/or workstations. This script uses a very similar logic to my service account audit script. Only difference is in the WMI query section.

Usage:

cscript q_FixedDrv.vbs filename

For example:

cscript q_FixedDrv.vbs serverlist.txt

To download the script and sample serverlist.txt file, click on "I agree", you will be forwarded to the download site. Modify the serverlist.txt file to fit your test environment, then start the script. If the result you get is satisfactory, then create another list file which includes your production servers/workstations. If you have any feedback regarding this script, feel free to contact me using the comment link. I really want to know if you like it or hate it.