Windows Server Group Policy

Conversion of Primary DNS Server to an Active Directory Integrated Primary Server

2010-02-11T14:08:00.000-08:00

Every website on Internet has a unique URL, which locates the website. The URL consist of the domain name, which is converted into the corresponding IP address with the help of DNS server.
You can also convert your Primary DNS server to an Active Directory Integrated Primary server, instead of adding secondary DNS servers. The concept behind adding secondary DNS server is to avoid any failure. With the following steps you can convert Primary DNS Server to Active Directory Integrated Primary server on Windows Server 2003:
STEP 1: On the current DNS server, start DNS Manager.
STEP 2: Right-click a DNS zone, click Properties, click the General tab, and then note the Type value. This will be Primary zone, Secondary zone or Stub zone.
STEP 3: Click Change.
STEP 4: In the Change Zone Type box, click to select the “Store the zone” in Active Directory check box. When you are prompted to answer whether want this zone to become Active Directory integrated, click Yes, and then click OK.
When you complete all the steps, then in the Domain properties, type will be shown as "Active Directory-Integrated". You can supplement other DNS servers in the domain controller after its replication becomes complete. So, in this way you can supplement other DNS servers, which lead to removal of any point of failure.

Remote Support Services

2010-02-08T12:07:00.000-08:00

Remote support services are an array of technical services offered through the Internet. Many technical service providers offer remote support for a range of services. Your system should have an Internet connection in order to utilize remote support services.

Services offered through remote support are enlisted below:

· Software installation

· Virus removal

· Windows upgrades

· System tune-up and routine maintenance to speed up the computer

· Configuring settings for e-mail, or Internet, or Microsoft Office

· Removal of spyware applications

· Troubleshooting

· Internet optimization

· Support for peripheral devices

Along with these services, remote support provides you many benefits. Most important benefit is the availability; you can access remote support from anywhere in the world. You do not have to take your system to any service provider, and no need to call someone at your premises.

You just have to contact any technical service provider, and your issue gets resolved. A technician from your service provider will access your system via remote connection. After that, he will diagnose the issue that is not letting your system perform better and fix it simultaneously.

So, it is viable to say that remote support services are much better than traditional services. You just have to pay once and get access to a wide variety of services through remote support.

Windows Server Support

2010-02-07T13:07:00.000-08:00

Microsoft had launched a series of server operating systems under the brand name Windows Server. Some of the server operating systems are, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, Windows Server 2003, Windows 2000 Server and others.
Microsoft offers support for all its products including server operating systems. You can visit Microsoft support website, in case you have any technical issues related to Windows Servers.
You can receive a lot of information related to Windows Servers from Microsoft support website. Some of the issues on which you can receive information are, how to configure an authoritative time server in Windows Server 2008 R2, how to troubleshoot shutdown problems in Windows Server 2003, Windows Server 2003 service pack 1 support tools, how to lock down Windows Server 2003, how to configure Internet printing in Windows Server 2003, how to enable Telnet Server in Windows 2000 Server and many others.
Beside this, you can contact a technical service provider for Windows Server support. Technicians at technical service providers make use of remote connection in order to access your system online. After accessing your system, your issues will be analyzed and resolved. So, you do not have to take pain of inviting a technician at your own place because your issues will be resolved through the Internet.

How to enable DHCP on Windows 7?

2010-02-03T12:52:00.000-08:00

DHCP Server for Windows 7
DHCP (Dynamic Host Configuration Protocol) server offers information about IP address, subnet mask and default gateway to the clients. DHCP server for Windows 7 has been enhanced in many areas like support for SSID caching, optimization for obtaining IP address and others.
Suppose, your Windows 7 computer is connected to an intranet having multiple subnets and the Internet, but having a default gateway for both adapters. In this situation, you can either communicate with all computers on the intranet or Internet, but not with both of them. In order to solve this problem, you have to configure a default gateway with the adapter connected to the Internet. This is where the role of DHCP server comes into play.
In case, you want to configure a default gateway on Windows 7 PC follow the procedure:
STEP 1: Open Network Connections by clicking the Start button, and then clicking Control Panel. In the search box, type adapter, and then, under Network and Sharing Center, click View network connections.
STEP 2: Right-click the network adapter that you want to configure a default gateway for, and then click Properties. If you're prompted for an administrator password or confirmation, type the password or provide confirmation.
STEP 3: Click the Networking tab.
STEP 4: Under “This connection uses the following items”, click either Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6), and then click Properties.
STEP 5: In the dialog box that appears, select either “Obtain an IP address automatically” or “Use the following IP address”.
a) If you configure the network adapter to obtain an IP address automatically, the default gateway is assigned by the DHCP server.
b) If you manually specify an IP address configuration, the default gateway is the IP address in the Default gateway box on the General tab
After completing this procedure, you can configure a default gateway on your Windows 7 PC.

Benefits of Print Server

2010-01-31T09:05:00.000-08:00

Print server can be a computer or any device which is capable of connecting with one or more printers along with the client computers over a network.
Print server has many benefits because it lowers the administrative and management workload. A print server enables an administrator to manage and control access to each printer. Three level of printer permissions are available, print, manage documents and manage printer. Print permission is granted to everyone in the group. It allows a user to print documents, pause, resume, start and cancel his documents.
Manage documents permission is allocated by administrator to some selected users for controlling job settings for all documents. Manage printer permission enables the user to pause and restart the printer, share a printer, adjust printer permissions, modify printer properties and modify spooler settings.
Client computer jobs are quickly spooled to print server when compared to printer. The main point to be noted is that while printing large jobs from an own printer, resources of client computer are used and he may have to leave his computer running until printing task gets completed. But with the use of print server, if any job has been spooled to it, then user can shutdown his system without any harm.
Print server can also work according to priority of documents. The document with the highest priority will be printed first.

Windows Server 2008 - Top 5 Extraordinary Features

2010-01-23T00:33:00.000-08:00

Server 2008 is one of Microsoft Windows' server series of operating systems. It is the successor to Windows Server 2003. Like Windows Vista and Windows 7, Windows Server 2008 is built on Windows NT 6.x. In this blog we’ll discuss some of its extraordinary features.
NTFS - Windows’s server 2008 used an improved version of NTFS, a new system service works in the background that can identify a file system error, and perform an automatic healing process without anyone taking the server down.
Address Space Load Randomization (ASLR) -Probably one of the most divisive included features already, especially since it’s introduced with Vista, ASLR makes sure that no two subsequent instances of an operating system load the same system drivers in the same location in memory each time.
Powershell - It's a part of the shipping operating system: the completely new command line tool that can either supplement or completely replace GUI-based administration.
Server-Core - Windows Server 2008 introduces a variation of installation called Server Core. Server Core is a radically scaled-back installation where no Windows Explorer shell is installed. All configuration and maintenance is performed completely through command line interface windows, or by connecting to the machine remotely using Microsoft Management Console. However, Notepad and some control panel applets, such as Regional Settings, are available.
Windows System Resource Manager- It offers resource management and can be very handy to control the amount of resources a process or a user can use based on business priorities. Process Matching Criteria, which is defined by the name, type or owner of the process, imposes restrictions on the resource usage by a process that matches the criteria. CPU time, bandwidth that it can use, number of processors it can be run on, and allocated to a process can be restricted. Restrictions can be set to be imposed only on certain dates as well.

Windows 7 DHCP Server - Steps for better networking

2010-01-14T13:14:00.000-08:00

The concept of Dynamic Host Configuration Protocol (DHCP) is an important aspect for better network in regards with security, reliability, manageability and usability. It also avoids conflict between similar IP addresses, which are often caused due to human error. Moreover, it has simplified the job of administrator where they don’t need to assign IP address again and again.
When this technology is implemented with Windows 7 user can gain excellent internet experience over their mobile network.
Key advantage of DHCP server along with Windows 7
• Easy to locate the client with the distinct IP address
• Easy to manage the client computer
• Least resource consumption, which attributes for enhance network performance
Hence, DHCP server along with Windows 7 will be very useful for the businesses and enterprises to manage their business from remote places over the laptop and PDAs mobile. This will increase the pace of communication with utmost security.
Let’s see how we can configure DHCP server for Windows 7.
STEP 1. Click Start, Control Panel, and then click Add Or Remove Programs
STEP 2. Select “Add/Remove Windows Components”
STEP 3. It will initiate Windows Components Wizard
STEP 4. From the Components list box, select Networking Services, and then click the Details button
STEP 5. The Networking Services dialog box opens
STEP 6. In the Subcomponents Of Networking Services list box, check the Dynamic Host Configuration Protocol checkbox
STEP 7. Click OK
STEP 8. Click Next
STEP 9. On the Windows Components Wizard page you will get the prompt of Complete process. Click “Finish”
Hope, you will find this blog extremely useful.

Role of IT Server in Business Growth

2010-01-13T08:33:00.000-08:00

IT server has changed the scope of business. Now the business has gained a global dispersal leading a healthy competition and better productivity.
Role of IT server
• Facilitates quick access of data over LAN and WAN
• Allows centralized data storage
• Centralized backup
• Implement efficient data security
• Permit resource sharing
• Secure data sharing
IT server should be dynamic in function, it must manage, store, send and process data on 24/7/365 basis. Hence, it should be reliable and secure. To get the job done, it must be equipped with:
• Duel processors; either equipped or capable
• Redundant hard drives or power supplies
• Hot swappable components
• Internet security package and firewall
Different IT servers are required to accomplish different tasks. Accordingly we can have the following categories of IT server.
Application IT Server: These are deployed for managing the multiple applications over a LAN or WAN from a centralized administrator computer. Different work stations are managed with respect to data flow. In order to manage huge application an IT server must have built-in redundancy, monitors for high-availability, high-performance distributed application services and support for complex database access.
Print IT Server: Installation of Print IT Server is a cost-effective approach and reduces the number of printer. You can share a single printer over your entire LAN network. Your print IT server will manage the print file request and sends the file to the requested printer.
Database IT Server
Design and architecture of Database IT server is resembles with client/server architecture model. Total number of applications running over the server is divided into two parts: a front-end running on a workstation (where users collect and display the database information) and the back-end running on a server where you need to perform data analysis and storage.
Mail IT Server: This is a life blood of corporate networks (LANs and WANs). It would facilitate easy, fast and cheap mode of communication. It will manage your e-mail clients.
Web IT Server: It is extremely useful for processing request of web browser through HTTP communication. Hence large enterprises who owns their websites needs to have an efficient Web IT server, so that the customer request can be processed without any delay.
FTP IT Server: Enterprises who have their offices in multiple locations should amend dynamic and reliable IT server, so that the file and data can be shared over the Internet without any issue. Hence, important for both downloading and uploading of a file.
Proxy IT Server: If your server is getting overloaded with client request you can establish a Proxy IT server which intermediates between web browser and real server. Real role is to maintain a time gap and perform filtration of request. Hence, it’s important for the security concern too.

Smart IT support for healthy competition

2010-01-12T10:18:00.000-08:00

IT industry has become the backbone of every infrastructure. Hence, vitality of IT support has increased by manifolds. IT support is available for every segment of users. Home user can take the IT support for their personal desktop or laptop. Businesses and enterprises need it to keep their Windows server running in smooth condition with maximum productivity.
Scope of IT support
• Installation and upgrade of operating/application software
• Cognizant solution on feature and product
• Develop user-interface program
• Troubleshoot and fix any bug
• Data backup and recovery
• Joint product analysis with manufacturer/developer
• Manage Internet security
Different enterprises are offering reliable and authentic IT support services on both remote and onsite visit basis. Remote support is getting too much popular because it is more reliable genuine and available round the time without any restriction of territorial boundary.
If you are equipped with reliable IT support service, you can concentrate on your core business in a better way. For every segment of user, they have consolidated and specific tariff plans.
Manufacturers of computer and software giants are working in collaboration with the certified Microsoft technical groups in order to build better customer relationship. They are outsourcing IT support to make it more authentic and cost efficient. But don’t worry for customer understanding services are available in plain English. Globally recognized organizations are offering IT server support in all languages to meet their objectives.

iYogi Secures $15 Million in Funding Led by Draper Fisher Jurvetson to Fuel Surging Market Share in Rapidly Growing Consumer Tech Support Market

2010-01-11T07:55:00.001-08:00

Significant New Round of Funding to Build on iYogi’s Global Delivery Platform and Enhanced Services with Channel Partners

New York, NY, January 6, 2010: iYogi, the fastest growing on-demand consumer tech services company, announced today it has raised $15 million in funding to accelerate the company’s continued global growth in consumer remote tech support services. Draper Fisher Jurvetson joined continuing investors Canaan Partners; SAP Ventures, a division of SAP AG; and SVB India Capital Partners in the new financing.

iYogi will use the investment capital to enhance services, expand its team of Global Tech Experts, and build on the significant growth it has experienced in the last year. Since 2008, iYogi has seen 300 percent growth in revenues and subscribers, and has doubled its employee base to 1,200. For the next year, iYogi is forecasting an additional 300 percent revenue growth and an increase to 3,000 Global Tech Experts worldwide.

“The surging demand for remote technical services stems from the critical need for computer owners to keep their systems up and running and retailers to differentiate their offerings, particularly as the PC market becomes increasingly commoditized and competitive,” said Mohanjit Jolly, Executive Director at Draper Fisher Jurvetson India. “With its global team of experts, advanced support services and intelligent knowledge platform, iYogi is well-positioned for significant expansion and differentiation in this category, and is partnering with top tier retailers, ISP’s, OEM’s and software vendors to broaden its footprint.”

iYogi’s Global Delivery Platform is powered by Microsoft Certified tech experts, an extensive knowledge base and advance tools for diagnostics, repair and maintenance. The company has witnessed exponential growth through online direct marketing across four primary geographies - US, United Kingdom, Australia and Canada. In the coming year, iYogi will continue to build on its online brand presence and expand upon its channel partnerships to accelerate global expansion in the vast market for remote computer tech support.

“We are delighted to have support from successful, high-profile venture firms like Draper Fisher Jurvetson along with Canaan Partners, SAP Ventures and SVB India Capital Partners,” said Uday Challu, co-founder and CEO of iYogi. “iYogi’s progress over the last year is both a strong reflection of the tremendous market opportunity for remote technical services and an indication of iYogi’s momentum in seizing significant market share. We are able to effectively and consistently address and resolve consumer concerns through our unique Global Delivery Model across multiple geographies with the highest resolution rates and customer satisfaction in this growing industry.”

Today, iYogi has more than 100,000 annual subscribers and provides thousands of single incident sessions every day on a 24/7 basis. Its Global Delivery Platform delivers on the highest customer quality benchmarks in the industry and gets smarter with every customer interaction, building a powerful knowledge base that provides unique customer insights on predictive needs to tech support

ABOUT DFJ

Draper Fisher Jurvetson ("DFJ") backs extraordinary entrepreneurs everywhere who set out to change the world. DFJ achieves its mission through its DFJ Global Network of Partner Funds. Together, DFJ and the Network manage over $6B and have made more than 600 investments on four continents. With a 24-year history of success across diverse sectors and market conditions, DFJ has led the way investing in emerging technologies, from the Internet and life sciences to clean energy and nanotechnology. DFJ has been proud to back over 500 companies across many sectors including such industry changing successes such as Hotmail (acquired by MSFT), Baidu (BIDU), Skype (acquired by EBAY), United Online (UNTD), Overture (acquired by YHOO), Athenahealth (ATHN), EnerNOC (ENOC), TicketsNow (acquired by TicketMaster), Feedburner (acquired by Google), Interwoven (IWOV), Four11 (acquired by YHOO), Parametric (PMTC), and Digidesign (acquired by AVID). For more information, visit: www.dfj.com

About iYogi

iYogi is a global on-demand services company that provides personalized computer support for consumers and small businesses in United States, United Kingdom, Canada and Australia. iYogi’s unique model, including proprietary technology iMantra and highly qualified technicians, is designed to eliminate computer-related stress and keep millions of digitally dependent consumers and small businesses always protected and productive. Only iYogi -- with its proven global expertise delivery model, intelligent customer insight systems, easy-to-use self-help tools and automated PC optimization and computer support services – offers users a simple yet comprehensive path to digital serenity. iYogi has perfected the remote technical support model to overcome the current limitations of in-store, on-site, or call center services to become the fastest growing provider of support in the industry. Major resellers and technology companies are increasingly turning to iYogi to improve customer satisfaction, reduce return rates, and deliver a compelling new-value added offering to customers. For more information on iYogi and a detailed list of technologies supported, visit: www.iyogi.net

