(c) Copyright Global IT Technologies PTY LTD 2005


Solutions > Microsoft Server Solutions > Windows 2003 Server

| Introduction | Benefits | What we Offer | Case Study |
| Variants |


The successor to Windows 2000 Server, Microsoft's Windows Server 2003 (codename Whistler Server, also known as Windows NT 5.2) is a step in the evolution of Microsoft's server operating systems. Windows 2003 takes the stability of Windows 2000 Server, and brings compatibility and other features from Windows XP. Unlike Windows 2000 Server, 2003 boots up with none of the server components turned on, to reduce the attack vectors for new install. Also Windows 2003 includes compatibility modes to allow older code to run with more stability. It also includes enhancements to various services such as the IIS web server. In particular it was made more compatible with NT 4 domain based networking. Incorporating and upgrading an NT 4 domain to Windows 2000 was considered difficult and time consuming, and generally was considered an all or nothing upgrade particularly when dealing with Active Directory. Windows 2003 brought in enhanced Active Directory compatibility, and better deployment support, to ease the transition from NT 4 to Windows 2003 and XP.

Benefits from this Server

Discover the increased productivity, greater security and a lower TCO that flows from your move to Windows Server 2003. Windows Server 2003 is going to be a big hit with systems administrators very quickly. Following are few reasons why we think that way:

  • More Secure by Default - Microsoft underwent a radical culture change several months ago, and a primary focus of all software development now is security. This has had a beneficial effect on all Windows products already, but Server 2003 is the first server product to be released under this newly adopted policy. What this means to the product is that non-essential services (e.g.: IIS) are turned off by default, and you have to make the choice to enable them. It also means no more default "Everyone with Full Permissions" configurations in file & share permissions. Under the hood, the code itself has undergone much more scrutiny for unchecked buffers and other poorly written code problems that have posed security risks in past versions of Windows. This is a big one.
  • Group Policy Management Console - This is a new management tool for domains that will make implementing Group Policies much easier and more consistent. Group Policies is a powerful tool in Windows 2000 Active Directory settings, but the MMC interface that has been available until now could be called clunky at best. This new tool is actually available for download for administering Group Policies in Windows 2000 Domains, even before you install Windows Server 2003.
  • Shadow Copy Restore - Upgrading your user File & Print servers to Server 2003 could pay for itself with this feature alone if your users corrupt or delete their files frequently. This new feature allows you (if you have the disk space) to keep multiple versions of files in a secret shadow directory. If a user inadvertently deletes or corrupts a file, they can use the Windows Explorer window to see what past versions are available, and grab a new copy without any administrator or help desk intervention. Did your day just gain a couple hours of free time, or what?
  • Software Update Service - Think Windows Update (Web Site), but you control it. You can configure your client Windows workstations to obtain their Windows Updates from your own server--after you've tested and approved them, of course.
  • System Resource Manager - I used to be optimistic, but after this many years of Windows applications with memory leaks, I've come to face the fact that some companies just can't write good code. Windows Servers have borne the brunt of memory leak criticism (and frequent reboots) in the past, but now we have more power over resources allocated to buggy programs. With the System Resource Manager, you can use Group Policies to assign priorities and allocations of CPU and RAM resources to processes. In other words, you can assign a leaky app only as much RAM as it should need, and it won't be able to leak any more away. Of course, you will probably need to restart that application when it runs out of its own RAM allocation, but that's a whole lot better than having to reboot, no?

There are many, many more good reasons for making the jump to Windows Server 2003, but these are some of the top reasons on my list. In these days of tight budgets and focus on quick ROI, these are some features that can help you get approval for an investment in an upgrade.

Move to Windows Server 2003 - You'll never look back

Customers who have already upgraded to Windows Server 2003 are reporting improved security, lower total cost of ownership (TCO) and increased productivity as a result. With the support lifecycle for Microsoft Windows NT4.0 Server now over, there's never been a better time to migrate.

Solution we provide

We as Microsoft Gold Certified partner, try to understand in depth working of your organization and implement Windows 2003 in your current working environment without any hassles. Our engineers look into the minute details of the business process and then tailor the solutions as per need.

Whether your organization wants to upgrade or implement a Windows environment from start, we provide all types of services concerned with Windows Operating Sustem.