Featured Posts

Exploring Kutch by Road “Why Kutch?” friends asked when I shared my mini-vacation plans with them and I said, “Why Not?”. Even Amitabh Bachchan say’s as a brand ambassador to Gujarat Tourism – “Kutch Nahi Dekha...

Read more

Canon vs Nikon: Which DSLR to Buy?  When it comes to serious photography, photographers from around the world either prefer a Canon or a Nikon. But the question is: which one is the better of the two? To answer in one word: "Depends". In...

Read more

How to completely erase a Hard Disk Have you ever sold or given away your old laptop or desktop to replace it with a new one? Certainly you might have at some point of time in life and you must also have backed up your data and then formatted...

Read more

Mailbox Report Script for Exchange Server One of the tasks that every Exchange Server administrator faces as part of their daily or weekly maintenance is getting the mailbox size report of the Exchange Server. The PowerShell commands do help in...

Read more

SEO Tips for Web Site Designing We all have come across this word “Search Engine Optimization”. Some must have read it somewhere; some must have heard their web designing company talk about it, while some must be providing the services...

Read more

Comments : 0

Automate Patch Management with WSUS

Category : Microsoft Windows Server

Patching the Windows Operating System in an organization with multiple desktops and many flavors of operating systems is a mammoth task. It is vital for any Systems Administrator to ensure all systems are properly patched and updated to safe guard against virus, worms, and Trojans. The biggest challenge in running Windows Update on individual machines is the inconvenience of visiting each desktop and approving the updates manually. Moreover, the amount of bandwidth used at each desktop to download the updates is huge not to forget the lack of centralized reporting.

So why do we need a centralized patch management policy? Well, the answer is simple – the systems are prone to risks and threats when exposed to the Internet or medias like USB pen drives, wireless networks and devices, etc. We all, at some point, might have experienced or read about the havoc caused by Blaster or the Sasser worms. Today software vendors have stepped up the releases of emergency and critical updates in a formalized manner to encounter these threats. Microsoft’s Patch Tuesday is a good example that highlights that. To learn more about this program, click here.

WSUS from Microsoft is a boon to Network and System Administrators in this scenario. WSUS (Windows Server Update Services) is basically designed to run on a company’s network and automate the process of patching. This free product from Microsoft does a fair job of streamlining the overall patch management process of an organization with centralized reporting. For a Network or System Administrator it is just a simple task of installing the WSUS server on a system and then configures all Desktops to use the WSUS server for software updates. This can be easily achieved by creating a group policy and linking the policy to the correct OU using Group Policy Editor. The Desktops would automatically announce their current status to the WSUS server with details like which patches are needed to be installed, which patches have failed to install, which patches have been successfully installed, etc.

In a nutshell, WSUS seems to be a good product especially when there is no price tag attached to it and starting with WSUS 3.0 the reports have also improved over its predecessor.

Comments : 0

Wolfram|Alpha: First Impressions

Category : Thoughts

On May 18, 2009 Wolfram|Alpha was officially launched. Basically, it is a web tool that could be as important as any Search Engine or rather as important as Google (most popular of the breed). It is the brain child of British born physicist Stephen Wolfram and has been developed by Wolfram Research.

Wolfram|Alpha is an online service that computes and provides results to factual queries. In Google when we search for something, it provides us a list of web sites, documents and links while the same when computed at Wolfram|Alpha would provide a web page with statistical data. This should prove to be a boon to college students, researchers and the like. So out of Google, Wikipedia and Wolfram|Alpha, what do we use and when? Technically, while Google’s automated search algorithms crawl tens of millions of web sites to gather data, Wikipedia is a human-driven effort. Meanwhile, Wolfram|Alpha, uses a team of dedicated experts to add, evaluate, judge, and parse data.

I decided to give this new computational knowledge engine a try and choose “distance between Sun and Earth” as my query.

The results from Google were about 2,060,000 links and pages and the first link that it showed me was that to Wikipedia but not the actual figure.

