*For group permissions, the least restrictive right takes precedence, except No Access- which always overrides all others! When combining NTFS and share permissions, the least restrictive takes precedence for each kind (except No Access), when combining resulting NTFS and share permissions, the most restrictive wins.

*In User Manager for Domains you can:

*Mandatory profiles: change NTUSER.DAT to NTUSER.MAN.

*To create directory or printer share: set sharing, define share name, set permissions.

*All new directory shares have default rights of Full Access to Everyone.

*All new printer shares have Print access to Everyone, Full Control to Administrator and Power Users, and Manage Documents to to the owner.

*Attach to printer share: New Printer, Network Printer Server.

* Attach to directory share: Map Drive or Network Neighborhood.

*Each shared logical printer can be set to different priorities and access times.

* NT Workstation is NOT FAULT TOLERANT.

*Only primary partitions can be active: Select Mark Activefrom the Partition menu in Disk Administrator.

*Rules for Permissions on NTFS Move and Copy operations:

*Convert FAT to NTFS using convert.exe; HPFS is NOT supported in NT 4.

*Two Registry editors: REGEDIT.EXE (search features) and REGEDIT32.EXE (security features)

*Remember that BOOT files reside in the system partition, and SYSTEM files reside in the BOOT partition.

*The most important components of the NT boot process:

• BOOT.INI Describes NT boot defaults, settings, OS location, & menu selections. It resides in the root directory of the system partition. This is a required file for a bootable floppy.
• NTDETECT.COM Hardware detection: reads device and config info before NT boots. It resides in the root directory of the system partition. This is a required file for a bootable floppy.
• NTLDR Loads NT or other designated OS; relinquishes control after loading completes. It resides in the root directory of the system partition. This is a required file for a bootable floppy
• BOOTSECT.DOS Used if NTLDR permits booting to another MS OS [i.e.DOS, Win95]. Resides in the root directory of the system partition.
• NTOSKRNL.EXE Includes all basic capabilities and items necessary to establish runtime environment. Resides in \Winnt_root\system32 on boot partition.
• OSLOADER.EXE Provides info and services equal to NTDETECT.COM, bootsect.dos and NTLDR on PCs. Resides in RISC boot PROM area.
• NTBOOTDD.SYS Used when system or boot SCSI drive has BIOS disabled. Replaces BIOS functions with software driver. resides in root directory of system partition.

IV Connectivity

*RAS only supports PPP clients (not SLIP).

*Multilink must be established at both ends.

*RAS encryption: clear text (CHAP, DES, PAP, SPAP) or MS-encrypted (MS-CHAP).

*Access methods: UNC, Network Neighborhood, Map Share.

*Using NT Workstation as a client for a NetWare server: NW Link, CSNW.

*Peer Web Services offers offers Web, FTP and Gopher info services.

V Monotoring & Optimization

*Isolate, identify and solve a performance related problem.

*Too little RAM= high rate of memory paging.

*Processor: %Processor Time should remain below a constant level of 80.

*Memory: %DiskTime should be less than 10 percent of Processor: %Processor Time.

*LogicalDisk and PhysicalDisk counters will read 0 until enabled by diskperf -y.

*Windows NT Diagostics or WINMSD can be used to view computer details not alter them.

VI Troubleshooting

*The ERD (Emergency Repair Disk) is created by rdisk /s

*The ERD and 3 setup floppies can be used to repair boot problems: reboot from setup floppies and select R from menu.

*Dr Watson saves memory dumps for failed or crashed applications. To access Dr Watson run DRWTSN32 from Start/Run.

*Starting and stopping the spooler service will often eliminate Printer spool problems.

*Last known Good Configuration returns system to state of last successful logon, accessed during bootup by pressing spacebar [and L] when prompted.

Here is Mad's best of the braindumps, a compilation of the best Q&As fromBraindump Heaven. I have actually looked up most of these, but you are highly encouraged to do your own research, as these concepts are very tricky. If you have any comments or suggestions, drop me a line...good luck!