Media Contact

Derek Kober

Global Fluency

Tel. :650-433-4233

Email:dkober@globalfluency.com

Contact:

Vishal Dhar

President, Marketing

Tel. : +1-212-229-0901

Email : vishal@iyogi.net

How to manage the Network Environment using Active Directory?

2010-01-06T14:22:00.000-08:00

Active directory –a property modifier
Active directory is the protocol which provides the platform to manage the network environment. Microsoft has done enough amendment to simplify the use of Active Directory in terms of management, migration and deployment.
Important feature of Active Directory include:
• Permission of X.500 close user group professional in the same company.
• Inception of secure data management
• Presence of hierarchical system allows the system administrator to have clean information of individual user accounts
• Object-targeted storage organization, allows easy access for information from anywhere in the network.

Benefits of Active Directory
• Organizations are able to perform their regular business operating while switching over from one network to other network platform.
• Users don’t have to do much amendment in the existing network.
• Existing user accounts and resource permission will be self migrated.
• Services and application running on the existing platform would also get migrated without any effort.

Deployment of Active Directory
User should follow the below suggestion to formulate Active directory over the new server platform.
• Test and verify the deployment process.
• Against the Forest Root create a DNS.
• Create the Forest Root.
• Map a new Regional Domain.
• Import your valuable data from other sources.

Installation of DNS Server in Windows Server 2003

2010-01-04T15:08:00.000-08:00

When you browse Internet, you always write alphanumeric address in the address bar. You write these type of addresses because these are easy to remember. The main point is that any server address is in the form of IP address. Then there arises the need of translating these alphanumeric addresses in the IP addresses. Here comes the role of DNS Server. DNS Server does the task of translating the alphanumeric address into the IP address. This server is required when you write any website address in the address bar or you click on any link. Before the installation of DNS Server, you should have the information about your domain name, the IP address and host name of each server for which you want to provide name resolution.

If you want to configure your computer as a DNS Server, then the following conditions should be fulfilled:

Your operating system should be configured in the correct way. DNS service is based on the correct configuration of the operating system and its services, in case you are using the Windows Server 2003 family. You have to allocate the available disk space. All the existing disk volumes should use the NTFS file system.

If you want to install DNS Server, then follow these steps:

Click on the Start, click on Control Panel and then click on the Add or Remove Programs. After this, click on Add/Remove Windows Components. Then open the Windows Components Wizard. In the Components, pick out the Networking Services check box and then click on the Details. In the Subcomponents of Networking Services, pick out the Domain Name System (DNS) check box, click on OK and then click on the Next. If you are prompted, then type the full path of the distribution files and then click on OK. In this way DNS Server will be installed on your system.

Alteration in Terminal Server's listening port

2009-12-15T21:36:00.000-08:00

It is a well-known fact that TCP port 3389 is used by Terminal Server and Windows 2000 Terminal Services for client connections. Alteration in this port is not recommended by Microsoft. But you can change this port. You have to perform this task carefully, otherwise you will face serious problems.
You have to give more concentration while modifying the registry. If you want to change the default port, then you have to follow these steps:
You start with the task of running Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. Then you have to find the port number subkey and notice the value of 00000D3D, hex is for 3389. After this, you have to change the port number in Hex and save the new value.
If you want to change the port for a particular connection on the Terminal Server, then follow these steps:
You have to run Regedt32 and go to this key, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\connection. After this, you have to find the port number subkey and notice the value of 00000D3D, here hex is for 3389. Then you have to change the port number in Hex and save this new value.
After performing this, you have to make alteration in the Port on the Client Side. Follow these steps to perform this:
You have to open Client Connection Manager. Then on the File menu, click on New Connection and then create the new connection. After executing the wizard, you will view a new connection listed there. Then you have to ensure that new connection is highlighted. After this, on the File menu, click Export. Then you have to edit the .cns file using Notepad. You have to make modifications in the server port, Server Port=3389 to Server Port= new port number, that you had specified on Terminal Server. Now import the file back into Client Connection Manager. Then you will be demanded to overwrite the current one. If it has the same name, then overwrite it. In this way, you will receive a client that has the correct port settings to match your Terminal Server settings.

Expanding the benefits of Terminal Server

2009-12-08T04:02:00.000-08:00

Terminal server allows the users to log in from any remote location and perform the desired task. It helps users in becoming more productive by enabling access to any of the recent applications on any device, admitting the under-powered hardware and non-Windows desktops. It can be considered as a basis for establishing an enterprise-wide, server-based computing platform and includes significant improvements in Windows Server 2003.

Terminal server supports many more users on each high-end server than Windows 2000. Support for Microsoft's network load balancing and other third-party load balancing technologies is given by the Session Directory available in the Windows Server 2003 Enterprise Edition. It takes the advantages of the technologies like Group Policy and provides remote manageability. If you want the complete remote management facilities, then you have to use a comprehensive read/write Windows Management Instrumentation (WMI) provider.

Remote Desktop Connection is an RDP 5.1 client has a much improved user interface, facilitating users to save connection settings. It is composed of a easily switch between windowed and full screen mode and dynamically modify their remote experience to check the available bandwidth. While connecting with a terminal server using an RDP 5.1 client, many of the local resources are present within the remote session. It also includes the client file system, smart cards, audio, serial ports, printers and the clipboard. These redirection facilities provide the users to easily take benefits of the facilities of their client device from within the remote session. For example, files can be opened, saved and printed on the users local PC, no matter whether the application is executing locally or remotely.

Improvements in Terminal Server

2009-12-08T03:38:00.000-08:00

The terminal server is one of the elements of Windows Server 2003. It is planned on the solid introduction given by the application server mode in Windows 2000 Terminal Services. It provides you the facility of delivering Windows-based applications, or the Windows desktop itself, to almost any computing device including those that cannot execute Windows. All the applications are executed on the server, when users run an application on terminal server.

Users are able to view only their own sessions, which are handled transparently by the server operating system. Sessions of one user remains independent of any other user's session. Windows 2000 Terminal Services remote administration mode is known as Remote Desktop for Administration in Windows Server 2003. It supports the Remote Desktop Protocol 5.1 feature set. It has the facility to monitor remotely the actual console session of the server.

Terminal server in Windows Server 2003 provides many important benefits. It can deploy Windows-based applications to computing devices across an enterprise. It can also deploy those applications that are frequently updated, infrequently used, or hard to manage. When any application is managed by it, it can be ensured by the administrators that the latest version of that application is under the execution. Terminal server considerably cuts down the amount of network bandwidth needed to access the data remotely. Use terminal server, when an application is executed over bandwidth-constrained connections, like dial-up or shared WAN links. It becomes very effective for remotely accessing and manipulating large quantity of data because only a screen view of the data is transmitted, instead of the data itself.

How to Manage Group Policy Objects in Windows Server 2003

2009-10-15T21:42:00.000-07:00

In order to create a GPO we must first make sure that our network has AD enabled so that Security Policies can be deployed, leaving us with the configuration of security specifications that we must manually configure when assigning GPO’s to a computer.

Our first steps in order to create a GPO, is to create a custom MM Console to manage Security Policy for our new GPO. Follow these steps indicated below to add a new GPO. This post provide help to create windows xp 2003 server terminal services group policy

Follow the steps given below

Step 1:Select Start--> Run, type MMC in the run dialog box and choose OK to open the MMC.

Step 2:From the Main Menu of the MMC, select File--> Add/Remove Snap-In.

Step 3:In the Add/Remove Snap-In dialog box, choose Add. The Add Standalone Snap-In is displayed.

Step 4:Highlight the Group Policy Object Editor Snap-In and choose Add. The Group Policy Wizard is displayed.

Step 5:The Group Policy Object specifies Local Computer by default. Choose Browse to browse for a Group Policy Object.

Step 6:The Domains/OU tab is the default showing the current domain. Notice that you can choose the default Domain Policy here and that you have a Create New Policy Object button to the right of the drop-down list of domains. In the Domains/OU tab, click the create New Group Policy Object button. Name the GPO Security Policy GPO. Choose Ok and then choose finish to return to the Add Standalone Snap-In window.

Step 7:Highlight the Event Viewer in the snap-in and choose Add.

Step 8:The select computer dialog box appears and Local Computer selected by default. Choose the Another Computer radio button and type the name of the domain controller computer from which you are doing this exercise.

Step 9:Click Finish then click Close.

Step 10:In the Add/Remove Snap-In dialog box, notice that the new GPO we created is now listed along with the Event Viewer.

Step 11:Choose Ok to return to the main console window.

Step 12:Select File--> Save As.. Save the console as Security Policy GPO in all Users\StartMenu\Programs\Administrative Tools folder and choose Save.

Step 13:Now you can access this console by selecting Startà Administrative Toolsà Security Policy GPO.

Now that we have installed our new GPO we need to set the appropriate permissions so that our users have ideal settings to certain information that may only be available to his or her department. In order to change the user permissions, we can easily set our settings in order to accommodate for our Security Policy that fits along with the GPO we created. In order set the proper settings please follow the sequence as indicated below to achieve this task.

Step 14:To access the Security Policy settings we have created for our GPO we need to access the Account Security Policies folder. Click Start--> Administrative Tools--> Security Policy GPO and the MMC Snap-In dialog appears.

Step 15:Expand Security Policy GPO--> Computer Configurationà Windows Settings--> Security Settings--> Account Policies.

Step 16:Under the Account Policy GPO Object we can control the settings for passwords, lockouts, local and user audits along with security options that can accessed and edited right from the MMC Console we created above.

How to Install AGPM Server

2009-10-13T22:24:00.000-07:00

his post proovides support to install AGPM server on your computer, you install AGPM Server on the member server or domain controller that will run the AGPM Service, and you configure the archive. All AGPM operations are managed through this Windows service and are executed with the service's credentials. The archive managed by an AGPM Server can be hosted on that server or on another server in the same forest.

To install AGPM Server on the computer that will host the AGPM Service

1. Log on with an account that is a member of the Domain Admins group.
2. Start the Microsoft Desktop Optimization Pack CD and follow the instructions on screen to select Advanced Group Policy Management - Server.
3. In the Welcome dialog box, click Next.
4. In the Microsoft Software License Terms dialog box, accept the terms and then click Next.
5. In the Application Path dialog box, select a location in which to install AGPM Server. The computer on which AGPM Server is installed will host the AGPM Service and manage the archive. Click Next.
6. In the Archive Path dialog box, select a location for the archive in relation to the AGPM Server. The archive path can point to a folder on the AGPM Server or elsewhere. However, you should select a location with sufficient space to store all GPOs and history data managed by this AGPM Server. Click Next.
7. In the AGPM Service Account dialog box, select a service account under which the AGPM Service will run and then click Next.

This account must be a member of the either the Domain Admins group or, for a least-privilege configuration, the following groups in each domain managed by the AGPM Server:
Group Policy Creator Owners

Backup Operators

Additionally, this account requires Full Control permission for the following folders:
The AGPM archive folder, for which this permission is automatically granted during the installation of AGPM Server if it is installed on a local drive.

The local system temp folder, typically %windir%\temp.

8. In the Archive Owner dialog box, select an account or group to which you assign the AGPM Administrator (Full Control) role. AGPM Administrators can assign AGPM roles and permissions to other Group Policy administrators, so that later you can assign the role of AGPM Administrator to additional Group Policy administrators. For this scenario, select the account to serve in the AGPM Administrator role. Click Next.
9. In the Port Configuration dialog box, type a port on which the AGPM Service should listen. Do not clear the Add port exception to firewall check box unless you manually configure port exceptions or use rules to configure port exceptions. Click Next.
10. In the Languages dialog box, select one or more display languages to install for AGPM Server.
11. Click Install, and then click Finish to exit the Setup Wizard.

More Installation tips for Install terminal server, small business server install, exchange server installation

How to Write a Network Security Policy

2009-08-27T00:22:00.000-07:00

Like all things dealing with security, the significant trade-off is security versus ease of use. Anything that's more secure will be intrusive, and one of the most compromised vectors for network security is the human element. If your security policies are onerous, and keep people from doing their work on the network, they will be circumvented by members of your organisation who will resent the put down on their time.

Communication with your organisation's members is important. A good network security policy addresses the human factors in securing your data. It needs to explain what your organisation's policies are, regarding proper use of computer and network equipment, and what procedures must be followed. It should have a clearly listed response chain for security incidents.

Some basic tips:

Be very clear in explaining why certain policy decisions have been made and what their costs are. Make people understand why they have to go through strange procedures, or have computers with no optical drives.

Understand that one size does not fit all; one of the worst examples of a network security policy is one that presumes that everything needs the same heightened level of security. In addition to driving productivity to a standstill, it often results in worse security, as people attempt to get their work done and leave classified documents out in the open rather than check them in and check them out every time they go to the rest room.

Evaluate your hardware as part of the policy. Do triage - what can you live with and live without? What absolutely needs to be restricted access, what needs off site backups to maintain organizational continuity and if an asset were lost, how much would it cost to replace? Will you spend more in employee time than the replacement costs, or are the replacement costs catastrophic?

Next, identify possible threats. What ways can someone access or distribute your data?

Once these have been identified, consider aspects such as physical security; who has access to the computers and the facility?, network security; who is to have access to which data sets, and authentication; how do you determine the right level of access per person and that the right people are using their pass codes?

How to manage Group Policy from command line

2009-06-29T22:32:00.000-07:00

H:\>gpupdate /?
Microsoftr Windowsr Operating System Group Policy Refresh Utility v5.1
c Microsoft Corporation. All rights reserved.

Description: Refreshes Group Policies settings.

Syntax: GPUpdate [/Target:{Computer | User}] [/Force] [/Wait:]
[/Logoff] [/Boot] [/Sync]

Parameters:

Value Description
/Target:{Computer | User} Specifies that only User or only Computer policy settings are refreshed. By default, both User and Computer policy settings are
refreshed.

/Force Reapplies all policy settings. By default, only policy settings that have changed are applied.

/Wait:{value} Sets the number of seconds to wait for policy processing to finish. The default is 600 seconds. The value '0' means not to wait. The value '-1' means to wait indefinitely. When the time limit is exceeded, the command prompt returns, but policy processing continues.

/Logoff Causes a logoff after the Group Policy settings have been refreshed. This is required for those Group Policy client-side extensions that do not process policy on a background refresh cycle but do process policy when a user logs on. Examples include user-targeted Software Installation and Folder Re direction. This option has no effect if there are no extensions called that require a logoff.

/Boot Causes a reboot after the Group Policy settings are refreshed. This is required for those Group Policy client-side extensions that do not process policy on a background refresh cycle but do process policy at computer startup. Examples include computer-targeted Software Installation. This option has no effect if
there are no extensions called that require a reboot.

/Sync Causes the next foreground policy application to be done synchronously. Foreground policy applications occur at computer boot and user logon. You can specify this for the user, computer or both using the /Target parameter.
The /Force and /Wait parameters will be ignored if specified.

Source: infotechguyz.com

How to Start the Group Policy Editor

2009-06-22T23:27:00.000-07:00

To start the group policy editor, follow these steps.

NOTE: You must be logged on to the computer using an account that has administrator privileges in order to use Group Policy Editor.

1. Click Start, and then click Run.
2. In the Open box, type mmc, and then click OK.
3. On the File menu, click Add/Remove Snap-in.
4. Click Add.
5. Under Available Stand-alone Snap-ins, click Group Policy, and then click Add.
6. If you do not want to edit the Local Computer policy, click Browse to locate the group policy object that you want. Supply your user name and password if prompted, and then when you return to the Select Group Policy Object dialog box, click Finish.

NOTE: You can use the Browse button to locate group policy objects linked to sites, domains, organizational units (OU), or computers. Use the default Group Policy Object (GPO) (Local Computer) to edit the settings on the local computer.
7. Click Close, and then in the Add/Remove Snap-in dialog box, click OK.

