Shut the system down pull the failed drive and the hot spare turn it back on. You should be up and running on a degraded RAID array

This deployment as stated he is also most likely illegal. You are not allowed to simply stream whatever you want. The original FM re-broadcast was actually illegal. I am basing that on the fact that there are 10 speakers so most likely the size of the office is too large for the small business allowance

@JasGot said in Taking over IT for a small business:

@JaredBusch How so?

Go back and count the steps that you just listed.

@JasGot said in Taking over IT for a small business:

@Dashrender said in Taking over IT for a small business:

In this customer's - from a power POV, I could easily designate a single machine as an always on machine for this purpose

I always set one or more machines to power on at 10:00pm (bios)
One if they prefer not to leave them on, then I use WoL to power the others up when I need to (updates).

All if they don't have a preference and it's a small office.

That is a crazy amount of work I don’t wanna do that

Bleh

@Dashrender said in Taking over IT for a small business:

@JaredBusch said in Taking over IT for a small business:

@Dashrender said in Taking over IT for a small business:

@Pete-S said in Taking over IT for a small business:

@Dashrender said in Taking over IT for a small business:

How are you dealing with machines that people turn off at night?

Change the defaults in windows to "sleep" instead of "shutdown".
Send Wake On LAN packet if you need to start it.

Remove hibernate unless it's a laptop. Frees up some disk space too.

Also, basically set all machines to go to sleep after X minutes of inactivity. It could be an hour or whatever. Saves on power and if someone forget to turn it "off" (sleep) it will automatically sleep.

2/3's of my fleet is laptops, so yeah.. wake-on-lan is not an option, I'm not sure sleep is even wake-able on a laptop on WiFi?

WoL is useless unless you have a known on system to send commands from

In my environment it would be a server or my desktop to to never sleep.

In this customer's - from a power POV, I could easily designate a single machine as an always on machine for this purpose - I love using ScreenConnect to send WoL commands to other sleeping machines.

Stop conflating your stuff. The point here is for not your environment, specifically.

I mean yeah, ideas can work both places. but focus please..

@Dashrender said in Taking over IT for a small business:

@Pete-S said in Taking over IT for a small business:

@Dashrender said in Taking over IT for a small business:

How are you dealing with machines that people turn off at night?

Change the defaults in windows to "sleep" instead of "shutdown".
Send Wake On LAN packet if you need to start it.

Remove hibernate unless it's a laptop. Frees up some disk space too.

Also, basically set all machines to go to sleep after X minutes of inactivity. It could be an hour or whatever. Saves on power and if someone forget to turn it "off" (sleep) it will automatically sleep.

2/3's of my fleet is laptops, so yeah.. wake-on-lan is not an option, I'm not sure sleep is even wake-able on a laptop on WiFi?

WoL is useless unless you have a known on system to send commands from

Answering my own question, it runs as system.

@Dashrender said in VOIP.ms more secure:

Just received this notice.

I'm not sure how this is more secure? I would assume you would have to know the password or be on forwarding through the listed registration IP to be able to use the sip trunk. How does limiting this to this specific IP or POP help? if you have the password, can't you just log in and change it to whatever you want?

Registered SIP trunking is not the recommended method by a lot of systems. Yeah, it makes magic with NAT most of the time, but still.

So by adding this, you can now securely use IP based trunking on VoIP.ms.