The following is a quote from the first Workstation BD:
"...Basically, I had about five questions that dealed [sic] with Workgroups. so- KNOW ALL ABOUT WORKGROUPS."
This sounds like good advice, so here are some workgroup basics:
A workgroup is a network of computers in which no single machine has control over the operation, activity or access to the entire network. Within a workgroup each machine is a peer, and has equal administrative control. Computers running WinNT WS/Server, WW, or Win95 can be configured to participate in either a domain or a workgroup. When setting up one of these computers for networking, you specify a computer name and a workgroup name. If the workgroup name matches a domain name, the computer name appears in the browse list for that domain. Remember that workgroups have:

• No central control
• Share-level security
• All user accounts must be created on each member

Workgroups are not recommended if you have more than 10 computers to tie together. NT WS can participate in a workgroup simply by defining the workgroup name in the right place. That place is the Identification tab of the network applet. Clicking the Change button on that tab causes the Identification Changes dialog box to appear. By selecting the Workgroup radio button and defining the name of the workgroup, you can transform the NT Workstation from a client in a domain to a peer in a workgroup.
You can reverse the process by simply redifining the domain in the same dialog box. Remember that for either change to take effect you'll have to reboot. Also a computer cannot be a member of both a workgroup and a domain simultaneously, but can be switched as needed...

Win16 apps and NTVDM

Q:"You want to run Win16 applications under NT Workstation. Where would these run by default?

A:In a single NT Virtual DOS Machine (NTVDM)."

Note: Tricky wording here from the MOC explanation: "By default, a single NTVDM starts when the first Win16 application is started, and then all Win16 applications run in that NTVDM"

Q:"You are running 16-bit Windows applications. The 3 applications share information. However one of these applications is faulty. How do you run the applications without effecting the other 16-bit Windows applications?
"
A: Run the 3 applications in the default configuration (which is shared memory) and the remainder in their own NTVDM’s

*NOTE: pg 302 Exam Cram "..it is possible to launch Win16 applications in their own individual instances of WOW(Windows-on-Windows)by modifying their PIFs or indicating this parameter from a Run instruction or command prompt. When multiple WOWs are in use, Clipboard data from one WOW app cannot be transferred into another WOW app because they no longer share resource space."

"Default where 16-bit applications are run.
A:In a single virtual DOS machine." [The first one, anyway!]

Q:"Three integrated 16-bit applications use shared memory blocks to communicate with each other. When one of the three integrated application halts, it stops the execution of all 16-bit, Microsoft Windows based application that are running. You want to continue using the three integrated applications but you want to prevent them from interfering with other 16-bit applications. How can you do this?

A:Run the three integrated applications in the default memory space. Run all other applications in separate memory spaces."

Mad Bonus: Here's HOW you start a Win16 app in its own NTVDM:

• At a command prompt: Type start/separate [path] application_executable.
• On the Start menu: ClickRun in the Open box, type [path] application_executable, and then select the Run in separate Memory Spacecheck box.
• From a shortcut: Create a shortcut, and on the Properties Shortcut tab, click the Run in separate Memory Spacecheck box.
• By file association: In Windows NT Explorer, on the View menu, click Options click the File Types tab, and then-click the Win16 application to be edited. Click Edit, and then double-click Open. Edit the opening line to include the /separate switch using the following syntax:
  cmd /c start /separate path\application_executable 1%

File association can also be done from the command prompt by using the ftype and assoc commands.

Q:"What happens when you run a 16-bit MS windows based application in its own memory space? (pick 2)

• A. Application runs at higher priority;
• B. Application uses less system memory;
• C. Application can be preemptively multitasked;
• D. Application cannot interfere with execution of other 16-bit windows based apps running at same time.

D is obviously correct. I researched C, it looks correct...

"The NTVDM process is multitasking: A thread in the process (in this case, a 16-bit Windows application) can run at the same time as threads of other processes if the computer has more than one processor. It is also preemptible: Threads can be interrupted and resumed to allow virtual multitasking on a single-processor computer." TechNet

