Scenario: A Citrix Architect has implemented a multi-location profile strategy as part of a large XenApp and XenDesktop solution. The architect needs to implement a single policy that sets the profile path for all users.
New York users – Server:NYC-FS.company.lan – Share: NYC-Profiles$
Miami users – Server:MIA-FS.company.lan – Share: MIA-Profiles$
San Francisco users – Server:SFO-FS.company.lan – Share: SFO-Profiles$
The architect has proposed the usage of the following path for all users:
\#Loc#-FS.company.lan#Loc#-Profiles$#sAMAccountName#%ProfileVer%
What does the architect need to define in order to use the above path for all users as the profile location?
A. A Loc variable using the Current-Location attribute
B. A new attribute called Loc using Active Directory Explorer
C. A user environment variable Loc using a login script
D. A DFS-ROOT variable per datacenter and incorporate the user environment variable %homeshare%
|
Download Printable PDF. VALID exam to help you PASS. |
 |
B for sure.
If you can’t use the #l# attribute, examine your AD user schema for other attributes such as #company# or #department# that achieve a similar partitioning.
You can also create custom attributes. Use Active Directory Explorer, which is a sysinternals tool, to find which attributes have been defined for any particular domain.
Answer B is the right solution.
Seen here: https://docs.citrix.com/en-us/profile-management/current-release/configure/specify-user-store-path.html
“Attributes of the AD user object enclosed in hashes (for example, #sAMAccountName#).”
I think Answer A would be right – https://docs.citrix.com/en-us/profile-management/current-release/configure/specify-user-store-path.html
well…I think A