SXe on Windows 2000 Installing Windows 2000 Server, Progress, and SXe

Windows 2000 Systems  Windows vs. Unix Windows offers:  Friendly User Interface  Less Specialized Administration  Less Expensive and Less Complex Windows brings with it:  Friendly User Interface  Easier to Break for Inexperienced Administrators  Untested on Higher Numbers of Users (50+)  Unstable?

Why Windows Fails Windows systems fail most often because of culture, not from the technology.

Why Windows Fails  Circumstances that make Windows Fail Treated Like Workstations Too Easy to Access and Use Poor Change Control Not Patched Properly Inexperienced Administrators Browsing the Internet Downloading Cool Things Playing Games

How to Make Windows Work  Microsoft’s Answer MOF  Wizards Auto updates Certifications  NxTrend’s Answer Education of MA’s Education of Customers Emphasis on a cultural shift in the approach to Windows 2000 Servers.

Best Practices for a Stable MS System 1. Culture 2. Hardware 3. OS 4. Recovery

Best Practices for a Stable MS System  Culture It is a Server Carefully Dedicated Function Combine functions in tested configurations only Control Changes (Change Management) Journaling Testing

Best Practices for a Stable MS System  Hardware Use Server Class Hardware Physical Security Redundancy  RAID  Processors  Network Card / Switches  UPS / Power Supplies  Redundant Servers / Clustering

Best Practices for a Stable MS System  OS Fresh Installs, not OEM Installs or Existing OS’s OS Standards Patches  Hotfixes  Critical Updates  Security Updates  Service Packs Standard Software Virus Protection Security  User level  Physical  Patches

Best Practices for a Stable MS System  Recovery System Diagrams and Inventory Warranty Active and Adequate Backups Running and TESTED Recovery Plan  Network Outage  Hardware Failure  Full Rebuild Times Contact Lists Automated Monitoring Engineering Assessment

Windows 2000 Stability Change in approach to Windows Servers The Key to SXe on 2000

SXe Hardware Requirements  RAM 1.5G for G for 50  Processors 2 Pentium III processors for 50 people  Network 20k of committed bandwidth per terminal client  Disks RAID  RAID 1 for OS  RAID 10 for Data I/O 4G OS and 9G Data as the minimum.

OS Installation Start OS Installation

OS Installation Finish OS Installation

Progress Installation Install Progress

Progress Installation Progress License Codes Client Networking X8GRS 6QETM 34G?P Enterprise DB ?ZAS9 XPETM K4CYJ Progress Appserver X?GR9 6PE2D 24C?3 ProVISION X8ARS XPG2M 2MCYP

SXe Installation GUI SXe Installation

SXe Installation CHUI SXe Installation

SXe Application Setup and Test  Enter license code Re-login

SXe Application Setup and Test  CONV (Conversions) Re-login  Set up printers SASP (Set up printers) SASC (Set print directory) SARSE and SAPJ (Check jobs and Report Manager)  SASO (Setup System Security)

Old SXe Function  Terminal Server Client Full Progress install Full SX code install Preferred deployment method  Full Push Client Full Progress install Full SX code install  Code Server Full Progress install Full SX code install Code Bundle  Network Client Little Progress code No SX code Available for reverse compatibility only

SXe Application Function  Windows 2000 Server Components SX Database SX Staging Server Terminal Services  Configuration No MARC Separate directories for backend database & staging environment Smaller user configurations

SXe Administration  Staging Environment Root dir.e:\NxT{env} Client dir.e:\NxT\Client or \\sysname\INS$  Database Environment Root dir.e:\Sxe{env} Database e:\Sxe\db\nxt.db Code dire:\Sxe\rd\src Librarye:\Sxe\rd\lib

SXe Administration  Location of Scripts E:\sxe\rd\bin  Location of Logs E:\sxe\rd\logs E:\sxe\rd\tmp (report logs)

SXe Administration  Starting Stopping DB and components Starting the Database  Start Admin Server Service  E:\sxe\rd\bin\nxtall.start.bat Stopping the Database  E:\sxe\rd\bin\nxtall.stop.bat  Stop Admin Server Service Starting Report Mangers  E:\sxe\rd\bin\rptmgr.start.bat Stopping Report Managers  E:\sxe\rd\bin\rptmgr.stop.bat

SXe Administration  Schedule Backups T-F Daily S Full  The Full Backup Rdclean  Configuring Backups Backup.data.full.bat Backup.data.daily.bat Backup.bks Nxt.env.bat

SXe Administration  Restores Same as Unix Take down DB DB Backup files should be in the backup directory Run Restore.db.bat

SXe Administration  Using Terminal Services What is it? Terminal Services and Temporary Files  Citrix

SXe on Windows 2000  Future Future of 3 rd Party Apps  Clippership  eSales  FRx Future Functionality  AI  Rdclean  Report Manager Cleanup  Dump and Loads