Q:"How do you start the command "ntbackup /r /e" with low priority?

A: Start /low ntbackup /r /e"

*Ibid pg 288 "...[U]sers can launch applications with 4(/low) or 13(/high) priority and an administrator can launch with 24 (/realtime) priority. To launch an application with an alternate priority level, use the following syntax at a command prompt:

start [/low| /normal| /high| /realtime] application

NT offers two other priority controls...[A] slide control [that] is located on the performance tab in the System applet in the Control Panel...[And] [t]he second control is accessed via the Task Manager. By selecting any of the listed processes on the Process tab, you can change the priority to low, normal, high, or realtime via the Set Priority menu accessed through the right-click pop-up menu. ...By default, foreground apps have a priority of 10[max]. You can move the slider to set foregrounds with an additional priority level of 1 [middle tick] or 0[none]."

Elementary, my dear Watson
Let's take a close look at the good doctor, before he makes a house call. As we shall see this little application debugger is hardly documented at all in the MOC.

Q:"Which utility do you use to record memory dump following an application failure?

A: Dr. Watson"

B Windows NT System properties setting

Answer: A, B " [B looks wrong to me]

Note: Remember application crash dumps are done in Dr. Watson, system STOP errors and memory dumps are done in FAULTLOG on the startup/shutdown menu.

Ibid Pg 339 "...Dr Watson...detects application errors, diagnoses the error, and logs the diagnostic information...Data captured...is stored in the DRWTSN32.LOG file." Ibid Pg 70 "The System applet is used to alter environmental variables, pagefile parameters, and startup options... Startup/Shutdown The top portion of this tab modifies the BOOT.INI file by setting the default startup selection and timeout; the bottom portion defines the action to take when a STOP error occurs, such as create a memory dump file and/or reboot the system."

"What would you enable to record a memory dump following an application failure?
[You are supposed to place a target with crosshairs on the correct area]

Create crash dump file on Dr. Watson window"

Note: This person didn't give us any other options, but if we assume that this answer is correct remember that you gotta know where to place those crosshairs, boys and girls. Play with Dr.Watson if you can, most of it is very straightfoward. Remember that:

• Dump Symbol Table Adds the corresponding symbol data to the dump file. This increases the size of the file substantially
  
• Dump All Thread Contexts Forces a dump file to be created for all active threads, not just the ones related to the failed app.
  

Here's a bit of trivia: The MOC devotes exactly 112 words to Dr.Watson, underscoring the fact that that the Drwtsn32.log file is created in the form of an electronic text file. There's not much someone outside of a trained tech can do with this information.

Note: there are 3 debug setup options; local debugging, remote debugging, and Crashdump

• Local Debugging Done on-site. Two computers, a host and a target are needed. These are connected by a null modem cable.
  
• Remote Debugging Call MS Tech Support, if you can afford it.
  
• CrashDump A memory dump that writes the entire memory contents to the paging file and marks this file with a special stamp.
  

Q:"I had question on creating an crash dump file for application error the[re] were two screens, one showing system properties -start\shutdown screen and other one was Dr.watson screen which had many check box[e]s u have to check on one [of] the box[e]s.
[My][a]nswer was to check create crash dump file which happens to be last check box in Dr.watson screen"

To review: application crash dumps are done in Dr. Watson, system STOP errors and memory dumps are done in FAULTLOG on the startup/shutdown menu.

Q:"What Control Panel applet is used to configure modems?

a. Modem applet
b. Devices applet
c. Services applet.
d. Adapter in network applet

Answer: a"

Ibid Pg 239 "When you install a modem or the RAS components of NT, TAPI [is] automatically ...installed. It is required to control any communications device. Each time a dial-out connection is attempted, TAPI controls the modem and moderates the connection...The Dialing Properties dialog box (reached through the Modems applet in Control Panel) controls how TAPI uses your modem to place calls. You can control long-distance dialing, calling card use, prefix numbers, and tone/pulse dialing...All of the functions and features of the modem...are configured through a TAPI-controlled interface."

