70-215 QOFD 22/06/2004

Discussion in 'Windows Server 2003 / 2008 / 2012 / 2016' started by AJ, Jun 22, 2004.

  1. AJ

    AJ 01000001 01100100 01101101 01101001 01101110 Administrator

    6,897
    182
    221
    You have decided to configure a Windows 2000 Terminal Server in application mode. To support the Windows 2000 Terminal Server, you configure a stand-alone Windows 2000 Advanced Server in the following configuration:
    -- 2 GByte RAM.
    -- Dual processors.
    -- Fast SCSI using NTFS as the File System.
    -- High-performance network adaptor.

    All the hardwares are listed in the HCL. After setting up the Windows 2000 Advanced Server and install the Windows 2000 Terminal Server. You follow the guidelines in the Microsoft Office Website to install Microsoft Office 2000. All users can connect to the Terminal Server and use the Microsoft Office application. However, after about three months, none of the users can access the Terminal Server any more. What could be a likely reason that users can not gain access to the Terminal Server again? Choose the correct answer.


    A) You need to activate the Terminal Server service.

    B) You should install Terminal Server service in Application Server mode.

    C) You should install Terminal Server service in Remote Administration mode.

    D) You need to install Terminal Services Licensing Server in the network.
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Breathing in and out, but not out and in, that's just wrong
  2. nugget
    Honorary Member

    nugget Junior toady

    7,796
    71
    224
    I'll take a stab at D for today's crash and burn lesson thanks AJ.
     
    Certifications: A+ | Network+ | Security+ | MCP (270,271,272,290,620) | MCDST | MCTS:Vista
    WIP: MCSA, 70-622,680,685
  3. tripwire45
    Honorary Member

    tripwire45 Zettabyte Poster

    13,493
    180
    287
    I'm not even going to try to look this one up. First of all, it's too early here (a tad after 4:30 a.m.) and only D makes any sort of sense. ABC would all have to have been set up from the first day. Often, an MS product will be accessable for some period of time, giving the administrator/owner time to license the thing and activate it with MS. I say, the 90 day window passed and TS Licensing Server needs to be installed. Official answer for me: D.

    Do I smell smoke? :eek:
     
    Certifications: A+ and Network+
  4. Nelix
    Honorary Member

    Nelix Gigabyte Poster

    1,416
    3
    82
    D it is for me
     
    Certifications: A+, 70-210, 70-290, 70-291, 74-409, 70-410, 70-411, 70-337, 70-347
    WIP: 70-346
  5. Jakamoko
    Honorary Member

    Jakamoko On the move again ...

    9,924
    74
    229
    Bunk over on the Bandwagon, Derek - I'll take d as well.
     
    Certifications: MCP, A+, Network+
    WIP: Clarity
  6. AJ

    AJ 01000001 01100100 01101101 01101001 01101110 Administrator

    6,897
    182
    221
    Correct answer is: D

    Explanation: To deploy Terminal Services, you enable the Terminal Services component either during installation of Windows 2000, or afterward by using the Windows Components wizard. You may enable Terminal Services in one of two modes: Application Server or Remote Administration. Remote Administration does not require licensing and only allows two connections.
    You can install Terminal Services Licensing with Terminal Services or you can install it by itself on a different computer. When you install Terminal Services licensing, you specify whether the license server will serve the domain or workgroup, or the site. Choosing enterprise licensing allows any Terminal server in the same physical site to use the license server, even across domain boundaries.

    On installation, the Terminal server will seek a license server. Terminal Services will operate for 90 days without a license server. After 90 days, the Terminal server will not allow unlicensed clients to connect unless a license server is available to supply the client with a CAL.

    Microsoft Link
     
    Certifications: MCSE, MCSA (messaging), ITIL Foundation v3
    WIP: Breathing in and out, but not out and in, that's just wrong

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.