Latency ranges from <1ms to 4ms, each way.

Most of this "wrong usage" of my e-mail comes into play with my Clutter (a feature which I like) and Junk folders.

Just a quick (even quicker) look through them to make sure nothing important filtered in.

@scottalanmiller said:

@s.hackleman said:

I played with x10 equipment back in the day and it worked for me. I haven't used the cameras, but you can setup a motion sensor outside that turns on a light inside, and even turn on a few a few seconds appart like someone is moving through the house. It was reliable, affordable, and kinda fun to setup.

How very "Home Alone" of you 🙂

We had all of our network gear in our College apartment on a trigger with a switch at everyones desk. That way we could reboot the 802.11b router every 2 hours with out standing up. 😉

@Jason said:

@axigen said:

@Jason said:

Comodo provides them

Hi @Jason. Thanks for your note. I do not seem to see how I can get one for free. I am browsing their site and see that in the Free SSL section they only appear to provide 90 days 'free' for SSL certificates, no mention of S/MIME anywhere...

https://secure.instantssl.com/products/frontpage?area=SecureEmailCertificate&currency=USD&region=North+America&country=US

Really curious about how you found that 😉 on their website.

@travisdh1 said:

@dafyre said:

Assembly programs give me nightmares, lol.

I had an assembly language class in college. While I don't really enjoy it, I very much appreciate someone who does. Just... not.... this. It's a itty bitty little package of evil.

This isn't meant to be offensive, but I've never met anyone who liked Assembly who was not at least border-line autistic. I think it's because it takes a certain type of mind or memory in order to deal with in an extended way and enjoy it. I can deal with it, but I don't really enjoy it. For smaller programs I'd rather use C and strip everything down... still won't be as small, but certainly better than any extra high level language.

@mlnews said:

And this is the current site for the project...

https://github.com/Pash-Project/Pash

I love it when people port garbage to other platforms

It's all racked, I hear. Can't wait till we get it all fired up!

The "working data" that I mentioned that scrolls by quickly before our summary chart appears from this example looks like the below output. Generally we can ignore this, but it can be useful should there be an error to see where something has gone wrong.

$ yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirrors.lga7.us.voxel.net * epel: mirror.cs.princeton.edu * extras: mirror.lug.udel.edu * updates: mirror.trouble-free.net Resolving Dependencies --> Running transaction check ---> Package NetworkManager.x86_64 1:1.0.0-16.git20150121.b4ea599c.el7_1 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-adsl.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-adsl.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-bluetooth.x86_64 1:1.0.6-29.el7_2 will be an update --> Processing Dependency: libbluetooth.so.3()(64bit) for package: 1:NetworkManager-bluetooth-1.0.6-29.el7_2.x86_64 ---> Package NetworkManager-glib.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-glib.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-libnm.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-libnm.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-team.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-team.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-tui.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-tui.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wifi.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wifi.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package NetworkManager-wwan.x86_64 1:1.0.6-27.el7 will be updated ---> Package NetworkManager-wwan.x86_64 1:1.0.6-29.el7_2 will be an update ---> Package avahi.x86_64 0:0.6.31-14.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-autoipd.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package avahi-libs.x86_64 0:0.6.31-15.el7 will be updated ---> Package avahi-libs.x86_64 0:0.6.31-15.el7_2.1 will be an update ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-libs-lite.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-license.noarch 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-license.noarch 32:9.9.4-29.el7_2.3 will be an update ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.2 will be updated ---> Package bind-utils.x86_64 32:9.9.4-29.el7_2.3 will be an update ---> Package ca-certificates.noarch 0:2015.2.4-71.el7 will be updated ---> Package ca-certificates.noarch 0:2015.2.6-70.1.el7_2 will be an update ---> Package coreutils.x86_64 0:8.22-12.el7_1.2 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7 will be updated ---> Package coreutils.x86_64 0:8.22-15.el7_2.1 will be an update ---> Package cronie.x86_64 0:1.4.11-13.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7 will be updated ---> Package cronie-anacron.x86_64 0:1.4.11-14.el7_2.1 will be an update ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-19.2.el7 will be updated ---> Package cyrus-sasl-lib.x86_64 0:2.1.26-20.el7_2 will be an update ---> Package device-mapper.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7 will be updated ---> Package device-mapper-libs.x86_64 7:1.02.107-5.el7_2.1 will be an update ---> Package filebeat.x86_64 0:1.1.0-1 will be updated ---> Package filebeat.x86_64 0:1.2.1-1 will be an update ---> Package glibc.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package glibc-common.x86_64 0:2.17-106.el7_2.1 will be updated ---> Package glibc-common.x86_64 0:2.17-106.el7_2.4 will be an update ---> Package htop.x86_64 0:1.0.3-3.el7 will be updated ---> Package htop.x86_64 0:2.0.1-1.el7 will be an update ---> Package initscripts.x86_64 0:9.49.24-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7 will be updated ---> Package initscripts.x86_64 0:9.49.30-1.el7_2.2 will be an update ---> Package kernel.x86_64 0:3.10.0-327.13.1.el7 will be installed ---> Package kernel-tools.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package kernel-tools-libs.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package kexec-tools.x86_64 0:2.0.7-19.el7_1.2 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7 will be updated ---> Package kexec-tools.x86_64 0:2.0.7-38.el7_2.1 will be an update ---> Package kpartx.x86_64 0:0.4.9-85.el7 will be updated ---> Package kpartx.x86_64 0:0.4.9-85.el7_2.1 will be an update ---> Package krb5-libs.x86_64 0:1.13.2-10.el7 will be updated ---> Package krb5-libs.x86_64 0:1.13.2-12.el7_2 will be an update ---> Package libblkid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libblkid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libgudev1.x86_64 0:219-19.el7 will be updated ---> Package libgudev1.x86_64 0:219-19.el7_2.7 will be an update ---> Package libmount.x86_64 0:2.23.2-26.el7 will be updated ---> Package libmount.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package libssh2.x86_64 0:1.4.3-10.el7 will be updated ---> Package libssh2.x86_64 0:1.4.3-10.el7_2.1 will be an update ---> Package libteam.x86_64 0:1.17-5.el7 will be updated ---> Package libteam.x86_64 0:1.17-6.el7_2 will be an update ---> Package libuuid.x86_64 0:2.23.2-26.el7 will be updated ---> Package libuuid.x86_64 0:2.23.2-26.el7_2.2 will be an update ---> Package mariadb-libs.x86_64 1:5.5.44-2.el7.centos will be updated ---> Package mariadb-libs.x86_64 1:5.5.47-1.el7_2 will be an update ---> Package nss-util.x86_64 0:3.19.1-4.el7_1 will be updated ---> Package nss-util.x86_64 0:3.19.1-9.el7_2 will be an update ---> Package numactl-libs.x86_64 0:2.0.9-5.el7_1 will be updated ---> Package numactl-libs.x86_64 0:2.0.9-6.el7_2 will be an update ---> Package openldap.x86_64 0:2.4.40-8.el7 will be updated ---> Package openldap.x86_64 0:2.4.40-9.el7_2 will be an update ---> Package openssh.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-clients.x86_64 0:6.6.1p1-23.el7_2 will be updated ---> Package openssh-clients.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssh-server.x86_64 0:6.6.1p1-12.el7_1 will be updated ---> Package openssh-server.x86_64 0:6.6.1p1-25.el7_2 will be an update ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.2 will be updated ---> Package openssl-libs.x86_64 1:1.0.1e-51.el7_2.4 will be an update ---> Package polkit.x86_64 0:0.112-5.el7 will be updated ---> Package polkit.x86_64 0:0.112-6.el7_2 will be an update ---> Package procps-ng.x86_64 0:3.3.10-3.el7 will be updated ---> Package procps-ng.x86_64 0:3.3.10-5.el7_2 will be an update ---> Package python-boto.noarch 0:2.38.0-2.el7 will be obsoleted ---> Package python-perf.x86_64 0:3.10.0-327.4.5.el7 will be updated ---> Package python-perf.x86_64 0:3.10.0-327.13.1.el7 will be an update ---> Package python-pyudev.noarch 0:0.15-7.el7 will be updated ---> Package python-pyudev.noarch 0:0.15-7.el7_2.1 will be an update ---> Package python2-boto.noarch 0:2.39.0-1.el7 will be obsoleting ---> Package screen.x86_64 0:4.1.0-0.19.20120314git3c2946.el7 will be updated ---> Package screen.x86_64 0:4.1.0-0.23.20120314git3c2946.el7_2 will be an update ---> Package selinux-policy.noarch 0:3.13.1-60.el7 will be updated ---> Package selinux-policy.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package selinux-policy-targeted.noarch 0:3.13.1-23.el7_1.21 will be updated ---> Package selinux-policy-targeted.noarch 0:3.13.1-60.el7_2.3 will be an update ---> Package sudo.x86_64 0:1.8.6p7-16.el7 will be updated ---> Package sudo.x86_64 0:1.8.6p7-17.el7_2 will be an update ---> Package systemd.x86_64 0:208-20.el7_1.6 will be updated ---> Package systemd.x86_64 0:219-19.el7 will be updated ---> Package systemd.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-libs.x86_64 0:219-19.el7 will be updated ---> Package systemd-libs.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-python.x86_64 0:219-19.el7 will be updated ---> Package systemd-python.x86_64 0:219-19.el7_2.7 will be an update ---> Package systemd-sysv.x86_64 0:219-19.el7 will be updated ---> Package systemd-sysv.x86_64 0:219-19.el7_2.7 will be an update ---> Package teamd.x86_64 0:1.17-5.el7 will be updated ---> Package teamd.x86_64 0:1.17-6.el7_2 will be an update ---> Package topbeat.x86_64 0:1.1.0-1 will be updated ---> Package topbeat.x86_64 0:1.2.1-1 will be an update ---> Package tuned.noarch 0:2.4.1-1.el7 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.1 will be updated ---> Package tuned.noarch 0:2.5.1-4.el7_2.3 will be an update ---> Package tzdata.noarch 0:2015g-1.el7 will be updated ---> Package tzdata.noarch 0:2016c-1.el7 will be an update ---> Package util-linux.x86_64 0:2.23.2-26.el7 will be updated ---> Package util-linux.x86_64 0:2.23.2-26.el7_2.2 will be an update --> Running transaction check ---> Package bluez-libs.x86_64 0:5.23-4.el7 will be installed --> Finished Dependency Resolution --> Running transaction check ---> Package kernel.x86_64 0:3.10.0-229.7.2.el7 will be erased ---> Package kernel.x86_64 0:3.10.0-229.11.1.el7 will be erased --> Finished Dependency Resolution Dependencies Resolved