The selected GPO is displayed in the Console Root.

Source:support.microsoft.com

Properly Shut Down the Network Server - Why?

2009-06-15T23:32:00.000-07:00

In cases of diagnosing and troubleshooting problems, properly shutting down the server ensures safety of the programs and information held by the network server as the individual units it manages.

Importance

• Properly shutting down the server would ensure proper network configuration. Since the data line managed by the server is a critical aspect of its operations, the computers that are connected into the network maintains protection one computer. Sometimes, specific configurations are done to safeguard against damage, which may be caused by a file-corrupting virus. Properly shutting down the server ensures that whatever protective measures the unaffected or uninfected units have will work.

• Properly shutting down will enable software or file recovery in case of problems. System recovery makes use of a number of configurations that helps protect the network against serious damage. It also ensures that all the recovery software, if present, is properly configured. Hence, it minimizes the risk of losing important files or information in case technical problems arise.

• Properly shutting down the server, depending on the application settings, will enable backing up of important files.

• In case of serious technical problems, properly shutting down the server may restore default configurations. It might cause some of the computer units in the network to lose some infected or affected files, but not those that are crucial to retaining its operations.

• Often, cleanly shutting down minimizes the damage caused by incorrectly configured and damaged software or hardware in a network setup.

• Properly shutting down allows certain changes, such as those made when rebooting, to take effect.

• With coexisting but conflicting devices or software, properly shutting down aids troubleshooting measures, which also protects the other computer units in the network setup from getting damaged by the affected unit or units.

Simply, shutting down the server correctly is a standard operating procedure that ensures optimal performance and consistency in application programs and system capabilities in each of the computer units that is included in the setup.

Source: Ezine

How to Use the Group Policy Editor

2009-06-09T00:52:00.000-07:00

The Group Policy snap-in contains the following major branches:

* Computer Configuration

Administrators can use Computer Configuration to set policies that are applied to computer, regardless of who logs on to the computers. Computer Configuration typically contains sub-items for software settings, Windows settings, and administrative templates.

* User Configuration

Administrators can use User Configuration to set policies that apply to users, regardless of which computer they log on to. User Configuration typically contains sub-items for software settings, Windows settings, and administrative templates.

To use the group policy editor, follow these steps:

1. Expand the GPO that you want. For example, Local Computer Policy.
2. Expand the configuration item that you want. For example, Computer Configuration.
3. Expand the sub-item that you want. For example, Windows Settings.
4. Navigate to the folder that contains the policy setting that you want. The policy items are displayed in the right pane on the Group Policy Editor snap-in.

NOTE: If no policy is defined for the selected item, right-click the folder that you want and then on the shortcut menu that appears, point to All Tasks, and then click the command that you want. The commands that are displayed on the All Tasks submenu are context sensitive. Only those commands that are applicable to the selected policy folder appear on the menu.

5. In the Setting list, double-click the policy item that you want.

NOTE: When you work with policy items in the Administrative Templates folder, click the Extended tab in the right pane of the MMC if you want to view more information about the selected policy item.

6. Edit the settings of the policy in the dialog box that appears, and then click OK.
7. When you are finished, quit the MMC.

Source

How do I enable BranchCache?

2009-06-02T22:58:00.000-07:00

First, you need to make the server hosting the data generate hash values. Open a Group Policy Object. Navigate to Computer Configuration, then Policies, Administrative Templates, Network, Lanman Server. Double-click Hash Publication for BranchCache. Set this to Enabled, then configure when the hash should be generated, as shown here. You can generate hashes if a folder is shared and enabled for cache, never generate a hash, or generate a hash for every shared folder. Make a choice and click OK. Click to expand.

If you configured the server to generate a hash only if a shared folder is set to use caching, you need to Right-click the shared folder in Explorer and select Properties. Select the Sharing tab. Click the Advanced Sharing button. Click the Caching button. Check the Enable BranchCache option, as shown here, and click OK to close all dialogs. Click to expand.

You can also use the hashgen command to force a hash generation for other files, such as web files served via HTTP.

If you're using hosted cache, you now need to enable the BranchCache feature on a Server 2008 R2 server. For this walkthrough, I'll configure distributed cache (peer to peer).

The next step is to enable BranchCache on the clients. Again, I'll use Group Policy. Navigate to Computer Configuration, then Policies, Administrative Templates, Network, BranchCache. Double-click Turn on BranchCache and set it to Enabled. Because you're using distributed BranchCache, double-click Set BranchCache Distributed Cache mode and set it to Enabled. You can also configure the latency required before caching is used. You probably don't want to cache data if the connection is very fast, so you might only cache if the latency is over 70 ms. Double-click Configure BranchCache for network files, set it to Enabled and set the latency. In the example here, I set latency to 0, so everything is cached. Click to expand. Note that you can also set the amount of disk space to be used for the cache on clients. The default value is 5 percent. Use the Set percentage of disk space used for client computer cache option to set this value.

Now you need to enable two firewall rules. Navigate to Computer Configuration then Policies, Windows Settings, Windows Firewall with Advanced Security, Inbound Rules. Select New Rule from the right-click menu. Under HTTP, Port, TCP 80, create a rule to allow all profiles (or just a domain, depending on environment). Also create a rule under WS-Discovery, Port, UDP 3702 to allow all profiles (or, again, just a domain), as shown here. Click to expand. Close the GPO

At this point, you have a GPO with all the required settings. Make sure the GPO is linked to the client and the client refreshes its policy, either by rebooting or using the command gpupdate /force.

Source

Server Management Group Policy on Windows Server 2003

2009-05-27T04:46:00.000-07:00

Creating a server management group policy is a critical task that needs to be completed before allowing users access to any Terminal Server or XenApp Server. By default, any user who can login to the server can do many dangerous things. For example, the user can:

* Shutdown the server
* Reboot the server
* Use Internet Explore to install Windows Updates
* Access the server's hard drives

Note: Instead of saying Terminal Server and or XenApp Server throughout this article, I will use the term Server or Servers.

Many administrators refer to this as "locking down the Server". I prefer to use "managing the Server". Many administrators add other group policy items that do not add to "locking down" a Server but add to the management of a Server.

Just like there is no one way to design Active Directory (AD), there is no one way to design a Server management group policy. What works for high security environments would probably be overkill for a small business. If you were to gather ten network administrators in a room there will probably be ten different viewpoints on the "proper and secure" way to manage a Server.

From this article you will learn the basics of creating a group policy for managing your Server. This article will be using Windows Server 2003 R2 with SP2 with all Windows Critical, or High Priority, Updates, except Internet Explorer 8, as of May 2009. The following assumptions are made:

* The Group Policy Management Console is installed. If not, please see this Microsoft site.
* Your Servers are in their own Organizational Unit (OU)
* You are familiar with the concept of Loopback Processing Mode
* You know how to create a Group Policy Object (GPO) and link it
* Internet Explorer 7 is installed on the Server

Start the Group Policy Management tool, create a GPO and link it to the OU containing your Servers (Figure 3).

n Computer Configuration, expand Administrative Templates, expand System, click on Group Policy, double-click User Group Policy loopback processing mode, select Enabled, change Mode to Replace and then click OK (Figure 4).

Collapse System, expand Windows Settings, expand Security Settings, expand Local Policies, click Security Options and Enable the following Settings (Figure 5):

Devices: Restrict CD-ROM access to locally logged-on user only
Devices: Restrict floppy access to locally logged-on user only
Interactive logon: Do not display last user name

Collapse Local Policies, click System Services and Disable the following service (Figure 6):

Help and Support

Collapse Windows Settings, expand Administrative Templates, expand Windows Components, click Windows Installer and Enable the following setting (Figure 7):

Allow admin to install from Terminal Services session

Source

IBM Launches All-In-One Small Business Server

2009-05-20T04:46:00.000-07:00

IBM is launching an all-in-one hardware and software package as part of an increasing drive to tap small to medium-sized businesses' growing technology needs.

Taking its cue from an experiment in the Indian market, IBM has started selling what it calls a "smart cube," a server that comes pre-bundled with a range of business-specific software, such as accounting tools from Intuit Inc., in the U.S. IBM will offer support for customers.

The company, most of whose products are aimed at heavy-duty corporate computing, has increasingly been trying to reach smaller customers, many of whom have traditionally favored the combination of Microsoft Corp.'s software products on Intel Corp's hardware.

Matthew Friedman, a vice president at IBM, said the product is priced at just under $8,000, which he estimates is around five times cheaper than a similar package comprising accounting software on comparable hardware.

IDC, which tracks technology spending trends, estimates the global market for small business technology to be worth $675 billion by 2013. IDC analyst Frank Gens said combining hardware, software and services in a product from a single vendor is likely to be attractive to small businesses in this environment.

IBM shares recently rose 95 cents, or nearly 1%, to $105.54.

Source:money.cnn.com

How to Install VMWare Tools Through Windows Group Policy

2009-05-14T04:02:00.000-07:00

Some Guidelines for Installing VMWare Tools through Group Policy

The VMWare Tools are available for your guest OS as an .ISO CD-ROM file. Find the file, and get access to it from another system. Open the CD .ISO file or write it to disk and retrieve the files. Be sure to place them in a share accessible to the systems you want to install VMWare Tools with an indicator of the version.

For example, \\SERVER1\Applications\VmwareTools\ESX3.02\ would indicate that this path would hold VMWare Tools for guest OSs on ESX server 3.02. Be sure to use the correct version of VMWare Tools with the corresponding guest OS if you have different VMWare host platforms in use. Each version of VMWare tools is optimized with the version provided with the installation.

Making the GPO

To make a new Group Policy Object (GPO) that would install the VMWare tools do the following from the Group Policy Management Console (gpmc.msc):

-Select the Organizational Unit (OU) you want to install VMWare tools
-Expand Computer Configuration
-Expand Software Configuration
-Click Software Installation
-In the right pane, select “New-Package”
-Browse to the VMWare Tools.msi file in your shared path
-Click Open
-Sending the package to “Assigned” will install the VMWare Tools package on the next refresh of the policy on the systems in the OU to which this GPO is linked.
-Once the package is listed, rename it from “VMWare Tools” to something more clear like “VMWare Tools - Windows - ESX 3.02″
-Once this is complete the VMWare tools will install on the server on the next boot without interaction. The Windows event log will have an entry similar to the following:

The install of application VMWare Tools - Windows - ESX 3.02 from policy Default Domain Policy succeeded.Changes to software installation settings were applied successfully.

Upgrades to VMWare Tools

In the situation where hosts are upgraded and guest OSs are moved dynamically, upgrading the VMWare Tools through the same fashion can be done as well. Be sure to use the version of the tools again in the package, and remove the old one if needed. Some proper testing is of course due, and a best practice would be to set up a test OU to apply the VMWare tools package before rolling out to more virtual machines.

Source: itknowledgeexchange.techtarget.com

How to manage local group policy on Windows Server 2008 Core Edition?

2009-05-11T00:17:00.000-07:00

In Windows Server 2008 Core Edition, you can manage the group policy remotely through a MMC snap-in. To configure this, you’ll need to go through a few hoops. First, get a MMC snap-in pointed to the Windows Server 2008 Core Edition server. For a default configuration, you’ll need to configure Windows firewall to allow this traffic. This command will stop Windows firewall:

netsh advfirewall set allprofiles state off

When the Group Policy configurations are finished, run this command to turn firewall back on:

netsh advfirewall set allprofiles state on

From a remote system, run MMC.exe, add the Group Policy Object, and point it to a remote system.

Once saved, the local console can interact with the remote group policy configuration of the core server. This can work in conjunction with a domain-based Group Policy configuration if applicable. Be sure not to overlap, as the domain configuration will override a local configuration by re-application. Permissions need to be in place for this to work correctly. This can include using domain-based credentials or passing administrative credentials manually with the ‘net use’ command.

Remember to turn the Windows firewall on if you turned it off. Now you’re finished!

For graphical view have a look at this: http://blogs.techrepublic.com.com/datacenter/?p=768

Security Settings in Group Policy for Windows Server 2000

2009-05-05T01:16:00.000-07:00

One of the most insecure settings that can be granted to an end user is local administrative access. By adding the user account to the local Administrators group, the user is being granted nearly ultimate control over their desktop. The user can perform almost any action, even if the network is configured to deny this access. Actions that a user can perform, due to them having local administrative access, include, but are not limited to, the following:

* Remove their computer from the domain
* Modify any Registry setting
* Modify permissions on any folder or file
* Modify any system setting, including settings that are in files in the System folder
* Install any application
* Uninstall applications, security patches, or service packs
* Access any Website allowed by firewall
* Download and install ActiveX controls, Web applications, or other malicious applications downloaded from the Internet

User Configuration\Preferences\Control Panel

Then, right-click on Local Users and Groups. From the menu, click on New - Local Group.

To configure the group policy, type in Administrators into the Group text box, then click on the “Remove the current User” check box. Upon the next Group Policy background refresh all user accounts that are under the scope of management of the GPO where this setting is configured will have their user account removed from the local Administrators group on the computer where they are logged in.

Reset Local Administrator Password

In conjunction with the first Group Policy setting, it is essential that the local Administrator password is also reset. This is due to the fact that the user had administrative privileges before removing them from the local Administrators group, therefore they could have reset the Administrator account password to something they know.

Therefore, after the user account has been removed from the local Administrators group, the local Administrator account password must be reset. If this setting can be made simultaneously with the removal of the user account, the user will have no chance to know or alter the new local Administrator password.

This setting controls Windows XP SP2 and greater operating systems. This setting falls under the new Group Policy Preferences settings. To access this setting, open up a Group Policy Object and expand:

Computer Configuration\Preferences\Control Panel

Windows Firewall with Advanced Security

In the past users and administrators alike have stayed away fro musing the Windows Firewall, due to limited capabilities compared to other products. Now, the Windows Firewall comes with advanced security settings, which are certain to raise some eyebrows.

The new advanced security features of Windows Firewall incorporate not only inbound and outbound filtering, but include IPSec.

These settings can only control Windows Vista, which is the only desktop operating system that includes these options. This setting falls under the security area within a Group Policy. To access this setting, open up a Group Policy Object and expand:

Computer Configuration\Policies\Windows Settings\Security Settings\Windows Firewall with Advanced Security\Windows Firewall with Advanced Security

When you expand the policy, you will see three nodes:

* Inbound rules
* Outbound rules
* Connection Security Rules

If you right-click on any of the options, you can select the New Rule option, which the inbound rule.

Detail Info: http://www.windowsecurity.com/articles/Top5-Security-Settings-Group-Policy-Windows-Server-2008.html

New group policies for DNS in Windows Server 2003

2009-04-23T23:31:00.000-07:00

Windows Server 2003 resolves the problem of centralized DNS management by introducing group policies to configure DNS clients. For example, the following parameters are available in Windows Server 2003:

* Enable or disable dynamic registration of the DNS records by a client
* Configure DNS suffix search list of the clients
* Devolution of the primary DNS suffix in a name resolution process
* DNS suffix search list

These group policies can be applied to DNS clients on computers that are running Microsoft Windows 2000 or Windows XP operating systems. To apply group policies to other servers that are running Windows Server 2003, you will have to export the group policies from the primary server and import them on other servers that are running Windows Server 2003.

These group policies are at the following location:

Computer Configuration/Administrative Templates/Network/DNS Client
Group policy always supersedes the local configuration as well as the DHCP configuration. The only exception to this rule is if the REG_DWORD value DoNotUseGroupPolicyForDisableDynamicUpdate is enabled under the following registry key to disable dynamic DNS registration:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
If this value exists and it is set to 0x1, then services do not use a group policy value; instead they use locally configured values. If DoNotUseGroupPolicyForDisableDynamicUpdate does not exist or is set to 0x0, services must use the value that is specified by the group policy.

For More Visit: http://support.microsoft.com/kb/294785

What’s New in Group Policy in Windows Server 2008 R2 (Beta)

2009-04-20T01:37:00.000-07:00

Following changes are available in Windows Server® 2008 R2 and in Windows 7 with Remote Server Administration Tools (RSAT):

