IMO, it is better to be safe than sorry. Pay the employee for the time worked and then discipline the employee for their violation of the HR policy.

@scottalanmiller said in Protecting companies from hourly employees:

At best you pay them once, and only once. But if HR policy is correct, I don't believe that you have to.

I hope that you have a good legal team on staff.

Going home and intentionally logging back in to work would be fraud - intentionally stealing time from the business.

You have a warped POV. How is working from home, even if unauthorized, "stealing time" from the business?

Your HR policy cannot override the DOL rules regarding employee compensation. What it can do is protect you when it comes time to terminate the employee for violations of said policy.

How large is the VM? I know you probably don't want to, but can my delete the other snapshot created by XO?

@scottalanmiller said in Protecting companies from hourly employees:

The issue is around people not reporting, though. So in the given scenario, no reporting system would help.

With an appropriate HR policy in place, the issue then becomes one of monitoring for non-compliance. It's the manager's job to know that the employee is / will be hitting OT if they continue working at the current pace.

Managements failure to monitor and take action becomes implicit approval for the employee to continue working and getting OT.

Should still be under warranty, correct?

XO v5.50 was just released with this functionality included.

Time to upgrade and check out the new features!

@DustinB3403 Seeing the same thing here. Looking in the logs, this is the likely culprit:

Dec 20 08:22:57 xo-5 xo-server[10726]: Tue, 20 Dec 2016 14:22:57 GMT xo:api [email protected] | backup.scanDisk(...) [20ms] =!> Error: spawn vhdimount ENOENT

@DustinB3403 The 2nd line is just your current command. So it appears that node / xo-server are running as root.

@DustinB3403 You could temporarily build from next-release.

@DustinB3403 said in Xen Orchestra - Permissions Issue - File level restore:

Seems to be specific to that backup, as I am able to restore files to my file server now without issue.

So a few things to we should try to compile into the update script, check for fuse, and install it if its not there.

Also for libvhdi-utils

@DustinB3403 No. There's an active thread over on the XO forum. I was just getting ready to post over there. Think I may have found the cause.

There have been some recent threads on this topic. Perhaps you could review them using the forum's Tags feature.

This looks pretty decent, and it's free as long as you don't need to clipboard syncing.

https://www.clipboardfusion.com/

Currently, those of us building XO from source can't easily move the XO config from one VM to another. See discussion here with @olivier. A simple change to this line of the XO source would make this feature available to us.

Any thoughts on the best way to implement this so that we can have access to this feature without breaking future builds?

The local file can be found in /opt/xo-web/src/xo-app/settings/config

@brandon I recently tested the script on Ubuntu Server 16.10 and it worked fine. Post the error shown so that we can see what is happening.

There is one known issue that you will need to deal with unless you build with the next-release branch.

@brandon said in Xen Orchestra on Ubuntu 15.10 - Complete installation instructions:

@DustinB3403 Yes I did: sudo su, sudo ./script

To ensure that you are using the most recent version of the installation script, it is recommended to install using --

sudo curl https://raw.githubusercontent.com/scottalanmiller/xenorchestra_installer/master/xo_install.sh | bash

Need to determine why git clone -b stable https://github.com/vatesfr/xo-web is failing.

It's their filtering extension that installed without permission last year. It doesn't offer any options to configure its behavior. For me, the reputation icons never properly showed in Google, so I have disabled it for the time being.

@JaredBusch Ok... just seems like you are trolling @DustinB3403. He's trying to help out, so why the constant need to bash him?