Wednesday, April 15, 2009

Windows Server 2008 Feature: Special Ops Software Password Policy and Password Reset

One of several significant advancements introduced in Windows Server 2008 domain functional level is the ability to configure multiple password policies targeting arbitrarily selected Active Directory users or global groups. While this new functionality, referred to as Fine-Grained Password Policies, brings long-awaited flexibility to rigid security structure that used to influence design of forest hierarchy (forcing the creation of additional domains whenever non-uniform rules governing password history, age, length, complexity or lockout behavior were required), its benefits remain somewhat limited. In particular, due to functional-level dependency, its implementation requires all domain controllers run Windows Server 2008. In addition, because Fine-Grained Password Policies lacks a friendly graphical interface, administrators must resort to a fairly cumbersome ADSIEdit console whenever a custom policy definition or configuration is needed.

Furthermore, the scope of these policies is determined based on global group membership, rather than the location of a target user within a designated Organizational Units, which further complicates their management.

If these shortcomings are not acceptable to you or if you are looking for more advanced password-related capabilities, you might want to consider taking advantage of third-party offerings, which go beyond the limited set of features built into the operating system.


Special Operations Software specializes in products targeting Windows environments with intention of filling functionality and manageability gaps existing in their original feature sets designed by Microsoft. In general, its portfolio can be grouped into several broader categories, such as system management, compliance or security, based on the type of need they address, with a certain degree of overlap between them.

Since the resulting restrictions become part of the User Configuration node of a Group Policy Object, they function in the same manner as other group policy settings. For this reason, they can be linked to individual Organizational Units and limited, if desired, based on security filtering to specific domain users or groups only. Note, however, that resulting passwords must comply not only with custom restrictions imposed by Specops password definitions but also with domain-wide, built-in password policy imposed via domain-level GPO. In addition, if you decide to install optional Active Directory Users and Computers extension, you will be able to determine password policies affecting individual user accounts (via Specops Password Policy... entry in the context-sensitive menu of their objects displayed in the management console) from the administrative systems where Specops Password Policy Admin is present.

For Detail Info visit: http://www.enterpriseitplanet.com/security/features/article.php/11321_3812801_1

Thursday, April 9, 2009

How to Install IIS Server 7.0 On Windows Server 2008

Internet Information Services 7.0 is a Web server component that is included with Windows Server 2008. By installing the service, you can turn your computer into a powerful Web server to host your Web sites, applications
and so on.

IIS 7.0 is not installed by default on Windows Server 2008. You can install IIS using Server Manager. The ‘Add Roles Wizard’ will walk you through the process and prompt you for any required information. The steps for installing IIS 7.0 are described in detail below.

  • Click Start, point to Administrative Tools and click Server Manager.
  • Click Add Roles.
  • The Add Roles Wizard will appear. Click Next.
  • If any required features are missing, you will be prompted to install them by clicking the Add Required Features button.
  • From the Select Server Roles window, click the box beside the Web Server (IIS) option. Click Next.
  • Click Next.
  • Select the specific role services to install for IIS. If you are unsure what a service is for, select the service and a short description will appear.
  • Click Next.
  • Review your installation selections and click Install.
  • When the installation is complete, review the results in the ‘Installation Results’ window and click Close.
Source From: http://www.lockergnome.com

Thursday, April 2, 2009

How to Configure Wireless settings via Group Policy

Wireless networking in an office environment can supplement the Ethernet network in case of an outage or, in some cases, replace it altogether. Using Wireless Access Points (WAPs) to connect remote users or desktop PCs can be a very simple way to get everything up and running quickly. And leveraging the power and centralization of Active Directory when setting up your wireless infrastructure can save time for all parties involved.

Getting started

To get the ball rolling, I suggest creating a new Group Policy Object (GPO) to configure for Wireless settings. This will keep all the wireless settings contained so they can be enabled and disabled easily. Note: when performing the steps needed to configure these settings, I will be using the Group Policy Management Console (GPMC) — available at Microsoft downloads.

Follow these steps:

1. Open the GPMC from the Administrative Tools menu.
2. Expand the Forest node on the left pane of the console.
3. Expand Domains and expand your domain.
4. Locate the Organizational Unit (OU) where you wish to link the GPO.
5. Right-click the OU and select Create and Link a GPO Here.

Note: Once the GPO is added here, any objects that exist in this OU will have the policies defined by the linked GPOs applied to them.

Enter a name for the GPO you are creating and click OK. Doing this will create the object and link to the OU. Be sure to use a descriptive name for the GPO to make future management a bit easier. Once the object is created, there will be no settings defined within the object. Right-click the GPO and select edit to configure the settings you need.
Many, many settings for a GPO

When opening the GPO for editing, there will be many options available for configuration. To find the Wireless settings, expand the computer configuration node, then expand Windows Settings and from there, Security Settings.

