Changing Linux group permissions 3

[telfire]

thread940-1788080

Janni78 - this was a thread you responded to that is now closed.
I was hoping you could share how you do this...
I do not want to use chmod, rather I would like to add Administrator to the vmpro group - if that is the way to solve what is happening below.
Apparently during my migration from Windows to Linux, all the existing mailboxes are set for Administrator.
When someone leaves a message, it does not write into the account folder.
I created a new user, left a message and it works fine. When I look at the 2 mailboxes in WinSCP, the only difference is the existing non-working user has the properties Group: Administrator and Owner: Administrator. The working mailbox has vmpro for both of those... Make sense?

APSS-SME
ACIS-SME
ACSS-SME
CTP+

 

[derfloh]

usermod -a -G examplegroup example username

As far as I understand you, you imported the backup files from Windows via WinSCP, so that all folders are owned by "Administrator"?

Then it will not help to add Administrator to the vmpro group. The only thing that would help is to add vmpro to the Administrator group. But that's not why there are separate groups...

Better would be to set vmpro user and group as the owner of the imported files/folders.

chown -R vmpro:vmpro /opt/Avaya/vmpro/Greetings

Please check the path if it is exactly correct.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[telfire]

mic drop!!!! Boom!
You are the man. Thank you!

APSS-SME
ACIS-SME
ACSS-SME
CTP+

 

[janni78]

That's the way to do it.

Avaya really should have created a user designed for moving files with SCP to VM Pro, the File Manager just isn't a good option.

"Trying is the first step to failure..." - Homer

 

[IPGuru]

I think Avaya are assuming that the opeators will have no experience beyond basic windows users (thayt is the polite way of saying they thing engineers are idiots) & have tried to keep the linux underpinning hidden.

Even Knowing how even engineers will run scared when they here the L word for the lasty time I think Avaya are doing us a great dis-service.

Fortunatly some of us are quite experienced with Linux (i do not have Windows at home!) so know how to fix their short-commings


Do things on the cheap & it will cost you dear

 

[derfloh]

Anyway... We can be happy that Avaya gives us access to the full Linux shell.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/