Subject: Re: NT 4 Server Dump -- attached
Hi!
I just like to say thanks too ALL from this list, the braindumps really helped me to pass my Workstation and Server (864 for WS and 909 for Server) exams. I am not going to write about the Workstation exam as I got almost all the questions that are already under the 073 braindump.
Server exam was a toughy.... I don't know if Microsoft is getting wise but I got a quite a few questions from the brain dump but with nasty twists:
95% of the exam was RAS, Disk stuff, Netware
Nothing on IIS,PWS, groups, trusts, MAC's, UNIX
So here goes what I can remember, that differs from the rest of the stuff on the list:
1. A really complex worded question basically asking how many disks are required for stripe with parity,( but they made you think they were talking about disk duplexing) & the answers included how many disk controlers,physical & logical drives were a minimum requirement. (I think 1 disk controller only is really needed & min 3 drvs)
2. Question on manditory profile, what happens when the server goes down (I said they can still logon with the default profile)
3. 3 ARC paths, make sure you know how to read them, & how to update a boot.ini file for mirror sets & what to do with it once you got it.
4. Making Installation disk for NT 4 (the qu dosn't say more than that about the PC in Question) do you:
A Boot from DOS & run winnt from CD (no mention of /ox anywhere)
B Boot from DOS & run winnt32 from CD (no mention of /ox anywhere)
C Boot from NT & run winnt from CD (no mention of /ox anywhere)
A Boot from NT & run winnt from hdd of another server (no mention of /ox anywhere)
I can't think of more exact questions but here is a summary of things I had to know for the exam:
- If you want to manage/create shares do it from Server Manager
- If you want to remotely manage file & folder permissions do it from NT Explorer (take my word for it this is correct, several of the brain dumps say server manager -- ITS WRONG), you can also specify the printer you want to implement security on through here.
- Moving 100MB file across network by few users, network slow --- need to install a second network card with a different IP & on a different subnet, enable Ip routing. Put the offenders on the new subnet
- Know that you first create a Domain Backup/Restore Group (which ever in qu), then you add the poor succer who has to do it to the global group, than you add the global to the local backup/restore group on each server.
- Know that Backup OPs Rights are backup & logon locally
- Know that Restore OPs Rights are restore, shutdown system & logon locally
- Import Server -- NT Servers & Workstation, not 95
- Export Server -- NT Servers ONLY
- Know PDC/BDC promotions
- Know Mirror Sets- need to break it first, then reasign the drive letter (if need be), delete failed disk, reboot with FT recovery disk (need to change ARC path in boot.ini)
- Stripe Sets - know that if one fails, need to select new drive of same/bigger space (if its physical disk you are adding then need to restart the PC), then type Regenerate in FT Menu of Disk Admin
- Remember that System Policy, manditory profiles need to be replicated to the BDC, not automatic
NWLinks - automatically installed with GSNW
- enough to connect to Cl/Se apps on netware
- enough for netware Cl to connect to Cl/Se apps that support netBIOS on NT
- RPC, Winsock
GSNW - need for migration + NTGateway group on Netware server with the right permissions
- installed from CD, network
- share netware dirs from here
- activate gw for volumes/printing queues
- form, banner notify changed here
- its a bridge between SMB & NCP
- All needed for SAP to work is to spec internal network numbers
- Netware VLM not supported by NT
- logon scripts run once connected to netware server
- new drive letters should be assigned to netware volumes
- if 2 IPX PC not talking probably wrong frame type, know that 802.2 is default & that if you want multiple frames connection need to configure it manually
- TCP/IP on server can use Winsock
- RAS connections can be logged if enable device logginf in registry
- can't be SLIP server, but can be SLIP client & as such connect to UNIX SLIP servers
- Grant premissions to use RAS to cl in UMD and in Ras Admin, altough Microsoft only accepts the UMD answer
- If have clients that need diffrent encryption/security features, configure 2 ports & make the clients dial in to the one that is appropriate for them
- RAS scripts - switch.inf
- use modem.inf to set configurations for unsupported modems
- PPP problems activate PPP.log
- Net Beui installed by default with it
- pool of IP's over PPP - make the CL have the same networkid as the RAS server, but different host.
AUTODIAL - maps network addresses to RAS phonebook entries
TAPI - remove it by reinstalling NT
- using workstation to monitor several servers, things slow, increase the time collecting server data
- use EXPORT or save log as to save data in PM
- enable SNMP for TCP/IP tarping on the PC to be monitored
- CP, networks, memory setting
- monitor paging counters
- excessive paging - add RAM, distribute paging file over disks, remove it of the boot partition (unless need it for fault tolerance)
- excessive paging - means disk is frag, apps start slower, I/O of disk access decreases (note here Microsoft tries to confuse you by putting network access in their answer)
- increase hdd performance - disk stripping, rearange data to balance the disk (defrag), second controler card, faster hdd