Listed under Security Settings you will see Wireless Network (IEEE 802.11) Policies. Click on this node to display any existing configuration items.
Creating a new Wireless Network Policy

Right-click in the details pane on the right of the console with the Wireless Network Policies node highlighted and select Create Wireless Network Policy.

This will open the Wireless Network Policy Wizard. Click Next to bypass the welcome screen. On the next screen, enter a name for the Wireless Network Policy and a description.

Note: Using a description can help you in the event that modifications are needed later.

Clicking Next in the dialog box will complete the wizard and display the Completing the Wireless Network Policy Wizard dialog box. Leave the Edit properties box checked so that you can move right into creating the settings for the policy.

On the properties sheet for the Wireless network policy, the general page displays the settings created by the wizard, the name and description, but also allows you to configure the following:

* Check for Policy Changes Every x Minutes allows you to set the interval for checking for updates.
* Networks to Access options:
o Any available network (access point preferred)
o Access point (infrastructure) networks only
o Computer to computer (ad hoc) networks only
* Use Windows to Configure Wireless Network Settings for Clients allows Windows to manage the wireless settings on client computers.
* Automatically Connect to Non-Preferred Networks allows you to connect to networks that are not listed on the preferred tab of the properties dialog box.

For More Information visit: http://blogs.techrepublic.com.com/networking/?p=1093&tag=rbxccnbtr1

Monday, March 30, 2009

How to Manage BIOS updates with Windows Server 2008

For Windows Server 2008, the Core Edition has scenarios where its use is appropriate. In some cases, the Core Edition is even required like the free version of Hyper-V. For managing the hardware, this throws some curve balls to the Windows administrator.

The first thing install Opera on Core Edition servers — primarily because using Opera on the Core Edition will give a crude file manager function by typing C:\ in the address bar.

To install Opera, simply download it from another system and save the installation file to the C:\ drive of the Core Edition server and run the setup. From there, I can get the server’s updated BIOS firmware. Figure A shows Opera functioning as a file browser.

Manage BIOS updates with Windows Server 2008

Prefer Opera, but other browsers may work. Remember, the Core Edition has no version of Internet Explorer, but other versions are installable on Core.

Get drivers and updates

For the hardware updates, you can get them from a local resource or the server support page and download them like you would on a full installation version. I recently updated an HP ProLiant ML350 G5 server to the latest BIOS, version D21 on a Windows Server 2008 x64 Core Edition system. The online flash tools for HP will run in the same fashion as they would on a full installation version. Figure B shows the installation of the update after the download.

BIOS Updates in Windows Server 2008

Legacy mechanisms such as floppy-based flashing are still possible, but they are archaic and more time-consuming than some of the online mechanisms available. It is worth going through the learning curve on Core Edition to maintain the same flexibility levels as the full installation versions of Windows Server 2008.

Source: http://blogs.techrepublic.com.com/

Monday, March 23, 2009

HP NS2000 Server Point for Small Businesses

HP Integrity NonStop NS2000 server offers 24/7 availability at price point for small businesses.

All of the websites and most of the applications that are used online are hosted on servers. In the corporate world, many applications used around the office are also server-based. Many of the servers in use in the IT world are required to be available constantly without downtime.

HP announced a new server today that promises non-stop availability at a low price called the HP Integrity NonStop NS2000 server is an entry-level product that offers fault tolerance at the lowest cost available for a multi-core Integrity NonStop system.

Jim Johnson from the Standish Group said in a statement, "There is a large segment of smaller enterprise customers that tends to be priced out of the market for high-end, fault-tolerant servers. For those customers, the NS2000 server offers significant value and additional choice for application availability and fault tolerance."

The NS2000 is a rack-mounted server HP claims offers double the performance of the previous NonStop entry-class systems. The system uses Intel Itanium processors and offers 24/7 data availability and real-time access to critical business systems.

HP's Winston Prather said, "Customers with limited IT resources are looking for cost-effective solutions that quickly and easily deliver the fault-tolerant capabilities they need to minimize risk of downtime. The NS2000 Integrity family delivers the performance and reliability our customers need right out of the box, at a very competitive price point."

Several NS2000 models are available with a variety of configurations based on customer needs. Systems offer a choice of four-core and eight-core CPUs with 8GB or 16GB of RAM per CPU with AC and DC powered versions available. Pricing depends on configuration reports HP.


For more information Visit Here

Sunday, March 15, 2009

How to migrate Windows Server 2003 TS License Server

License Server migration is an added feature in Windows Server 2008 R2. In Windows Server 2008 R2, when you right-click on the server name you will see the ‘Manage RDS CALs’ option. After selecting this, you will see the ‘Manage RDS CALs Wizard’ to guide you through the migration process. But to migrate Windows Server 2008 license server, you need to follow the same steps as mentioned in the post.

The migration of your license server requires three stages.

1. First, you must activate the new license server.

2. Next, you need to deactivate the old server.

3. Lastly, you need to move all the licenses from the old server to the new server.

