<div>
<div class="content wysiwyg-content">
I am stuck. 
 
I am trying to put together a termination script for former employees. 
 
The issue is that we use gpo's to redirect their profiles to different servers. &nbsp;One other issue is that when a user's username changes (ie married, divorced, etc), we continue to redirect their roaming profile to the old profile created under the original user account. 
 
I have tried using the following AD attributes: 
msTSProfilePath 
msTSHomeDirectory 
ProfilePath 
psbase.InvokeGet(&quot;terminalservicesHomeDirectory&quot;) 
psbase.InvokeGet(&quot;terminalservicesprofilepath&quot;) 
 
The above all show as blank. &nbsp; 
 
If we manually input the users information in AD under Remote Desktop Services Profile, the correct information is only shown under psbase.InvokeGet(&quot;terminalservicesHomeDirectory&quot;) and psbase.InvokeGet(&quot;terminalservicesprofilepath&quot;) 
 
Is there an AD attribute that holds the current roaming profile and roaming home directory information even if that location is redirected based on a GPO? 
 
 
***The purpose of the script is to find a user's roaming profiles and roaming home directory on a file server and then to move those folders to an archive server after the user is no longer with us.
</div>
</div>

I am stuck.

I am trying to put together a termination script for former employees.

The issue is that we use gpo's to redirect their profiles to different servers.  One other issue is that when a user's username changes (ie married, divorced, etc), we continue to redirect their roaming profile to the old profile created under the original user account.

I have tried using the following AD attributes:
msTSProfilePath
msTSHomeDirectory
ProfilePath
psbase.InvokeGet("terminalservicesHomeDirectory")
psbase.InvokeGet("terminalservicesprofilepath")

The above all show as blank.  

If we manually input the users information in AD under Remote Desktop Services Profile, the correct information is only shown under psbase.InvokeGet("terminalservicesHomeDirectory") and psbase.InvokeGet("terminalservicesprofilepath")

Is there an AD attribute that holds the current roaming profile and roaming home directory information even if that location is redirected based on a GPO?


***The purpose of the script is to find a user's roaming profiles and roaming home directory on a file server and then to move those folders to an archive server after the user is no longer with us.

Roaming Profiles - AD Attribute

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

The term 'shell' refers to a general class of text-based command interpreters most often associated with the UNIX and Linux operating systems. Popular shells include Bourne, Debian Almquist (dash), Korn (ksh), Bourne Again (bash) and the C shell family (csh). Some view the DOS 'cmd' prompt as a minimal shell of sorts. It is also possible to install Cygwin on Windows and emulate a full Unix environment with complete shell capabilities. Terminal emulators, such as xterm, GNOME Terminal and OS X Terminal, can be used to access shell.

Shell Scripting

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.