Server 2003 Setup

This topic contains 0 replies, has 1 voice, and was last updated by  Webmaster 2 years ago.

  • Author
  • #2220


    Applies To:Windows Server 2003 with SP1
    What does Setup do?
    Setup is the program that installs and configures the operating system on your computer.When you originally install Windows
    Server 2003,Setup installs and configures the operating system to work properly with thecomputer.
    Often,any program that is used to install and configuresoftware programs is called Setup. However, in Windows Server 2003,
    therearetwo different programs that install and configure programs after the operating system is operational.When Windows
    Server 2003 Service Pack 1 (SP1) or any other software updateis installed on Windows Server 2003, the PackageInstaller for
    Windows updates and changes theexisting installation of Windows Server 2003. If an application, such as Microsoft Office, is
    installed,configured, or upgraded, then Windows Installer is the program that is responsiblefor that task.
    Who does this feature apply to?
    All users and administrators who install or deploy Windows Server 2003 Service Pack 1 should becomefamiliar with the
    changes in this feature.
    What new functionality is added to this feature in Windows Server 2003 Service Pack 1?
    Package Installer for Windows
    Detailed description
    The PackageInstaller for Windows (Update.exe) installs Windows Server 2003 Service Pack 1.This is different installation
    technology from what is used to install thecomplete operating system.For a complete discussion of the PackageInstaller, see
    “The PackageInstaller for Windows and Windows Components” on the Microsoft Web siteat
    Changes in PackageInstaller in Windows Server 2003 Service Pack 1 include:
    Command lineswitches
    Microsoft has moved to a standard for Installer switches, which will beavailablelater this year.Thereare no new
    switches to replacethe/D and /S switch functions; the old switches arestill valid.Thefollowing table describes the
    former, new,and legacy switches for use with the PackageInstaller.
    Old Switch New
    None /Uninstall Used to automateremoval of a service pack.
    /? /Help Displays help text.
    /D:FolderName No change For service pack installations, backs up files to thespecified folder.
    None /ER Enables extended return codes. (For moreinformation aboutextended return
    codes, see AppendixF in the”The PackageInstaller for Windows and Windows
    Components” white paper.)
    /F /F Forces other applications to close when thecomputer restarts after theinstallation.
    None /ForcerestartForces restartafter installation finishes.
    /L /L Lists installed hotfixes (Windows updates only).
    /N /N Does not back up files for removing theservice pack or hotfix. In Add or Remove
    Programs, thereis no Remove button for the hotfix, so it cannot be uninstalled.
    /O /O Overwrites OEM files without prompting.
    /Q /Quiet Uses quiet mode, which is thesameas unattended mode,except that the user
    interfaceis hidden. No prompts appear during theinstallation.
    /Intergrate:FolderName No change Combines the operating system image with Windows Server 2003 Service Pack 1
    in a shared distribution folder for an integrated installation.When using this
    switch, typethe name of theshared distribution folder after thecolon.
    /U /Passive Uses unattended setup mode. Only critical errors and a progress bar appear during
    /Z /Norestart Does not restart thecomputer after theinstallation finishes.
    /O command lineswitch
    The/O command lineswitch prevents Update.exefrom performing an exhaustivesearch for original equipment
    manufacturer (OEM) supplied files, such as video drivers. Usethis switch only if you want to overwriteall files supplied
    by the OEM on your system. By default, OEM files are not overwritten.
    Do notapply updates during installation
    If you arerunning in an environment that uses a utility to scan and apply updates or security updates automatically, the
    utility may conflict with theservice pack installation.This conflict can occur when a service pack is in the process of
    installation or uninstallation and has not fully completed dueto the need to restartand then run the post-installation
    processes. If the update utility attempts to apply updates to thesystem at shutdown or restart, it may attempt to install
    updates prior to completing theservice pack installation, which may result in thecomputer being left in an unusable
    Improved recovery following installation failure
    In theevent that thereis a failureto completetheservice pack installation, in most cases,automatic recovery will occur.
    For example, if power failure occurs during thelatter parts of installation, when you restart thecomputer, theservice
    pack uninstall procedureautomatically starts and rolls back all thechanges that were made during theservice pack
    Antivirus software
    Although antivirus softwareis a critical factor in keeping a computer secure, it can affect the overall timerequired to
    install a service pack. Disabling your antivirus software during installation of theservice pack could reducethe
    installation time by up to 20%. If you decideto disabletheantivirus software, beaware of therisks involved and besure
    to enableitafter theservice pack is installed.
    What works differently?
    A new prerequisiteto service pack installation is a check as to whether thefileSpUpdSvc.inf exists on thecomputer.This file
    will be present only if Windows Server 2003 Service Pack 1 was previously installed on thecomputer. If this fileis found on
    your computer by theSP1 installer you will be presented with the message:
    Setup has detected an .INFfile from the beta installation that will prevent successful installation of the Service
    Pack. Please see Deleting SpUpdSvc.inf before install in the Readme document accompanying this release for
    details on how to unblock the Windows Server 2003 Service Pack 1 installation.
    Thereis also a prerequisitethat blocks installation of theservice pack if the Distributed Transaction Coordinator (also know as
    MSDTC) servicestatus is Disabled and Stopped at thetime of installation. In this casetheinstallation will stop and you will be
    presented with the message:
    Setup has detected that the Distributed Transaction Coordinator (MSDTC) service is disabled. The MSDTC service is
    required for the successful installation of Microsoft ® Windows Server™ 2003 Service Pack 1 (SP1). Please enable
    the MSDTC service, and then restart the installation of Windows Server 2003 SP1.For more information about
    enabling the MSDTC service,contact your network administrator.
    How do I resolve these issues?
    To manually delete the SPUpdSvc.INFfile
    1. LocatetheSPUpdSvc.INF filein the Windows directory.
    2. Renamethefilefrom SPUpdSvc.INF to SPUpdSvc.BAK.
    3. Restartyour computer.
    4. Attempt to install theservice pack
    5. If theservice pack successfully installs, deletetheSPUpdSvc.BAK file.
    To enable the MSDTC service
    1. Open a command prompt.
    2. At thecommand prompt, typethefollowing command:
    sc config MSDTC start=demand
    This will change the status of the MSDTC service from disabled to enabled, but will not start the service.

You must be logged in to reply to this topic.