To migrate your license server:

Step 1: Activate the new license server:

  1. Set up the VM guest as a Win2003 TS license server.
  2. Open the TS License Manager tool (licmgr.exe)
  3. Activate the server by right-clicking on the server name under the ‘All servers’ node in the left pane and selecting ‘Activate Server’. The Activate Server Wizard will open.
  4. Click Next. Select ‘Telephone’ as your connection method and click Next.
  5. On the ‘Country or Region Selection’ page, select your appropriate country and region.
  6. The next page will provide you with the License Server ID and the Microsoft Clearinghouse telephone number to call. Write them on a piece of paper but don’t make the call yet. You may want to keep the wizard open.
Step 2: De-activate the old license server:
  1. Open the TS License Manager tool on your old license server.
  2. Change the connection method to telephone by right-clicking the server name under the ‘All servers’ node in the left pane, selecting ‘Properties,’ and setting the connection method to ‘Telephone’.
  3. Again right-click the server name under the ‘All servers’ node in the left pane, select ‘Advanced’ and then select ‘Deactivate Server.’ The License Server Deactivation Wizard will open. Click ‘Next’.
  4. On the ‘License Server Deactivation’ page, you will be provided with the same clearinghouse phone number and the License Server ID of your old server. Make a note of this License Server ID as you need to provide this to Microsoft Clearinghouse.
  5. Call Microsoft Clearinghouse at the number you have noted and give them the product ID of the new license server which you want to activate and of the old license server which you want to deactivate. Once you have given them this information, Microsoft Clearinghouse will provide you with the confirmation code. Enter this code into the License Server Deactivation Wizard when prompted.
Step 3: Move each of the license key packs one by one, from the older LS to the new one:
  1. On the same call with the clearinghouse, inform them that you also want to migrate the licenses.
  2. Open the License Install Wizard on the new license server.
  3. Provide the following information to the clearinghouse which they will use to generate the new License Key Pack ID:
    1. The license server ID of the old license server
    2. Paper work for the original TS licenses
  4. Enter the new license key pack ID in the Install License Wizard and complete the License Installation on the new license server.
  5. Repeat the same process for migration of all license key packs.
Source: http://blogs.msdn.com/ts/archive/2009/03/06/migrating-a-windows-server-2003-license-server.aspx

Thursday, March 5, 2009

Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2 Release

Windows Server 2008 Service Pack 2 (SP2) Release Candidate and Windows Vista Service Pack 2 (SP2) Release Candidate is an update to Windows Server and Windows Vista that addresses feedback from our customers.

Windows Server 2008 SP2/Windows Vista SP2 Release Candidate is prerelease code offered to the public through our Customer Preview Program. Please see the Windows Server SP2/Windows Vista SP2 Customer Preview Program page on TechNet/MSDN for additional details, documentation, and forums.

Windows Server 2008/Windows Vista SP2 Release Candidate apply to people, organizations, and technical enthusiasts who are comfortable evaluating prerelease software. This prerelease software is provided for testing only. We do not recommend installing this software on primary or mission-critical systems. Installation of Service Pack 2 Release Candidate will result in Microsoft collecting information about the installation process, even if the installation is not completed. Wet recommend that you have a backup of your data before you install any prerelease software.

SP2 is an update to Windows Vista and Windows Server 2008 that addresses feedback from our customers and partners. By providing these fixes integrated into a single service pack, Microsoft provides a single high-quality update that minimizes deployment and testing complexity for customers. In addition to all previously released updates, SP2 will contain changes focused on addressing reliability and performance issues, supporting new kinds of hardware, and adding support for several emerging standards. SP2 will also continue to make it easier for IT administrators to deploy and manage large installations of Windows Vista and Windows Server 2008.

Service Pack 1 is a prerequisite for installing Service Pack 2. Please make sure that your system is running Service Pack 1 before you install Service Pack 2.
This is a DVD ISO image contains Service Pack 2 for Windows Server 2008 SP2 for x86, x64, IA-64 and Windows Vista for x86, x64. This image is only applicable to computers that have one or more of the following languages: English, German, French, Japanese, or Spanish. If you have an OS or language pack that is not one of these languages please use the "All Languages" version of Service Pack 2.

Support for Windows Server 2008 SP2 Beta and Windows Vista SP2 Beta can be received by visiting the Windows Server 2008 Service Pack 2 and Windows Vista Service Pack 2 TechNet forum.

System Requirements

* Supported Operating Systems: Windows Server 2008; Windows Vista
* Windows Server 2008, Windows Vista

Instructions

1. To start the download, click the Download button and then do one of the following, or select another language from Change Language and then click Change.
* Click Run to start the installation immediately.
* Click Save to copy the download to your computer for installation at a later time.



Source: http://www.microsoft.com/downloads/details.aspx?FamilyId=0A3D7A63-46AF-4E04-AC8C-91B8BC476450&displaylang=en