Move User in PPOMA_BBP

Hi Experts,
When i move the User in the SRM Org.Structure, the system sends out an automated e-mail to the User with a short msg. "Please check employee xxxxxx". Here the xxxxxx stands for the CP# in the SRM Org.Structure for this User. This msg is really confusing to the User and the automated e-mail goes on my name, becuase i have made the changes in the org. structure. Is there any way to stop this e-mail or make changes in the msg. content? Where exactly is the control/settings for this e-mail? Please suggest. Thanks!

Hi Harsha,
See the foll thread for solution:
Disable Alert Triger In SRM
BR,
Deepti.

Similar Messages

Move user in organisation with FM

Hello, have anyone an idea how can I move a user in the organisationmodel with a FM. Today I must drag-and-drop user for user manuel with the mouse.
Marc

Hello Marc,
To revert the changes do the following:
- remember text and short text in user position text
- in PPOMA_BBP delete assigment for bad user.
- right click on Org Unit and choose create.
- choose 'position' from list
- fill text and short text
- right click on already created position and choose 'assign'.
- find your user on list and click OK button.
I will find better way to move users.
Regards,
Marcin

How do I move users, including my user library (which is invisible) to a different hard drive?,

I have two 750 GB hard drives in my new mac mini. Lion is installed on hard drive A and I want to move users to hard drive B. I have dragged the user files from HD A to HD B and have re-mapped the users to the folders. Turns out, in Lion the users libraries are hidden and won't copy. I can unhide them (using Finder, go to folder, ~/Library, GO). But it will not let me copy the library folders because it is invisible.

Open the Terminal application in the Utilities folder and paste this to unhide the user library:
sudo chflags nohidden ~/Library
Hit enter and put your password in.

GW2012 move: Does it make sense to move users to a new PO?

Moving from GW8 on OES-NW to GW2012 on OES11: Does it make sense to create new post office and move users?
We have a medium size GroupWise 8 system with a single post office holding less than 600 user accounts, 128 resources and 77 distribution lists.
Due to politics we also have a non-GroupWise external domain that contains a non-GroupWise external post office with a large number of "users".
The post office is on the primary domain.
3 secondary domains hold a GWIA and two web access agents.
I've never been real clear where the external stuff exists...
One of the web access gateways resides on an OES11 server.
The other webaccess agent and the GWIA are on OES-NW servers.
All reside in NSS volumes.
Given the lack support for NSS volumes on Linux servers by most backup applications (including mine), I've pretty much determined that it makes sense to move my GW system to EXT3 volumes.
Even if I change backup software and stick with NSS, and even though all my data is stored on SAN arrays, from what I've read on the forums and from Danita's books, it's preferable to copy your GW system files to a new NSS volume, as opposed to just re-attaching the OES-NW LUN to the new OES11 server.
Point being, whatever I do will involve copying the entire system via dbcopy and at some point, will also involve shutting down the existing domain and PO for the last phase of the copying process.
So..., I'm contemplating the following scenario:
Create a new OES11 server with EXT3 volumes sufficient for holding my GroupWise system.
Create new GroupWise 8 domain on the server.
Promote the new domain to primary and upgrade this new domain to GroupWise 2012.
Once the new domain is upgraded, create new GW2012 post office on new server/primary domain and migrate the users, resources and distribution lists to the new post office.
In the past I've had an additional post office and had migrated a about 20-25 users to that post office.
It wasn't a terrible process, and fortunately, I didn't run into any problems with the migration of those users.
When I re-consolidated my system, moving them back was also problem free
On the pro side:
No downtime of entire system
Relatively simple
Any issues in the migration process would be user-specific and would not effect the entire system.
On the con side:
Process could take far longer, since you can't move a lot of users simultaneously.
In addition, we have a small group of users with anywhere from 40,000 to 80,000 email in their account, so I'd have to factor that into haw many users I migrate at one time.
The chance of running into a stalled migration, for whatever reason, is probably much higher than running into a problem with moving the domain and PO via dbcopy.
The unknown factors for me and my level of experience:
It's been a while since I've had multiple post offices, so I don't recall what changes the users might see with regard to distribution lists, web access or external email.

