|
The terminal server profile is stored as part of
the userParameters blob. This attribute is made of a number of other settings,
not just terminal server specific ones.
You can manipulate these settings via WTSSetUserConfig() BOOL WTSSetUserConfig(
LPTSTR pServerName, LPTSTR pUserName, WTS_CONFIG_CLASS WTSConfigClass, LPTSTR pBuffer, DWORD DataLength ); typedef enum _WTS_CONFIG_CLASS { WTSUserConfigInitialProgram, WTSUserConfigWorkingDirectory, WTSUserConfigfInheritInitialProgram, WTSUserConfigfAllowLogonTerminalServer, WTSUserConfigTimeoutSettingsConnections, WTSUserConfigTimeoutSettingsDisconnections, WTSUserConfigTimeoutSettingsIdle, WTSUserConfigfDeviceClientDrives, WTSUserConfigfDeviceClientPrinters, WTSUserConfigfDeviceClientDefaultPrinter, WTSUserConfigBrokenTimeoutSettings, WTSUserConfigReconnectSettings, WTSUserConfigModemCallbackSettings, WTSUserConfigModemCallbackPhoneNumber, WTSUserConfigShadowingSettings, WTSUserConfigTerminalServerProfilePath, WTSUserConfigTerminalServerHomeDir, WTSUserConfigTerminalServerHomeDirDrive, WTSUserConfigfTerminalServerRemoteHomeDir } WTS_CONFIG_CLASS; I believe there are a number of wrappers that folks have written for this
set of API's , just google it.
If you are using Windows 2003 you can set the users Terminal Server profile
path per machine via GPO - there is also a WMI provider for general Terminal
Server settings.
As far as dsget, dsmod etc.. these generally manipulate ldap data - it
doesnt have the know-how to break down the blobs to respective data.
-steve
|
- [ActiveDir] Terminal Server profile path in ADSIEDIT? Jeremy Waldrop
- RE: [ActiveDir] Terminal Server profile path in ADSIE... Steve Patrick
- RE: [ActiveDir] Terminal Server profile path in ADSIE... Cotter, Paul M.