"Situation (Long): You are planing to reconfigure an NT Workstation with 32 MB RAM for optimum speed of access to its local (mainly graphic data) files, varying in size from 1MB to 10MB, for other computers in the same LAN. You have there a SCSI controller with 4 disks of 2 GB each, formatted with FAT.

Required result: To optimize performance for optimum speed of access to local data files.

Optional results: Reconfigure for optimum speed of access to paging file.

Optimize network access performance.

Proposed solution:

Configure the first hard disk as boot partition. Configure the other 3 disks as a Volume Set.
Use FAT on all partitions. Place data on the Volume Set. Place paging file on the boot partition. Configure binding order of protocols; move most used protocols to the bottom of binding order.

The solution produces:

A The required result and 2 of the optional results.
B The required result and 1 of the optional results.
C The required result and none of the optional results.
D None of the required results.

Note: Volume sets DO NOT speed up disk access.

Answer: D" Mad's note: Moving the most used protocols to the bottom of the binding order will also slow you down...

386 computer with NT 3.51, how do you upgrade to 4?
Can't-must be 486

Windiff and other utilities...
There seems to be an awful lot of confusion on this utility. One braindumper even claimed that there was no such thing! Allow me to clear the air with a few quotes from TechNet: "The Windiff utility allows you to compare two text files. This is useful when you want to compare Registry settings before and after [Win95] Office installation."

"How can you compare registry entries before and after an upgrade, the installation of a new software package, or between two computers?
"...[U]se the Windows NT 3.51 or 4.0 Resource Kit utility Windiff.exe to compare the differences between the registry entries before and after an upgrade..."

Q: "U need to do an automated installation of wks & 5 applications on 200 PCs. U decide to use NT server as the source to install. Which 3 files are required?*

• Poledit.exe
  
• Setup.inf
  
• Windiff.exe
  
• Unattend.txt (ANS)
  
• Sysdiff (ANS)
  
• UDF (ANS)
  

*There are lots of nearly identical braindumps, all say that UDF is right, but is it? Is UDF really a text file, a file name extension, or a command line parameter? Does this make a difference? And if we assume that UDF is wrong, could any other answer be correct? Read on, McDuff, the plot thickens...

TechNet: "Uniqueness Database Files (UDFs) are an extension of the answer file functionality"
"Information that the Setup program uses during text-mode setup can only be specified in the answer file, not in the UDF."


Q: "Workstation and 5 applications need to be installed on 200 Intel computers. All will have identical hardware and applications installed. NT server will be the source of all installation files. Which files do you need? Choose 3"

• A Poledit
  
• B Unattended.txt
  
• C Sysdiff
  
• D Setup.inf
  
• E UDF
  
• F Windiff
  

No answers from our braindumper here, but that's ok. The Gopher just loves to dig. Let's look at Poledit [System Policy Editor]:

From Tech Net: "The System Policy Editor is a graphical tool that allows you to easily update the registry settings to implement a System Policy. The System Policy Editor is included with Windows NT Server 4.0, but you can install it on Windows NT Workstation-based machines and on Windows 95-based machines as well. Note that a policy file is valid only for the platform on which it was created. For example, if you run Poledit.exe on a Windows 95-based machine, and you save the policy file, the file will be written in a format that can be interpreted by Windows 95-based machines only. The same is true when you create policy files on Windows NT-based machines. As a result, Windows 95 and Windows NT policy files are not interchangeable."
Poledit looks wrong to me. It is dismissed from further inquiry here...


"System Difference Tool: SYSDIFF.EXE
The System Difference tool enables you to distribute and install applications automatically during or after Windows NT setup."[more above, in case you forgot] Ibid "...Workstation deployment..."
Correct-a-mundo. This one is definitely right, as we shall soon see...

