K
Kristin L. Griffin
Guest
Hi,
I’m working on the TS Resource kit and I’ve run into a really weird problem
with mandatory profiles. Any help would be greatly appreciated.
Roaming profiles are working fine, no problems. Mandatory profiles work so
long as they’re in user-specific directories. As soon as I attempt to get
everyone pointing to the same mandatory profile (as described in this KB
article), the user can’t get a profile and logs on with a temp. The terminal
server’s Event log shows error 1521, but the network share is visible in
Explorer and there are no permissions on it—we decided to eliminate that
variable.
What I’m looking for is either:
• a way to permit all TS users to access the same mandatory profile file
(which, based on the KB article 908011, appears that it should be possible)
• or the definite word that this doesn’t work and I should stop worrying
about it
Build number is 6001.18000.amd64fre.longhorn_rtm.080118-1840. All servers
are WS08 RTM; all clients are Vista.
I’m working on the TS Resource kit and I’ve run into a really weird problem
with mandatory profiles. Any help would be greatly appreciated.
Roaming profiles are working fine, no problems. Mandatory profiles work so
long as they’re in user-specific directories. As soon as I attempt to get
everyone pointing to the same mandatory profile (as described in this KB
article), the user can’t get a profile and logs on with a temp. The terminal
server’s Event log shows error 1521, but the network share is visible in
Explorer and there are no permissions on it—we decided to eliminate that
variable.
What I’m looking for is either:
• a way to permit all TS users to access the same mandatory profile file
(which, based on the KB article 908011, appears that it should be possible)
• or the definite word that this doesn’t work and I should stop worrying
about it
Build number is 6001.18000.amd64fre.longhorn_rtm.080118-1840. All servers
are WS08 RTM; all clients are Vista.