* Windows PowerShell Cmdlets for Group Policy: Ability to manage Group Policy from the Windows PowerShell™ command line and to run PowerShell scripts during logon and startup

* Group Policy Preferences: Additional types of preference items

* Starter Group Policy Objects: Improvements to Starter GPOs

* Administrative Template Settings: Improved user interface and additional policy settings

What does Group Policy do?

Group Policy provides an infrastructure for centralized configuration management of the operating system and applications that run on the operating system.

Who will be interested in this feature?

The following groups might be interested in these changes:

* IT professionals who have to manage users and computers in a domain environment

* Dedicated Group Policy administrators

* IT generalists

* Support personnel

Are there any special considerations?

You can manage local and domain Group Policy by using domain-based versions of Windows Server 2008 R2. Although the Group Policy Management Console (GPMC) is distributed with Windows Server 2008 R2, you must install Group Policy Management as a feature through Server Manager.

You can also manage local and domain Group Policy by using Windows 7. For managing local Group Policy, the Group Policy Object Editor has been replaced by the Local Group Policy Editor. To manage domain Group Policy, you must first install the GPMC. The GPMC is included with RSAT, which is available for download:

* Windows Server 2008 R2 Remote Server Administration Tools for Windows 7

* Windows Server 2008 Remote Server Administration Tools for Windows Vista with SP1

RSAT enables IT administrators to remotely manage roles and features in Windows Server 2008 R2 from a computer that is running Windows 7. RSAT includes support for the remote management of computers that are running either a Server Core installation or the full installation option of Windows Server 2008 R2. The functionality RSAT provides is similar to Windows Server 2003 Administration Tools Pack.

Installing RSAT does not automatically install the GPMC. To install the GPMC after you install RSAT, click Programs in Control Panel, click Turn Windows features on or off, expand Remote Server Administration Tools, expand Feature Administration Tools, and select the Feature Administration Tools and Group Policy Management Tools check boxes.

Which editions include this feature?

Group Policy is available in all editions of Windows Server 2008 R2 and Windows 7. Both local and domain-based Group Policy can be managed by using any version of Windows Server 2008 R2 and any version of Windows 7 that supports RSAT.
Does it function differently in some editions?

Without RSAT, only local Group Policy can be managed using Windows 7. With RSAT, both local and domain-based Group Policy can be managed using any edition of Windows 7 that supports RSAT.

Is it available in both 32-bit and 64-bit versions?

Group Policy is available in both 32-bit and 64-bit versions of Windows Server 2008 R2. The choice of a 32-bit or 64-bit version does not affect interoperability, scalability, security, or manageability for Group Policy.

Source: technet.microsoft.com/en-us/library/dd367853.aspx

New x64 servers by Sun Microsystem

2009-04-15T02:12:00.000-07:00

The new Sun Fire x64 blade servers, rack servers, and workstations, which are powered by Intel's Xeon processor 5500 series, are expected to carry a starting retail price of $1,488.

"Our new x64 systems with integrated networking technologies, advanced thermal management, open software and Open Storage enhancements will give the data center an extreme makeover, boosting efficiency and maximizing IT investment," John Fowler, Sun's Systems Group executive vice president, said in a statement.

The lineup of new products includes these servers designed for virtualization, the Sun Fire x4270 server and Sun Blade x6270 server module.

Other new x64 products for the enterprise and Web include the Sun Fire x4170 server, Sun Fire x2270 server, Sun Fire x4275 server, and Sun Ultra 27 workstation, as well as the Sun Blade x6275 server module.

Sun's new servers and workstations are part of its Open Network Systems strategy and will support multiple operating systems, such as Microsoft's Windows, Sun's Solaris, as well as Linux.

Source: CNET

Install a COM add-in Windows Server Group Policy

2009-04-09T02:30:00.000-07:00

Let’s proceed to step-by-step instructions on how to use Group Policy to automatically distribute a COM add-in to domain users.

Create a Distribution Point

To install an add-in, you need to create a distribution point on a publishing server:

1. Log on to a Windows Server as an administrator.
2. Create a shared network folder where you will place the MSI package that you want to install.
3. Set permissions on the share to allow access to the installation package.
4. Copy the MSI package to the distribution point.

Create a Group Policy object in Windows Server 2000 and 2003

Use a Group Policy object (GPO) to install the software package. Here are 9 easy steps to create it:

1. Start the Active Directory Users and Computers snap-in (Start -> All Programs -> Administrative Tools -> Active Directory Users and Computers).
2. Right-click on your domain in the console tree, and then choose Properties.
3. Switch to the Group Policy tab, and then click New.
4. Type the name you want for this policy (e.g. My Addin Distribution), and then press ENTER.
5. Click Properties, and then switch to the Security tab.
6. Click the Add button to add security groups or users to the list.
7. Unselect the Apply Group Policy check box for those groups or users that you don’t want this policy to apply to.
8. Select the Apply Group Policy check box for the groups or users that you want this policy to apply to.
9. When you get through, click OK.

Create a Group Policy object in Windows Server 2008

To create a Group Policy object (GPO) that you’ll use to install the software package:

1. Start the Group Policy Management snap-in (Start -> Administrative Tools -> Group Policy Management).
2. Right-click on your domain in the console tree, and then choose Create a GPO in this domain, and Link it here.
3. Type the name you want to call this policy (e.g. My Addin Distribution), and click OK.
4. Expand the Group Policy Objects item and select the newly added policy.
5. Click the Remove button to delete the Authenticated Users security group.
6. Click the Add button to add security groups or users.

Assign the installation package

To assign software to users that are logging on to Windows 2000 and higher workstations:

1. Windows Server 2000/2003. Start the Active Directory Users and Computers snap-in.
Windows Server 2008. Start the Group Policy Management snap-in.
2. Windows Server 2000/2003. Right-click your domain in the console tree, click Properties, switch to the Group Policy tab, select the group policy object that you want, and then click Edit.
Windows Server 2008. Locate and expand your domain in the console tree, then expand Group Policy Objects, right-click on the group policy object that you want, and then click Edit.
3. The Group Policy Object Editor will start.
4. Windows Server 2000/2003. Expand Software Settings under User Configuration.
Windows Server 2008. Under User Configuration, expand Policies, then Software Settings.
5. Right-click “strong>Software installation, point to New, and then click Package.
6. In the Open dialog box, type the full Universal Naming Convention (UNC) path to the shared folder with the MSI package that you want (e.g. \\server\share\setup.msi).
Warning. If the Windows Installer file resides on the local hard disk, do not use a local path. You need to use the UNC path to indicate the location of the installation files.
7. Click Open.
8. Click Assigned, and then click OK. The package will be listed in the right pane of the Group Policy window.
9. Right-click the package, click Properties, switch to the Deployment tab.
10. Select the Install this application at logon check box, and click OK.
11. Close the Group Policy Editor, then quit the Active Directory Users and Computers or Group Policy Management snap-in. When the user logs on, the managed software package is automatically installed.

Remove the installation package

1. Windows Server 2000/2003. Start the Active Directory Users and Computers snap-in.
Windows Server 2008. Start the Group Policy Management snap-in.
2. Windows Server 2000/2003. Right-click your domain in the console tree, click Properties, switch to the Group Policy tab, select the group policy object that you want, and then click Edit.
Windows Server 2008. Locate and expand your domain in the console tree, then expand Group Policy Objects, right-click on the group policy object that you want, and then click Edit.
3. The Group Policy Object Editor opens.
4. Windows Server 2000/2003. Expand Software Settings under User Configuration.
Windows Server 2008. Under User Configuration, expand Policies, then Software Settings.
5. Select the Software installation container with the package.
6. In the right pane of the Group Policy window, right-click the package, point to All Tasks, and then click Remove.
7. Click Immediately uninstall the software from users and computers, and then click OK.
8. Close the Group Policy Editor, then quit the Active Directory Users and Computers or Group Policy Management snap-in.

Source: http://www.add-in-express.com/creating-addins-blog/2009/01/25/automatic-installation-windows-group-policy/

How To Use the Group Policy Editor to Manage Local Computer Policy in Windows XP

2009-04-02T03:47:00.000-07:00

Uses of Group Policy

In Microsoft Windows XP, you use Group Policy to define user and computer configurations for groups of users and computers. You create a specific desktop configuration for a particular group of users and computers by using the Group Policy Microsoft Management Console (MMC) snap-in. The Group Policy settings that you create are contained in a Group Policy Object (GPO), which is in turn associated with selected Active Directory containers, such as sites, domains, or organizational units (OUs). With the Group Policy snap-in you can specify policy settings for the following:

* Registry-based policies

These include Group Policy for the Windows XP operating system and its components and for programs. To manage these settings, use the Administrative Templates node of the Group Policy snap-in.

* Security options

These include options for local computer, domain, and network security settings.

* Software installation and maintenance options.

These are used to centrally manage program installation, updates, and removal.

* Scripts options

These include scripts for computer startup and shutdown, and user logon and logoff.
* Folder redirection options.
These allow administrators to redirect users' special folders to the network.

How to Start the Group Policy Editor

To start the group policy editor, follow these steps.

1. Click Start, and then click Run.
2. In the Open box, type mmc, and then click OK.
3. On the File menu, click Add/Remove Snap-in.
4. Click Add.
5. Under Available Stand-alone Snap-ins, click Group Policy, and then click Add.
6. If you do not want to edit the Local Computer policy, click Browse to locate the group policy object that you want. Supply your user name and password if prompted, and then when you return to the Select Group Policy Object dialog box, click Finish.
7. Click Close, and then in the Add/Remove Snap-in dialog box, click OK.

The selected GPO is displayed in the Console Root.

How to Use the Group Policy Editor

The Group Policy snap-in contains the following major branches:

* Computer Configuration

Administrators can use Computer Configuration to set policies that are applied to computer, regardless of who logs on to the computers. Computer Configuration typically contains sub-items for software settings, Windows settings, and administrative templates.

* User Configuration

Administrators can use User Configuration to set policies that apply to users, regardless of which computer they log on to. User Configuration typically contains sub-items for software settings, Windows settings, and administrative templates.

To use the group policy editor, follow these steps:

1. Expand the GPO that you want. For example, Local Computer Policy.
2. Expand the configuration item that you want. For example, Computer Configuration.
3. Expand the sub-item that you want. For example, Windows Settings.
4. Navigate to the folder that contains the policy setting that you want. The policy items are displayed in the right pane on the Group Policy Editor snap-in.
5. In the Setting list, double-click the policy item that you want.
6. Edit the settings of the policy in the dialog box that appears, and then click OK.
7. When you are finished, quit the MMC.

Source: http://support.microsoft.com/kb/307882

Group Policy Template Behavior in Windows Server 2003

2009-03-30T00:08:00.000-07:00

In Enterprise environments, there may be hundreds of Group Policy objects that you want to deploy in a domain. Each Group Policy object is stored in the Sysvol share of each domain controller. By default, a copy of the Administrative Templates (.adm) files are copied to each policy object in the file path:

%systemroot%\sysvol\domainname\Policies\POLICYGUID\Adm

In Windows Server 2003, the size of the Administrative Templates has grown. As a result, the set of Administrative Templates has grown to almost 1.75 MB. When you multiply this size by each Policy that Sysvol contains, you can see that much space is devoted to these templates.

Based on these facts, Administrators may want to use two Group Policy settings that reduce some of the strain that this Sysvol size growth causes. You must make sure that you set the settings correctly. If you do not, you may not be able to manage the Administrative Templates settings on some Group Policy objects. The two settings are Always use local ADM files for Group Policy Editor and Turn off automatic update of ADM files.

To locate these settings, in Group Policy expand Computer Configuration, expand Administrative Templates, expand System, and then expand Group Policy. Complete descriptions of these settings are included in the "More Information" section of this article.

The following list of scenarios describes how Group Policy behaves after you modify the settings:

Scenario 1:

Turn off Automatic Update of ADM files is enabled:
Always use local ADM files for Group Policy Editor is enabled:
o Local Administrative Template files (.ADM files) are not copied to SYSVOL.
o Displays the settings in Group Policy by using the local .adm files in %systemroot%\inf.

Scenario 2:

Turn off Automatic Update of ADM files is enabled:
Always use local ADM files for Group Policy Editor is disabled:
o Local copies of .adm files are not copied to SYSVOL.
o Displays the settings based on the .adm files located in SYSVOL
On this setting, if the SYSVOL copies of the .adm files are deleted, then you cannot view or edit the Administrative Templates section of Group Policy. If the copies of the .adm files in SYSVOL are Windows 2000 versions, new settings are not available in the policy.

Scenario 3:

Turn off Automatic Update of ADM files is disabled:
Always use local ADM files for Group Policy Editor is enabled:
o Local copies of the .adm files are copied to SYSVOL.
o Displays the settings based on the .adm files located in the %Systemroot%\inf folder.

Scenario 4:

Turn off Automatic Update of ADM files is disabled:

Always use local ADM files for Group Policy Editor is disabled:
o Local copies of the .adm files present in the %Systemroot%\inf folder are not copied to SYSVOL
o Copies of the .adm files in SYSVOL determine policy

In this scenario, the automatic method of upgrading policy templates is disabled, but the client continues to reference SYSVOL for the .adm files. If you must upgrade a template, you must do so manually.

Source: http://support.microsoft.com

Microsoft Internet Explorer for Windows Server 2003

2009-03-23T00:03:00.000-07:00

Microsoft Internet Explorer for Windows Server 2003 8.0. Internet Explorer has been designed to make everyday tasks easier, provide dynamic security protection and improve the development platform and manageability. End user improvements include a streamlined interface, tabbed browsing, printing advances, improved search functionality, instant feeds (RSS), dynamic security protection, and more.

Internet Explorer provides improved navigation through tabbed browsing, web search right from the toolbar, advanced printing, easy discovery, reading and subscription to RSS feeds, and much more. It also provides security through a robust new architecture, security features that help defend against malicious software, and new ways to better protect against the theft of personal data from fraudulent websites. It has improved support for cascading style sheets, a rich RSS feeds platform, and robust tools for deploying and managing Internet Explorer 7 in large enterprise environments.

Source:

Default Backup Utility in Windows Server 2008

2009-03-15T23:44:00.000-07:00

One of the biggest changes to the default backup utility in Windows Server 2008, as compared to earlier versions, is that you can no longer backup to tape drive. Scheduled backups can only be written to removable disks or DVD drives. Given the limited amount of data that you can store on a DVD, it is most likely that your scheduled backups will be written to removable disks.

Which brings up an interesting problem. What steps do you need to take to set up removable disks in a library so that you can rotate them off site as a part of your disaster recovery plan? As any systems administrator knows, if you leave your backups in the same place that your server is, a disaster that destroys the server is probably going to destroy the backups as well.

When you set up the original scheduled backup job, you need to specify all the target removable disks that you will use as a part of a rotation. If you only have fewer USB slots than you have removable disks, you can go back and edit the job to add more removable disks so that all of them are prepared to accept backups. This allows you to add and remove removable media from the backup rotation at a later state.

Backups will only be written to the first available media in the listed pool. So if you have an internal disk and an external disk, the backup will be written to the first disk in the list only. If you have two external disks connected, the backup will only be written to one of them. Ensure that only one backup disk target is connected at a time. When you rotate the media, just disconnect the existing drive and reconnect the replacement.

Keep in mind that a full backup will be written to each disk and then incremental backups after that. When you perform a recovery, you’ll only need to attach one disk – you won’t need to go hunting around for other disks.

Source: http://windowsitpro.com/article/articleid/101647/setting-up-a-backup-rotation-with-windows-server-backup.html

Low-cost, low-end version of Windows Server with stripped functionality.

2009-03-05T01:58:00.000-08:00

Microsoft CEO Steve Ballmer has indicated to investors that Microsoft is preparing to release a low-cost, low-end version of Windows Server with stripped functionality.

The new Windows Server SKU is designed to capitalize on the ever increasing demand for basic computer functionality, which has been introduced into the market along with the netbook craze. Ballmer noted that Microsoft has a relatively small share of the hosting market where the Linux platform prevails heavily and suggested that the new ‘Foundation Server’ will be an attempt to grab server market share away from Linux.