@garak0410 said:

@MattSpeller said:

@garak0410 said:

@scottalanmiller said:

What GPU does that have?

It is a custom GPU along the lines of a Nvidia GeForce 860M. So it isn't a gamers dream, but that said, I CAN game and game well on the go. I've not loaded GeForce Experience on it since this is a custom GPU and before the last firmware update, there were many unstable issues with both the Surface Book and Surface Pro 4.

I've played ALIEN: Isolation with details maxed but but a much lower resolution. Video Rendering speeds with Adobe Premiere have been quite impressive.

Does it have dedicated vram or does it sneak around like a thief in the night, hungry for some delicious ram

It has 1GB of dedicated, GDDR5 video RAM.

That is the only reason we got them. Sales wanted Surface Pro 4's, but lacked the video to support certain services. Got Surface Books and they faired a little better. Keep in mind, $350 of the cost is going into the keyboard whereas I think the Surface Pro 4 keyboards are a bit cheaper so the price difference is something to consider. If you don't need the VRAM, the Surface book isn't a much better device in my trials. The kickstand on the Surface Pro 4 (without the keyboard attached) essentially turns the Surface Book into using the keyboard as a flexible stand. I prefer the kick stand but using either device on your lap, I prefer the Book.

@scottalanmiller said:

@BBigford said:

@scottalanmiller said:

@BBigford said:

@scottalanmiller said:

@BBigford said:

@scottalanmiller said:

@BBigford said:

@scottalanmiller said:

@BBigford said:

@scottalanmiller said:

But that doesn't explain how the copiers POINT to the Exchange 2007 instance. How do they send the email to it in the first place? IP address?

Uses the hostname instead of IP... Some of the settings I've saw in the config:

Server FQDN: exchange-server.domain.com (older server with relay configured)
Server Port: 25
From Address: [email protected] (has a resource mailbox in Exchange, with a password to authenticate)

I can't think of any other settings off the top of my head...

Right... so what are the questions about how to do this with a Linux relay? You already have a dedicated relay. It's just swapping out the name of the OS and the cost and stability involved. Nothing "changes." You are already doing everything as if you had a Linux relay.

There's no more confusion. You answered it way up the thread already. 🙂

I just didn't know how the Linux relay tied to hosted Exchange, but you already said you can define that in the relay by entering credentials for the hosted instance.

They tie through the magic of email 🙂

No, you wouldn't really use the credentials, that's pretty silly. You just... relay. Email is WAY simpler than I think you are picturing. None of that is necessary.

ok, so you point the Linux relay at the IP issued to the O365 instance, with a transport rule setup on the O365 instance to accept the traffic from the relay?

No... still way too complex. You do nothing. I literally listed all of the steps.

Email doesn't need any of those things. It doesn't get pointed anywhere.

How would the Linux relay know how to pass on the traffic from the copier to the hosted Exchange instance then...?

How does email ever get to where it is going? It just sends the email. It looks up the server's MX record. It's how every email everywhere gets delivered.

