1
00:00:00,00 --> 00:00:03,000
We've all been gathered here today in this 
war room

2
00:00:03,400 --> 00:00:07,000
to discuss our recovery plan to execute when 
our K2 license key expires

3
00:00:08,000 --> 00:00:11,500
We have Phil here with us from K2 Support

4
00:00:12,000 --> 00:00:16,400
Who is a K2 expert, and should ensure a smooth 
update of the license key

5
00:00:17,300 --> 00:00:20,800
and we've made sure there are no known issues 
with the key correct?

6
00:00:24,600 --> 00:00:25,000
sir

7
00:00:27,500 --> 00:00:28,900
there's

8
00:00:31,000 --> 00:00:35,200
there's a known issue involving 37 character 
license keys which expire beyond Dec. 31, 
2022

9
00:00:52,600 --> 00:00:53,900
Everyone needs to leave

10
00:00:54,100 --> 00:00:55,200
except

11
00:00:55,300 --> 00:00:55,800
Phil

12
00:00:56,300 --> 00:00:57,300
the DBA guy

13
00:00:58,200 --> 00:00:59,200
and Jimmy

14
00:01:12,900 --> 00:01:14,200
This is an absolute outrage!

15
00:01:15,000 --> 00:01:17,700
How could you all let this happen again?!

16
00:01:18,500 --> 00:01:19,400
I've been a K2 customer

17
00:01:19,500 --> 00:01:24,300
since the three of you were in diapers!

18
00:01:29,000 --> 00:01:30,600
we pay good money every month

19
00:01:31,000 --> 00:01:34,200
to make sure things like this never happen

20
00:01:34,800 --> 00:01:40,200
I even brought it up jokingly with our Account 
Manager that we might consider buying a Premium 
entitlement soon!

21
00:01:40,600 --> 00:01:42,500
But sir the alternative is K2 Cloud which 
is filled with bugs every new Update they 
release

22
00:01:42,600 --> 00:01:44,000
I don't care about K2 Cloud!

23
00:01:44,100 --> 00:01:45,700
I need an on-prem server!

24
00:01:46,100 --> 00:01:46,500
but sir

25
00:01:46,900 --> 00:01:48,000
it's not that big of a deal

26
00:01:48,400 --> 00:01:49,300
of course it's a big deal

27
00:01:49,600 --> 00:01:52,000
I have a racquet ball tournament tonight 
that I'll have to cancel

28
00:01:52,700 --> 00:01:53,800
This happens way too often

29
00:01:55,700 --> 00:01:57,500
First it was the Developer license issue

30
00:01:57,600 --> 00:02:00,100
which we had figured out a way to scam them 
and not pay for a Non-Prouduction version

31
00:02:00,400 --> 00:02:03,100
and they went and fixed it right under our 
noses!

32
00:02:04,300 --> 00:02:05,800
and now they go and pull this crap

33
00:02:05,900 --> 00:02:08,600
and introduce a brand new licensing issue!

34
00:02:08,700 --> 00:02:11,000
The only thing that can make this worse

35
00:02:11,100 --> 00:02:13,400
is if we get locked out of K2 Management

36
00:02:14,000 --> 00:02:16,600
because Bob the DBA guy is a complete moron

37
00:02:17,200 --> 00:02:21,500
The man couldn't write a query to update 
the license key in the DB if someone had 
a gun to his head!

38
00:02:26,900 --> 00:02:28,800
The only thing not making my day worse

39
00:02:30,000 --> 00:02:31,600
is that Phil is here

40
00:02:31,700 --> 00:02:33,500
and he is a K2 expert

41
00:02:34,000 --> 00:02:36,300
Well versed in all areas of K2

42
00:02:40,700 --> 00:02:41,800
The rest of you...

43
00:02:42,700 --> 00:02:47,400
are hereby demoted to the lowest level of 
Developer  Interns, and from this day forward

44
00:02:48,500 --> 00:02:52,300
will work on rebuilding our old 4.7 workflows 
using the new HTML Five Designer

45
00:02:53,500 --> 00:02:55,400
and you can't use JeyLabz!

46
00:02:56,300 --> 00:02:59,000
you will work day and night dragging new 
steps onto the workflow canvas!

47
00:02:59,800 --> 00:03:02,200
until each of our 37 workflows have been 
rebuilt!

48
00:03:04,800 --> 00:03:05,600
it's ok

49
00:03:06,100 --> 00:03:07,700
the new workflow Designer is a lot better

50
00:03:14,300 --> 00:03:16,300
Phil is here to save us though

51
00:03:18,500 --> 00:03:23,500
we are confident your expertise will resolve 
this issue for us

52
00:03:25,000 --> 00:03:26,000
Right Phil?

53
00:03:31,000 --> 00:03:33,700
At least we don't need to install any new 
updates

54
00:03:40,200 --> 00:03:41,900
Please tell me Phil

55
00:03:42,700 --> 00:03:45,700
that we won't need to run the K2 Setup Manager 
again to resolve this

56
00:03:46,300 --> 00:03:48,800
because I hate running the K2 Setup Manager

57
00:03:53,800 --> 00:03:55,900
Get the Licensing team on the phone