Quoting Ballmer:

“So we have something that’s akin to netbook at the server, and we’ll be introducing our Foundation Edition over the next month or two.”

Ballmer also mentions that the Foundation Server announcement is quite interesting as well as the analogy to the netbook platform, stating that it is “yet another scenario where (a), Linux has made a serious inroads and (b), Microsoft sells a version of Windows for less than the usual price.” Some feel that Foundation Server could pose a risk and actually drive server prices down or that Foundation Server is a reaction to the recession.

The new low-cost Foundation Server will also provide benefit to the virtualization side of computing. With the availability of a lower cost version of Windows Server we may see increased usage of server virtualization. The decision to release the lower cost Foundation Edition could also be a tactical move by Microsoft that fits well with the recent virtualization agreement between itself and Redhat.

Source: http://www.tomshardware.com/news/microsoft-windows-server-foundation,7145.html

Windows Server 2008 Is 45 Times Faster Than Windows Server 2003

2009-02-24T03:14:00.000-08:00

Windows Server 2008, formerly codenamed Longhorn, is no leas than 45 times faster than its predecessor, Windows Server 2003, in terms of network transfer speeds. Now whatever the perspective is on Microsoft's last 32-bit server operating system, the fact of the matter is that faster transfer speeds for of up to 45 times is quite an evolution compared to Windows Server 2003. Back in June 2007, Microsoft commissioned a study to the Tolly Group focused on the networking performances of its latest Windows client and server operating system, which ended up as the "Enhanced Network Performance with Microsoft Windows Vista and Windows Server 2008" whitepaper.

"Windows Server 2008 and Windows Vista are introducing some of the biggest changes to our networking stack in recent memory. From the server side, I think this is one of the biggest overlooked features of Windows Server 2008. To that point, earlier this year we released the Tolly Group Whitepaper that showed the how the improvements to our TCP/IP stack and SMB 2.0 Protocol gave us a 3.5x time-to-completion improvement over Windows Server 2003. The paper really is a good read and it has some good technical details of what the exact improvements are that allow this to happen. (receive window auto-tuning, SMB File handles and buffer size," revealed Ward Ralston, senior technical product manager in the Microsoft Windows Server division.

Well, you will be surprised of the actual extent of "dramatic" benefits. Microsoft has a long tradition of dogfooding its own products. And Windows Server 2008 is no exception to this rule. Ralston explained that the MSN group has implemented Windows Server 2008 release Candidate 0, available for download via this link on Softpedia. The tests the MSN group performed revealed that Windows Server 2008 is 45 times faster than Windows Server 2003. Namely, a transfer that took almost six hours with Windows Server 2003, took just 7 minutes with Windows Server 2008. At this point in time, Windows Server 2008 is scheduled for RTM in early 2008, and for release at the end of February, next year.

"First set of tests is to transfer 10.793 GB ( a collection of 10 VirtualEarth Stitch files) from TK2 Datacenter to BLU Datacenter and from BLU Dataceneter to TK2 Datacenter. a. In windows 2003, from TK2 to BLU, it took 5 hours, 40 minutes and 13 seconds. Transfer rate observed was 567813 Bytes/sec. From BLU to TK2, it took 6 hours, 6 minutes and 26 seconds. Transfer rate observed was 527182 Bytes/sec. b. In LH RC0 build, from TK2 to BLU, it took 7 minutes and 45 seconds, Transfer rate observed was 25062249 Bytes/sec. From BLU to TK2, it was 8 minutes and 10 seconds, Transfer rate observed was 23712912 Bytes/sec. The improvement observed was ~45 times faster over windows 2003", Ralston added.

Source: http://news.softpedia.com/news/Windows-Server-2008-Is-45-Times-Faster-than-Windows-Server-2003-71575.shtml

10 Amazing things about Windows Server 2008

2009-02-18T00:11:00.000-08:00

Windows Server 2003 felt like a refresh of Windows Server 2000. There were few radical changes, and most of the improvements were fairly under the surface.

Windows Server 2008, on the other hand, is a full-size helping of "new and improved". While the overall package is quite good, there are a few surprises, "gotchas", and hidden delights you will want to know about before deciding if you will be moving to Windows Server 2008 any time soon.

1: The 64-bit revolution is not complete

There have been 64-bit editions of Windows Server for years now, and Microsoft has made it quite clear that it wants all of its customers to move to 64-bit operating systems. That does not mean that you can throw away your 32-bit Windows Server 2008 CD, though! Over the last few months, I have been shocked on more than one occasion by the pieces of Microsoft software that not only do not have 64-bit versions, but will not run under a 64-bit OS at all. This list includes Team Foundation Server and ISA Server. If you are planning on moving to 64-bit Windows Server 2008, be prepared to have a 32-bit server or two around, whether it be on physical hardware or in a VM.

2: Who moved my cheese?

While the UI changes in Windows Server 2008 are not nearly as sweeping as the Aero interface in Vista, it has undergone a dramatic rearrangement and renaming of the various applets around the system. In retrospect, the organisation of these items is much more sensible, but that hardly matters when you have years of experience going to a particular area to find something, only to have it suddenly change. Expect to be a bit frustrated in the Control Panel until you get used to it.

3: Windows Workstation 2008 might catch on

In an odd turn of events, Microsoft has provided the ability to bring the "Vista Desktop Experience" into Windows Server 2008. I doubt that many server administrators were asking for this, but the unusual result is that a number of people are modifying Windows Server 2008 to be as close to a desktop OS as possible. There have always been a few people who use the server edition of Windows as a desktop, but this makes it much easier and friendlier. These home-brewed efforts are generally called "Windows Workstation 2008", in case you're interested in trying it out on your own.

4: Hyper-V is good, but...

Hyper-V was one of the most anticipated features of Windows Server 2008, and it's surprisingly good, particularly for a version 1 release from Microsoft. It is stable, easy to install and configure, and does not seem to have any major problems. For those of us who have been beaten into the "wait until the third version" or "don't install until SP1″ mentality, this is a refreshing surprise.

5: ...Hyper-V is limited

Hyper-V, while of high quality, is sorely lacking features. Considering that it was billed as a real alternative to VMWare and other existing solutions, it is a disappointment (to say the least) that it does not seem to include any utilities for importing VMs from products other than Virtual PC and Virtual Server. Even those imports are not workaround-free. Another real surprise here is the lack of a physical-to-virtual conversion utility. Hyper-V may be a good system, but make sure that you fully try it out before you commit to using it.

6: NT 4 domain migration -- it's not happening

If you have been putting off the painful migration from your NT 4 domain until Windows Server 2008 was released, don't keep waiting. The older version (3.0) Active Directory Migration Tool (ADMT) supports migrations from NT 4, but not to Windows Server 2008. The latest version (3.1) supports migrations to Windows Server 2008, but not from NT 4. Either migrate from NT 4 before changing your domain to be a Windows 2008 domain or get your NT 4 domain upgraded first.

7: The ashtrays are now optional

In prior versions of Windows Server, a lot of applications came installed by default. No one ever uninstalled them because they did not cause any harm, even if you didn't use them or installed an alternative. Now, even the "throwaway" applications, like Windows Backup, are not installed by default. After installation, you need to add "features" to get the full Windows Server suite of applications. This can be frustrating if you are in a hurry, but the reduced clutter and resource overhead are worth it.

8: Licensing is bewildering

Continuing a hallowed Microsoft tradition, trying to understand the licensing terms of Windows Server 2008 feels like hammering nails with your forehead. So maybe this isn't so much a surprise as a gotcha. The Standard Edition makes sense, but when you get into the issues around virtualisation in Enterprise and Datacenter Editions, things can be a bit confusing. Depending upon your need for virtual machines and the number of physical CPUs in your server, Enterprise Edition may be cheaper -- or it may be more expensive than Datacenter Edition. One thing to keep in mind is that once you start using virtual machines, you start to like them a lot more than you thought you would. It's easy to find yourself using a lot more of them than originally expected.

9: There's no bloat

Maybe it's because Vista set expectations of pain, or because hardware has gotten so much cheaper, but Windows Server 2008 does not feel bloated or slow at all. Microsoft has done a pretty good job at minimising the installed feature set to the bare minimum, and Server Core can take that even further. Depending upon your needs, it can be quite possible to upgrade even older equipment to Windows Server 2008 without needing to beef up the hardware.

10: Quality beats expectations

Microsoft customers have developed low expectations of quality over the years, unfortunately, with good reason. While its track record for initial releases, in terms of security holes and bug counts, seems to be improving, customers are still howling about Vista. As a result, it has come as a real surprise that the overall reaction to Windows Server 2008 has been muted, to say the least. The horror stories just are not flying around like they were with Vista. Maybe it's the extra year they spent working on it, or different expectations of the people who work with servers, but Windows Server 2008 has had a pretty warm reception so far.

Source:http://www.builderau.com.au/program/windows/soa/10-surprising-things-about-Windows-Server-2008/0,339024644,339292005,00.htm

Small Business Computer Support Services

2009-02-11T04:15:00.000-08:00

Whether you own a home business or small scale business, you must have noticed the pace of change in technology. For a non-tech person, it is virtually impossible to stay abreast of increasing advancements in technology. Fortunately, there is a variety of computer support and online computer help resources to restore a sense of security when faced with technical complexities.

Emerging at the top of the chain of small business computer support options is online PC repair. The latter has become an effective service offering the best to companies’ especially small businesses and is best suited to assist customers with troubleshooting computer problems, virus and spyware infections, and other critical issues such as the blue screen of death error. As such, online personal computer repair has proved its mettle for most issues.

Every good technical support company first diagnoses your computer problems through an online session or over the phone. Online PC repair is most helpful for small businesses at the time of troubleshooting software problems. Starting out with simple issues such as those of installation of any software programs to critical like fixing blue screen of death error, you can contact these technicians for anything related to your PC.

Likewise, online PC repair is the simplest, cheapest yet the most self sufficient service for small business computer support to sort out any kind of software defaults. Also it eliminates a need for you to hire full time IT staff, thereby saving loads of money.

The ongoing fierce competition has led several server support centers to launch service packages including a comprehensive array of support services for different purposes. For ex: You can ask for a Small Business Support pack to fulfill your individual computer needs. You may also ask your support technicians for customized solutions depending upon specific business needs.

Small businesses are finding support sessions useful as they offer support to meet the criteria of your business. Whether it's a sudden server crash or virus outbreak, you can be assured to get your computer problems solved onsite within no time.

By working with a company that offers a combination of computer technician services and online PC repair, small businesses can avail the IT support services they need without the heavy price tag associated with it.

Source: http://www.articlebiz.com/article/223021-1-small-business-computer-support-services/

How to Start With a Small Business Server?

2009-02-05T23:32:00.000-08:00

Your small office probably relies on more than one computer to get work done. For managing tasks across all of your company's PCs, consider using a small-business server. Initially, shared storage space would be the main benefit of this central hub, and you'd have more backup options. And as your company's needs grow, you could use your server to design and test a Web site, host intranet services, and, potentially, host your own Internet presence.

Choosing a Server

The cheapest server requires only the kind of hardware you may already have in a closet--something as slow as a PC with a Pentium Pro can handle an Ubuntu Linux-based server. Windows Small Business Server 2008 is a step up from that; you might get by running it on a recent, unused PC, or you could buy a new server with it preinstalled.

Small Business Server 2008 is ideal for a few employees up to about a dozen or two. With 25 or more employees, you'll likely want to step up to Windows Essential Business Server 2008. PC companies that sell hardware-and-software systems usually assist in setting it up, but you'll probably need an on-site or consulting IT pro to keep it running.

Using an Ubuntu Linux-Based Server

If you're already comfortable running a network, you might be ready for a simple server that uses Ubuntu Linux. The free operating system comes in server and desktop versions, each of which can run the same applications. The server version is preconfigured with networking tools, including Samba file sharing and OpenSSH, and its kernel is tuned to be more responsive to server tasks. Beginners could find its command-line interface daunting; thankfully, however, enabling the Ubuntu desktop graphical interface is easy.

The free Ubuntu download can get you started quickly: Just burn it to a CD and run the installer. Note, though, that you should understand a lot of networking basics before giving it a shot. Do you know the concepts behind manual IP addresses, router hardware, and file sharing permissions? Are you comfortable with hard-drive installations, RAM upgrades, and other hardware basics? Great! You should be able to figure out Ubuntu and configure the PC as you go along. If not, a for-pay, preinstalled server--and the support that usually accompanies it--might be better for your needs.

Setting Up Windows Small Business Server 2008

Windows Small Business Server 2008 is a new, entry-level business server targeted at companies with a few dozen employees, and those without any on-site IT staff. Some bigger companies without an IT staff might manage with the software, but it supports a maximum of only 75 users. The server's wizard-heavy system asks plain-language questions about your needs and makes configurations based on your answers.

Think of Small Business Server as a preconfigured Windows Server installation; it includes nearly all of the same features, but you manage everything from a single console instead of having to install packages. I found the installation process easier than that involved in installing Ubuntu, but you'll still need some basic networking know-how to make everything come together.

Like other Microsoft products, Small Business Server comes in multiple editions, which can cause confusion. The Standard Edition should amply cover most small-business needs, and it even includes Exchange Server for calendars and e-mail. However, I recommend growing into hosting your own e-mail and Web services, if you manage those functions at all; without IT staff, I'd much rather pay another company for hosting. That said, Small Business Server connects to registrars to help you along if you have the dedicated bandwidth and the IT know-how.

Small Business Server also follows the per-license pricing structure of other for-pay server OSs. The base packages include five licenses to be divided per user or per PC. Additional per-user licenses cost $77 for Standard Edition and $189 for Premium Edition. The costs cover licenses for all of the server products included in the respective editions; be sure to factor those extra costs into your decision.

Look at Windows Essential Business Server 2008

Buying Essential Business Server (or Small Business Server) bundled with new hardware might be your easiest option. Dell, HP, IBM, and others sell tower-size server hardware with your choice of operating system. (Rackmount gear can save space and allow for easier upgrades, but it's inconvenient unless you're converting all of your server hardware to that design.)

Complete Information Available here: http://www.pcworld.com/businesscenter/article/158881-2/get_started_with_a_smallbusiness_server.html

HowTo: Install a COM add-in automatically using Windows Server Group Policy

2009-02-03T05:51:00.000-08:00

Let’s proceed to step-by-step instructions on how to use Group Policy to automatically distribute a COM add-in to domain users.

Create a Distribution Point

To install an add-in, you need to create a distribution point on a publishing server:

1. Log on to a Windows Server as an administrator.
2. Create a shared network folder where you will place the MSI package that you want to install.
3. Set permissions on the share to allow access to the installation package.
4. Copy the MSI package to the distribution point.

Create a Group Policy object in Windows Server 2000 and 2003

Use a Group Policy object (GPO) to install the software package. Here are 9 easy steps to create it:

1. Start the Active Directory Users and Computers snap-in (Start -> All Programs -> Administrative Tools -> Active Directory Users and Computers).
2. Right-click on your domain in the console tree, and then choose Properties.
3. Switch to the Group Policy tab, and then click New.
4. Type the name you want for this policy (e.g. My Addin Distribution), and then press ENTER.
5. Click Properties, and then switch to the Security tab.
6. Click the Add button to add security groups or users to the list.
7. Unselect the Apply Group Policy check box for those groups or users that you don’t want this policy to apply to.
8. Select the Apply Group Policy check box for the groups or users that you want this policy to apply to.
9. When you get through, click OK.

Create a Group Policy object in Windows Server 2008

To create a Group Policy object (GPO) that you’ll use to install the software package:

1. Start the Group Policy Management snap-in (Start -> Administrative Tools -> Group Policy Management).
2. Right-click on your domain in the console tree, and then choose Create a GPO in this domain, and Link it here.
3. Type the name you want to call this policy (e.g. My Addin Distribution), and click OK.
4. Expand the Group Policy Objects item and select the newly added policy.
5. Click the Remove button to delete the Authenticated Users security group.
6. Click the Add button to add security groups or users.

Assign the installation package

To assign software to users that are logging on to Windows 2000 and higher workstations:

