https://www.usatoday.com/story/tech/2017/09/05/ftc-settles-lenovo-over-built-snooping-software-scanned-users-computers/632775001/

@ccwtech FWIW, i see similar behavior when viewing this page from both home and work. No JS popups though...

https://support.mozilla.org/en-US/kb/i-found-fake-firefox-update

@ccwtech The page has been opened for about 15 mins without any popups. FWIW, the page eventually finished loading after between 10 and 15 mins.

Not sure of your timeframe, but XOSAN is currently in beta.

There are likely other local storage solutions that will work. Tagging @olivier and @scottalanmiller for additional input.

How much storage do you need (allow for future growth)? Is HA required? If not, you could likely get away with using XO's Continuous Replication feature.

@olivier said in Xenserver and Storage:

would you like to add hosts in the future? (if you think it's yes, HA lizard is out of the equation)

I believe HA Lizard is not limited to two hosts.

After upgrading to Yarn 1.1.0, the majority of the warnings are gone. For me, all that remains is

[4/5] Linking dependencies...
warning "[email protected]" has unmet peer dependency "prop-types@^15.5.4".
warning The case-insensitive file /opt/xo-web/node_modules/react-bootstrap-4/node_modules shouldn't be copied twice in one bulk copy

and I haven't investigated those yet.

@DustinB3403 Have you read the "something for everyone" link? Citrix has changed the rules regarding availability of updates.

Is the directory in your path? What do you get from echo $PATH?

@travisdh1 Wow... didn't realize it would be that simple. So just update the subnet on all devices? To test this, can I just implement the change on my PC or does it need to occur everywhere?

@jaredbusch Sorry if I wasn't clear. I meant to update the wireless router to start handing out the matching IPs for 192.168.1.x instead of 192.168.169.x.

Problem resolved. The server was previously been hooked up to a Dell Powerconnect. Switched back to it and everything is now fine.

Updated the script earlier today to deal with a change in the yarn build process.

@bnrstnr If the errors are related to Yarn, then see this prior forum post --
https://www.mangolassi.it/topic/12809/xen-orchestra-community-edition-installing-with-yarn/123

@bnrstnr Looks like your XO install is very out of date.

Also not have the service would indicate that you didn't install using the install script from this foru m. m

@jaredbusch I have the same issue with AutoIt. PITA to deal with because Webroot also triggers on executables created with AutoIt.

Dealt with this previously here. Initially they stopped flagging it. But then they reneged and refused to change it.

Already a thread on this. :smiling_face_with_open_mouth_smiling_eyes:
https://www.mangolassi.it/topic/16904/cloudflare-launches-privacy-first-dns-service/

@kju said in Xen Orchestra - Community Edition - Installing with Yarn:

how can i update to 5.18 ?
the script for updating
sudo curl https://raw.githubusercontent.com/Jarli01/xenorchestra_updater/master/xo-update.sh | bash -s -- -f
stays on 5.17

Not enough details here to know how to help. You could post the output from the console window showing the results from running the above command.

Also, show us the contents of the /opt directory.