Originally Posted by gathagan
Moving from GW8 on OES-NW to GW2012 on OES11: Does it make sense to create new post office and move users?
Is there any reason you think that warrants to do so?
If the system is performing normally I'd opt to stick to upgrading the current setup as is.
I'm also curious, are you intending to upgrade to 2014 after the 2012 upgrade?
Originally Posted by gathagan
The post office is on the primary domain.
3 secondary domains hold a GWIA and two web access agents.
I've never been real clear where the external stuff exists...
Ok, that setup makes the upgrade easier. As you will start the upgrade with the primary holding the PO's... the PO's can be upgraded right after or during the domain upgrade (depending on if the MTA and POA are running on the same server).
That means you don't have to think about upgraded webaccess/GWIA connectivity issues with a lower PO version.
The external stuff are simply configurations found in the existing GroupWise domain databases. Or do you mean where those connected systems actually run?
Originally Posted by gathagan
One of the web access gateways resides on an OES11 server.
The other webaccess agent and the GWIA are on OES-NW servers.
All reside in NSS volumes.
And the primary Domain and PO are also still on NetWare (version 6.5 SP8 I presume), correct?
Originally Posted by gathagan
Given the lack support for NSS volumes on Linux servers by most backup applications (including mine), I've pretty much determined that it makes sense to move my GW system to EXT3 volumes.
Which backup application is that? With GroupWise op Linux not much NSS support is needed IMO.... as long as the files get backed up properly other metadata (rights, ownerships, etc) is irrelevant.
As for EXT3 vs NSS, when dealing with OES I always choose NSS. But that's me.
Another option could be to use XFS instead of ext3. That does perform much better, but has to be noted that it is more prone to file corruption in unexpected power loss situations.
With ext3, watch out for the scheduled filesystem check cycles at boot, that is one thing I really dislike about ext3 as disabling that check completely is not recommended and it means at least once a year the system will take an extensive amount of time to complete a (re)boot due to the check running on the ext3 filesystem. That usually pops up on you when you are not counting on it and "just quickly" want to reboot the server in a patching routine or other.
Originally Posted by gathagan
Even if I change backup software and stick with NSS, and even though all my data is stored on SAN arrays, from what I've read on the forums and from Danita's books, it's preferable to copy your GW system files to a new NSS volume, as opposed to just re-attaching the OES-NW LUN to the new OES11 server.
Yes, it's always good if you can start with a clean volume when transitioning from NetWare to OES.
Depending on how long you can afford to have the system down during upgrade, you can also choose the route of moving the NetWare LUN to the new OES server. Adding a second new LUN to the OES server with the needed size and initializing it with a new NSS volume and then just simply do a volume to volume copy using the cp of rsync command. As it's on the same server that can go quite quickly within an acceptable maintenance window to complete all move/upgrade steps.
Originally Posted by gathagan
Point being, whatever I do will involve copying the entire system via dbcopy and at some point, will also involve shutting down the existing domain and PO for the last phase of the copying process.
Sure, though you don't necessarily have to use dbcopy... depending on what you are planning to do. An offline copy won't require it for example.
How much data are we talking about (in GB's)?
Originally Posted by gathagan
So..., I'm contemplating the following scenario:
Create a new OES11 server with EXT3 volumes sufficient for holding my GroupWise system.
Create new GroupWise 8 domain on the server.
Promote the new domain to primary and upgrade this new domain to GroupWise 2012.
Once the new domain is upgraded, create new GW2012 post office on new server/primary domain and migrate the users, resources and distribution lists to the new post office.
If you really want to move users.... sure. I'd again opt for upgrading the existing system.
Also, it's a good rule to have the PO's running the same GroupWise version and patchlevel before commencing user moves. Moves between PO's with a different GroupWise version can lead to issues.
Originally Posted by gathagan
In the past I've had an additional post office and had migrated a about 20-25 users to that post office.
It wasn't a terrible process, and fortunately, I didn't run into any problems with the migration of those users.
When I re-consolidated my system, moving them back was also problem free
If you would want to move users, for whatever reason, I'd opt to first upgrade to the latest version first, then move. There have been many enhancements and bugfixes made in the move procedure over these last couple of years.
Originally Posted by gathagan
On the pro side:
No downtime of entire system
Relatively simple
Any issues in the migration process would be user-specific and would not effect the entire system.
On the con side:
Process could take far longer, since you can't move a lot of users simultaneously.
In addition, we have a small group of users with anywhere from 40,000 to 80,000 email in their account, so I'd have to factor that into haw many users I migrate at one time.
The chance of running into a stalled migration, for whatever reason, is probably much higher than running into a problem with moving the domain and PO via dbcopy.
I prefer a system upgrade over moving users. The process of moving when dealing with 100+ users, requires more effort and there are always things that need attention for a portion of the users. Also things like mobile devices can require some extra attention after having moved an account for example.
True, problems during a system upgrade can potentially affect all users. That is a factor. From the many upgrades I've done that's rarely really been an issue and problems encountered during an upgrade did not cause too much delay. Just make sure you always have a good full backup handy so you can reverse the upgrade if ever needed.
Originally Posted by gathagan
The unknown factors for me and my level of experience:
It's been a while since I've had multiple post offices, so I don't recall what changes the users might see with regard to distribution lists, web access or external email.
If by this you are referring to user moves and address book visibility between PO's, that should not be different to what users are seeing now. At least, the default is that within a GroupWise system all is visible throughout the system. If you have specifically set GroupWise objects to Postoffice visibility... then that would be something to check.
Cheers,
Willem

Help creating a script to move users in and out of an OU based on a time limit

Here's my scenario: we currently have OUs based on the locations of our facilities, we also have a sub-OU(?) underneath it for users that need a group policy applied to them where whitelist applications allowed to run. From time to time we have need to pull
users out of that sub-OU for a short period of time to let them run applications they normally wouldn't be able to and won't need to run long term. Sometimes we also forget to add these people back into that policy controlled sub-OU because we get busy do
other things. Server is 2008 R2.
Here's what I'm looking for: A script that prompts for the users name, pulls that user out of the sub-OU, puts them in the main OU but only for 24 hours. After that time limit is up, a script/command runs that puts the user back in the policy controlled
sub-OU. I'm thinking a PS script would be the best way to do this.
Research: Looking at these posts here and here I'm
thinking I should be able to Frankenstein something together but I have very limited PS scripting experience.
Can anyone help me create this?

You've probably figured this out, but we're not typically in the business of writing complete solutions for people. With that said, there are projects I find particularly interesting, such as this one, where I am willing to help get someone started if they
are willing to take the time to work through the examples and learn from them.
You have two requests - one is a script that prompts for a user it then moves to a different location in Active Directory. The second request is a way to move them back without manual interaction. This will require an automated task (scheduled task)
that will run at select times during a day.
Here's the first script (1/2): The first two lines set two different variables. The first line sets the $OUPath variable to the SubOU. The second line prompts for a user and, once a user is entered, sets that user to the $User variable. It then runs the
first try-catch, attempting to replace the $User variable with the data returned from the Get-ADUser cmdlet. Notice the use of the -Properties parameter. By default the modified date and the extensionAttributes are not returned. We will be using the modified
date so we can be certain that 24 hours passes before we move them back (see part 2/2). Including extensionAttribute13 will ensure we only move users out of the OU if they were moved in by the script. Note: The modified date on a user in AD is changed when
it is moved from one OU to another. If the user cannot be located in the first try-catch it will say it cannot locate the user in Active Directory. If it can locate it, it will set the $User variable, as described so far, and then move on.
In the second (or, nested) try-catch we split the user's DistingusihedName at the first comma so that we have two parts. We use the second part (that doesn't include their CN) and see if that matches the $OUPath variable. If it does match then that user
has already been moved. If it doesn't match then we 1. Move the user, 2. Replace extensionAttribute13 with the string 'MovedUser,' and 3. Output that the user has been moved.
$OUPath = 'OU=SubOU,OU=MainOU,DC=mydomain,DC=com'
$User = Read-Host -Prompt 'Enter SamAccountName'
try {
$User = Get-ADUser -Identity $User -Properties Modified,extensionAttribute13
try {
If ($User.DistinguishedName.Split(',',2) -eq $OUPath) {
Write-Output -Verbose 'User already moved.'
} Else {
Move-ADObject -Identity $User.DistinguishedName -TargetPath $OUPath
Set-ADUser -Identity $User.SamAccountName -Replace @{extensionAttribute13='MovedUser'}
Write-Output "'$($User.SamAccountName)' has been moved."
catch {
Write-Output "'$($User.SamAccountName)' cannot be moved."
catch {
Write-Output -Verbose "Unable to locate '$User' in Active Directory."
The second script (2/2): Here we also set a couple variables - one is the SubOU's DistinguishedName where we want to return the user and the other is the all of the users from the MainOU. Foreach user in $Users we check if their extensionAttribute13 is set
to 'MovedUser' and if their modified date is greater than or equal (-ge) to 24 hours. If it is, the script will move the user, clear extensionAttribute13, and let us know the user was moved. If for some reason your $OUPath variable is wrong, the script will
run the catch portion of the only try-catch we used in this script. Again, you'll have to schedule Task Scheduler to run this script. Good luck!
$OUPath = 'OU=MainOU,DC=mydomain,DC=com'
$Users = Get-ADUser -Filter * -SearchBase $OUPath -Properties Modified,extensionAttribute13
Foreach ($User in $Users) {
$TimeSince = New-TimeSpan -Start $User.Modified -End (Get-Date)
If ($User.extensionAttribute13 -eq 'MovedUser' -and $TimeSince.Hours -ge 24) {
try {
Move-ADObject -Identity $User.DistinguishedName -TargetPath $OUPath
Set-ADUser -Identity $User.SamAccountName -Clear extensionAttribute13
Write-Output "$($User.SamAccountName) has been moved."
catch {
Write-Output "$($User.SamAccountName) cannot be moved."
} Else {
Write-Output 'No Users to move.'
If you decide to use this, be sure to change the paths you use for the $OUPath variables. Also, if you're using this with PowerShell 2.0, you will need to use the Import-Module cmdlet to import the ActiveDirectory module. In versions above 2.0 it will be
imported automatically if you try to use an AD cmdlet.
Edit: Typo - Get-ADUser property

Move users from free trial to paid Intune group

Before the free trial ended I paid for a 10 user subscription. Now that the free trial has ended my users can no longer use Intune from Windows Phone 8 devices. I think the problem is my users are still associated with the free trial licenses instead
of the paid ones. How can I move users to the paid license as I cannot find any options for doing this.
Subscriptions -> Manage -> Billing and subscription management
This area lists two Windows Intune subscriptions, the first for my 10 paid for licences and the second for 25 expired free licenses.

Microsoft support may be able to help you to transfer the users but why bother. It's easy just to re-enrol the phones (you don't have many). Delete the Company App account and re-enrol. This will pick up the paid subscription.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Move users and schemas from one instance to another

Hi, I'm starting out in a DBA position.
My task at the moment is to move users and schemas from one instance to another.
We're using 9.2.0.7.
I have concluded that the following steps are necessary to move users and schemas from one instance to another :
1. Create the needed tablespaces.
2. Create the users that exist in the source instance
3. Use exp to do a full export
4. Use imp to re-create the schemas from the output file created by exp in step 3
Am I missing anything ?
Thanks,
Gabriel

3. Use exp to do a full exportInstead of doing a FULL export just export the users you want to move and imp that in other database using FROMUSER & TOUSER parameter.
Daljit Singh

How to Move users from one OU to another

I need move user for one OU another, but show error
this my script:
Import-Module activedirectory
$Users = Import-Csv -Delimiter ";" -Path "D:\Joan\teste.txt"
foreach ($User in $Users)
    $DisplayName = $User.Usuarios
    $TempUser = Get-ADUser -Filter { DisplayName -like $DisplayName }
Move-ADObject -Identity $DisplayName -TargetPath "OU=teste,DC=teste,DC=br"
This error:
ove-ADObject : Não é possível localizar um objeto com identidade: 'ALCIDES ALVES MACHADO
' em: 'DC=teste,DC=br'.
Em linha:8 caractere:14
+ Move-ADObject <<<< -Identity $DisplayName -TargetPath "OU=teste,DC=teste,DC=br"
    + CategoryInfo          : ObjectNotFound: (ALCIDES ALVES M...               :ADObject) [Move-ADObject], ADIdentityNotFoundException
    + FullyQualifiedErrorId : Não é possível localizar um objeto com identidade: 'ALCIDES ALVES MACHADO
' em: 'DC=teste,DC=br'.,Microsoft.ActiveDirectory.M
   anagement.Commands.MoveADObject

I try, but... :/
Move-ADObject : Não é possível validar o argumento no parâmetro 'Identity'. O argumento é nulo. Forneça um argumento que não seja nulo e tente o comando novamente.
Em linha:8 caractere:25
+ Move-ADObject -Identity <<<< $TempUser.distinguishedname -TargetPath "OU=teste,DC=teste,DC=br"
    + CategoryInfo          : InvalidData: (:) [Move-ADObject], ParameterBindingValidationException
    + FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.ActiveDirectory.Management.Commands.MoveADObject

How to move users between OU's from an exported list

Hey Guys
New to Powershell
We are going to move large number of users from one OU to another.. For that I am using
get-aduser -filter * -searchbase "OU=ou1,DC=domain" | move-adobject -targetpath "OU=ou2,DC=domain"
As a backout plan we want to reverse that.. so what I am thinking is to right click on the OU1 and export list as txt. So we have all users in a tab/csv format with username.. How can I then write a one liner / script to search for all the users in the list
in AD (or in specific OU2 in AD) and then move them to another OU (or OU1 as above example)?
Or if there is a better quicker method please let me know.
Cheers

Hi,
Here's something to start with:
$targetOU = 'OU=Test 2,DC=domain,DC=com'
Get-ADUser -Filter * -SearchBase 'OU=Test 1,DC=domain,DC=com' | ForEach {
$props = @{
Name = $_.Name
Username = $_.SamAccountName
OriginalOU = ($_.DistinguishedName -split ',OU=' -split ',')[1]
NewOU = ''
Status = ''
try {
Move-ADObject -Identity $_.DistinguishedName -TargetPath $targetOU -ErrorAction Stop
$props.NewOU = ($targetOU -split ',' -replace 'OU=','')[0]
$props.Status = 'Success'
} catch {
$props.Status = 'FAILED'
New-Object PsObject -Property $props
} | Sort Name | Select Name,Username,OriginalOU,NewOU,Status | Export-Csv .\userMoveDetails.csv -NoTypeInformation
Don't retire TechNet! -
(Don't give up yet - 12,950+ strong and growing)
Sorry new to coding.. but this looks awefully complicated for my situation.. Won't the code which I have said simple move users from one container to another existing one? Just need to know how to do the reverse if needed .. OU2 will already have users..
so need to differentiate and was thinking the right click on OU1 and export list.
Thanks

Best way to move users

what is the best way to move user data and settings from one system to another? and how about backing up users? thanks in advance...

Just wanted to clarify:
1. Mike Bombich's method entails moving the entire /Users folder to another drive so everyone's home is moved?
2. David Pogue's method (as described in the Missing Manual) only entails moving individual, selected home folders to another drive (and no soft links needed)?
3. It sounds like Pogue's method is preferable anyway (for the paranoid at least), so if the 2nd drive dies or needs maintenance, I can still login as a user whose home folder is in the boot drive?
4. So, if I use Pogue's method, all that is needed are the steps listed in my original post above, and nothing else?
Thanks.

Modify the Move User workflow to change AD location

All,
I what to move a user within an IDM organization and have it move the user within AD to different Organization UNIT.
I think that I can modify the Move User workflow and add an additional action to the Process Org Moves Activity. I want to clarify is this is what everyone else has been doing for department transfers.

You will need to specify RenameUserViewer as the type when checking out the view.
                <Action id='0' name='Checkout Rename View' application='com.waveset.session.WorkflowServices'>
                    <Argument name='op' value='checkoutView'/>
                    <Argument name='type' value='RenameUserViewer'/>
                    <Argument name='id' value='$(accountId)'/>
                    <Argument name='subject' value='$(WF_CASE_OWNER)'/>
                </Action>

Bulk move users from one group to another in XI 3.1

Hi all,
I have a group that contains approximately 20,000 users. I now need to move around 7,500 of these users into a different group.
How can I do this programatically in bulk as I don't want to go through and manually change the groups of 7,500 users?
Thanks,
Chris

Hi Christian,
Assuming you would need to move users from one group to another and remove them from the previous group, you could use the attached java code.
To run the code, you would need to save it as .jsp file and paste it inside AdminTools application context.
The pre-requisite to run this code is to create a Text file with all the 7500 user names in it. The text file should contain one user per line
(example:
User1
User2
User3
You can get this information from query builder by running the below query
Select top 20000 si_name from ci_systemobjects where si_kind='user'
Initially do it for 2-3 users to text the results.
You would need to edit the jsp and modify these three lines
1.
                * Assign user to a group
               //Query for the group ID
               boQuery = "Select SI_ID From CI_SYSTEMOBJECTS Where SI_KIND='UserGroup' And SI_Name='UserGroup name'";
Above in SI_NAME, you would need to provide the usergroup name you want your users to be added to.
2.
if (boUserInfoObject.getGroups().remove(Group Id from which it has to be removed)) {
                        out.print("User removed from group successfully. ");
Above you would need to provide the id of the group you want the users to be removed from(i.e the current group from where you want them to be moved).
3.
* Path to file containing User names.
final String USER_FILE_PATH = "<Path of txt file from which list of users will be imported>";
Above you need to specify the path of the text file which contains all the user names.
Incase you require further assistance on SDKs, raise your concerns in the below space
http://scn.sap.com/community/bi-platform/java-sdk
Thanks,
Prithvi

Move Users from OCS 2007 R2 to New Lync 2013

I am trying to move users from OCS to Lync 2013 from within the Lync 2013 Control Panel and am getting an error that states "Cannot find Registrar pool. Verify that "FQDN of old pool" is a valid registrar pool.

Give this Lync powershell command a go:
Move-CsLegacyUser <user> -Target <Lync2013 Pool Name>
Move-CsLegacyUser -Identity "Pilar Ackerman" -Target "atl-cs-001.litwareinc.com"
Have you reviewed the OCS to 2013 migration documents?
http://technet.microsoft.com/en-us/library/jj205375.aspx
Did you add the OCS pool to the 2013 topology?
Have you visited Lync News lately? All of the latest Lync news, articles, and tips collected in one giant aggregator. http://lyncne.ws

Move user between two pool in Lync 2013

after Adding Your Second Lync Standard Edition Server 2013 & Creating an Associated Backup Pool for Resiliency, when i am log in to Lync Server Control Panel when go to Once the LSCP is open well click Users | Find | Select [email protected]
| Action .
I cant see Move Selected Users to Pool… |
what do i do?
help

Hi,
Please check if CMS replication update to the latest status with the following cmdlet:
Get-CsManagementStoreReplicationStatus. If the status not to the latest status, you can invoke by the following cmdlet:
Invoke-CsManagementStoreReplication
Also, you can temporary use Windows PowerShell cmdlets to move users from one pool to another.
More details you can refer to the part of “To move users from one pool to another using Windows PowerShell cmdlets” below:
http://technet.microsoft.com/en-us/library/gg182600.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Use a soft link to move /Users to another volume

I'd like to move /Users to another volume, so that I can have the OS and applications on an SSD, without having to get an SSD of several terabytes.
Users log in to a Mac Pro using Active Directory accounts. Consequently, they do not have accounts on the Mac, and I cannot use Mac user properties to move their home directories. Also, the set of users who can log in is limited only by the AD user base, which has tens of thousands of entries. Of course, I cannot change the AD schema. So it has to be a solution that happens automatically. If a new user logs, her home directory must be automatically created on a volume which is not the startup.
I made a soft link from the startup volume to the new volume where I want the homes to go. This seems to work. After a restart, all the applications I tried had no problem following the soft link.
Is there any danger here? Or is there some better solution? I tried, following a suggestion which apparently worked in older versions of the OS, to make an entry in /etc/fstab to mount the new disk as /Users. This did not work in Mavericks (my test machine). The new disk appeared in Disk Utility, but could not be mounted. Perhaps it would work on Mountain Lion, which is the machine where this change ultimately needs to be implemented.
I will be obliged for any suggestions or warnings.

Reading through the article you referenced, I noticed they talked about downsides to moving home directory.
The issue about non-boot drives not being as protected as the boot drive.
Specifically related to permissions. I'm not exactly sure what they mean. If you ignore permissions on the non-boot drive that means that others can browse any of those files?
I'm assuming they mean you would have to change the permissions on the non-boot drive? But does that mean that only the original owner can change those permissions? Or can any user change permissions on a non-boot drive?
How is this different from user files on the boot drive? Can't you change permissions on your home directory?
I'm interested in moving my directory to the non-boot drive, so I'd like to understand the downsides. Especially anything related to user security.
Thanks.

Move User in PPOMA_BBP

Similar Messages

Maybe you are looking for