What Are You Doing Right Now
-
@wrcombs Go home
-
-
@scottalanmiller said in What Are You Doing Right Now:
@wrcombs said in What Are You Doing Right Now:
Just had someone cancel on a training scheduled for this afternoon. . . now what do I Do?
Well, don't train them!
We yeah I guess so! haha this is the 2nd time they have cancelled on me this week.
-
@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.
-
@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.
-
@pchiodo and I earlier this week, it's rare to see me all suited up.
-
@scottalanmiller said in What Are You Doing Right Now:
@pchiodo and I earlier this week, it's rare to see me all suited up.
And with your beard trimmed. You no longer look like someone that was just let out of a parking garage...
-
@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.
-
@scottalanmiller said in What Are You Doing Right Now:
@pchiodo and I earlier this week, it's rare to see me all suited up.
Looks like someone had a big wig business meeting.
-
@scottalanmiller Just felt like suiting up or special occasion?
-
@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, but we see similar problems on fresh Windows 10 not being able to list programs that are installed. No matter what indexing there is, the only goal is to return what is on the Start Menu list. Nothing else is desired, and in fact is extremely strongly not desired. It worked perfectly in Windows 7. Lighting fast, and 100% accurate. Not it is slow and worse than useless, it's actively misleading.
Still works perfectly in every other OS that I know of.
-
@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.
