What Are You Doing Right Now
-
@scottalanmiller said in What Are You Doing Right Now:
@dbeato said in What Are You Doing Right Now:
Dealing with an Slack Outage
https://status.slack.com/2018-06/142edcb9e52c7663Yup, we are pretty impacted here.
I don't use Slack for anything big. But I have a client that lives in it all day. Sucks to be them.
-
Impatiently waiting...
Of course they have to go through customs and then transfer to a domestic flight before getting to Chicago...
Also really glad that they had a 3+ hour layover right now. Because it is down to 2 hours. Only 1.5 hours if you consider boarding time.
And they will have to go through TSA after customs.
-
@jaredbusch said in What Are You Doing Right Now:
Impatiently waiting...
Of course they have to go through customs and then transfer to a domestic flight before getting to Chicago...
Also really glad that they had a 3+ hour layover right now. Because it is down to 2 hours. Only 1.5 hours if you consider boarding time.
And they will have to go through TSA after customs.
Nice, family soon to be at your home.
-
The plane for their connecting flight is in Chicago at the moment, scheduled for a 2:40 departure to Detroit.
That is 4 hours away still but...
-
Looking at "Cloud" servers (need to host a small VM for zabbix 2vCPU 2GB RAM)
But getting confused on pricing.
Just give me ...... it's £5/mth simple.
-
Windows search index still rebuilding 20 hours later. So slow. Contentdb will be over 80GB when its done i think.
-
call just came in from a customer who was using a KVM switch to toggle between two computers.
The other computer was turned off and they didnt know that 2 totally different computers connected to the same monitor.
The sounds one makes when they figure it out = PRICELESS
I laughed as soon as the phone was hung up..
brightened up my day a little bit. -
Just rebooted the home lab box. I think that makes it time for lunch.
-
Dealing with DFS replication issues...
-
Looks like tonight with be NodeBB 1.10 deploy night!
-
@dbeato said in What Are You Doing Right Now:
Dealing with DFS replication issues...
Figured it out, Staging Quota Size was set to default...
-
Corning is hiring a Linux position.
-
It's a very slow part of the day, let's do updates....
-
And we are back, major update released.
-
don't think i've ever had more grief with a windows os version post 95, more than i have with 10. bsod, bsod, bsod.
&
sth korea defeated germany, outstanding. -
@siringo said in What Are You Doing Right Now:
don't think i've ever had more grief with a windows os version post 95, more than i have with 10. bsod, bsod, bsod.
&
sth korea defeated germany, outstanding.You probably weren't unlucky enough to use Windows Me.
-
@wrx7m said in What Are You Doing Right Now:
@siringo said in What Are You Doing Right Now:
don't think i've ever had more grief with a windows os version post 95, more than i have with 10. bsod, bsod, bsod.
&
sth korea defeated germany, outstanding.You probably weren't unlucky enough to use Windows Me.
Took a look at ME and thought nup, it was junk.
I was lucky enough to install NT 3.1 off 30 or so 1.44Mb FDD though, quite a few times.
I don't know what has happened to Microsoft (with 10 and 2016 and their updates in mind). They seem to have forgotten or chosen to overlook all the data & experience they would have gained from the past 30 years working with businesses that use their OSs. These feature updates, does anyone actually use the crap that is included in them?
Everywhere I go and everywhere I read people hate these massive unneeded, unwanted downloads. -
Reading about the Linux boot process .
-
@siringo I’ve only had 1 version of Windows 10 break shit at scale. That was 1709, I had to totally block this for more than a month. While 1803 has been fully deployed to clients since the end of May.
-
@jaredbusch said in What Are You Doing Right Now:
@siringo I’ve only had 1 version of Windows 10 break shit at scale. That was 1709, I had to totally block this for more than a month. While 1803 has been fully deployed to clients since the end of May.
I haven't deployed the 1803 upgrade yet via WSUS, but do deploy new machines at 1803. Had too many issues due to the upgrade process, so we're waiting until a good time we're all available the next day or two after we'd schedule the 1803 upgrade deployment.
If something is 1803, it's fine afterwards.
