|
Home > Archive > 70-217 > April 2002 > Wed 70-217 Question of the Day
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 |
Wed 70-217 Question of the Day
|
|
| wbafrank 2002-04-03, 9:41 am |
|  And today's poser is ....
Q47. The default setting for the users profile size in a Windows 2000-based domain is unlimited. You can modify the users profile size by using Group Policy to restrict profile size to a default maximum of 30 MB. However, if you increase the maximum profile size so that it is greater than 30 MB (but not unlimited), you may receive the following error message:
number is greater than the maximum allowed value of 30000. 30000 will be saved instead of number
What could cause this error message?
A. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MinProfileSize value for users' roaming policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
B. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' mandatory policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
C. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' roaming policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
D. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' roaming policies on the network, which is located in the Systemroot.adm file. The default setting for this value is 30 MB.
Good Luck .... see you tomorrow for the answer!! | |
| CyberDude 2002-04-03, 12:49 pm |
| I will go for B, as I think a mandatory policy cannot be overridden. Lets see if my guess pays out. | |
| jeff_j_black 2002-04-03, 1:16 pm |
| 'C' | |
| unreal 2002-04-03, 8:35 pm |
| I'll pick 'C' in favour of 'B', because when 'mandatory' is concern, 30MB means 30MB, not a penny more .
C. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' roaming policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB. | |
| wbafrank 2002-04-04, 8:58 am |
| quote:
Originally posted by wbafrank
And today's poser is ....
Q47. The default setting for the users profile size in a Windows 2000-based domain is unlimited. You can modify the users profile size by using Group Policy to restrict profile size to a default maximum of 30 MB. However, if you increase the maximum profile size so that it is greater than 30 MB (but not unlimited), you may receive the following error message:
number is greater than the maximum allowed value of 30000. 30000 will be saved instead of number
What could cause this error message?
A. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MinProfileSize value for users' roaming policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
B. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' mandatory policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
C. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' roaming policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
D. This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' roaming policies on the network, which is located in the Systemroot.adm file. The default setting for this value is 30 MB.
Good Luck .... see you tomorrow for the answer!!
And the answer is ....
Correct Answers: C
This issue can occur because when you use Group Policy to restrict the profile size, the computer uses the MaxProfileSize value for users' roaming policies on the network, which is located in the System.adm file. The default setting for this value is 30 MB.
To resolve this issue:
Use Microsoft Notepad to open the System.adm file on a Windows 2000 domain controller.
This file is found the %SystemRoot%\Winnt\Inf folder by default.
Locate the following section:
PART !!ProfileSize NUMERIC REQUIRED SPIN 100
VALUENAME "MaxProfileSize"
DEFAULT 30000
MAX 30000
MIN 300
END PART
Increase the maximum size value (Max) to the size that is required for your network users. (This value is set to 30000 by default, which is equal to 30 MBs.)
Save the file in the %SystemRoot%\Winnt\Inf folder.
Click Start , click Programs , click Administrative Tools , and then click Active Directory Users and Computers .
Click to expand Active Directory Users and Computers , and then click to expand the domain name.
Right-click the organizational unit that you want the policy restriction to be applied for, click Properties , and then click the Group Policy tab.
Click New , and then add a new Group Policy.
Click the new policy, and then click Edit .
Click to expand User Configuration , click to expand Administrative Templates , click to expand System , and then click Logon/Logoff .
Double-click Limit profile size in the right pane, and then click Enable .
Change the new maximum profile size to accommodate the network, click Apply , and then click OK .
Close the Group Policies window, and then quit the Active Directory Users and Computers snap-in.
The policy is replicated to other domain controllers during the next Active Directory cycle. For domain controllers that are located in the same logical site, replication occurs every five minutes. Replication with domain controllers in different sites can occur in 90 minutes (plus or minus 30 minutes), or at a time that is based on the custom replication schedule that is established in the Active Directory Sites and Services snap-in.
MORE INFORMATION
If you increasing the maximum profile size to greater that 30 MB, it may take users longer to log on while the profile is loaded from the network. |
|
|
|
|