Blake

Yeah some guy named Tasman just left it here. 

If your running the controller app or the cloudkey on your network somewhere, that handles the roaming.

Was more getting at, the fact that if it is production, it should be on a planned life cycle (i.e. purchase the extended support for X years and retire the system once that support period end).

the difference in cost to the end user is connecting one or both of the UNI-V ports to the existing wiring. 
 
sure there 'may' be trenching required, but in the 10+ places that I have overseen getting installed at work, not a single one required to be re-trenched, sure some of the pits needed to be cleared of mud, but the trenches where fine.
 
We didn't even spend $5000 at work to modernise each branch's network infrastructure. Just grab a ~$500 network cabinet, throw it on the wall, replace existing Ethernet runs with newer ethernet (about $1000), grab a cisco box that supports ethernet and 4g (approx $1000). and thats that, would do it cheaper if NBN had actually acceptable SLA's / their contractors weren't shit.

the difference in cost to the end user is connecting one or both of the UNI-V ports to the existing wiring. 
 
sure there 'may' be trenching required, but in the 10+ places that I have overseen getting installed at work, not a single one required to be re-trenched, sure some of the pits needed to be cleared of mud, but the trenches where fine.
 
We didn't even spend $5000 at work to modernise each branch's network infrastructure. Just grab a ~$500 network cabinet, throw it on the wall, replace existing Ethernet runs with newer ethernet (about $1000), grab a cisco box that supports ethernet and 4g (approx $1000). and thats that, would do it cheaper if NBN had actually acceptable SLA's / their contractors weren't shit.

Yeah... this is alot more common then you think. has to do with MSP's doing things on the cheap and internal IT not knowing anything about security. When I started where I am we had the same, but it was fine because "the FSMO roles are on the other DC". Needless to say this wasn't fine at the next PCI audit.
 
But yeah just because something can be installed on a DC doesn't mean it should be. if it is two separate virtual hosts you're fine.
 

Nah it's fine, you would need to virtualise the pfsense box. Modem -> pfsense first then to the rest of the network via a separate interface and you could throw in a virtual interface to connect directly to the minecraft server.
 
If you wanted you could throw the minecraft server directly on the pfsense box, would just need to get access to the BSD host os.

If i recall he said something like "we getting someone from the vendor to install because it's above our heads"

If i recall he said something like "we getting someone from the vendor to install because it's above our heads"

Not an expert with HIPPA, but I doubt vets care about it...?
 
Anyway you are fine with azure, so i'd assume your AWS is also good: https://www.google.com.au/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=0ahUKEwiArIKH5ujRAhUHHJQKHeVzD2kQFggtMAE&url=http%3A%2F%2Fdownload.microsoft.com%2Fdownload%2F8%2F4%2F8%2F8483b6a9-1865-4d17-b6f1-5b66d5c29b10%2Fwindows%20azure%20hipaa%20implementation%20guidance.pdf&usg=AFQjCNGj_DRHalHH6Icw3EPyRNOcMbNqHA&sig2=F0_0t9pCl2vuonXCZAFqdQ
 
Your not really going to find cheaper then AWS/Azure, for cloud. Explain to your client that the 99% uptime versus the 99.99% uptime from azure/aws basically covers the difference.
 
Next ask him to figure out if he wants redundant hosting locally, if he does the difference in needing 2x every second item of hardware will push him to cloud. if not the cost of a single hours downtime will likely push him to the cloud. Basically unless you are at the size that needs to onsite it functions, cloud based AaaS/IaaS/XaaS will win hands down.
 
In saying all this, CRM, proprietary vet software, Quickbooks, not a heavy load.

1. No-one cares it's the internet.
2. Gods of egypt was shit but it was the only one that was shit in a good way.
3. Rest of these films where just shit, this is well established fact at this point.
4. this is the internet, for all you know you could have been arguing with a dog.
5. Sure on a technicality your are right there is going to be a loss of quality as there is a lossy codec being used, but it will not be noticeable, unless OP was re-encoding then re-encoding then re-encoding etc etc, multiple times.

fyi, there doesn't need to be a 'batch' because there is handbrakecli. just do up a powershell script and then let it go nuts. heck if you know how to run bash there is a bash script for this exact thing on github.
 
That being said, you do have you nas as an APIPA address....
 
Also new version lets you choose between a single file and a batch job straight up.

it's ccna, packet tracer is all you need.

it's ccna, packet tracer is all you need.

it's ccna, packet tracer is all you need.

No, with RAID 5 you have like a 75% chance of the array failing before you can rebuild in a failure. Just go look at http://www.raid-failure.com/raid5-failure.aspx
Windows (server at least) has multiple options, and does support LACP go have a look at https://gallery.technet.microsoft.com/windows-server-2012-r2-nic-85aa1318 for a simplified summary of nic teaming.

