What Are You Doing Right Now
-
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller Just felt like suiting up or special occasion?
Had a meeting.
-
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
This, to me, sums up Windows 10 and Windows 2016...
New install, totally clean and vanilla... Install SQL Server 2017...
and then...
How does this area look for you:
Its' blank, because that's how Windows is by default. If search doesn't work by default, it shouldn't be presented as the default mechanism, and it shouldn't use the same interaction that didn't used to require indexing. I'm trying to do the same task they told us was "how the start button works" since Windows XP. And it doesn't work, full stop.
If every user has to modify Windows to make it work, that's just another way of saying it's broken.
The index locations should not be blank. Blank is not default. Indexing is on to those locations by default.
Trust me, this is default. Just installed, nothing changed. This is as default as Windows gets. Not even domain joined.
I suppose there are two defaults then. Fresh install of Win10 results in indexing already working set setup as pictured. I know this because I had just installed a bare-metal install.
This is 2016
Ohhhhh sorry, I thought Win10 this whole time. I don't know what 2016 is by default, I never use the search there.
-
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
This, to me, sums up Windows 10 and Windows 2016...
New install, totally clean and vanilla... Install SQL Server 2017...
and then...
How does this area look for you:
Its' blank, because that's how Windows is by default. If search doesn't work by default, it shouldn't be presented as the default mechanism, and it shouldn't use the same interaction that didn't used to require indexing. I'm trying to do the same task they told us was "how the start button works" since Windows XP. And it doesn't work, full stop.
If every user has to modify Windows to make it work, that's just another way of saying it's broken.
The index locations should not be blank. Blank is not default. Indexing is on to those locations by default.
Trust me, this is default. Just installed, nothing changed. This is as default as Windows gets. Not even domain joined.
I suppose there are two defaults then. Fresh install of Win10 results in indexing already working set setup as pictured. I know this because I had just installed a bare-metal install.
This is 2016
Ohhhhh sorry, I thought Win10 this whole time. I don't know what 2016 is by default, I never use the search there.
I'd prefer not to, but the Start Menu is horrible and Microsoft has been pushing that using the GUI is wrong and that you should just type in what you need after hitting "Start" for over a decade. But it's been broken for half that time. So their theory of how to access things plain doesn't work.
-
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
This, to me, sums up Windows 10 and Windows 2016...
New install, totally clean and vanilla... Install SQL Server 2017...
and then...
How does this area look for you:
Its' blank, because that's how Windows is by default. If search doesn't work by default, it shouldn't be presented as the default mechanism, and it shouldn't use the same interaction that didn't used to require indexing. I'm trying to do the same task they told us was "how the start button works" since Windows XP. And it doesn't work, full stop.
If every user has to modify Windows to make it work, that's just another way of saying it's broken.
The index locations should not be blank. Blank is not default. Indexing is on to those locations by default.
Trust me, this is default. Just installed, nothing changed. This is as default as Windows gets. Not even domain joined.
I suppose there are two defaults then. Fresh install of Win10 results in indexing already working set setup as pictured. I know this because I had just installed a bare-metal install.
This is 2016
Ohhhhh sorry, I thought Win10 this whole time. I don't know what 2016 is by default, I never use the search there.
I'd prefer not to, but the Start Menu is horrible and Microsoft has been pushing that using the GUI is wrong and that you should just type in what you need after hitting "Start" for over a decade. But it's been broken for half that time. So their theory of how to access things plain doesn't work.
On Server, I always pin what I use to the task bar after I install it. I don't use the start menu on servers.
-
Running Windows Updates and Deploying Chocolatey
-
Cursing Windows Update. 3 laptops just taken out of the box, 1 says it's trying to update to 1709, the other two are properly going to 1803
-
@travisdh1 said in What Are You Doing Right Now:
Cursing Windows Update. 3 laptops just taken out of the box, 1 says it's trying to update to 1709, the other two are properly going to 1803
Same thing just happened here.
-
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
This, to me, sums up Windows 10 and Windows 2016...
New install, totally clean and vanilla... Install SQL Server 2017...
and then...
How does this area look for you:
Its' blank, because that's how Windows is by default. If search doesn't work by default, it shouldn't be presented as the default mechanism, and it shouldn't use the same interaction that didn't used to require indexing. I'm trying to do the same task they told us was "how the start button works" since Windows XP. And it doesn't work, full stop.
If every user has to modify Windows to make it work, that's just another way of saying it's broken.
The index locations should not be blank. Blank is not default. Indexing is on to those locations by default.
Trust me, this is default. Just installed, nothing changed. This is as default as Windows gets. Not even domain joined.
I suppose there are two defaults then. Fresh install of Win10 results in indexing already working set setup as pictured. I know this because I had just installed a bare-metal install.
This is 2016
Ohhhhh sorry, I thought Win10 this whole time. I don't know what 2016 is by default, I never use the search there.
I'd prefer not to, but the Start Menu is horrible and Microsoft has been pushing that using the GUI is wrong and that you should just type in what you need after hitting "Start" for over a decade. But it's been broken for half that time. So their theory of how to access things plain doesn't work.
On Server, I always pin what I use to the task bar after I install it. I don't use the start menu on servers.
Yeah, but where is it after you install it
-
@scottalanmiller said in What Are You Doing Right Now:
But it's been broken for half that time.
It has never worked immediately after install. It is an index service that takes time to run.
I use hit start and type almost exclusively because the start menu is so damned bad.
I never have the problems you always claim are broke by default.
Yet, I never change any defaults.
-
Installed Hyper V 2016 Server on a Dell R220. Now to figure out how to connect to it since I cant just type in ip address, username and pw from HyperV manager.
-
Playing with my new Yealink T46S. This phone is on point. Such a smooth interface.
-
Not Watching the clock . . .
-
@fuznutz04 said in What Are You Doing Right Now:
Playing with my new Yealink T46S. This phone is on point. Such a smooth interface.
It is a solid phone. I need to spin up a clean FreePBX 14 install and see if the LE certs work again or not.
This is a really annoying bit as I had jsut started migrating all my clients to encrypted VoIP when it all fucking broke.
-
@jaredbusch What's not working with LE?
-
@fuznutz04 said in What Are You Doing Right Now:
@jaredbusch What's not working with LE?
Yealink phones (all models I have tested) will not talk over TLS to a FreePBX 14 system that used the built in LE cert generation process.
-
@fuznutz04 said in What Are You Doing Right Now:
@jaredbusch What's not working with LE?
https://mangolassi.it/topic/15274/yealink-t4xg-phones-will-not-talk-to-freepbx-14-over-https
But it is now the S models also.
-
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
@obsolesce said in What Are You Doing Right Now:
@scottalanmiller said in What Are You Doing Right Now:
This, to me, sums up Windows 10 and Windows 2016...
New install, totally clean and vanilla... Install SQL Server 2017...
and then...
How does this area look for you:
Its' blank, because that's how Windows is by default. If search doesn't work by default, it shouldn't be presented as the default mechanism, and it shouldn't use the same interaction that didn't used to require indexing. I'm trying to do the same task they told us was "how the start button works" since Windows XP. And it doesn't work, full stop.
If every user has to modify Windows to make it work, that's just another way of saying it's broken.
The index locations should not be blank. Blank is not default. Indexing is on to those locations by default.
Trust me, this is default. Just installed, nothing changed. This is as default as Windows gets. Not even domain joined.
I suppose there are two defaults then. Fresh install of Win10 results in indexing already working set setup as pictured. I know this because I had just installed a bare-metal install.
This is 2016
Ohhhhh sorry, I thought Win10 this whole time. I don't know what 2016 is by default, I never use the search there.
I'd prefer not to, but the Start Menu is horrible and Microsoft has been pushing that using the GUI is wrong and that you should just type in what you need after hitting "Start" for over a decade. But it's been broken for half that time. So their theory of how to access things plain doesn't work.
On Server, I always pin what I use to the task bar after I install it. I don't use the start menu on servers.
Yeah, but where is it after you install it
After you install something... well it appears you already know exactly where to find your "Recently added" programs...
@scottalanmiller said in What Are You Doing Right Now:
Right-click on the one you want, pin to start or task bar.
-
Just moved the UNMS Appliance from Google Cloud to Vultr. Working well and backup and restore worked well.
-
@dbeato said in What Are You Doing Right Now:
Just moved the UNMS Appliance from Google Cloud to Vultr. Working well and backup and restore worked well.
I'm debating movine my UniFi and UNMS to asingle Vultr instance. Currently they are on two separate VMs in my colo.
But the colo has occasionally had issues that caused a bunch of alerts to go out.
-
@jaredbusch said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
Just moved the UNMS Appliance from Google Cloud to Vultr. Working well and backup and restore worked well.
I'm debating movine my UniFi and UNMS to asingle Vultr instance. Currently they are on two separate VMs in my colo.
But the colo has occasionally had issues that caused a bunch of alerts to go out.
That might work, I have them separate for now on the $5 instance as UNMS although it does say to have 2GB of RAM can run on 1 GB so I am testing that.