Opening up Wikipedia provided me not only the figures but lot of interesting facts and data as well.

Feeding Wolfram|Alpha with the above query gave me the numbers in astronomical units – something which would not interest a common person. What I needed was either Kilometers or Miles.

The bottom line? Well, Wolfram|Alpha is surely promising as it offers a good amount of organized data along with charts and graphs. Moreover, Wolfram’s legacy application Mathematica has been put to use in Wolfram|Alpha and so this means that the site will shine in parsing mathematic queries. Maybe I’ve just scratched the surface of the knowledge engine here, but the fact is – how many Internet users would be interested in the statistical data.

Website: http://www.wolframalpha.com/

Comments : 0

Moving Mailboxes from Exchange 2003 to Exchange 2007 SP1

Category : Exchange Server

In the first part of this series, we discussed how to Install Exchange Server 2007 SP1 in a coexistence environment with Exchange 2003. For those who missed the article, they can view the same by clicking here.

Now that we have installed the Exchange Server 2007 SP1 in the organization, it’s time to move the user Mailboxes to Exchange 2007. Moving mailboxes is a very easy task and can be accomplished by using the Exchange Management Console or by using the PowerShell commands from command line. In this post I’m going to use the Exchange Management Console.

So, let’s open the Exchange Management Console and in the tree on the left, navigate to the Recipient Configuration and expand it. Under the node, select Mailbox.

Here we can see in the results pane that now we are able to see all the mailboxes that we have on our Exchange 2003 server and they are all marked as Legacy Mailboxes. This means that all the mailboxes are still on the Exchange 2003 Server and need to be moved to Exchange 2007.

In this example, we will move the Administrator mailbox. So we choose the account, right-click it and choose Move Mailbox.

The next screen provides us options as to where we want to move the mailbox and here we need to choose the mailbox database. I assume here that the Storage Groups and Mailbox Database are already created on Exchange Server 2007. If not, then that’s the first thing that you need to do.

 

In my example, I’m going to move the Administrator mailbox to the General Mailbox Database.

 

There now that we have selected the Mailbox Database, Exchange 2007 automatically appends it with the Server Name and the Storage Group. Click Next to proceed.

 

On the next screen we are presented with lot of options as what should be done if the Move Mailbox process encounters any errors or finds any corrupt messages in the mailbox. Either we can Skip the entire mailbox move or we can allow Exchange Server to move the mailbox and simply Skip the corrupted messages. Moreover, if we go ahead with that option, we can even define how many corrupted messages should be skipped before the Move Mailbox stops the process. Since, I would not like to skip any messages, I’ll choose “Skip the Mailbox” and move further.

 

Next we are presented with the scheduling screen which allows us to schedule the Move Mailbox process. This helps in particular when you are in a production environment with heavy traffic and want to schedule this unattended during off-peak hours. Moving mailboxes does not take much time and is entirely dependent on the number of items in the mailbox. Even in a production environment, while moving mailboxes, the user will hardly notice any issues and after moving the mailbox, the user may simply need to restart Outlook to get everything working again.

In the scheduling option, you can choose to move the mailboxes during off peak hours and also you have a choice to cancel the running task if the move mailbox task runs for certain hours. I’ll chose “Immediately” and move ahead in this example.

 

That’s the last screen that we see before we actually tell exchange to move the mail box. It allows you to do a quick round up of what we have selected and what options have been set. Once we have reviewed the options, click on “Move”.

While the mailbox is being moved, we can see the progress, the number of items found, the number of items moved, etc. If you select multiple mailboxes, note that by default Exchange 2007 moves only 4 mailboxes at a time. The remaining mailboxes will be shown as “Pending”.  Lot of checks are performed in the background by the Exchange Server during this process.

 

 

If all goes well, the final screen that we see is the confirmation showing us the status of the Move Mailbox process. Click on “Finish” to close the wizard. That’s it to Moving Mailboxes from Exchange 2003 to Exchange 2007.