From a recent braindump:
"just like to say thanks to those who submitted previous braindumps. I passed with a 921 this week - 21/9/98. One question in the scenario type which I could not find any documentation on was the Setup.inf file - I even tried Microsoft support- who only described it as a script file not associated with unattended installs. -check it out."
Mad note: the questions posed above have nothing to do with unattended installation. Automated installation seems to be the topic. But are they the same thing?

"SETUP.INF is the key file that Setup uses to install the Windows for Workgroups system and application files and to create program groups that you can use to run applications from Program Manager."
It would seem that SETUP.INF is really a Windows for Workgroups file only- can this be the trick? Nothing I found relates this file and WS, except the /I switch in WINNT.EXE/ WINNT32.EXE, and the SYSDIFF "inf" function.
"Setup.inf: "Automating Selection of Windows Accessories and Components" Each Windows NT component or accessory has an associated setup information file (.INF). Each .INF uses the value InstallType to specify whether the application is to be installed. InstallType values:
0 = Manual Only
10 = Typical or Custom
14 = Typical, Custom, or Portable". TechNet

This appears to be more of a concept than a single file named "Setup.inf". Yet the concept seems to fit the scenario. This would have to be the correct answer IF UDF is wrong, since Windiff and Poledit are obviously wrong...but if unattended and automated are one and the same, and there is every reason to believe that they are, then you could concievably use a UDF parameter. But if you have identical requirements do you really need a "Uniqueness" file to specify changes in each machine?

"An 'unattended (or automated) install' can be performed by using special script files...The first file [is] UNATTEND.TXT...You can modify this file to match your needs manually. Or you can use the SETUPMGR.EXE utility...to simplify the process of creating [this]...file. A second script file can be used in conjunction with the UNATTEND.TXT file to specify different computer-specific details...This is called a Uniqueness Database Files [UDF]" Exam Cram, Pgs 35-36.

Do you really need a Uniqueness Database File in this scenario. Or could they be trying to trick us with semantics? Consider this: the REAL file name extension for a Uniqueness Database File is .UDB, NOT .UDF! Could this be the real trick here, that UDF is NOT a "file", and therefore wrong? Or simply not needed here?
From TechNet:
"Note The Windows NT setup command line parameter is /UDF but the file name extension for the Uniqueness Database File is .UDB."
It continues:
"Configure Machine-Specific Information Using Uniqueness Database Files (.UDB) Windows NT setup includes a feature designed to enable you to create one common Windows NT 4.0 setup script for use with a number of target computers to overcome the problem of "How to specify machine-specific information?" with out creating a unique setup script for each computer by specifying the unique settings in a separate database file. This file is a Uniqueness Database File (.UDB). .UDBs are used to provide replacements for sections of setup script, or supply additional section. This file is indexed using strings called UniqueIDs. The .UDB is used to specify a set of sections that should be merged into the setup script file at the start of GUI setup. This process takes place before any affected components actually read the internal representation of the setup script file, and is transparent to the user."

let's take a more concise look at the entire process:

Steps to Automating Windows NT Deployment
Step 1 - Build the Windows NT setup script file (UNATTEND.TXT). Start by creating a basic Windows NT setup script. You can do this by using one of the examples that are included or by using the Windows NT Setup Manager. Once you have created and tested your basic script, add the more advanced options of the Windows NT setup script.
Step 2 - Build pre-installation packages using the System Difference tool (SYSDIFF.EXE). Use the System Difference tool to automate pre-installation of applications during Windows NT setup.
Step 3 - Create process to configure machine-specific information. Create a Uniqueness Database (UDB) file or create machine specific setup script files for each computer. You have several options for building a setup process that includes configuring systems with machine-specific information without requiring user interaction during setup.
Step 4 - Build process to automate your distribution method. The final step is distributing the Windows NT source files and any other files to each computer. You can use a network distribution point, hard drive duplication, software distribution tools such as Microsoft Systems Management Server or a local device such as a CD-ROM. If you are installing Windows NT on a newly formatted hard drive you will need a boot disk to either access the network or possibly access a local device.
Building the Distribution Server Before beginning the process of automating Windows NT setup you must build a distribution server. In most cases the best distribution point is a network server. Make sure you have read, write, and change privileges on the network server you use.
Copy the Windows NT Source Files To build the distribution server, copy Windows NT source files from the Windows NT retail CD to your network server. For Intel and Intel compatible-based processors copy the I386 directory and all of its contents to your network server.
Copy Custom Files Using the $OEM$ Directory Windows NT setup includes a feature that can be used to automatically copy directories, standard MS-DOS 8.3 files, and any tools needed for your automated installation process, to the local hard drive during setup. It is based on a pre-defined directory name and structure. If you include this directory and structure in the root of your distribution point, the files and directories will be copied to your local hard drive during Windows NT setup. The pre-defined directory name is $OEM$. If Windows NT setup finds the $OEM$ directory in the root of the distribution point, it will copy all of the files found in this directory to the temporary directory created during the text mode portion of Windows NT..."

Final word: I'm going to side with the popular answer here, mainly because there's no mention of an .INF file anywhere in my sources. Of course, if the question that comes up mentions a .UDF file, I know that it's wrong, since there's no such thing.
Let's look at a few other questions, before my head explodes...

Q:"Peter Smith wants to install Windows NT Workstation without user in[ter]vention. He plans to do this by running winnt.exe with the /u switch. Which additional file must he use? (Choose one)

• A Uniqueness database file (UDF).
• B An unattended.txt file (answer file).
• C A customized setup.sif file.
• D A customized setup.inf file.

Answer: B " Correct.

Ibid: "Answer files are text files that provide the answers to some or all of the prompts that the end user would otherwise need to respond to during Setup. The answer file is specified with the /u option to the winnt or winnt32 command. "

"When Windows NT Workstation or Windows NT Server is installed using the winnt /u:answer_file or winnt32 /u:answer_file command, the options specified in the answer file (Unattend.txt) are applied to the installation. If the /udf:uniqueness_database_file option is also specified on the winnt or winnt32 command line, the entries in the specified uniqueness database file (UDF) are also applied, overriding entries in the answer file."

Q: How should you use an unattended.txt file (answer file) during the automated installation of a Windows NT Workstation on 100 identical new computers? (Choose one)

• A To provide hardware-specific configuration information and other configuration data for the computers.
  
• B To provide user account information, a unique computer name, and a unique identifier specific to each computer.
  
• C To automate installation of applications on the computers during the installation of
• WinNT WS.
  
• D To place application specific registry data into the registry on each computer including serialization and registration data.
  

Answer: A
WRONG- What do YOU think?
Printing

Q:"How do you print to a TCP/IP printer?"

• A. Host name and printer name
• B. Hostname and IP address
• C. Printer name and IP address
• D. Printer name and Host name

Ans. C

Correct. "Logical printers are created to send documents to the TCP/IP printer through the Add Printer Wizard. This is done by using the IP address...and the name of the printer, as defined by the print server."

Q:"You have sent a job to a printer and it jams. You cannot resend the job to the printer, what do you do?

• 1. Select resume from document menu?
• 2. Select restart from document menu?
• 3. Select cancel from document menu and then restart?
• 4. Select refresh from view menu and then resume?

Q:"What do you do if a document is jammed in a printer and was too damaged to reprint?
A Restart from the document menu"

Correct. After pausing the document you restart it "Pause the printer if there is a problem with the print device...Resume printing when a non-operational print device is repaired MOC#803 Pg170

Q:"You want to send a document from your Windows NT workstation computer to a printer that is located on another Windows NT WS computer. You want to do this without permanently installing drivers for that printer on your hard disk. What should you do? (Choose one)

• A Use "net print" to send the document to the printer.
• B Drag and drop the document file onto the printer in Windows NT explorer.
• C Use Windows NT Explorer to temporarily capture the printer, and then send the document to the printer.
• D Use the Add Printer Wizard to temporarily connect to the printer, and then send the document to the printer.
  