1. Windows Server 2000/2003. Start the Active Directory Users and Computers snap-in.
Windows Server 2008. Start the Group Policy Management snap-in.
2. Windows Server 2000/2003. Right-click your domain in the console tree, click Properties, switch to the Group Policy tab, select the group policy object that you want, and then click Edit.
Windows Server 2008. Locate and expand your domain in the console tree, then expand Group Policy Objects, right-click on the group policy object that you want, and then click Edit.
3. The Group Policy Object Editor will start.
4. Windows Server 2000/2003. Expand Software Settings under User Configuration.
Windows Server 2008. Under User Configuration, expand Policies, then Software Settings.
5. Right-click “strong>Software installation, point to New, and then click Package.
6. In the Open dialog box, type the full Universal Naming Convention (UNC) path to the shared folder with the MSI package that you want (e.g. \\server\share\setup.msi).
Warning. If the Windows Installer file resides on the local hard disk, do not use a local path. You need to use the UNC path to indicate the location of the installation files.
7. Click Open.
8. Click Assigned, and then click OK. The package will be listed in the right pane of the Group Policy window.
9. Right-click the package, click Properties, switch to the Deployment tab.
10. Select the Install this application at logon check box, and click OK.
11. Close the Group Policy Editor, then quit the Active Directory Users and Computers or Group Policy Management snap-in. When the user logs on, the managed software package is automatically installed.

Remove the installation package

To remove a package:

1. Windows Server 2000/2003. Start the Active Directory Users and Computers snap-in.
Windows Server 2008. Start the Group Policy Management snap-in.
2. Windows Server 2000/2003. Right-click your domain in the console tree, click Properties, switch to the Group Policy tab, select the group policy object that you want, and then click Edit.
Windows Server 2008. Locate and expand your domain in the console tree, then expand Group Policy Objects, right-click on the group policy object that you want, and then click Edit.
3. The Group Policy Object Editor opens.
4. Windows Server 2000/2003. Expand Software Settings under User Configuration.
Windows Server 2008. Under User Configuration, expand Policies, then Software Settings.
5. Select the Software installation container with the package.
6. In the right pane of the Group Policy window, right-click the package, point to All Tasks, and then click Remove.
7. Click Immediately uninstall the software from users and computers, and then click OK.
8. Close the Group Policy Editor, then quit the Active Directory Users and Computers or Group Policy Management snap-in.

Source: http://www.add-in-express.com/creating-addins-blog/2009/01/25/automatic-installation-windows-group-policy/

Forefront Security for Office Communications Server Beta 3 Available

2009-01-28T02:00:00.000-08:00

Taking IM security one step forward, Microsoft has announced the availability of the third Beta of the Forefront Security for Office Communications Server. The Beta bits were delivered at the end of the past week, and the Redmond company indicated that it planned to release FSOCS to manufacturing in just a couple of months. The security solution is designed to protect Office Communications Server 2007 instant messaging environments not only from malware, but also from out-of-policy content. With the Beta 3 build of FSOCS, Microsoft is offering support for the successor of Office Communications Server (OCS) 2007.

“In this latest release, we have updated FSOCS to add support for the upcoming Office Communications Server (OCS) 2007 R2 release! RTM availability is scheduled for March 2009. This Beta release also includes: support for OCS 2007 R2; support for OCS 2007 Enterprise Edition server roles; integration with OCS 2007 Access Edge role to protect corporate IM from external public IM threats an localization in 11 languages,” Mike Chan product manager for Forefront Server for Exchange (FSE), stated.

For the time being, the company headquartered in Redmond, Washington, is offering the Beta 2 of FSOCS only in English. The bits are designed to integrate with Windows Server 2003 or Microsoft Windows Server 2008 running on at least a dual-processor, 2.6 gigahertz (GHz), 1 gigabyte (GB) of available memory (2 GB recommended), 2 gigabytes (GB) of available disk space, and also with Microsoft Office Communications Server 2007 Standard Edition or Enterprise Edition or Microsoft Office Communications Server 2007 R2.

Forefront Security for Office Communications Server combines multiple scanning engines from what the software giant referred to as industry-leading security partners. “Like other Forefront server security products, FSOCS provides superior detection of the latest threats when compared to single engine solutions by using our multiple engine scanning technology,” Chan added.

Microsoft Forefront Security for Office Communications Server Beta 3 is available for download here.

Source: http://news.softpedia.com/news/Forefront-Security-for-Office-Communications-Server-Beta-3-Available-102985.shtml

Microsoft Moves Managed Services Leader Into Server Group

2009-01-21T06:08:00.000-08:00

Microsoft continues to tweak its managed services organization.

Ron Markezich, vice president of managed solutions and co-CIO at Microsoft, is relinquishing the CIO role and, along with 500 Microsoft IT people focused on managed services, is moving into the company's Server and Tools division. Markezich will report to senior vice president Bob Muglia.

The upshot of the move, announced internally on Monday, is that Markezich will take sole ownership of MIcrosoft's emerging managed services efforts, and Stuart Scott will become the sole CIO, a company spokesman said. Scott and Markezich shared the CIO post.

Last week, Markezich's old boss, Rick Devenuti, announced his retirement, effective at the end of this calendar year. Together, the two executives drove Microsoft's managed services strategy.

That effort, pegged as a way to help Microsoft develop and deploy managed desktops and e-mail in heterogeneous accounts, was viewed as a conflict with systems integrator and VAR partners, despite Microsoft's contentions that partners were involved at the test-bed sites: Energizer Holdings and XL Capital.

Both Hewlett Packard and Siemens are working with Microsoft on the Energizer effort, for example, said Ed Cummings, senior director of customer offerings for Microsoft Managed Solutions.

Several partner sources close to Microsoft said the Redmond, Wash., company had learned via these early implementations just how hard this work is and, as a result, is moving toward more of a partner-led model. Cummings and group spokesman Tom Ryan said there has been no change in strategy.

"We are very early in the process," Cummings said. "What we've done with the two customers at this point is learning how managed desktop services work. We're learning the business to the level our partners already know. Then if we start thinking about advancing the state of the art, we'd want to do that with our partners."

Managed server services are a priority for Microsoft, which has traditionally garnered its revenue through the license sales of its software. But with the proliferation of broadband, more VARs and vendors are looking at hosting and managing applications for customers.

Whereas Salesforce.com and other new-age software providers are self-hosting the infrastructure and applications for customers, Microsoft has to weigh the consequences of doing that against the damage it could do to its license-driven partner model.

Source: http://www.crn.com/managed-services/193303054

Microsoft Stomps Beastly Server Bugs

2009-01-16T02:36:00.000-08:00

Microsoft More about Microsoft issued a critical software update Tuesday, plugging three vulnerabilities in all versions of its Windows Consolidate Mac Servers. Run Windows Server on your Mac. Watch a Demo or Download a Trial. operating system. The three flaws, two of which were reported privately and the third of which was publicly disclosed, deal with a hole in the Microsoft Server Message Block (SMB) Protocol.

The vulnerabilities could enable an attacker who successfully exploits them to install programs; view, change or delete data; or create new accounts with full user rights. The security update addresses the flaws by validating the fields inside the SMB packets, according to Microsoft.

The software maker rated two of the security holes -- CVE-2008-4834 and CVE-2008-4835 -- as critical in Windows 2000, Windows XP and Windows Server 2003. The third flaw -- CVE-2008-4114, which also affects those OSes -- was given a moderate rating. The same vulnerabilities in Windows Vista and Windows Server 2008 were given a moderate rating by Microsoft.

The flaws are serious, insofar as exploits could lead to remote code execution and thereby to hackers controlling an affected computer, said Richard Wang, U.S. SophosLabs manager.

Critical Situation

The first two flaws concern unauthenticated remote code execution vulnerabilities, which exist in the way that Microsoft SMB Protocol handles specially crafted SMB packets. Efforts by hackers to exploit the flaws would not require authentication, thereby allowing attackers to exploit the vulnerabilities by sending a specially crafted network message to a computer running the Server service. Most attempts to exploit the security hole would result in a system denial of service condition; however, remote code execution is possible, at least theoretically, Microsoft said.

"CVE-2008-4834 and CVE-2008-4835 both allow remote code execution, meaning that a computer that is connected to the Internet is at risk. A remote attacker can install and execute programs, compromise the confidentiality, integrity or availability of sensitive data, and create administrator accounts," Chris Rodriguez, an analyst at Frost & Sullivan More about Frost & Sullivan, told TechNewsWorld.

The remaining problem rests with a denial of service vulnerability that exists in the way that Microsoft SMB Protocol software handles specially crafted SMB packets. As with the other two flaws, an attempt to exploit the vulnerability would not require authentication, allowing an attacker to exploit the vulnerability by sending a specially crafted network message to a computer running the service. Unlike the other vulnerabilities addressed in the patch, if an attacker successfully exploits the flaw, it could cause the user's computer to stop responding and restart.
Get the Shot

Microsoft recommends that Windows users install the security update immediately.

If a system is left unpatched, "it is possible hackers will be able to exploit this vulnerability to break into networks and install their own programs," Wang noted.

Source:http://www.technewsworld.com/story/Microsoft-Stomps-Beastly-Server-Bugs-65833.html

IYogi Partners with GlobalLogic for Software Product Development to Create "Generation V" Technical Support Platform

2009-01-14T02:05:00.000-08:00

New York, NY - January 13, 2009 –iYogi today announced a software product development partnership with GlobalLogic Inc. to create a "Generation V" services platform for iYogi's proprietary technical support application framework, iMantra. The fastest growing direct-to-consumer and small business technical support brand from India, iYogi has more than 50,000 subscribers worldwide.

GlobalLogic, the leader in global software product development, will assist in the enhancement of iYogi's service delivery framework using best-of-breed Web 2.0 tools and applications. Some of the innovative features to be introduced through this software product development tie-up include an application that resides on the customer's desktop and provides integration with iMantra ("Support Dock") and a global MPLS-based IP transport platform that provides customers with the instant deployment of remote access and voice-based support with a single click. This advanced implementation allows for integration with POS payment systems to facilitate real-time processing at the point of sale.

Uday Challu, co-founder and CEO of iYogi, said, "The partnership with GlobalLogic for software product development reiterates iYogi's commitment to offer affordable access to the highest quality computer support and tech help technical support for home users and small businesses with disruptive applications and tools to manage their everyday technology needs. GlobalLogic's expertise will help us further enhance iYogi's widely acclaimed iMantra support platform with a new breed of applications and services, bringing us even closer to our customers".

iYogi provides live computer support for home and small business users globally for the technologies they use every day. iYogi's live 24/7 support extends to multiple brands of computers, software and peripherals. iYogi services also include virus removal, spyware removal ,optimizing slow computer, setup, configuration and troubleshooting your computer and peripheral devices, issues or errors with software applications. Currently available to customers in the United States, United Kingdom, Canada, Australia and Singapore, iYogi is on an aggressive expansion spree, extending services to several new geographies in 2009. iYogi’s Customer Satisfaction Rate of 93% and Resolution Rate of 84% ranks it as the highest bench marked company in the computer support industry.

Peter Harrison, CEO of GlobalLogic Inc., said, "We are excited about this partnership, which will enable us to bring our specialized skills across the full software product development life cycle to iYogi. Already a proven leader in delivering innovative product engineering services to Web 2.0 companies, GlobalLogic will help iYogi continue to deliver the effective solutions for which it has come to be known".

In contrast to many firms that focus on IT support services, GlobalLogic specializes in software product R&D for emerging and established technology companies. Its services include everything from market analysis and product conceptualization to product engineering, migration, testing and support. The company has received widespread recognition for innovation in software product R&D, including its InfoWorld award-winning platform for distributed Agile development (GlobalLogic Velocity) and GlobalLogic Version 1.0SM, an offering for both early and late-stage companies that has helped GlobalLogic clients launch innovative and disruptive technologies at major conferences such as Demofall-2008.

About iYogi

iYogi is the first direct-to-consumer and server support service from India. Providing an Annual Unlimited subscription to technical support for $139.99 per year, iYogi now boasts of more than 50,000 customers. The company employs 600 professionals servicing customers in the US, UK, Canada, Australia and Singapore. Backed by Canaan Partners, Silicon Valley Bank and SAP Ventures, the company has been featured in MSNBC, ZDnet, Yahoo Finance and eWeek. It has also been declared a winner of the Red Herring 100 Award, a selection of the 100 most innovative private technology companies based in Asia. For further information please visit www.iyogi.net.

About GlobalLogic

The leading specialist in global software product development services, GlobalLogic Inc. partners with emerging and established technology companies to help them bring great software products to market in less time and at less cost. GlobalLogic has developed a unique joint-venture model of partnering with technology companies to create a dedicated global delivery center in the US, India, China, Ukraine and Israel to serve as a virtual extension of a client's local development team. In other cases where the client does not have any internal engineering staff, GlobalLogic provides a "fab less" partnership from the start, with GlobalLogic taking ownership of the product engineering, platform and architecture. This approach allows companies to focus on the other aspects of a successful product launch, such as strategy, marketing, customer acquisition, go-to-market challenges and the demands of ever-changing markets. By leveraging GlobalLogic's global facilities, world-class engineers and state-of-the-art tools and processes, companies can increase the quality of their software products while dramatically reducing timeliness and operating costs - often by 30 percent or more.

Implementing Group Policy and how to troubleshoot Group Policy processing issues

2009-01-06T02:56:00.000-08:00

Before you start running various Group Policy troubleshooting tools and techniques however, take a moment to step back and ask some simple questions. This phase of the troubleshooting process is based on the motto that a minute of thinking is worth an hour of brute force effort. Below are some simple questions you should ask yourself before you dive into the troubleshooting process.

1. Should the policy be applied to the affected users and computers? That’s a great question to begin with, isn’t it. Say a user comes to you and says he can’t install a certain application by invoking a shortcut on the Start menu. His neighboring workers can do this, but his machine must be broken because he doesn’t have the shortcut for that program. So he complains and you scratch your head wondering why the software installation policy that installs this program isn’t being applied to that user. But should it apply in the first place? What does the user mean by his "neighboring workers"? Maybe other employees on the same floor but belonging to a different department, and while users in that department need that particular program, the complaining user doesn’t and perhaps shouldn’t have access to the program. So actually Group Policy is working just fine in this situation—it’s the user that’s broken! Users are particularly envious of other users’ privileges, and this sort of thin happens a lot in some companies. The key troubleshooting question here is “Who should this policy apply to?

2. What is common to the users or computers to whom the policy is not being applied? This question is applicable if several people or machines aren’t getting the policy they’re supposed to receive. Five people in the Marketing Department come to you and complain that they can’t access Control Panel anymore from the Start menu. What does this tell you? Check the GPO linked to the OU for Marketing users and see whether the policy “Prohibit access to the Control Panel” is Enabled (this policy is found under User Configuration\Administrative Templates\Control Panel). If this policy is Disabled or Not Configured, check GPOs linked to parent OUs to Marketing or linked to the domain and see whether security filtering is mistakenly configured so that users in the Marketing security group have this policy applied.

3. When did users start complaining about the issue? Was it immediately after you made some change to your Group Policy settings, for example by creating and linking a new GPO to an OU? That should tell you something right away. Or did it happen when you made some administrative change to Active Directory, for example moving some computer accounts out of the default Computers container into an OU created specially for such accounts. In this case, the computer accounts were previously receiving their policy from domain-linked GPOs, but now any GPOs linked to the new OU will affect them as well. Or did the complaints start coming with no warning out of the blue and you’ve made no changes to any GPOs for several months? In that case something else is interfering with Group Policy processing for the affected users or computers, and you’ll need to use some of the tools described below to try and find the cause. Or maybe users haven’t been complaining to you at all.

4. When did you actually configure the policy in question? In this situation what happened is that you configured a policy and then checked with the targeted users to see if the policy has been applied and it hasn’t. Well, don’t forget that Group Policy refreshes in the background only periodically, so maybe everything is fine and you just have to wait a while for Group Policy to refresh itself automatically. Or maybe the policy you configured is one that can’t be applied during background refresh and requires the user to log off and on again or to restart their machine.

Bring On The Tools