Oh ok, so the relay relies on MX records found in DNS?

Of course, that's how all email is sent that is not internal to the server itself, which wouldn't actually be email. So to simplify... yes, that is how all email is sent.

Sorry that took so long. Thanks for explaining.

I was overthinking it. It's been a long week. I was overthinking it.

...and after people tearing me down all day about SQL and Apple Mail, I'm pretty brain dead. 😐

@dafyre said:

@johnhooks said:

@scottalanmiller said:

@johnhooks said:

@dafyre said:

Why are there two NFS servers to start with? (Just curious)

They're only 20-24 drives each. About 50TB per server. All of the engineer's home folders are on them so one isn't enough.

At some point down the road we are going to implement a clustered storage but we just don't have the time right now because of time constraints for this project.

Gluster could be done in an hour. I have how tos posted for both NFS Home Automounting and Gluster 🙂

Ha yes anywhere else it would take no time at all. We have so much red tape to jump through it's ridiculous.

Start setting up and testing a Gluster Cluster (see what I did there?)... and maybe by the time you get it set up and tested, you'll be done playing jump rope with the red tape.

The other issue is the NFS servers we have right now are applicances (was done before I got here I've only been here less than a month). We can install certain things, but too much and we might lose "support."

We have to have these inspectors come in and approve stuff if any changes are made to this network. It's ridiculous.

In this case, it was a matter of the settings during the restore.

Under GENERAL you had to select your source and destination as normal. Destination was changed so that it was the new History file. Under FILES you updated the DB and LOG files to reflect the new DB, otherwise you would over write the originals.

This is where they borked it. They didn't mention FILES only going to OPTIONS, and there is where they mentioned updating the file names. The main discovery was that you need to uncheck LEAVE Source database in the restoring state.

When I emailed them about removing the 'borked' databases I had created the called me back. I mentioned it to the fellow and we had a short discussion on the matter where he took notes and agreed that the directions were incorrect. When I got to the part about unchecking LEAVE Source database in the restoring state he mentioned that he uncheck Take tail-log backup before restore

Hope this helps.

0_1460118217976_2016-04-08 08_22_29-NTG - SSI-SQL01 - Connected.png

@RoopanKumar said:

@scottalanmiller that will be side by side learning while facing any AD related issue or any task related i have to work on.

asking now apart from this what should i learn or what can i improve

Explore other virtualization platforms such as XenServer, KVM, etc...

i use what is now PCM. Used to be global, then comp usa, then tiger direct, now PCM...

I use https://www.wetransfer.com/ myself. I don't need to transfer huge files and when I do, I use a Dropbox link. I got a TB with them, so uploading and sharing is no biggie for me. I must say, though... transfer.sh is pretty cool.

@Jason said:

@Dashrender said:

@brianlittlejohn said:

@LAH3385 Once you get the upgrade it converts your Win7 key to a Win 10. So you have to upgrade at that point since you are no longer licensed for win7

Well - that's sorta true.

Assuming you're upgrading a Windows 7 Pro legally licensed machine, you can legally use downgrade rights to install Windows 7 again.

That's not downgrade rights.. You own both. You have an upgrade which "sits" on top of the full version. You have never needed downgrade rights to go back to a previous version from an upgrade.

That's an interesting way to look at it. Without reading the Windows 10 license I'm not sure if that's accurate or not.. but definitely makes sense. In either case, you do have the right to use Win7 Pro still, once you upgrade to Windows 10 Pro.

@PSX_Defector said:

@Brains said:

It's just bad timing and we are in the healthcare market and subject to Texas's Workers Compensation craziness, so its been a rough year or two for us.

Then you best not be using PPTP. Compliance audits will come down on you hard.

If anyone will be at Lone Star PHP in Texas this weekend, let me know. Ill be there and will buy you a beer.

I thought you were talking about Big Texas Beer Fest, which was last weekend.

I was planning on trying to use L2TP and darn for missing the Beer Fest. That's my kind of place! Well Whiskey Fest would be MORE my kinda place haha.

I also wanted to ask you about this as well:
3 Year Warranty & InControl 2 for Balance One/Balance One Core

I really doubt the cloud management would be useful for us since we only have 2 local devices (one active at a time). We will get free firmware updates AFAIK, so I don't really know why that is mentioned. Is there any reason we should get this package? 25% price increase for 2 additional years of warranty doesn't seem worth it to me.

@aaronstuder said:

We are using flowroute, and they provide CNAM Lookup at the same price as OpenCNAM - Any reason to use OpenCNA over the one my provider provides?

No reason to use one over the other.