Windows 2000 can be deployed to a site via various methods. It can be installed onto servers via traditional media (such as CD) or via distribution folders that reside on a shared folder. Installations can be attended or unattended. During a manual installation, the administrator must specify configuration options. Unattended installations are scripted via an answer file, or a predefined script in the form of an INI file that has all the options filled in. An answer file can be created manually or using the graphical Setup manager. The Winnt.exe or Winnt32.exe program then uses that answer file to automate the installation. Unattended installations can be performed via a bootable CD, using Microsoft Systems Management Server (SMS), via the System Preparation Tool (Sysprep), via the Winnt32.exe program using the /syspart switch or via Remote Installation Services (RIS). The ability to slipstream a service pack into the original operating system setup files is also introduced in Windows 2000.[105]
Windows 2000 has received four full service packs and one rollup update package following SP4, which is the last service pack. Microsoft phased out all development of its Java Virtual Machine (JVM) from Windows 2000 in SP3. Internet Explorer 5.01 has also been upgraded to the corresponding service pack level.
((NEW)) Microsoft Jet 4.0 Service Pack 8 For Windows 7 17
Microsoft had originally intended to release a fifth service pack for Windows 2000, but Microsoft cancelled this project early in its development, and instead released Update Rollup 1 for SP4, a collection of all the security-related hotfixes and some other significant issues.[114] The Update Rollup does not include all non-security related hotfixes and is not subjected to the same extensive regression testing as a full service pack. Microsoft states that this update will meet customers' needs better than a whole new service pack, and will still help Windows 2000 customers secure their PCs, reduce support costs, and support existing computer hardware.[115]
The Windows 2000 family of operating systems moved from mainstream support to the extended support phase on June 30, 2005. Microsoft says that this marks the progression of Windows 2000 through the Windows lifecycle policy. Under mainstream support, Microsoft freely provides design changes if any, service packs and non-security related updates in addition to security updates, whereas in extended support, service packs are not provided and non-security updates require contacting the support personnel by e-mail or phone. Under the extended support phase, Microsoft continued to provide critical security updates every month for all components of Windows 2000 (including Internet Explorer 5.0 SP4) and paid per-incident support for technical issues. Because of Windows 2000's age, updated versions of components such as Windows Media Player 11 and Internet Explorer 7 have not been released for it. In the case of Internet Explorer, Microsoft said in 2005 that, "some of the security work in IE 7 relies on operating system functionality in XP SP2 that is non-trivial to port back to Windows 2000."[125]
Out of the box, Win32 machines lack the ability to be efficiently managed. It is up to an administrator to implement some form of system management. For many administrators with relatively small networks this means walking from machine to machine to install new software or check to see how many CDROM drives exist on the computer. Considering the sheer size of some networks it becomes a nightmare to do something such as deploying an updated driver or service pack. Even a simple task as discovering which computers have enough free hard drive space for a software upgrade can take many hours of an administration teams time.
CellBell had a network of approximately 1700 NT boxes scattered across the state. The machines were running a combination of NT 3.51 and NT 4.0. Some had different service packs installed while others had none. Some machines had 32 megs of ram while others had only 16. Some had large hard drives with plenty of free space while others had practically no space available. Some had 486 processors while others were Pentiums. The point is that the network was non-homogenous and there was no documentation to help sort out how each machine was configured. To make matters worse the IT team was competent but under funded. There was no money to send the team to SMS training let alone money to purchase SMS licenses.
One crucial component of this system was a database server. Our team of administrators needed a reliable way of generating an accurate and up-to-date list of attributes regarding the machines. Attributes such as hard drive sizes (physical and available), amounts of ram, pagefile size, processor speed and service pack level just to name a few. A database server was installed to maintain this information.
This script will setup a machine so that it is ready to use the management system. This script will: Gather information about the computer, processor and operating system.
Gather information about each drive.
Update a database with the gathered information.
This script requires the following extensions: Win32::ODBC
Win32::AdminMisc
# OS.PL# ----------# This is a management system script designed to discover # information about both the computer and OS. Once the# information has been obtained it is then set to a database# where it is stored.## This script assumes that the database has 2 tables:# 1) Computer:# ID int(), primary key, autoincrimenting# Name char# Processor char# Speed int# OS char# ServicePack char# Version float# Build int# MMX int (used as a boolean or bit)# Ram int# PageFile int## 2) Drives:# ID int, primary key, autoincrimenting# Size int# Free int# Drive char # Type char# Computer int# # Dave Roth# Roth Consulting# Win32::AdminMisc;use Win32::ODBC;$DSN = "Machines";$Machine = Win32::NodeName();%DriveType = ( &DRIVE_REMOTE => "remote", &DRIVE_REMOVABLE => "removable", &DRIVE_FIXED => "fixed", &DRIVE_CDROM => "cdrom", &DRIVE_RAMDISK => "ramdisk",);# Get memory info...%Mem = Win32::AdminMisc::GetMemoryInfo();# Get processor info...%Processor = Win32::AdminMisc::GetProcessorInfo();# Get OS info then fix the servicepack and platform values...%OS = Win32::AdminMisc::GetWinVersion();( $OSServicePack ) = ( $OSCSD = /(\d*?)$/ );$OSPlatform = s/win32_//i;# Get drive info...foreach $Drive ( Win32::AdminMisc::GetDrives() ) my $Type = Win32::AdminMisc::GetDriveType( $Drive ); if( DRIVE_REMOTE != $Type ) $Drives$Drive = size => 0, free => 0 ; if( DRIVE_FIXED == $Type ) ($Drives$Drive->size, $Drives$Drive->free ) = Win32::AdminMisc::GetDriveSpace( $Drive ); $Drives$Drive->type = $Type; if( DRIVE_REMOVABLE != $Type && DRIVE_CDROM != $Type ) my %Volume = Win32::AdminMisc::GetVolumeInfo( $Drive ); $Drives$Drive->filesystem = $VolumeFileSystemName; if( $db = new Win32::ODBC( $DSN ) ) $Id = GetDbId( $db, $Machine ); if( ! $Id ) $db->Sql( "INSERT INTO Computer (Name) VALUES ('$Machine')" ); $Id = GetDbId( $db, $Machine ); if( $Id ) $Update = "UPDATE Computer SET " . " ServicePack = '$OSServicePack', " . " Version = $OSMajor.$OSMinor, " . " OS = '$OSPlatform', " . " Build = $OSBuild, " . " Processor = '$ProcessorProcessorType', " . " Speed = $ProcessorWin32ProcessorSpeed, " . " MMX = $ProcessorMMX, " . " Ram = $MemRAMTotal, " . " PageFile = $MemPageTotal " . "WHERE ID = $Id"; if( $db->Sql( $Update ) ) print "Could not update computer info: " . $db->Error() . "\n"; if( $db->Sql( "DELETE Drives WHERE Computer=$Id" ) ) print "Could not delete drive info: " . $db->Error() . "\n"; foreach $Drive ( sort( keys( %Drives ) ) ) my $Insert = "INSERT INTO Drives " . "(Drive,Size,Free,Type,Computer) " . "VALUES ( '$Drive', $Drives$Drive->size, " . "$Drives$Drive->free, '$DriveType$Drives$Drive->type', " . "$Id )"; if( $db->Sql( $Insert ) ) print "Could not insert drive $Drive info: " . $db->Error() . "\n"; $db->Close();else print "Unable to connect to the database: " . Win32::ODBC::Error() . "\n";print "Finished.\n";sub GetDbId my( $db, $Computer ) = @_; my( %Data ); if( ! $db->Sql( "SELECT DISTINCT * FROM Computer WHERE Name like '$Computer' " ) ) if( $db->FetchRow() ) %Data = $db->DataHash( 'ID' ); return( $DataID ); 7.5 Script 5: A script to report event log warnings and errors. This script will setup a machine so that it is ready to use the management system. This script will: 2ff7e9595c
Comments