Ans : B"
This one I'm going to say is wrong, and this is why: I haven't found a single instance of any mention of a "drag and drop". So I'm ruling out B. Instead, MOC and Exam Cram both suggest the Add Printer wizard.
"Client computers need access to print devices, so they must add the printer via the Add Printer Wizard. [emphasis mine] ...All that is needed for printing from an NT client is that the driver be installed on the print server. That's it!" Exam Cram Pg 257
From MOC:
"Clients running Window[s]NT 4.0 and Windows 95 use the Printers folder to connect to a shared network printer. When they first connect, the appropriate printer driver is automatically installed into client memory." It continues:" To connect to a printer: 1) In the Printers folder, double-click the Add Printer icon. The Add Printer Wizard appears..." [emphasis mine] MOC#803 Pg 152
A is wrong, because the net use command is used for "LAN Manager clients running MS-DOS or OS/2..." Ibid, Pg 153
C is wrong. Capture is a NetWare comand.

Permissions

From BDHeaven: "A number of questions on both times, I did well in this area the second time...they give you a grid (it was different on each test) Across the top columns are listed Share, Directory, and file On the side they listed various groups that our hero was a member and permissions that each group had for the share, the directory and the files. Then you asked to give the effective permission for the files.
For me I just keep on[e] rule in mind. Like permission groups are cumulative and different groups are most restrictive. So I went down the share column and determined the effective permission, same for the directory and then the file. So I'm thinking in terms of single permissions for each level. [F]rom there you['re] down to a much simpler question."
Q:Meng is a member of Webusers group and Webserver group. Webusers group has Change access to XX folder. Webserver group has read only access to XX. What are Meng's access rights to xx?

• A. Change
• B. Read Only
• C. Full Controll
• D. No Access

Ans : A (Rights are cumulative with highest one rewarded except for No Access of course)
Correct. "The permissions from all groups of which a user is a member are cumulative. This applies both to shares and objects. The most restrictive set of common permission between a share and an object are used." Exam cram pg 125

Q:You are the Administrator in a NT server domain of 10 NT Workstations and 20 [Windows]95 computers. You create a new sys[t]em policy that applies to all user[s] on the network. Some of the users have roaming profiles. Which setting will take precedence when there is a conflict?].

• A. The roaming profile
• B. The system policy.
• C. The most permissive of system policy and roaming profile combined
• D. The least permissive of system policy and roaming profile combined

Ans. B (Just remember Profiles < System Policy < Individual Policy < Machine Policy - Machine Pol overides all.)

Q:"When a system policy and users profiles have a conflict, what happens?"

• a) user profiles have priority
• b) system policy have priority
• c) the least restrain with system policy and profiles
• d) the most restrain with system policy and profiles

Answer: b

Apparently these two agree, but hours of researching this question have yielded no firm answer to confirm the above. Exam Cram offers nothing on system policies, and the MOC has a few words about how to set up account policies, but no cross-reference on the roaming profile. Further research is forthcoming...

Q:"Question on setting up 50 roaming profiles, ensuring the client keep the current profile? Difficult question, the options were;

• a) copy all profiles to the PDC
• b) create a default profile and enable repl
• c) user user manager for domain to set roaming profiles
• d) use a system policy to create a roaming profile for all users

Not sure of the answer - I went for a) - but have zero confidence it is right."

Was a multiple answer required? Here are the steps to create a roaming profile:
1. Copy the user's profile from the WS to a shared network path. This means copy the [WINNT Root]\Profiles\[USERNAME] directory and all of its contents.
2. Open Control Panel and double-click System.
3. Select the user's profile entry, select Copy To, and type in the full UNC path name to the server where the profile will reside.
4. In the User Profile dialog box [accessed through a user's account's Properties via User Manager by clicking the Profile button], enter the full UNC path name for the profile in the User Profile path field.