|
Home > Archive > 70-210 > March 2001 > RIS clarity please
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
RIS clarity please
|
|
| shaxx 2001-03-06, 11:55 am |
| Please clarify these 2 for me
Would the answer to 1 be C and the answer to 2 be D? Would the answer to 1 be C because you are Installing just standard applications and you did not log on as an administrator when you were configuring the RIS. Is the answer to 2 D because you are installing a bunch of fancy stuff an you logged on as administrator? Please clarify.
1. You want to configure the RIS image so that the standard applications will be accessible to the user when the user first logs on to the network. What should u do?
a. Run rbfg.exe before installing the standard applications.
b. Run riprep.exe before installing the standard applications.
c. Copy the all users profile to the default users profile.
d. Copy the local administrator account profile to the default users profile 15.
2) You want to install Win2K PRO on X new computers on your company’s network. You first
install Win2K PRO on one of the new computers. You log on to the computer by using
local admin account. You install MS Office 97, a virus scanner, and other company
standard applications. You then create a RIS image of the computer you configured.
You want to configure the RIS image so that the standard applications will be
accessible to the user when the user first logs on to the network.
What should you do?
a) Run RBFG.exe before installing the standard apps
b) Run RIPREP.exe before installing the standard apps
c) Copy the ALL USERS profile to the DEFAULT users profile
d) Copy the LOCAL ADMINISTRATOR account profile to the DEFAULT user profile
Increasing the paging file does not help for the situation In queston 3, right?
3) A user name Tom report that application on his W2P computer are running slowly. You notice Tom's computer has 64 MB of RAM and 100 MB of free disk space. What should you do to improve the performance. (Check all that apply)
A add Tom to the Power user group
B Set the total paging file to 75 % of physical memory
C Perform a disk analysis and use the disk defragmenter if recommended
D Use Disk cleanup to delete tempory files and unnecessary program files
E Ensure that the Performance Options windows is optimised for background services
Ans: C and D. Setting the page file wouldn’t help would it?
Thanks for the help | |
|
| Question 1 & 2: I am pretty sure that the answer for question 1 & 2 is B. Riprep is used to create images of Windows 2000 Pro and apps for a RIS Server. rbfg.exe is used to create boot disks for RIS clients without PXE network cards.
Question 3: B, C, D - This is a bit of a trick question. The pagefile should be 1.5 times the physical RAM (in other words 75%). As there is only 100Mb of disk space you would have thought that increasing the pagefile is the wrong answer, but don't forget you are clearing temporary files etc so this should clear enough disk space for the pagefile. | |
|
| 1. If you read the answer B question1, it says to run risprep before the apps are installed, so that would be incorrect to me.
3. umm, 1.5x = 150%
if you have 64MB, you should set the swap to atleast 96MB.
I think the correct answers are analyze the disk and defrag. Also, disk cleanup. C&D
quote:
Originally posted by MrRay
Question 1 & 2: I am pretty sure that the answer for question 1 & 2 is B. Riprep is used to create images of Windows 2000 Pro and apps for a RIS Server. rbfg.exe is used to create boot disks for RIS clients without PXE network cards.
Question 3: B, C, D - This is a bit of a trick question. The pagefile should be 1.5 times the physical RAM (in other words 75%). As there is only 100Mb of disk space you would have thought that increasing the pagefile is the wrong answer, but don't forget you are clearing temporary files etc so this should clear enough disk space for the pagefile.
| |
|
| Your right 1.5 is not 75%, I must be going crazy! | |
|
| too much studying huh!
quote:
Originally posted by MrRay
Your right 1.5 is not 75%, I must be going crazy!
| |
|
| This what MS has to say about Pagefiles (extract from Technet): http://www.microsoft.com/TechNet/win2000/usingthe.asp
When Windows runs low on available RAM and needs more memory to complete a task, it uses the hard drive to simulate system RAM. This is called virtual memory and is much slower than system RAM. This is because hard drive speeds are measured in milliseconds while RAM is measured in nanoseconds. Another name for virtual memory in Windows 2000 is the pagefile, and, in fact, Windows creates and uses a special file called pagefile.sys for virtual memory.
The default size for the pagefile in Windows 2000 is the amount of system RAM plus 12 MB. So, a system with 128 MB of RAM would initially have a pagefile of 140 MB. For a basic workstation or server, this number might be appropriate but servers running other Microsoft BackOffice applications such as Exchange Server or SQL Server usually need to increase the default virtual memory size. Refer to the product specific documentation for recommended virtual memory settings. You set the size of the pagefile by selecting the drive you want the file to be located on, typing a number into the Initial Size box shown in Figure 5-7 and the Maximum Size box and clicking Set. You will be prompted to reboot after clicking OK. The initial size is just that--the size of pagefile.sys when Windows 2000 starts up. The maximum size is how large pagefile.sys is allowed to grow during the processing of tasks as the system works.
Tip It might seem advantageous at this point to simply set a pagefile much higher than you need so you will not have to worry about running out of memory. However, Windows 2000 will not efficiently use a pagefile that is too large, resulting in potentially worse system performance than if the virtual memory size had been left at the default settings.
The default virtual memory settings are often not the most efficient, but there are some guidelines that you can use when configuring virtual memory settings.
Windows 2000 sets up the pagefile to be on the boot partition where the operating system was installed. This is inefficient because Windows will by nature perform a lot of disk I/O on the system files. Having to simultaneously read and write to the pagefile while doing the same with system files slows Windows down. Therefore it is recommended that the pagefile be moved to a different physical disk, preferably onto a partition that has no other data or programs that will be frequently accessed. Windows 2000, like Windows NT before it, supports advanced disk configuration options on NTFS partitions such as disk mirroring and disk striping. These features provide fault tolerance and performance benefits, and are discussed later in this book in a chapter on managing disks.
The downside to moving the entire pagefile though is that if Windows crashes it will be unable to write debugging information to a dump file (discussed later in this chapter). To address that, a pagefile using the default settings should be left on the system partition and another pagefile should be created on a different physical disk as outlined above. The Windows 2000 operating system has algorithms that allow it to use multiple pagefiles in the most efficient manner, and in this case it will opt to use the pagefile on the less frequently used drive rather than the one on the system partition. Should Windows crash, though, it would be able to create a dump file for troubleshooting purposes.
In addition to configuring the size of the pagefile, you can also configure the maximum size of the Registry from the Virtual Memory property sheet. As with the pagefile you can specify the largest size the Registry is allowed to grow, and nothing is gained by setting the maximum size artificially high.
http://www.microsoft.com/technet/images/FIG5-07.GIF
Figure 5-7 The Virtual Memory property sheet
Hope this clears things up 
PS the answer to Question 3 is C & D all the rest a bogus!!!
Yeti the Resourceful  | |
|
| Don't you just love conflicting information?
According to the Microsoft official Study Guide, the recommended paging file size for Windows 2000 Professional is 1.5 times the total amount of RAM.
All the practice tests i have seen so far make use of 1.5x. YMMV | |
|
| Becareful not to confuse Default settings with Recommended they are very different.
NOTE
Yes MS RECOMMENDS 1.5 x Physical Memory for Professional & Servers; However the Default Setting is 12 + Physical Memory for the pagefile!!! | |
|
| Configuring Windows 2000 Performance Options
Extract from Technet http://www.microsoft.com/TechNet/win2000/usingthe.asp
The first option on this property sheet is for application response. By default Windows 2000 will optimize performance for applications rather than background services. Windows 2000 manages system processing, which includes allocating processor time to processes that are running. The operating system can allocate tasks between multiple processors or multiple processes on a single processor. Choosing the Application Response preference, however, allows you to decide whether Windows should give more processor time to the programs you are working in or to background tasks such as printing. Setting the response to favor applications will result in a faster response time from the application you are actively working in, which is generally the desired option. A print server, though, would be set up to favor background tasks rather than active applications since the majority of the server's work would be processing background tasks. Windows 2000, like Windows NT, uses a thread priority process in order to determine which application to give CPU time to and in which order to do it. Windows 2000 does this on a scale of 1-31, with 31 being the highest priority and 1 being the lowest.
Yeti | |
|
| After further consoltation with the same book, pg 92.
Paging File Size
When you install Windows 2000, Setup creates a virtual-memory paging file, Pagefile.sys, on the partition where you installed Windows 2000. The minimum size is 2MB. The default or recommended pagine file size for Windows 2000 Professional is equal to 1.5 times the total amount of RAM.
Not trying to start an argument here, but obviously we have conflicting information. | |
|
| Looks like even Microsoft doesn't know the right answer
According to the online documentation for Server & Professional:
http://windows.microsoft.com/window...perf_mgmt.htm?
You are correct and even in the Training Kit for Professional as you quite rightly pointed out on page 92,paragraph 4, line 4 it is as you stated: 1.5 x Physical Memory.
So this begs the question, " Does Microsoft know the definitive answer?"
Yeti the Just as Confused as the rest of the World | |
|
| Maybe in an effort to save time & typing some bright spark at MS used the NT4 information rather than the Windows 2000????
Plausable? | |
|
| IRC, NT4 used physical + 11 ? | |
|
| So how bout the first 2 questions? Originally I though the answer would be the same for both...Copy the local administrator account profile to the default users profile.... but I've found different answers in different books. Yikes!!! | |
|
| Questions 1 & 2 are B
Question 3 the answer is C&D. The page file has nothing to do with it. The problem is low disk space. So a disk clean-up and a defrag all ya need.
Geek out | |
|
| I disagree,
If riprep is ran before the apps are installed then how can they be made available the first time a user logs in? To me, the apps would be installed then all the profiles are combined then riprep is ran to make the apps available. Anyone else shed some light on this? |
|
|
|
|