Once you’ve asked these preliminary questions, which are essential to ask as they can often pinpoint the problem exactly but usually at least help to narrow the scope of what you need to investigate, it’s time to start testing things using tools ranging from ping to userenv logging. It’s difficult to cover such a broad topic in a short article, so I’ll just give you some tips to point you in the right direction:

1. Check the network connection for the affected machine. Maybe it’s not just Group Policy processing that’s not working; maybe the affected user can’t even connect to the network because the network cable for her computer is unplugged! It’s amazing how something as simple like this can be the source of what seems at first to be a complex problem. For Group Policy is quite complicated in how it operates, and an understanding of how it works can help you pinpoint problems more easily.

2. Check if the affected machines can correctly perform DNS resolution. Probably half of all Group Policy processing issues are related to DNS problems such as corrupt resource records on DNS servers, misconfigured DHCP options on DHCP servers, users changing DNS settings on their machines, and so on. Remember that to process Group Policy a computer must first obtain a list of GPOs that apply to it. To do this, they need to query a domain controller. And to locate a domain controller, they need correct client DNS settings so they can obtain SRV records by querying the DNS server. So if DNS is broken then Group Policy is also. Tools for verifying and testing DNS include ipconfig, nslookup, netdiag, and Network Diagnostics in Help and Support.

3. If you’re using the Group Policy Management Console (GPMC) to work with Group Policy, run the Group Policy Results wizard, specifying an affected user and computer on the wizard pages. This will query WMI on the affected machine and create an HTML report that displays which GPOs have been processed and which policy settings have been applied. You can save these reports and view them on any machine using Internet Explorer, and it’s a great way to troubleshoot Group Policy issues. An alternative to using the wizard is to run the command-line tool Gpresults.exe on the affected machine, see the article by Brien Posey on this topic right here on WindowsNetworking.com. In addition to generating RSoP reports, the GPMC can also help you troubleshoot Group Policy problems in other ways. For example, if you right-click on a GPO you can select Save Report to generate an HTML report showing all the configured settings in the GPO.

Source: http://www.windowsnetworking.com/articles_tutorials/Troubleshooting-Group-Policy-Processing.html

Cluster configuration recovery tools in Server 2008

2008-12-30T03:02:00.000-08:00

Microsoft clustering services on versions prior to Windows Server 2008 used a command line tool to fix drive issues. Windows Server 2008 puts this in the interface, making drive tasks more accessible.

If you've done moves of shared storage in a cluster configuration, you may have had to use various recovery tools in versions prior to Windows Server 2008.

Specifically, the resource kit tool dumpcfg.exe is used to repair drive signatures depending on certain conditions that could cause the shared storage hard drives to lose the disk signature. This can be quite a scary endeavor, and the frantic search for the resource kit tools to get the dumpcfg.exe tool from the install media only then offers little comfort on the repair of the situation.

Remember that this situation is a safeguard of the clustering services, and that with the proper recovery techniques, the system can be running again quite quickly.

Windows Server 2008 offers key improvements in the clustering services functionality, and drive recovery is one of the more important features. In lieu of entering a command like this:

dumpcfg -s 0ADD5FAE 1

Windows Server 2008 allows you to correct these types of issues one of two ways. One is within the cluster administrator console with a new repair functionality with the physical disk resource. The other way is within the diskpart utility. Diskpart is not new to Windows Server 2008, but the functionality is.

The new functionality of the cluster resource manager and the additional diskpart commands are a welcome compliment to your arsenal of recovery. If Windows Server 2008 clusters are in your future, it is a good investment to allocate the time to set up a test cluster and go through the recovery process with shared storage using both mechanisms to access the disk signature configuration.

Source:http://www.zdnetasia.com/techguide/windows/0,39044904,62049466,00.htm

Windows Small Business Server 2003 Features & Drawbacks

2008-12-22T06:28:00.000-08:00

The Microsoft Windows Small Business Server 2003 is built on the robust Windows Server 2003 Operating System. Its secure and manageable supporting a wide range of third party solutions to face everyday business management challenges.

Windows Small Business Server 2003 is a server operating system with special features that help small businesses in keeping their company data secure, and improve productivity.

Contents of Windows Small Business Server 2003:

Windows Small Business Server 2003 is a package of different software products that run on single server. It is available in two different editions, Standard Edition and Premium Edition. The Standard Edition comprises of Windows Server 2003, Exchange Server, and Outlook. It comes with five Client Access Licenses, either for each user or for each computer. The Premium Edition includes all the above and also SQL Server, ISA Server, and FrontPage.

The contents of Windows Small Business Server 2003 after all the updates and their features are discussed here. It uses Windows Server 2003 operating system and all other servers run on this. Windows Server 2003 is a reliable and safe operating system and has features like file print, application sharing, and firewall for improving security of company data.

Microsoft Windows Share Point Services that are required for internal company website (intranet) and are useful in document and information sharing is the other important content of Small Business Server 2003.

Also included are Microsoft Exchange Server 2003 and Microsoft office Outlook 2003 with special features like E-mail and messaging services with expanded mailbox limits of up to 75 GB, shared calendaring, shared fax service that works with fewer phone lines from desktops and has enabled receiving of faxes via e-mail or printer, Windows Server update services that help in automatic network wide patch and update management, and daily reporting service for the status of desktop and on functioning of servers that run Microsoft software.

The ISA server 2004 that also comes with the revised premium edition provides firewall for multi-layer security and tools to manage internal internet access.

Features of Small Business Server 2003:

Quick Start setup chart guides pictorially through the setup steps, making it easier to setup as compared to previous versions.
Windows 2000 and XP clients are directly supported by Small Business Server 2003.
Its Easy and simple to maintain through wizards that guide you. This can be done by a user who is well-informed about the network configuration, users and computers.
For the end users the file sharing, printing, sending and receiving e-mails and fax has become fast and easy.
Exchange filters the attachments and keeps the users PC safe from Trojan Horses and viruses, the junk mail filter in Outlook 2003 helps to deal with spam.
Enhanced support for remote and mobile users is available.
Highly reliable, just a restart will help in fixing the problems if any occur.
The firewall in Premium Edition works better and provides high security.
Its competitively priced making it best fit for companies running on low budgets as well.

Drawbacks of Small Business Server 2003:

Its not Do-It-Yourself simple, basic knowledge of Microsoft Windows servers is mandatory to setup and run this version. A person with good knowledge of Windows Business Servers is necessary for managing advanced issues.
PCs running the versions prior to windows 2000 need to be configured manually.
You can have only 75 workstations connected to a Windows Small Business Server 2003 and you can not have multiple Windows Small Business Server 2003 systems in one domain. This is a problem for business with even 1 more workstation in the network.
When setting up users on client systems, they are given local administrator accounts, which is not safe from system security point of view.
You need to protect the server by using antivirus and spam-blocking tools when accessing mails remotely through Outlook Web Access.
The firewall in Standard edition is touchy as to its settings and hence its settings shouldnt be changed, instead an external firewall has to be used.
You can not install the programs that come with Windows Small Business Server on any system other than the server running Windows Small Business Server 2003 itself, to make different SQL server and Exchange server you need to buy a different copy of these servers, costing you more money and It is not a good practice to run all these critical servers from a single server system as the Windows Small Business Server 2003 Premium Edition does.

Source: http://www.dart-creations.com/business-tree/onb/small-business-server-2003.html

Windows Server 2003 Modules

2008-12-15T05:48:00.001-08:00

Small Business Server 2003 is an excellent choice for your computer consulting business. It is sold as a suite so you get a lot of great features. And Small Business Server 2003 is designed strictly with the needs of small business computer consultants in mind. Server 2003 loads the same way XP does. Set the bios to boot from the CD/DVD drive, pop the disk in and follow the instructions. Once it is fully installed and loaded you will be taken to the "Manage Your Server" screen. On this screen you can enable and configure the following options: - File server

enabled by default. Basically allows folders to be shared from the server
SharePoint Services
Creates a web where users can share information
Print Server
A printer installed directly to the server will act as a network printer
Application Server
Turn you server into a web server as well as FTP host
Mail Server - Kinda useless unless you have exchange installed
Terminal Server
Lets users login directly to the server to run applications
Remote Access/VPN Server
Connect to the server remotely via VPN
Domain Controller (Active Directory)
Server controls policies for the entire network domain
DNS Server
Controls name to IP address resolution
DHCP Server
Assignees IP addresses to DHCP clients
Streaming Media Server
Streams video content over the web
WINS Server

Older name to IP address resolution method. Whatever your needs are will determine which of these options get enabled and configured. In this article we are going to briefly touch on Terminal Server, Remote Access, Domain Controller w/Active Directory and DNS Server. I will get into further details about all of them in future articles. Terminal Server: As mentioned earlier Terminal Server allows users to login to the server to run applications installed on the server. Besides enabling Terminal Serevr you will also need a Terminal License Server. This is where the licenses, to user Terminal Server, are installed. Depending on the amount of licenses you have that will determine how many users can login. Terminal Server and Terminal License Server can both be on one machine.

To enable the licensing server go to control panel

add/remove programs
add/remove windows components
select "Terminal Server Licensing" and install.

To login to the server from a workstation you can use Remote Desktop which is built directly into Windows XP and Vista. To find remote desktop click start

all programs
accessories
communications
remote desktop.

When remote desktop appears enter in the server name or IP address to connect. Remote Access/VPN: Virtual Private Networking gives you the ability to remotely connect to your server and share it resources. The server will assign you an IP address either from its DHCP pool or you can manually enter a range of IP addresses the server will hand out to its remote clients. Once connected the next step will be establishing a connection to the server's shared resources.

To do this click start -> run
-> and type in server name or server IP Address (replace with your server's name or IP address) if everything is configured correctly your server's shares will appear. Domain Controller: Setting your server as a Domain Controller means you can control network policy through your server. If all the workstations are on the server's domain, through group and/or domain policy you can restrict user's movements. Control where they are allowed to go and what they are able to change.

With the Domain Controller comes the Active Directory. In the Active Directory you can add network/server users, view/configure domain controllers and domain workstations. This is where you assign users their privileges and whether they can login to the server via Terminal server Services. DNS Server: As stated DNS resolves IP addresses to easier to remember names. Let's say your server's IP address is 192.168.1.2 and its name is PCServer. DNS allows you to search using PC Server .Out of all the modules this is the one that is most confusing in setting up properly. This was a very basic introduction to some of the modules available in Windows Server 2003. In future articles I will be going into further details about each one.

Via: http://www.goarticles.com/cgi-bin/showa.cgi?C=1009313

Start planning a deployment mechanism for Windows Server 2008

2008-12-05T06:28:00.000-08:00

Deployment mechanisms for Windows Server products has been a touchy topic over the years. Many administrators find various requirements warranting a by-hand installation, but the time cost and configuration inconsistencies are something that a deployment solution can address. Further, other mechanisms such as virtual machine cloning can get the job done but are not a native solution to the operating system. This is where Windows Deployment Services (WDS) can step in to fill the gap.

Regardless of the quantity of Windows Server 2008 systems that are installed, it is a good time to get a WDS implementation configured and running correctly. Windows Server 2008 offers many appealing new features to the server administrator, such as the GlobalNames zone, hard drive size changes made easy, and enhanced scheduled task functionality. On the other side of the fence, Web developers are anxious to get Web applications tested and deployed on some of the new features of IIS 7, which is available only on Windows Server 2008.

This impending demand is why WDS needs to be in place and ready when the time comes. WDS exists as a server role and is easily installed from the Server Management console. Figure A shows the WDS role being added.

Once the role is installed, there are a few planning points that you need to configure before a system is ready to receive the image from the WDS server. These include DHCP scope options and image file management from the Windows installation media. Or you can choose to use the Unattended Installation option; this install uses a special file, unattended.xml, to be linked to an image.

Take the time to invest in WDS, at least in an experimental capacity to make the server build process a non-event as environments migrate from Window Server 2003 to Windows Server 2008.

Source: blogs.techrepublic.com.com/datacenter/?p=473

How to Disable a service or Device Drivers using Group Policies

2008-11-26T01:25:00.000-08:00

Group Policies are used to apply system and security policies for the client PCs
in a Windows Active Directory based Domains. While Group Policies is vast in itself to explain, here is a simple procedure on how to enable/disable a service or a Device driver using Group Policies.

The registry keys that the Group Policy targets to disable the service or the drivers is here

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services]

All the device drivers, services & applications can be found here. I’m disabling my Audio device driver for example in this case.

The Audio driver in my PC is aeaudio.sys and the registry key is

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\aeaudio]

In the right-pane, there is a DWORD entry “Start”

The possible values are

“4″ - Disable
“3″ - Manual
“2″ - Automatic
“1″ - System
“0″ - boot

The value “4″ disables the driver. Set the value of the DWORD to “4″ to disable the driver.

Disable Audio in GPO

Ok. Now, how we do it to multiple client PCs using Group Policies.

Create a new Administrative Template (say sound_dis.adm) with the following

; Replace aeaudio with actual driverkey or service in Registry
; Start = 4 (disable), 3 (manual), 2(automatic), 1 (system), 0 (boot)

Class Machine
CATEGORY “Hardware Control”
POLICY “Disable Soundcard”
KEYNAME “SYSTEM\CurrentControlSet\Services\aeaudio”
PART “HW: Analog Devices (Soundmax)” Checkbox
VALUENAME “Start”
VALUEON NUMERIC 4 VALUEOFF “3″
END PART
END POLICY
END CATEGORY

Once done, import the template in GP snap-in and apply to the group of PCs. The next GP update will disable the registry key on the PCs. Test to see there is no more sound from the system.

Source:windowsreference.com/windows-xp/how-to-disable-a-service-or-device-drivers-using-group-policies/

Group Policy Preferences in Windows Server 2008

2008-11-20T01:20:00.000-08:00

Last year, Microsoft acquired DesktopStandard and obtained GPOVault and most of the PolicyMaker family. GPOVault has been updated and released as Advanced Group Policy Management (AGPM), part of the Microsoft Desktop Optimization Pack for Software Assurance (MDOP). For more information about AGPM see my previous post. PolicyMaker Standard Edition and PolicyMaker Share Manager will be available to Microsoft customers in two ways as "Group Policy Preferences" and will be integrated into the Group Policy Management Console (GPMC) in:

Windows Server 2008 (starting with November CTP)
Remote Server Administration Tools (RSAT) for Windows Vista SP1

So, Windows Server 2008 includes the new Group Policy Preferences built-in to the Group Policy Management Console (GPMC). Additionally, administrators can configure preferences by installing the Remote Server Administration Tools (RSAT) on a computer running Windows Vista Service Pack 1 (SP1).

But what is actually the difference between "Group Policy settings and Group Policy Preferences"??

The key difference between "Group Policy Preferences" and "Group Policies (settings)" is enforcement. "Group Policies" enforce policy settings and prevent users from changing them. Group Policy Preferences does not (necessarily) enforce settings to machines/users, but merely applies the settings as preferences.

"Group Policy Preferences" extend more than 20 Group Policy categories within a Group Policy Object (GPO) and enable IT professionals to configure, deploy, and manage operating system and application settings including mapped drives, scheduled tasks, power options, files and/or folders, printers, folder options and Start menu settings for Windows Server 2008, Windows Vista, Windows Server 2003, and Windows XP systems.

"Group Policy Preferences" do not require you to install any services or components onto your servers. Windows Server 2008 includes Group Policy Preferences by default as part of the Group Policy Management Console (GPMC). Administrators will also be able to configure and deploy Group Policy preferences in a Windows Server 2003 environment by installing the Remote Server Administration Tools (RSAT) on a computer running Windows Vista with SP1. Both RSAT and Windows Vista SP1 will be available in the first quarter of 2008.

Although you don’t have to install any services to create GPOs (Group Policy Objects) that contain Group Policy Preferences, you must deploy the Group Policy Preferences client-side extension (CSE) to any client computer to which you want to deploy these preferences. The CSE will be available as a separate download from Microsoft and will support the following Windows versions:

Windows XP with SP2
Windows Vista
Windows Server 2003 with SP1
Windows Server 2008 already includes the CSE.

