@Breffni-Potter said:

If you don't own the PC why do you have local admin.

I think that you'll find that if you have the local admin... you do own the PC 😉

@wirestyle22 said:

@travisdh1 said:

@wirestyle22 said:

@travisdh1 said:

@wirestyle22 said:

This is all interesting stuff. I can't wait to finish my server build. Here it is if you're interested: http://pcpartpicker.com/p/9gPqjX

Is this server for a home lab?

Yessir

Nice!

I'm going to experiment with SSD caching on a software raid using ZFS Striped Mirrored Vdev’s as well as a ton of VM testing.

Just curious, which hypervisor are you planning to use? I'm assuming you'll be passing the drives through to a vm running the storage?

@DustinB3403 said:

@coliver said:

You can set VMs to run at boot too. That doesn't solve the issue but it could alleviate some downtime.

Setting them to start at boot breaks HA and isn't recommended.

Right, HA would be a separate mechanism to handle this. In this case it sounds like it may be a lab server so HA isn't necessary. Although that is good info if I do work in an HA setup.

I updated the firmware and its working now. Thank you to all who helped.

Oxford here ..
s

@Dashrender said:

When I was first hanging my own shingle as an IT consultant we were suggesting to all of our clients that they should purchase and install AV everywhere.

Even in the 1990s that was ridiculous. How does someone manage to get enough money to start a business or hire an IT consultant but doesn't have the brain power to use AV?

A third party uninstaller is often necessary for SEP. This is one of the reasons that people use to show that it is legitimately classified as malware. Once you desire to remove it and it will not let you do so, you have a malware situation.

I agree, business world needs to just image and be done with it.

So I did that and found the pertino client file was already in the root directory from when I ran the smb client get command. Ha! Thanks again!

@LAH3385
Eventually I will end up where you are suggesting - though I currently use Dell's Appassure Replay, not Veeam.

I am going to try installing the "server" software on my workstation just to make sure they haven't limited it in any way.

@Dashrender said:

The whole point of my post was simply to ask if XO (or XS) was really something normal IT admins should be using.

Knowing that you are pushing this product (XO) is definitely helpful toward that end.

I got the answer I was looking for, which is - yes it's definitely something IT admins should be using or at least learning.

Perfect timing...

http://community.spiceworks.com/topic/1433805-vmware-patches-esxi-fusion-payer-and-workstation-vulnerability

I never do anything formal. In the setup process a lot of things get stressed anyway. Normally I am using the server quite a bit before turning it over to users so I do not tend to worry about further testing.

Especially if you are dealing with a virtualized platform, it's been doing a lot of things before this point.

There are systems that do this with version control. You could do this with GIT or Mercurial, in theory. But eventually a human always has to sort things out.

It is a very popular project.

And adding Topbeat too, to send performance information to the ELK system as well.

Yes it's sorted. Sadly, the 2003 iso I had it didn't help me.

I resorted to a Win7 iso to set the first partition to active so it would boot, problem solved.

Thank you very much. Its working now.

@hobbit666 You can install anywhere. On the same server is fine, on a different server is fine. It connects over the XAPI interface, so very flexible.