if by "go to" you mean for personal use and small businesses. I'd even go so far as to say, Dell SonicWall (or insert brand names' equivilant) is the defacto.
 
Why? because when there are 3 of you and there are 100+ sites when it breaks you call dell and they sort that shit out. when the machine pfsense runs on breaks while it is a relatively simple fix (repair/replace, reimage, reconfigure, or even use a backup to a new system) that is still far too much work to do during a potential outage (yes you should have some sort of EIGRP deployed to make use of redundant links, but management wont always approve the budget), especially considering your are already over worked.
 
Too be honest this may have changed, i'd assume it has, last time I looked at pfsense in any detail was 2007 and they didn't even support OSPF back then (seriously RIPv2 only, who has time to manage a network line that?).

Wow...
 
1. Not everyone has partol reads. Backups are fine, but if you look at the ATO... backups still didn't protect them from having to restore 1PB of data. Your looking at a long downtime.
2. Management tend to not always make the correct decision/think that some things are acceptable risks. so may not approve HA or correct DR plans.
 
which brings me to:
Sure I do admit that these numbers are theoretical, never said you where wrong about real world, but you must be insane if your not at least going to choose more then 1 disk redundancy for anything mission critical. A lot of IT people know about HA and DR (a lot talk about it but don't actually know it), but you'll find very few of them understand that spending that $1m on a spare SQL server + SAN isn't their choice, its management. So go ahead and set up HA/DR on that imaginary Server. 

if by "go to" you mean for personal use and small businesses. I'd even go so far as to say, Dell SonicWall (or insert brand names' equivilant) is the defacto.
 
Why? because when there are 3 of you and there are 100+ sites when it breaks you call dell and they sort that shit out. when the machine pfsense runs on breaks while it is a relatively simple fix (repair/replace, reimage, reconfigure, or even use a backup to a new system) that is still far too much work to do during a potential outage (yes you should have some sort of EIGRP deployed to make use of redundant links, but management wont always approve the budget), especially considering your are already over worked.
 
Too be honest this may have changed, i'd assume it has, last time I looked at pfsense in any detail was 2007 and they didn't even support OSPF back then (seriously RIPv2 only, who has time to manage a network line that?).

Yeah, they are, but if this is just a bunch of stuff you downloaded, sure who cares if it failed. But, lets say you store you CRM/Finance database on it? yeah no.
 
Sure having a single record being corrupted or something might not, but it also might be a massive deal. then consider how the disk failed. considering most of the time disks are purchased together/at the same time from very similar batches, so.... if you loose the 2nd disk then your up shit creek without a paddle. then you need to make sure you have DR or backups. which, lets face it, most organisations (not their it departments) don't fund/invest in.
 
Also in real life you where probs using an actual enterprise disks, which is what mitigates this, they are normal 10^15+ where as WD RED 3TB disks listed are 10^14.

Folder redirection.
 
Basically, use GPP to configure also:
open GPMC.msc, make a new or edit the appropriate GPO, then navigate to:

 
Haven't done it in a while (it's a set and forget kind of thing), but I remeber there being a 'bug' with redirecting to \\path\to\user\profiles\%username%\Desktop I remember there being an issue where this failed, but I am assuming this has been patched to you can scale correctly across an organisation.
 
EDIT: Should also add that roaming profiles are rearely used in the real world. if you change computer and have a 50GB OST to download and it takes 1hour to login, your not going to be a happy chappy.

Spinning up a new Windows build is trivial, and having it patch itself is also very easy. Having it also call a configuration script (Powershell DSC) is also fairly trivial.
 
Oh look you now have a fully patched system. you can now suspend the the old system/systems, and depending on requirements keep to destroy them.
 
Yes but there are a lot of other issues that develop from having extreme uptimes, even when virtualised.
 
tl;dr treat your servers like cattle not pets.

I'll admit it is rare, and alot of applications (read this as shitty devs not knowing how to dev), don't provide proper configuration options. But ALOT do provide a simple msi installer and use a config file. It's a simple matter of transferring the config file across after a silent install.
 
Also I wouldn't do this with windows services, most of them are cluster-able from the get go, why bother? DHCP for example, just go wild, install updates, use powershell to update one then the other.
 
Once you have done it once, you'd be surprised at how easy it is. Soon you'll discover what bliss is when it's patching night and you go home @ 5 and not remote in to do the patching.
 
I've got this process semi automated at this point (with PowerCLI and PowerShell/DSC and Shitty batch scripts, if you use Hyper-V just get rid of the PowerCLI, if you hyper visor is linux based that's a hole other game), It should only be a few months before I have the entire setup automated (assuming I can find the time to work on it).

makes sense, average apple users don't even know what routers do

How come I never have these problems? Do people on this forum not know how to PC?