Source:trycatch.be/blogs/roggenk/archive/2007/11/26/group-policy-preferences-in-windows-server-2008.aspx

Cloud Computing: Tools Give IT Direct Access

2008-11-12T21:36:00.000-08:00

Talk to IT leaders about cloud computing and two big worries come through loud and clear: security and management. As noted by many respondents to CIO's recent survey of IT leaders on cloud computing, IT departments fear losing too much control over their data and application service levels. Sounds a lot like IT's concerns during the early days of virtualization, doesn't it?

"It's almost a repeat of what we saw with virtualization," says Javier Soltero, CEO of Hyperic, one of the early entrants in the race to help IT groups manage data and applications residing in the cloud. "Companies are looking for the right on-ramps. Until there are robust management tools, it's going to stay the land of experimentation."

As IT groups working with virtualization know, the past two years have spawned an ever-increasing number of startup vendors pitching virtualization management tools. It's unclear yet whether the same phenomenon will happen around cloud computing, analysts say. RightScale, one of Hyperic's early rivals, also offers monitoring and management tools for Amazon EC2.

Hyperic aims its tools at companies managing highly-dynamic environments that utilize virtualization, cloud computing, or both; its 400 or so current cutomers include SaaS and technology providers (such as Rackspace), media companies (such as CNet) and financial institutions, Soltero says.

Such companies have been early movers on virtualization and cloud because the economics of their businesses demand it. At the same time, these companies must ensure that application performance to users and customers does not suffer, clouds or no clouds.

Hyperic's latest offering, Hyperic HQ 4.0, being released today, aims to help IT manage application performance in internal data centers or in cloud services. The tool allows a company that wants to use Amazon's EC2 cloud services, for example, have a detailed window into how its apps are running in Amazon's cloud.

Customers using the Hyperic tools can look at every layer of the equation, say a Web server, database, OS and end-user application. Data is sent back to a central dashboard where IT can examine it alongside other performance measures, Soltero says.

This kind of transparency is important for security and capacity planning as enterprises begin to move into the cloud, especially in instances where they want to "burst up" and tap into the cloud only at times of peak need.

But shouldn't Amazon already offer this kind of service directly to its customers? Enterprises must think of Amazon as the utility company, Soltero contends. Asking Amazon to track performance issues like this would be like expecting your local electric company to diagnose what was wrong with your clothes washer or dryer at home, he says.

Source: pcworld.com

Control user access to Windows Update with Windows Server 2003 Group Policy

2008-11-06T23:15:00.000-08:00

Windows Update is a wonderfully useful application that allows central management and automatic installation of updates for Windows Server 2003. There are other solutions that do this, but Windows Update and Windows Server Update Services Server are cost-effective solutions that work well in many cases.

However, there may be times when you don’t want a balloon to pop up notifying users of the updates. Configuring a few Group Policy settings will allow you to control the update process in your environment and ensure that users cannot load updates using Windows Update.

Administrators should be the only ones who can load updates using Windows Update. You can prevent users from accessing Windows Update by managing the Windows Update Access settings; this does require you to configure Group Policy. If you want to give some users access to Windows Update, you can manage who gets access through these settings.

You can remove access to the Windows Update features in separate steps — one which prevents updates using Windows Update, another which removes links to Windows Update items, and another which disables or configures automatic updates. Using the Group Policy configurations discussed here will disable Automatic Updates for the users or computers to which the modified Group Policy objects apply. Keep this in mind when configuring these items.

To prevent Windows Update from updating the operating system, complete the following steps:

Open the Group Policy Editor.
Create a new Group Policy object, for example, No Updates.
Select the User configuration.
Click Administrative Templates.
Click System.
Click Internet Communication Management.
Select Internet Communication Settings.
In the right pane of the Group Policy Editor, double-click Turn Off Access To All Windows Update Features, select the Enabled radio button, and click OK.

To disable access to Windows Update commands, such as links in the Start menu or Internet Explorer, complete the following steps:

Click User Configuration.
Click Administrative Templates.
Click the Start Menu and Task Bar.
In the right pane of the Group Policy Editor, double-click Remove Links And Access To Windows Update.
Set the policy to Enabled and click OK.

To prevent the use of Windows Update entirely, complete the following steps:

Open the Group Policy Editor.
Select Computer Configuration.
Click Administrative Templates.
Click Windows Components.
Click Windows Update.
Double-click Configure Automatic Updates.
Select the Disabled radio button and click OK.

Source: http://blogs.techrepublic.com.com/datacenter/?p=202

How to Manage Group Policy Objects in Windows Server 2003

2008-10-14T01:22:00.000-07:00

Select Start--> Run, type MMC in the run dialog box and choose OK to open the MMC.
From the Main Menu of the MMC, select File--> Add/Remove Snap-In.
In the Add/Remove Snap-In dialog box, choose Add. The Add Standalone Snap-In is displayed.
Highlight the Group Policy Object Editor Snap-In and choose Add. The Group Policy Wizard is displayed.
The Group Policy Object specifies Local Computer by default. Choose Browse to browse for a Group Policy Object.
The Domains/OU tab is the default showing the current domain. Notice that you can choose the default Domain Policy here and that you have a Create New Policy Object button to the right of the drop-down list of domains. In the Domains/OU tab, click the create New Group Policy Object button. Name the GPO Security Policy GPO. Choose Ok and then choose finish to return to the Add Standalone Snap-In window.
Highlight the Event Viewer in the snap-in and choose Add.
The select computer dialog box appears and Local Computer selected by default. Choose the Another Computer radio button and type the name of the domain controller computer from which you are doing this exercise.
Click Finish then click Close.
In the Add/Remove Snap-In dialog box, notice that the new GPO we created is now listed along with the Event Viewer.
Choose Ok to return to the main console window.
Select File--> Save As.. Save the console as Security Policy GPO in all Users\StartMenu\Programs\Administrative Tools folder and choose Save.

Now you can access this console by selecting Start Administrative Tools Security Policy GPO.

Now that we have installed our new GPO we need to set the appropriate permissions so that our users have ideal settings to certain information that may only be available to his or her department. In order to change the user permissions, we can easily set our settings in order to accommodate for our Security Policy that fits along with the GPO we created. In order set the proper settings please follow the sequence as indicated below to achieve this task.

To access the Security Policy settings we have created for our GPO we need to access the Account Security Policies folder. Click Start--> Administrative Tools--> Security Policy GPO and the MMC Snap-In dialog appears.
Expand Security Policy GPO--> Computer Configurationà Windows Settings--> Security Settings--> Account Policies.
Under the Account Policy GPO Object we can control the settings for passwords, lockouts, local and user audits along with security options that can accessed and edited right from the MMC Console we created above.

Source:ehow.com/how_4528185_group-policy-objects-windows-server.html

Tool Solves Windows Admin Rights Issues

2008-09-29T06:18:00.000-07:00

Avecto has unveiled a product that enables organisations to lock down their Windows PCs without running into the problems this can cause when applications need a higher privilege level in order to run.

The UK-based startup said that Privilege Guard allows group policy settings to govern the privilege level of individual applications, enabling workers to log-in with minimal access rights for a greater level of security.

In the past, malware writers have exploited the fact that most Windows users operate with full administrator privileges by default.

Forcing users to run with minimal rights can prevent malicious code from causing harm, but this can also stop many common business applications from accessing the resources they need to run.

Privilege Guard works by elevating the process tokens of individual applications to a higher privilege as they launch, according to Avecto chief technology officer Mark Austin.

"It creates a token based on the user's token, but with administrator rights, " he explained.

While other methods exist for elevating application privileges, very few allow administrators to control this on an application-by-application basis or without ending up giving the user full admin rights as well.

In the current version, privilege levels are defined via a central management console and delivered to endpoint systems as an XML configuration file.

This can be distributed along with the Privilege Guard client using standard IT deployment tools, according to Austin.

Avecto plans to integrate future versions of Privilege Guard with Active Directory, so that application privilege levels can be set and updated via Group Policy settings on a Windows domain.

"We're trying to keep it simple at first," Austin said.

Privilege Guard supports Windows XP and Vista, and Windows Server 2003 and 2008 including Terminal Services. Licences cost £20 per seat.

The software is currently available directly from Avecto, but Austin said the firm is working on building a distribution channel.

Source:vnunet.com

Windows Server Group Policy

2008-07-11T01:34:00.000-07:00

In Windows 2000, administrators use Group Policy to enhance and control users' desktops. To simplify the process, administrators can create a specific desktop configuration that is applied to groups of users and computers. The Windows 2000 Active Directory service enables Group Policy. The policy information is stored in Group Policy objects (GPOs), which are linked to selected Active Directory containers: sites, domains, and organizational units (OUs).

A GPO can be used to filter objects based on security group membership, which allows administrators to manage computers and users in either a centralized or a de-centralized manner. To do this, administrators can use filtering based on security groups to define the scope of Group Policy management, so that Group Policy can be applied centrally at the domain level, or in a decentralized manner at the OU level, and can then be filtered again by security groups. Administrators can use security groups in Group Policy to:

Filter the scope of a GPO. This defines which groups of users and computers a GPO affects.
Delegate control of a GPO. There are two aspects to managing and delegating Group Policy: managing the group policy links and managing who can create and edit GPOs.

Administrators use the Group Policy Microsoft Management Console (MMC) snap-in to manage policy settings. Group Policy includes various features for managing these policy settings. In addition, third parties can extend Group Policy to host other policy settings. The data generated by Group Policy is stored in a Group Policy object (GPO), which is replicated in all domain controllers within a single domain.

The Group Policy snap-in includes several MMC snap-in extensions, which constitute the main nodes in the Group Policy snap-in. The extensions are as follows:

Administrative templates. These include registry-based Group Policy, which you use to mandate registry settings that govern the behavior and appearance of the desktop, including the operating system components and applications.
Security settings. You use the Security Settings extension to set security options for computers and users within the scope of a Group Policy object. You can define local computer, domain, and network security settings.
Software installation. You can use the Software Installation snap-in to centrally manage software in your organization. You can assign and publish software to users and assign software to computers.
Scripts. You can use scripts to automate computer start up and shutdown and user logon and log off. You can use any language supported by Windows Script Host. These include the Microsoft Visual Basic® development system, Scripting Edition (Vb Script); JavaScript; PERL; and MS-DOS®-style batch files (.bat and .cmd).
Remote Installation Services. You use Remote Installation Services (RIS) to control the behavior of the Remote Operating System Installation feature as displayed to client computers.
Internet Explorer maintenance. You use Internet Explorer Maintenance to manage and customize Microsoft® Internet Explorer on Windows 2000-based computer.
Source: technet.microsoft.com

Windows Server 2000 & 2003

2008-07-07T07:05:00.000-07:00

It may look like Windows Vista. It shares the same code base as Vista. It even rolls in Vista's first Service Pack. But in terms of customer adoption plans, Windows Server 2008 is no Vista.

A new Computer world survey shows that 63% of the 403 respondents plan to adopt Microsoft's server operating system. (You can read more extensive survey results here.) This contrasts with the intention of some IT organizations to skip Vista entirely and move directly to Windows 7 on the desktop. According to an online survey of 372 IT professionals conducted by Sanford C. Bernstein in May, companies expect just 26% of their PCs to be running Vista by the beginning of 2011, down from an estimate of nearly 68% of computers based on a similar survey a year ago.

"I haven't seen any shadow of Vista being cast over Windows Server 2008," says John Enck, analyst at Gartner Inc. Most industry watchers, in fact, agree that deployment is not a matter of if, but when and where.

IT executives say that for the most part, Windows Server 2008's many new features won't compel them to change their normal refresh schedules to adopt it right away. "It's just an evolutionary step from Server 2003," says Rick Redman, senior IT analyst for the city of Amarillo, Texas.

Jim Thomas, director of IT operations at window manufacturer Pella Corp. in Pella, Iowa, says Microsoft's new virtualization hypervisor, Hyper-V, is interesting. But other than that, he says, there's "not a whole lot" that he finds compelling. And Hyper-V is too new and immature to warrant rushing ahead to convert his 425 Windows servers, he adds.
Overall, however, IT decision-makers give the operating system qualified thumbs up and plan to move to it as part of the normal server refresh cycle, which typically ranges from three to five years. Some customers, for instance, phase in new servers by replacing one-third of their machines each year; others replace all of their servers at once.

"We're coming at it much more from a normal rollout of an operating system," says Bob Yale, IT principal at The Vanguard Group Inc. in Valley Forge, Pa. Vanguard has about 1,200 Windows servers, most of which are running Windows Server 2003.

Overall, 59% of Computerworld’s survey respondents who said they plan to adopt Windows Server 2008 (WS '08) expect to get started within the next 12 months. More than half -- 55% -- expect to complete the transition within two years. The highest level of interest came from respondents at midsize organizations with 100 to 1,000 employees; 69% of them said they expect to get started within the next 12 months.

In most cases, the early adopters are deploying WS '08 selectively in a bid to leverage specific new features in the operating system. While more than half of respondents in our survey said they will follow the usual upgrade schedule, about one in four said they will accelerate adoption for some applications. One in three respondents said that their organizations have a business need for a new feature in WS '08.

Windows Server Group Policy

2008-07-01T07:54:00.000-07:00

Group Policy & Active Directory services infrastructure enable IT administrators to automate one-to-many management of users and computers—simplifying administrative tasks and reducing IT costs. Administrators can efficiently implement security settings, enforce IT policies, and distribute software consistently across a given site, domain, or range of organizational units.

It may look like Windows Vista. It shares the same code base as Vista. It even rolls in Vista's first Service Pack. But in terms of customer adoption plans, Windows Server 2008 is no Vista.

A new Computerworld survey shows that 63% of the 403 respondents plan to adopt Microsoft's new server operating system. This contrasts with the intention of some IT organizations to skip Vista entirely and move directly to Windows 7 on the desktop. According to an online survey of 372 IT professionals conducted by Sanford C. Bernstein in May, companies expect just 26% of their PCs to be running Vista by the beginning of 2011, down from an estimate of nearly 68% of computers based on a similar survey a year ago.
"I haven't seen any shadow of Vista being cast over Windows Server 2008," says John Enck, analyst at Gartner Inc. Most industry watchers, in fact, agree that deployment is not a matter of if, but when and where.

IT executives say that for the most part, Windows Server 2008's many new features won't compel them to change their normal refresh schedules to adopt it right away. "It's just an evolutionary step from Server 2003," says Rick Redman, senior IT analyst for the city of Amarillo, Texas.

Jim Thomas, director of IT operations at window manufacturer Pella Corp. in Pella, Iowa, says Microsoft's new virtualization hypervisor, Hyper-V, is interesting. But other than that, he says, there's "not a whole lot" that he finds compelling. And Hyper-V is too new and immature to warrant rushing ahead to convert his 425 Windows servers, he adds.
Overall, however, IT decision-makers give the operating system a qualified thumbs up and plan to move to it as part of the normal server refresh cycle, which typically ranges from three to five years. Some customers, for instance, phase in new servers by replacing one-third of their machines each year; others replace all of their servers at once.

"We're coming at it much more from a normal rollout of an operating system," says Bob Yale, IT principal at The Vanguard Group Inc. in Valley Forge, Pa. Vanguard has about 1,200 Windows servers, most of which are running Windows Server 2003.

Overall, 59% of Computer world 's survey respondents who said they plan to adopt Windows Server 2008 (WS '08) expect to get started within the next 12 months. More than half -- 55% -- expect to complete the transition within two years. The highest level of interest came from respondents at mid size organizations with 100 to 1,000 employees; 69% of them said they expect to get started within the next 12 months.

Mike Moore, IT principal at Vanguard, says his company has implemented a few WS '08 machines where the new features filled a business need. For instance, Vanguard has servers in place that leverage WS '08's new Network Access Protection (NAP) features. "We'd like to extend that further with the more-granular policy servers that Windows Server 2008 provides," he says. But he doesn't expect to get serious about WS '08 rollouts until sometime in 2009.
Neither does the city of Amarillo's Redman, who says he'd like to see a base of documentation and best practices before moving forward. "The biggest problem is getting useful technical articles out of Microsoft that don't have a lot of marketing hype," he says.