• Chapter 1. Installing and Configuring Windows Server 2003
  • software development Company Server 2003
  • Chapter 1. Installing and Configuring Windows Server 2003
  • New Features in Windows Server 2003
  • Best Practices
  • Moving Forward
  • Version Comparisons
  • Hardware Recommendations
  • Installation Checklist
  • Functional Overview of Windows Server 2003 Setup
  • Installing Windows Server 2003
  • Post Setup Configurations
  • Functional Description of the Windows Server 2003 Boot Process
  • Correcting Common Setup Problems
  • Chapter 2. Performing Upgrades and Automated Installations
  • New Features in Windows Server 2003
  • NT4 Upgrade Functional Overview
  • Upgrading an NT4 or Windows 2000 Server
  • Automating Windows Server 2003 Deployments
  • Moving Forward
  • Chapter 3. Adding Hardware
  • New Features in Windows Server 2003
  • Functional Description of Windows Server 2003 Architecture
  • Overview of Windows Server 2003 Plug and Play
  • Installing and Configuring Devices
  • Troubleshooting New Devices
  • Moving Forward
  • Chapter 4. Managing NetBIOS Name Resolution
  • New Features in Windows Server 2003
  • Moving Forward
  • Overview of Windows Server 2003 Networking
  • Name Resolution and Network Services
  • Network Diagnostic Utilities
  • Resolving NetBIOS Names Using Broadcasts
  • Resolving NetBIOS Names Using Lmhosts
  • Resolving NetBIOS Names Using WINS
  • Managing WINS
  • Disabling NetBIOS-over-TCP/IP Name Resolution
  • Chapter 5. Managing DNS
  • New Features in Windows Server 2003
  • Configuring a Caching-Only Server
  • Configuring a DNS Server to Use a Forwarder
  • Managing Dynamic DNS
  • Configuring Advanced DNS Server Parameters
  • Examining Zones with Nslookup
  • Command-Line Management of DNS
  • Configuring DHCP to Support DNS
  • Moving Forward
  • Overview of DNS Domain Structure
  • Functional Description of DNS Query Handling
  • Designing DNS Domains
  • Active Directory Integration
  • Configuring DNS Clients
  • Installing and Configuring DNS Servers
  • Configuring Secondary DNS Servers
  • Integrating DNS Zones into Active Directory
  • Chapter 6. Understanding Active Directory Services
  • New Features in Windows Server 2003
  • Active Directory Support Files
  • Active Directory Utilities
  • Bulk Imports and Exports
  • Moving Forward
  • Limitations of Classic NT Security
  • Directory Service Components
  • Brief History of Directory Services
  • X.500 Overview
  • LDAP Information Model
  • LDAP Namespace Structure
  • Active Directory Namespace Structure
  • Active Directory Schema
  • Chapter 7. Managing Active Directory Replication
  • New Features in Windows Server 2003
  • Replication Overview
  • Detailed Replication Transaction Descriptions
  • Designing Site Architectures
  • Configuring Inter-site Replication
  • Controlling Replication Parameters
  • Special Replication Operations
  • Troubleshooting Replication Problems
  • Moving Forward
  • Chapter 8. Designing Windows Server 2003 Domains
  • New Features in Windows Server 2003
  • Design Objectives
  • DNS and Active Directory Namespaces
  • Domain Design Strategies
  • Strategies for OU Design
  • Flexible Single Master Operations
  • Domain Controller Placement
  • Moving Forward
  • Chapter 9. Deploying Windows Server 2003 Domains
  • New Features in Windows Server 2003
  • Preparing for an NT Domain Upgrade
  • In-Place Upgrade of an NT4 Domain
  • In-Place Upgrade of a Windows 2000 Forest
  • Migrating from NT and Windows 2000 Domains to Windows Server 2003
  • Additional Domain Operations
  • Moving Forward
  • Chapter 10. Active Directory Maintenance
  • New Features in Windows Server 2003
  • Loss of a DNS Server
  • Loss of a Domain Controller
  • Loss of Key Replication Components
  • Backing Up the Directory
  • Performing Directory Maintenance
  • Moving Forward
  • Chapter 11. Understanding Network Access Security and Kerberos
  • New Features in Windows Server 2003
  • Windows Server 2003 Security Architecture
  • Security Components
  • Password Security
  • Authentication
  • Analysis of Kerberos Transactions
  • MITv5 Kerberos Interoperability
  • Security Auditing
  • Moving Forward
  • Chapter 12. Managing Group Policies
  • New Features in Windows Server 2003
  • Group Policy Operational Overview
  • Managing Individual Group Policy Types
  • Moving Forward
  • Chapter 13. Managing Active Directory Security
  • New Features in Windows Server 2003
  • Overview of Active Directory Security
  • Using Groups to Manage Active Directory Objects
  • Service Accounts
  • Using the Secondary Logon Service and RunAs
  • Using WMI for Active Directory Event Notification
  • Moving Forward
  • Chapter 14. Configuring Data Storage
  • New Features in Windows Server 2003
  • Functional Description of Windows Server 2003 Data Storage
  • Performing Disk Operations on IA32 Systems
  • Recovering Failed Fault Tolerant Disks
  • Working with GPT Disks
  • Moving Forward
  • Chapter 15. Managing File Systems
  • New Features in Windows Server 2003
  • Overview of Windows Server 2003 File Systems
  • NTFS Attributes
  • Link Tracking Service
  • Reparse Points
  • File System Recovery and Fault Tolerance
  • Quotas
  • File System Operations
  • Moving Forward
  • Chapter 16. Managing Shared Resources
  • New Features in Windows Server 2003
  • Functional Description of Windows Resource Sharing
  • Configuring File Sharing
  • Connecting to Shared Folders
  • Resource Sharing Using the Distributed File System (Dfs)
  • Printer Sharing
  • Configuring Windows Server 2003 Clients to Print
  • Managing Print Services
  • Moving Forward
  • Chapter 17. Managing File Encryption
  • New Features in Windows Server 2003
  • File Encryption Functional Description
  • Certificate Management
  • Encrypted File Recovery
  • Encrypting Server-Based Files
  • EFS File Transactions and WebDAV
  • Special EFS Guidelines
  • EFS Procedures
  • Moving Forward
  • Chapter 18. Managing a Public Key Infrastructure
  • New Features in Windows Server 2003
  • Moving Forward
  • PKI Goals
  • Cryptographic Elements in Windows Server 2003
  • Public/Private Key Services
  • Certificates
  • Certification Authorities
  • Certificate Enrollment
  • Key Archival and Recovery
  • Command-Line PKI Tools
  • Chapter 19. Managing the User Operating Environment
  • New Features in Windows Server 2003
  • Side-by-Side Assemblies
  • User State Migration
  • Managing Folder Redirection
  • Creating and Managing Home Directories
  • Managing Offline Files
  • Managing Servers via Remote Desktop
  • Moving Forward
  • Chapter 20. Managing Remote Access and Internet Routing
  • New Features in Windows Server 2003
  • Configuring a Network Bridge
  • Configuring Virtual Private Network Connections
  • Configuring Internet Authentication Services (IAS)
  • Moving Forward
  • Functional Description of WAN Device Support
  • PPP Authentication
  • NT4 RAS Servers and Active Directory Domains
  • Deploying Smart Cards for Remote Access
  • Installing and Configuring Modems
  • Configuring a Remote Access Server
  • Configuring a Demand-Dial Router
  • Configuring an Internet Gateway Using NAT
  • Chapter 21. Recovering from System Failures
  • New Features in Windows Server 2003
  • Functional Description Ntbackup
  • Backup and Restore Operations
  • Recovering from Blue Screen Stops
  • Using Emergency Management Services (EMS)
  • Using Safe Mode
  • Restoring Functionality with the Last Known Good Configuration
  • Recovery Console
  • Moving Forward
  • Who Should Read This Book
  • Who This Book Is Not For
  • Conventions
  • Acknowledgments
  • About the Author
  • About the Technical Reviewers
  • Index
  • Index A
  • Index B
  • Index C
  • Index D
  • Index E
  • Index F
  • Index G
  • Index H
  • Index I
  • Index J
  • Index K
  • Index L
  • Index M
  • Index N
  • Index O
  • Index P
  • Index Q
  • Index R
  • Index S
  • Index SYMBOL
  • Index T
  • Index U
  • Index V
  • Index W
  • Index X
  • Index Z
  • Preface
  • Previous Section Next Section

    Using the Secondary Logon Service and RunAs

    The examples throughout this chapter show local administrators going about their daily work while logged on using their Administrative accounts. This is generally not a good practice. Quite a few bad things can happen when logged on with full admin permissions. Viruses can get activated and make sweeping changes. Innocent mistakes can cause serious damage. Leaving your workstation open gives access to nefarious users. The list goes on and on.

    Windows Server 2003 comes with a Secondary Logon Service (SLS) that makes it possible to log on as a standard user and then launch applications with alternative credentials to perform administrative tasks. This is philosophically similar to the su (superuser) command in UNIX, but is implemented somewhat differently.

    The Secondary Logon Service is installed by default and starts at boot time. The service is hosted by Services.exe. The code is contained in Seclogon.dll.

    RunAs Syntax

    One of the easiest ways to use SLS is to open a command console window and launch an application using the RunAs command. Here is the syntax:

    runas /u:administrator@company.com executable_name
    runas /u:company\administrator executable_name

    You can open a console in another security context by entering cmd as the executable name. You are prompted for a password and a second console window opens with a title bar that shows the alternate name you used. Applications launched from this console retain the alternate security context. For example, you can launch AD Users and Computers by typing dsa.msc. The console opens with your admin credentials so you can perform privileged operations.

    If you prefer using the Explorer shell, you can specify alternate credentials by holding down the Shift key then right-clicking the icon for an executable or its shortcut. This adds a RUNAS option to the flyout menu. Selecting this option opens a RunAs window where you can enter the alternate credentials. Figure 13.14 shows an example.

    Figure 13.14. RunAs window when launching from the Explorer shell.


    RunAs and Profiles

    By default, RunAs opens an application with the profile of the user specified by the /u: switch. This differs from Windows 2000, which uses the Default User profile unless told otherwise. Opening the user's own profile ensures that applications making calls to standard shell elements such as My Documents open the user's elements, not the Default User elements.

    There is a /noprofile switch that loads the Default User profile rather than the user's profile. This speeds up an application launch if the designated user has no local profile on the machine, but can cause unexpected behavior if an application calls standard shell elements. Watch where you put your documents if you use the /noprofile switch.

    RunAs Switches

    The RunAs command has several other useful switches:

    • /env. Uses the current environment variables rather than the variables for the alternate user. This helps troubleshooting application troubles at a local user's desktop.

    • /savecred. Opens the window with the specified user's saved credentials, if any. This option helps when you are on a laptop that is not connected to the network and you need to launch a console using an Admin account with locally cached credentials.

    • /smartcard. Uses smart card authentication instead of standard Kerberos or NTLMv2. This is a new feature in Windows Server 2003 that greatly simplifies network administration in organizations that use smart cards for logon authentication.

    • /netonly. Uses the same credentials as those used to log on to the desktop. This helps avoid problems when running applications across the network using different credentials than those used to create the connection.

    If you initiate a network connection from the console, you can access the connection through the console but not through the shell. For example, you can map a drive to an admin share at another server while you are at elevated permissions by entering net use * \\server_name.company.com\c$. The connection succeeds because you have sufficient credentials. If you go to a My Computer window and look at the drive you just mapped, however, it shows an X and denies access if you try to use it because the shell is still running with your logon permissions.

    Use caution when launching interfaces that tie directly to the Explorer shell from a command console using RunAs. For example, if I'm working at a console prompt and I want to get a graphical view of the folder contents, I enter start. (start followed by a dot) on the command line. This opens the My Computer view of the current folder in Explorer. If I do this from RunAs, the window opens but the underlying security context is the same as my logon account.

    If you want to run the shell at elevated permissions, too, you can shut down Explorer and then restart it using RunAs from the Task Manager. To do this, follow Procedure 13.6.

    Procedure 13.6 Starting Explorer Shell Using RunAs

    1. Open Task Manager by pressing Ctrl+Alt+Del and then clicking Task Manager.

    2. Select the Processes tab.

    3. Highlight Explorer and click End Process. Confirm when prompted.

    4. When Explorer shuts down, select File, Run from the Task Manager menu and start Explorer as follows:

      runas /u:administrator@company.com explorer.exe

    After Explorer opens, some components such as the status bar and System Tray continue to run in the original logon context and are therefore unavailable to Explorer.

      Previous Section Next Section