2.62 score from hupso.pl for:
garvis.ca



HTML Content


Titlethe world according to mitch « the day to day ramblings of an it professional and community leader

Length: 104, Words: 18
Description the day to day ramblings of an it professional and community leader

Length: 67, Words: 12
Keywords pusty
Robots
Charset UTF-8
Og Meta - Title exist
Og Meta - Description exist
Og Meta - Site name exist
Tytuł powinien zawierać pomiędzy 10 a 70 znaków (ze spacjami), a mniej niż 12 słów w długości.
Meta opis powinien zawierać pomiędzy 50 a 160 znaków (łącznie ze spacjami), a mniej niż 24 słów w długości.
Kodowanie znaków powinny być określone , UTF-8 jest chyba najlepszy zestaw znaków, aby przejść z powodu UTF-8 jest bardziej międzynarodowy kodowaniem.
Otwarte obiekty wykresu powinny być obecne w stronie internetowej (więcej informacji na temat protokołu OpenGraph: http://ogp.me/)

SEO Content

Words/Characters 3753
Text/HTML 26.24 %
Headings H1 1
H2 11
H3 25
H4 0
H5 0
H6 0
H1
the world according to mitch
H2
annoyed with cogeco? here are some alternatives.
windows to go gotcha in windows 10
scheduling server restarts
a big, huge microsoft security fail.
107 days: a microsoft security nightmare
outlook / hotmail: we’re back in business
outlook / hotmail issues acknowledged
annoyed with cogeco? here are some alternatives.
windows to go gotcha in windows 10
scheduling server restarts
a big, huge microsoft security fail.
H3
start here
rate this:
share this:
like this:
rate this:
share this:
like this:
rate this:
share this:
like this:
rate this:
share this:
like this:
rate this:
share this:
like this:
rate this:
share this:
like this:
rate this:
share this:
like this:
post navigation
latest posts
donate
H4
H5
H6
strong
customer (dis)service:
billing:
retention:
teksavvy
distributel ontario
execulink
bell canada
lara internet
wrs web solutions
taskschd.msc
create basic task…
reboot system
task trigger
one time
one time
action
start a program
start a program
shutdown.exe
add arguments
/r /t 0
f
r
t
**note:
do it in powershell!
107 days: a microsoft security nightmare
a big, huge microsoft security fail.
my windows computers
so why didn’t i publish sooner?
microsoft! how dare you?
b
i
em customer (dis)service:
billing:
retention:
teksavvy
distributel ontario
execulink
bell canada
lara internet
wrs web solutions
taskschd.msc
create basic task…
reboot system
task trigger
one time
one time
action
start a program
start a program
shutdown.exe
add arguments
/r /t 0
f
r
t
**note:
do it in powershell!
107 days: a microsoft security nightmare
a big, huge microsoft security fail.
my windows computers
so why didn’t i publish sooner?
microsoft! how dare you?
Bolds strong 31
b 0
i 0
em 31
Zawartość strony internetowej powinno zawierać więcej niż 250 słów, z stopa tekst / kod jest wyższy niż 20%.
Pozycji używać znaczników (h1, h2, h3, ...), aby określić temat sekcji lub ustępów na stronie, ale zwykle, użyj mniej niż 6 dla każdego tagu pozycje zachować swoją stronę zwięzły.
Styl używać silnych i kursywy znaczniki podkreślić swoje słowa kluczowe swojej stronie, ale nie nadużywać (mniej niż 16 silnych tagi i 16 znaczników kursywy)

Statystyki strony

twitter:title pusty
twitter:description pusty
google+ itemprop=name pusty
Pliki zewnętrzne 32
Pliki CSS 4
Pliki javascript 28
Plik należy zmniejszyć całkowite odwołanie plików (CSS + JavaScript) do 7-8 maksymalnie.

Linki wewnętrzne i zewnętrzne

Linki 91
Linki wewnętrzne 17
Linki zewnętrzne 74
Linki bez atrybutu Title 54
Linki z atrybutem NOFOLLOW 0
Linki - Użyj atrybutu tytuł dla każdego łącza. Nofollow link jest link, który nie pozwala wyszukiwarkom boty zrealizują są odnośniki no follow. Należy zwracać uwagę na ich użytkowania

Linki wewnętrzne

#@*% mailto:#@*%
share #
share #
share #
share #
share #
share #
share #
cancel #
cancel #cancel

Linki zewnętrzne

home https://garvis.ca/
about https://garvis.ca/about/
the world according to mitch https://garvis.ca
about https://garvis.ca/about/
annoyed with cogeco? here are some alternatives. https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/
april 26, 2017 11:06 am https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/
leave a comment https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/#respond
- https://mgarvis.files.wordpress.com/2017/04/cogeco.png
www.teksavvy.com/internetsavings http://www.teksavvy.com/internetsavings
http://landing.distributel.ca/internet-deals/burlington http://landing.distributel.ca/internet-deals/burlington
www.execulink.ca http://www.execulink.ca
www.lara.on.ca http://www.lara.on.ca
http://www.wrswebsolutions.ca/burlington-high-speed-internet-service-provider-cable-fibre.html http://www.wrswebsolutions.ca/burlington-high-speed-internet-service-provider-cable-fibre.html
email https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/?share=email
print https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/
twitter https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/?share=twitter
facebook https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/?share=facebook
windows to go gotcha in windows 10 https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/
april 19, 2017 9:45 am https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/
2 comments on windows to go gotcha in windows 10 https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/#comments
email https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/?share=email
print https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/
twitter https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/?share=twitter
facebook https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/?share=facebook
scheduling server restarts https://garvis.ca/2017/04/17/scheduling-server-restarts/
april 17, 2017 8:45 am https://garvis.ca/2017/04/17/scheduling-server-restarts/
leave a comment https://garvis.ca/2017/04/17/scheduling-server-restarts/#respond
- https://mgarvis.files.wordpress.com/2017/04/image.png
- https://mgarvis.files.wordpress.com/2017/04/image1.png
email https://garvis.ca/2017/04/17/scheduling-server-restarts/?share=email
print https://garvis.ca/2017/04/17/scheduling-server-restarts/
twitter https://garvis.ca/2017/04/17/scheduling-server-restarts/?share=twitter
facebook https://garvis.ca/2017/04/17/scheduling-server-restarts/?share=facebook
a big, huge microsoft security fail. https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/
march 23, 2017 9:45 am https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/
leave a comment https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/#respond
- https://mgarvis.files.wordpress.com/2016/12/image.png
email https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/?share=email
print https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/
twitter https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/?share=twitter
facebook https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/?share=facebook
107 days: a microsoft security nightmare https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/
march 23, 2017 8:45 am https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/
leave a comment https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/#respond
- https://mgarvis.files.wordpress.com/2017/03/107.jpg
- https://mgarvis.files.wordpress.com/2017/03/proof-of-hack-2.jpg
email https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/?share=email
print https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/
twitter https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/?share=twitter
facebook https://garvis.ca/2017/03/23/107-days-a-microsoft-security-nightmare/?share=facebook
outlook / hotmail: we’re back in business https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/
march 7, 2017 1:27 pm https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/
leave a comment https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/#respond
- https://mgarvis.files.wordpress.com/2017/03/image2.png
email https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/?share=email
print https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/
twitter https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/?share=twitter
facebook https://garvis.ca/2017/03/07/outlook-hotmail-were-back-in-business/?share=facebook
outlook / hotmail issues acknowledged https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/
march 7, 2017 11:14 am https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/
2 comments on outlook / hotmail issues acknowledged https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/#comments
- https://mgarvis.files.wordpress.com/2017/03/image1.png
email https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/?share=email
print https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/
twitter https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/?share=twitter
facebook https://garvis.ca/2017/03/07/outlook-hotmail-issues-acknowledged/?share=facebook
older posts https://garvis.ca/page/2/
annoyed with cogeco? here are some alternatives. https://garvis.ca/2017/04/26/annoyed-with-cogeco-here-are-some-alternatives/
windows to go gotcha in windows 10 https://garvis.ca/2017/04/19/windows-to-go-gotcha-in-windows-10/
scheduling server restarts https://garvis.ca/2017/04/17/scheduling-server-restarts/
a big, huge microsoft security fail. https://garvis.ca/2017/03/23/a-big-huge-microsoft-security-fail/
blog at wordpress.com. https://wordpress.com/?ref=footer_blog
the world according to mitch https://garvis.ca/
create a free website or blog at wordpress.com. https://wordpress.com/?ref=footer_website

Zdjęcia

Zdjęcia 12
Zdjęcia bez atrybutu ALT 3
Zdjęcia bez atrybutu TITLE 4
Korzystanie Obraz ALT i TITLE atrybutu dla każdego obrazu.

Zdjęcia bez atrybutu TITLE

https://www.paypalobjects.com/en_us/i/scr/pixel.gif
https://s2.wp.com/wp-content/mu-plugins/post-flair/sharing/images/loading.gif
https://sb.scorecardresearch.com/p?c1=2&c2=7518284&c3=&c4=&c5=&c6=&c15=&cv=2.0&cj=1
https://pixel.wp.com/b.gif?v=noscript

Zdjęcia bez atrybutu ALT

https://www.paypalobjects.com/en_us/i/scr/pixel.gif
https://sb.scorecardresearch.com/p?c1=2&c2=7518284&c3=&c4=&c5=&c6=&c15=&cv=2.0&cj=1
https://pixel.wp.com/b.gif?v=noscript

Ranking:


Alexa Traffic
Daily Global Rank Trend
Daily Reach (Percent)









Majestic SEO











Text on page:

homeabout the world according to mitch the day to day ramblings of an it professional and community leader search search start here about annoyed with cogeco? here are some alternatives. april 26, 2017 11:06 am / leave a comment last night my world went dark. my lights were on of course… and i had plenty of other alternatives, but when my internet service and my cable tv service go down, and they stay down for the entire night, it is as if my world went dark… especially the night before i leave on vacation, and had a lot of work to do to prepare for that. this morning i spoke with three people at cogeco: customer (dis)service: what do you want us to do? there was a power failure! we are the victims here! woe is me! billing: you think you’re special? #@*% you mr. garvis, we don’t care about you. retention: if you agree to stay on we can deduct $10/month from your bill for the next six months. that’s a $60 savings for you. when i told the retention guy that it was not a savings – it was compensation for their poor service, he told me that if i cancelled now i would be billed $75 for early cancellation. i accepted their paltry compensation, but i also promised him that i would be writing articles about them. so for those of you living in the oakville/burlington/milton region (did i mention i live five blocks from cogeco’s head office?) there are alternatives… better alternatives to cogeco. some of them are: teksavvy. they have great service and right now they have a deal for new customers. click www.teksavvy.com/internetsavings for details. distributel ontario: they have plans for high speed internet from $35/month (which is much cheaper than cogeco)… click http://landing.distributel.ca/internet-deals/burlington for details. execulink: i don’t know much about them but they still have to have better customer service than cogeco. click www.execulink.ca for details. bell canada: okay, who are we kidding? they suck too. lara internet: another one i don’t know, but check them out at www.lara.on.ca. wrs web solutions: they offer cable internet packages for as low as $39.95 on their site… check them out at http://www.wrswebsolutions.ca/burlington-high-speed-internet-service-provider-cable-fibre.html. there are a ton of options out there and if you look around there will be a solution that suits your needs… ask your friends in the area, they may have other suggestions! oh and @cogeco, a word of advice… before you treat a customer like dirt, you should check out a) if they happen to be a technology blogger, and b) how many hits they get in a year. maybe then your people will think twice about it. rate this:share this:shareemailprinttwitterfacebooklike this:like loading... windows to go gotcha in windows 10 april 19, 2017 9:45 am / 2 comments on windows to go gotcha in windows 10 so here’s an interesting fact about windows to go. when windows 10 first came out i was still running windows 8.1 on my corporate desktop, and when i went to create my wtg image i couldn’t because the windows 8.1 wtg engine did not support building windows 10 wtg keys. ok, that is understandable. windows 10: the last operating system microsoft will release, right? well my corporate laptop is on build 1607, and when i downloaded the latest build (1703) it would not recognize it. so my two options are: download the earlier build and make my key based on that build; or take the time to upgrade my laptop. with all due respect microsoft, if you are going to tell us that windows 10 is the last desktop os, don’t pull these games. as a tech guru i understood right away what the problem was… how much time do you think the regular joe trying to use your products would have spent on this? rate this:share this:shareemailprinttwitterfacebooklike this:like loading... scheduling server restarts april 17, 2017 8:45 am / leave a comment if you manage servers you have likely come to a point where you finished doing work and got a prompt ‘your server needs to reboot. reboot now?’ well you can’t reboot now… not during business hours. i guess you’ll have to come back tonight… or this weekend, right? wrong. scheduling a reboot is actually pretty easy in windows. try this: open task scheduler (taskschd.msc). in the actions pane click create basic task… name the task accordingly… reboot system for example. on the task trigger page click the radio button one time on the one time page enter the date and time when you want the server to reboot. on the action page select start a program. on the start a program page enter the name of the program shutdown.exe. in the add arguments box enter /f /r /t 0. this will force the programs to close, restart the server (instead of just turning it off), and set the delay time to 0 seconds. once you have done this your server will reboot at the precise time you want it to, and will come back up. **note: don’t forget to check. it is not unheard of in this world for servers to go down and not come back up as they are supposed to! do it in powershell! using powershell to script this will allow you to not only save the script, but also run it on remote servers. from justin rich’s blog article i found this script: register-scheduledjob -name systemreboot -scriptblock { restart-computer -computername $server -force -wait send-mailmessage -from mitch@email.com -to mitch@email.com -subject "rebooted" -smtpserver smtp.mail.com } -trigger (new-jobtrigger -at "04/14/2017 8:45pm" -once) -scheduledjoboption (new-scheduledjoboption -runelevated) -credential (get-credential) have fun! rate this:share this:shareemailprinttwitterfacebooklike this:like loading... a big, huge microsoft security fail. march 23, 2017 9:45 am / leave a comment (note: this article was written december 7, 2016. not one word has been changed since that date.  to understand why it can only now be published, read the article on this site called 107 days: a microsoft security nightmare. -mdg) for reasons that will become obvious, i am going to delay posting this article until the issue has been resolved. a few days ago a colleague of mine discovered the password to my microsoft account.  i won’t go into the how and why… i knew that my password had been compromised and i took the immediate steps to change it. ok, i understand that things break… i tried a few times, and then i decided to follow the advice and try later.  i trust my colleague not to actually use my password, so even though i felt uncomfortable with it being compromised, i knew i could wait a couple of hours. throughout the evening i tried (unsuccessfully) to change my password.  as i was sitting with my father having dinner, as i had drinks and cigars with my friends… no joy, i still got the same message.  ‘there’s a temporary problem with the service. please try again. if you continue to get this message, try again later.’ i want to be clear… if my network had an error that was preventing users from changing their passwords i would consider it reasonably important, and i would take immediate steps to fix it.  but having trusted microsoft for so many years, i assumed this would be fixed eventually. four days passed. yes, it was literally four days before i decided that my passivity would not eventually lead to a solution.  i sat down and figured out how to request support. i was hoping to be able to speak with a human being.  before i could, however, the virtual support assistant got me to try this link and that link.  it then made me go through seventeen steps to finally confirm that the account in question was mine… and once it confirmed that i really am me, it tried to reset my password… and i ended up with the same error message that ‘there’s a temporary problem with the service. please try again. if you continue to get this message, try again later.’ okay, it’s been nearly an hour… and i am chatting with someone who is quite obviously not their first round draft pick.  after all, i asked for help with outlook.com, not with something that people actually pay for.  i spent twenty minutes explaining to him the situation, and the added (and i assume rare) complication that i have two accounts with the same address… my office 365 account and my microsoft account are both the same address that are completely different.  ‘please don’t touch my office 365 account, i only want to change my microsoft account.’  this led to another five minute discussion on the meaning of the word change. he had me fill out another form on-line.  i did.  at the end of that form i got a message that said that the product team would contact me within 24-48 hours to help me.  i told the support agent that i had filled out the form.  he told me that now i had to wait until they contacted me. all in all, my microsoft account (which is the account i use for my mct & mcp benefits, skype, and myriad other features) will have been compromised for the better part of a week… and there was nothing i could do about it.  yes, i could have contacted answer desk a few days earlier, so it would have been compromised for only three days.  i want to know in what world is that considered an acceptable delay to be able to change a compromised password? some time ago i started using multi-factor authentication (mfa) for many of my most important systems, which is why i am never concerned that my blog or my password vault could be compromised.  for various systems i have a hard key (yubikey) and soft keys (google authenticator and microsoft authenticator) which keep most of what i do safe.  but most of the microsoft systems do not support mfa and i am stuck with only a password.  i use reasonably complex passwords so i usually am not concerned, but in a case where my password is compromised and i am not able to change it, i wonder how it is that a company as advanced as microsoft (in this case) does not allow me to use mfa.  i would love to be able to require my yubikey in order to log in to windows and many of the on-line systems i use, but it is simply not an option. i am disappointed by microsoft this week… and i hope that they take the lessons learned from this experience to improve.  however i sit here today, thinking of the myriad occasions i stood on stage in over a dozen countries on five continents and defended microsoft’s security systems as among the best in the world; i was always sure in my knowledge that i spoke the truth.  today i would not feel comfortable making that claim… and my faith in their systems, like shattered glass, will not be easily fixed. rate this:share this:shareemailprinttwitterfacebooklike this:like loading... 107 days: a microsoft security nightmare march 23, 2017 8:45 am / leave a comment i have held off talking about something for quite some time. i do not mess around when it comes to security, especially for my critical accounts. when the actual security of an account has been compromised, as was the case with my microsoft account, i do not advertise it. on december 7th i sat in the second cup cafe on bank street in ottawa and wrote an article called a big, huge microsoft security fail. i wrote about how i had been unable to change my password and that their engine to do so was broken, but that it turned out it was not everyone, it was just me. ‘there’s a temporary problem with the service. please try again. if you continue to get this message, try again later.’ it took several days for anyone at microsoft to take me seriously, but my issue was finally escalated to a 2nd level support tech named gary (who, i want to be clear, was a nice guy, and as helpful as he could be under the circumstances). gary and i got to know each other sometime in mid-december. remember, the issue started happening the last days of november, i reported it on december 5th, and the case was escalated (grudgingly) around december 9th. gary spent a couple of hours trying to help, and then in discussions with the product engineering team trying to get it fixed. by the end of the day he said something to the effect of: “yeah, neither i not our engineers have ever seen a problem like this. it might take some time, but if you are willing we will work with you to get it fixed.” some time… it might take some time… that was on or about december 9th. i am happy to say that the problem has now been resolved… as i sit and write this, with the resolution less than an hour old, it is 1:15pm, wednesday march 22. i spent nearly a decade touting the virtues of microsoft’s security… and then from the day i informed them that my password had been compromised, and that a glitch in their system was preventing me from changing it, it took 107 days to resolve the issue. so let’s take a quick rundown of some of the sites and services that are accessed with my microsoft account: skype (one of the ways i communicate with hundreds of people) onedrive (all of my files!) microsoft certified trainer (mct) account (including my mct renewal, courseware downloads) microsoft certified professional (including my mcp transcripts) msdn subscription (including all my software licenses and keys) windows store (including credit card information) microsoft volume license center (vlc) microsoft store (including credit card information) bing microsoft partner portal msn outlook/hotmail my windows computers and so, you can see, this is not like having my words with friends account compromised… this is extremely serious and far-reaching. this was… everything. once a week i would get an e-mail from gary telling me that they had not yet resolved the issue… but they were still working on it, and he would continue to keep me informed. on march 6th a hacker compromised my skype account, and sent a link to dozens of my contacts with malicious content. naturally those contacts let me know, and i reached out to gary and told him that now that hackers had indeed compromised my account, they needed to resolve the issue and pronto. gary replied with: “i have taken a look into your account, to look for any evidence of unauthorized access, and i did not see any. was any account info changed? can you still login?” a few days later that he had not been able to open the embedded picture, and asked that i resend it as an attachment. thank heavens for that, because had he taken the next step immediately i would not have been able to renew my microsoft certified trainer (mct) credential in time. so when gary did finally get the picture (as seen above) he wrote (on march 18th): if you received that message, then it could be that someone attempted to access the account. to prevent that, i have placed a suspension on the account that will prevent any login activity. while my engineering team investigates this issue, no one will be able to break into the account. i have also left a note on the account so that the attacker will not be able to attempt to remove it. wonderful. you are suspending my account now, probably after the damage has been done, but all this is doing is punishing me. fix the damned problem! on the same day as i received this e-mail i wrote the following one line response: gary this is no longer acceptable. i am calling a lawyer. on tuesday (march 21) i received gary’s reply: in light of this recent reply, i have escalated this issue to a second team within microsoft, and am awaiting to hear their response. i understand the frustration, but please know that i cannot do anything to speed up the engineers and ops teams working on this issue. wouldn’t you know it… the following day (that’s today, wednesday march 22, 2017 – 107 days after i first reported the issue) i received a call from gary that started with: well mitch, it seems that when you threaten to call a lawyer things get done faster. i think we have solved your problem. indeed, before the phone call ended i had successfully changed my password. one hundred and seven days after i first reported the problem. one hundred and seven days since i told microsoft there was a problem with their security. one hundred and seven days since i told microsoft that my account had been compromised, that someone had my password, and that i needed their help to secure my data and reputation. one hundred and seven days. actually it was only 105 days since i wrote the original article (which will be published shortly after this one, untouched since the original writing). so why didn’t i publish sooner? there are a handful… maybe four or five people who know the story and who understand some of my frustrations with this case. these are also people who know i have a great bully pulpit in the form of this blog. they have all asked me ‘why didn’t you publish sooner?’ two of them asked why i did not go to the mainstream technology media to let them know about this. simple… i have an account that is easy enough to guess, to which i could not change the password. if the wrong people knew about that they would have focused on getting that password and, once they had it, they knew i couldn’t change it. they would have literally owned me. and so i sat quietly, seemingly patiently, waiting for microsoft to fix the problem. i waited those 107 days knowing that when it was finally resolved i would a) breathe a big, huge sigh of relief, and b) sit down and write this piece, venting my facts and frustrations. microsoft! how dare you? how can you let any problem, let alone one as serious as this, fester for so long unresolved? do you think you owe me nothing? at this point i am still considering a lawsuit, and if you don’t think damaging my reputation and peace of mind is worth damages in a court of law then you are seriously misreading the system. you should be ashamed of yourselves, and you should be tracking down who is responsible for this travesty, this shame, and firing them. i got that off my chest. i have, over the past two weeks, asked friends and colleagues for recommendations on lawyers. i might just reach out to one this afternoon. we’ll see. rate this:share this:shareemailprinttwitterfacebooklike this:like loading... outlook / hotmail: we’re back in business march 7, 2017 1:27 pm / leave a comment according to the dashboard microsoft account authentication is back on-line. i have confirmed this is the case for my accounts, but hope you are having the same experience. rate this:share this:shareemailprinttwitterfacebooklike this:like loading... outlook / hotmail issues acknowledged march 7, 2017 11:14 am / 2 comments on outlook / hotmail issues acknowledged when i posted my last couple of posts microsoft was reporting that ‘all is well.’ dashboards were green, nothing to see here. that has now changed: so we know now that the issues are pretty serious… at least, serious enough that they are now acknowledging them. as for me, i have been having an issue with my microsoft account that has been ongoing since december 5th. i have held off talking about it for security reasons, but with all that has been going on today, and the fact that yesterday my account might have been hacked, i am planning on writing about it tonight. and boy are you guys going to be shocked. all i will say for now is this: do not trust microsoft security. yes, i said it. for a decade i have been espousing the virtues and benefits of microsoft’s security. unfortunately i have had to change my position on this, and in a very big way. do not trust them. it has cost me terribly, and i will tell you about it tomorrow. m rate this:share this:shareemailprinttwitterfacebooklike this:like loading... post navigation ← older posts latest posts annoyed with cogeco? here are some alternatives.last night my world went dark. my lights were on of course… and i had plenty of other alternatives, but when my internet service and… windows to go gotcha in windows 10so here’s an interesting fact about windows to go. when windows 10 first came out i was still running windows 8.1 on my corporate desktop,… scheduling server restartsif you manage servers you have likely come to a point where you finished doing work and got a prompt ‘your server needs to reboot. … a big, huge microsoft security fail.(note: this article was written december 7, 2016. not one word has been changed since that date.  to understand why it can only now be… donate blog at wordpress.com. the world according to mitch create a free website or blog at wordpress.com. post to cancel send to email address your name your email address cancel post was not sent - check your email addresses! email check failed, please try again sorry, your blog cannot share posts by email. %d bloggers like this:


Here you find all texts from your page as Google (googlebot) and others search engines seen it.

Words density analysis:

Numbers of all words: 3607

One word

Two words phrases

Three words phrases

the - 5.57% (201)
and - 2.66% (96)
that - 1.97% (71)
this - 1.91% (69)
you - 1.75% (63)
for - 1.58% (57)
not - 1.3% (47)
are - 1.28% (46)
soft - 1.08% (39)
- 1.08% (39)
have - 1.03% (37)
microsoft - 1.03% (37)
out - 1% (36)
all - 1% (36)
with - 0.91% (33)
day - 0.89% (32)
was - 0.86% (31)
account - 0.83% (30)
now - 0.83% (30)
our - 0.8% (29)
one - 0.78% (28)
this: - 0.67% (24)
word - 0.67% (24)
here - 0.61% (22)
they - 0.61% (22)
like - 0.58% (21)
but - 0.58% (21)
been - 0.55% (20)
windows - 0.55% (20)
had - 0.55% (20)
would - 0.53% (19)
will - 0.5% (18)
days - 0.5% (18)
some - 0.47% (17)
able - 0.47% (17)
password - 0.47% (17)
about - 0.47% (17)
know - 0.44% (16)
share - 0.42% (15)
your - 0.42% (15)
change - 0.42% (15)
end - 0.42% (15)
time - 0.42% (15)
promised - 0.39% (14)
can - 0.39% (14)
email - 0.39% (14)
this:share - 0.39% (14)
try - 0.39% (14)
led - 0.39% (14)
issue - 0.39% (14)
when - 0.39% (14)
even - 0.36% (13)
security - 0.36% (13)
log - 0.36% (13)
server - 0.36% (13)
compromised - 0.36% (13)
any - 0.33% (12)
problem - 0.33% (12)
service - 0.33% (12)
get - 0.33% (12)
from - 0.3% (11)
their - 0.3% (11)
down - 0.3% (11)
then - 0.3% (11)
them - 0.3% (11)
there - 0.3% (11)
system - 0.3% (11)
ask - 0.3% (11)
could - 0.28% (10)
sit - 0.28% (10)
use - 0.28% (10)
start - 0.28% (10)
reboot - 0.28% (10)
got - 0.28% (10)
how - 0.28% (10)
gary - 0.28% (10)
rate - 0.28% (10)
has - 0.28% (10)
it. - 0.25% (9)
post - 0.25% (9)
new - 0.25% (9)
take - 0.25% (9)
march - 0.25% (9)
2017 - 0.25% (9)
mess - 0.25% (9)
article - 0.22% (8)
see - 0.22% (8)
look - 0.22% (8)
blog - 0.22% (8)
december - 0.22% (8)
ton - 0.22% (8)
other - 0.22% (8)
internet - 0.22% (8)
did - 0.22% (8)
under - 0.22% (8)
night - 0.22% (8)
form - 0.22% (8)
world - 0.22% (8)
message - 0.22% (8)
off - 0.22% (8)
only - 0.19% (7)
come - 0.19% (7)
loading... - 0.19% (7)
key - 0.19% (7)
this:like - 0.19% (7)
this:shareemailprinttwitterfacebooklike - 0.19% (7)
add - 0.19% (7)
want - 0.19% (7)
once - 0.19% (7)
comment - 0.19% (7)
think - 0.19% (7)
(in - 0.19% (7)
who - 0.19% (7)
fix - 0.19% (7)
ever - 0.19% (7)
work - 0.19% (7)
people - 0.19% (7)
told - 0.19% (7)
resolve - 0.19% (7)
again - 0.19% (7)
me. - 0.19% (7)
since - 0.19% (7)
still - 0.19% (7)
don’t - 0.19% (7)
why - 0.19% (7)
let - 0.17% (6)
name - 0.17% (6)
serious - 0.17% (6)
call - 0.17% (6)
solved - 0.17% (6)
owe - 0.17% (6)
support - 0.17% (6)
last - 0.17% (6)
same - 0.17% (6)
hour - 0.17% (6)
systems - 0.17% (6)
which - 0.17% (6)
leave - 0.17% (6)
case - 0.17% (6)
engine - 0.17% (6)
understand - 0.17% (6)
please - 0.17% (6)
script - 0.17% (6)
after - 0.17% (6)
wait - 0.17% (6)
low - 0.17% (6)
check - 0.17% (6)
alternatives - 0.17% (6)
having - 0.14% (5)
it, - 0.14% (5)
asked - 0.14% (5)
going - 0.14% (5)
help - 0.14% (5)
outlook - 0.14% (5)
run - 0.14% (5)
changed - 0.14% (5)
hundred - 0.14% (5)
law - 0.14% (5)
seven - 0.14% (5)
account, - 0.14% (5)
went - 0.14% (5)
contact - 0.14% (5)
team - 0.14% (5)
task - 0.14% (5)
address - 0.14% (5)
two - 0.14% (5)
(including - 0.14% (5)
solution - 0.14% (5)
back - 0.14% (5)
info - 0.14% (5)
later - 0.14% (5)
107 - 0.14% (5)
before - 0.14% (5)
here’s - 0.14% (5)
link - 0.14% (5)
wrote - 0.14% (5)
fact - 0.14% (5)
first - 0.14% (5)
resolved - 0.14% (5)
sat - 0.14% (5)
mitch - 0.14% (5)
week - 0.14% (5)
actual - 0.14% (5)
build - 0.14% (5)
click - 0.14% (5)
big - 0.14% (5)
fixed - 0.11% (4)
step - 0.11% (4)
publish - 0.11% (4)
than - 0.11% (4)
actually - 0.11% (4)
password. - 0.11% (4)
finally - 0.11% (4)
line - 0.11% (4)
message, - 0.11% (4)
big, - 0.11% (4)
me, - 0.11% (4)
restart - 0.11% (4)
just - 0.11% (4)
round - 0.11% (4)
program - 0.11% (4)
note - 0.11% (4)
huge - 0.11% (4)
page - 0.11% (4)
enter - 0.11% (4)
friends - 0.11% (4)
prevent - 0.11% (4)
continue - 0.11% (4)
them. - 0.11% (4)
tech - 0.11% (4)
cancel - 0.11% (4)
many - 0.11% (4)
compromised, - 0.11% (4)
spent - 0.11% (4)
received - 0.11% (4)
knew - 0.11% (4)
were - 0.11% (4)
posts - 0.11% (4)
each - 0.11% (4)
today - 0.11% (4)
hotmail - 0.11% (4)
also - 0.11% (4)
what - 0.11% (4)
might - 0.11% (4)
mct - 0.11% (4)
customer - 0.11% (4)
trust - 0.11% (4)
hours - 0.11% (4)
site - 0.11% (4)
media - 0.11% (4)
desk - 0.11% (4)
point - 0.11% (4)
five - 0.11% (4)
according - 0.11% (4)
few - 0.11% (4)
servers - 0.11% (4)
account. - 0.11% (4)
right - 0.11% (4)
well - 0.11% (4)
details. - 0.08% (3)
consider - 0.08% (3)
later.’ - 0.08% (3)
yes, - 0.08% (3)
again. - 0.08% (3)
service. - 0.08% (3)
temporary - 0.08% (3)
savings - 0.08% (3)
couple - 0.08% (3)
‘there’s - 0.08% (3)
four - 0.08% (3)
certified - 0.08% (3)
on-line - 0.08% (3)
reported - 0.08% (3)
him - 0.08% (3)
writing - 0.08% (3)
keys - 0.08% (3)
mfa - 0.08% (3)
today, - 0.08% (3)
over - 0.08% (3)
early - 0.08% (3)
second - 0.08% (3)
escalated - 0.08% (3)
fixed. - 0.08% (3)
microsoft’s - 0.08% (3)
knowledge - 0.08% (3)
those - 0.08% (3)
most - 0.08% (3)
accounts - 0.08% (3)
office - 0.08% (3)
something - 0.08% (3)
someone - 0.08% (3)
words - 0.08% (3)
ended - 0.08% (3)
skype - 0.08% (3)
guy - 0.08% (3)
this, - 0.08% (3)
started - 0.08% (3)
nothing - 0.08% (3)
better - 0.08% (3)
said - 0.08% (3)
product - 0.08% (3)
confirm - 0.08% (3)
took - 0.08% (3)
reach - 0.08% (3)
web - 0.08% (3)
trying - 0.08% (3)
using - 0.08% (3)
done - 0.08% (3)
scheduling - 0.08% (3)
problem. - 0.08% (3)
desktop - 0.08% (3)
light - 0.08% (3)
another - 0.08% (3)
tell - 0.08% (3)
bill - 0.08% (3)
lawyer - 0.08% (3)
around - 0.08% (3)
delay - 0.08% (3)
reboot. - 0.08% (3)
venting - 0.08% (3)
needs - 0.08% (3)
where - 0.08% (3)
doing - 0.08% (3)
should - 0.08% (3)
one, - 0.08% (3)
8:45 - 0.08% (3)
date - 0.08% (3)
security. - 0.08% (3)
trigger - 0.08% (3)
follow - 0.08% (3)
may - 0.08% (3)
issues - 0.08% (3)
fail. - 0.08% (3)
colleague - 0.08% (3)
send - 0.08% (3)
into - 0.08% (3)
access - 0.08% (3)
speed - 0.08% (3)
wtg - 0.08% (3)
create - 0.08% (3)
corporate - 0.08% (3)
immediate - 0.08% (3)
8.1 - 0.08% (3)
email. - 0.08% (3)
tried - 0.08% (3)
credential - 0.08% (3)
steps - 0.08% (3)
april - 0.08% (3)
much - 0.08% (3)
(which - 0.08% (3)
very - 0.08% (3)
now, - 0.08% (3)
download - 0.08% (3)
gotcha - 0.08% (3)
cable - 0.08% (3)
power - 0.08% (3)
dashboard - 0.06% (2)
seriously - 0.06% (2)
long - 0.06% (2)
- 0.06% (2)
write - 0.06% (2)
waiting - 0.06% (2)
acknowledged - 0.06% (2)
less - 0.06% (2)
9th. - 0.06% (2)
wrong - 0.06% (2)
engineering - 0.06% (2)
professional - 0.06% (2)
time… - 0.06% (2)
this. - 0.06% (2)
compensation - 0.06% (2)
engineers - 0.06% (2)
seen - 0.06% (2)
on-line. - 0.06% (2)
reputation - 0.06% (2)
benefits - 0.06% (2)
spoke - 0.06% (2)
wordpress.com. - 0.06% (2)
called - 0.06% (2)
you. - 0.06% (2)
say - 0.06% (2)
original - 0.06% (2)
sent - 0.06% (2)
contacts - 0.06% (2)
indeed - 0.06% (2)
needed - 0.06% (2)
damage - 0.06% (2)
following - 0.06% (2)
e-mail - 0.06% (2)
hear - 0.06% (2)
working - 0.06% (2)
hacker - 0.06% (2)
with: - 0.06% (2)
taken - 0.06% (2)
(on - 0.06% (2)
picture - 0.06% (2)
that, - 0.06% (2)
renew - 0.06% (2)
next - 0.06% (2)
login - 0.06% (2)
attempt - 0.06% (2)
that’s - 0.06% (2)
break - 0.06% (2)
cannot - 0.06% (2)
retention - 0.06% (2)
sooner? - 0.06% (2)
didn’t - 0.06% (2)
issue. - 0.06% (2)
published - 0.06% (2)
frustrations - 0.06% (2)
informed - 0.06% (2)
decade - 0.06% (2)
virtues - 0.06% (2)
enough - 0.06% (2)
ways - 0.06% (2)
trainer - 0.06% (2)
successfully - 0.06% (2)
information) - 0.06% (2)
license - 0.06% (2)
three - 0.06% (2)
card - 0.06% (2)
credit - 0.06% (2)
(mct) - 0.06% (2)
days. - 0.06% (2)
store - 0.06% (2)
wednesday - 0.06% (2)
assume - 0.06% (2)
options - 0.06% (2)
powershell - 0.06% (2)
allow - 0.06% (2)
wrs - 0.06% (2)
-scheduledjoboption - 0.06% (2)
mitch@email.com - 0.06% (2)
set - 0.06% (2)
force - 0.06% (2)
guess - 0.06% (2)
hours. - 0.06% (2)
pretty - 0.06% (2)
easy - 0.06% (2)
action - 0.06% (2)
open - 0.06% (2)
-credential - 0.06% (2)
know, - 0.06% (2)
days: - 0.06% (2)
read - 0.06% (2)
reasons - 0.06% (2)
until - 0.06% (2)
mine - 0.06% (2)
ago - 0.06% (2)
 to - 0.06% (2)
date. - 0.06% (2)
(note: - 0.06% (2)
23, - 0.06% (2)
written - 0.06% (2)
2016. - 0.06% (2)
okay, - 0.06% (2)
lara - 0.06% (2)
business - 0.06% (2)
alternatives, - 0.06% (2)
right? - 0.06% (2)
ok, - 0.06% (2)
laptop - 0.06% (2)
latest - 0.06% (2)
course… - 0.06% (2)
earlier - 0.06% (2)
9:45 - 0.06% (2)
comments - 0.06% (2)
came - 0.06% (2)
go. - 0.06% (2)
running - 0.06% (2)
desktop, - 0.06% (2)
because - 0.06% (2)
couldn’t - 0.06% (2)
plenty - 0.06% (2)
lights - 0.06% (2)
likely - 0.06% (2)
manage - 0.06% (2)
happen - 0.06% (2)
finished - 0.06% (2)
‘your - 0.06% (2)
prompt - 0.06% (2)
restarts - 0.06% (2)
technology - 0.06% (2)
microsoft, - 0.06% (2)
dark. - 0.06% (2)
these - 0.06% (2)
maybe - 0.06% (2)
was… - 0.06% (2)
high - 0.06% (2)
distributel - 0.06% (2)
week… - 0.06% (2)
part - 0.06% (2)
acceptable - 0.06% (2)
authentication - 0.06% (2)
systems, - 0.06% (2)
important - 0.06% (2)
myriad - 0.06% (2)
mcp - 0.06% (2)
discussion - 0.06% (2)
minute - 0.06% (2)
fill - 0.06% (2)
cogeco. - 0.06% (2)
contacted - 0.06% (2)
within - 0.06% (2)
concerned - 0.06% (2)
search - 0.06% (2)
comfortable - 0.06% (2)
dozen - 0.06% (2)
nightmare - 0.06% (2)
held - 0.06% (2)
time. - 0.06% (2)
talking - 0.06% (2)
stood - 0.06% (2)
however - 0.06% (2)
keep - 0.06% (2)
authenticator - 0.06% (2)
wonder - 0.06% (2)
yubikey - 0.06% (2)
experience - 0.06% (2)
hope - 0.06% (2)
annoyed - 0.06% (2)
touch - 0.06% (2)
preventing - 0.06% (2)
error - 0.06% (2)
changing - 0.06% (2)
passwords - 0.06% (2)
stay - 0.06% (2)
reasonably - 0.06% (2)
great - 0.06% (2)
deal - 0.06% (2)
decided - 0.06% (2)
things - 0.06% (2)
advice - 0.06% (2)
password, - 0.06% (2)
password.  - 0.06% (2)
being - 0.06% (2)
it.  - 0.06% (2)
literally - 0.06% (2)
quite - 0.06% (2)
nearly - 0.06% (2)
are: - 0.06% (2)
all, - 0.06% (2)
365 - 0.06% (2)
interesting - 0.06% (2)
teksavvy. - 0.06% (2)
confirmed - 0.06% (2)
lead - 0.06% (2)
eventually - 0.06% (2)
alternatives. - 0.06% (2)
through - 0.06% (2)
cogeco? - 0.06% (2)
especially - 0.06% (2)
i have - 0.42% (15)
that i - 0.36% (13)
at the - 0.36% (13)
if you - 0.3% (11)
that the - 0.28% (10)
my password - 0.28% (10)
of the - 0.28% (10)
on the - 0.25% (9)
i would - 0.25% (9)
able to - 0.25% (9)
in the - 0.25% (9)
with the - 0.22% (8)
microsoft account - 0.22% (8)
this is - 0.22% (8)
my microsoft - 0.22% (8)
windows 10 - 0.22% (8)
to change - 0.19% (7)
this:like loading... - 0.19% (7)
i could - 0.19% (7)
this:share this:shareemailprinttwitterfacebooklike - 0.19% (7)
has been - 0.19% (7)
this:shareemailprinttwitterfacebooklike this:like - 0.19% (7)
rate this:share - 0.19% (7)
it was - 0.19% (7)
try again - 0.19% (7)
the issue - 0.19% (7)
out the - 0.17% (6)
the same - 0.17% (6)
the account - 0.17% (6)
when i - 0.17% (6)
have been - 0.17% (6)
have a - 0.17% (6)
microsoft security - 0.17% (6)
been compromised - 0.17% (6)
about it - 0.14% (5)
a comment - 0.14% (5)
to get - 0.14% (5)
/ leave - 0.14% (5)
with my - 0.14% (5)
windows to - 0.14% (5)
that my - 0.14% (5)
here are - 0.14% (5)
you are - 0.14% (5)
leave a - 0.14% (5)
do not - 0.14% (5)
be able - 0.14% (5)
107 days - 0.14% (5)
to the - 0.14% (5)
and that - 0.14% (5)
my account - 0.14% (5)
one hundred - 0.11% (4)
that a - 0.11% (4)
seven days - 0.11% (4)
on this - 0.11% (4)
the problem - 0.11% (4)
that they - 0.11% (4)
a big, - 0.11% (4)
would have - 0.11% (4)
please try - 0.11% (4)
and so - 0.11% (4)
hundred and - 0.11% (4)
want to - 0.11% (4)
problem with - 0.11% (4)
and my - 0.11% (4)
change my - 0.11% (4)
and seven - 0.11% (4)
i told - 0.11% (4)
would not - 0.11% (4)
had been - 0.11% (4)
continue to - 0.11% (4)
was not - 0.11% (4)
in windows - 0.11% (4)
for the - 0.11% (4)
will be - 0.11% (4)
they have - 0.11% (4)
steps to - 0.08% (3)
for my - 0.08% (3)
now that - 0.08% (3)
couple of - 0.08% (3)
know i - 0.08% (3)
go gotcha - 0.08% (3)
me that - 0.08% (3)
then i - 0.08% (3)
you should - 0.08% (3)
service. please - 0.08% (3)
/ hotmail - 0.08% (3)
you think - 0.08% (3)
there was - 0.08% (3)
the day - 0.08% (3)
now be - 0.08% (3)
going to - 0.08% (3)
i want - 0.08% (3)
outlook / - 0.08% (3)
7, 2017 - 0.08% (3)
a temporary - 0.08% (3)
again. if - 0.08% (3)
before i - 0.08% (3)
with a - 0.08% (3)
again later.’ - 0.08% (3)
down and - 0.08% (3)
message, try - 0.08% (3)
get this - 0.08% (3)
temporary problem - 0.08% (3)
‘there’s a - 0.08% (3)
try again. - 0.08% (3)
for details. - 0.08% (3)
this issue - 0.08% (3)
not be - 0.08% (3)
this message, - 0.08% (3)
would be - 0.08% (3)
you continue - 0.08% (3)
that has - 0.08% (3)
there are - 0.08% (3)
account that - 0.08% (3)
world went - 0.08% (3)
days since - 0.08% (3)
some of - 0.08% (3)
the service. - 0.08% (3)
according to - 0.08% (3)
my world - 0.08% (3)
the last - 0.08% (3)
the case - 0.08% (3)
you have - 0.08% (3)
gotcha in - 0.08% (3)
come back - 0.08% (3)
to reboot. - 0.08% (3)
2017 8:45 - 0.08% (3)
windows 8.1 - 0.08% (3)
on that - 0.08% (3)
service and - 0.08% (3)
email address - 0.08% (3)
is the - 0.08% (3)
trying to - 0.08% (3)
the world - 0.08% (3)
microsoft certified - 0.08% (3)
i wrote - 0.08% (3)
huge microsoft - 0.08% (3)
my corporate - 0.08% (3)
security fail. - 0.08% (3)
microsoft’s security - 0.08% (3)
this article - 0.08% (3)
do you - 0.08% (3)
to mitch - 0.08% (3)
yes, i - 0.08% (3)
was on - 0.06% (2)
but they - 0.06% (2)
take some - 0.06% (2)
wrote the - 0.06% (2)
fix the - 0.06% (2)
has now - 0.06% (2)
can you - 0.06% (2)
plenty of - 0.06% (2)
(including my - 0.06% (2)
it might - 0.06% (2)
credit card - 0.06% (2)
(including credit - 0.06% (2)
other alternatives, - 0.06% (2)
some time… - 0.06% (2)
wednesday march - 0.06% (2)
store (including - 0.06% (2)
had not - 0.06% (2)
nearly a - 0.06% (2)
the virtues - 0.06% (2)
from gary - 0.06% (2)
was preventing - 0.06% (2)
the account. - 0.06% (2)
my internet - 0.06% (2)
to resolve - 0.06% (2)
certified trainer - 0.06% (2)
card information) - 0.06% (2)
compromised my - 0.06% (2)
it, and - 0.06% (2)
working on - 0.06% (2)
my mct - 0.06% (2)
but when - 0.06% (2)
him that - 0.06% (2)
of microsoft’s - 0.06% (2)
been able - 0.06% (2)
their system - 0.06% (2)
trainer (mct) - 0.06% (2)
publish sooner? - 0.06% (2)
were on - 0.06% (2)
my lights - 0.06% (2)
of course… - 0.06% (2)
had plenty - 0.06% (2)
alternatives, but - 0.06% (2)
of other - 0.06% (2)
went dark. - 0.06% (2)
are some - 0.06% (2)
are you - 0.06% (2)
talking about - 0.06% (2)
i will - 0.06% (2)
not trust - 0.06% (2)
cogeco? here - 0.06% (2)
annoyed with - 0.06% (2)
when my - 0.06% (2)
internet service - 0.06% (2)
needs to - 0.06% (2)
‘your server - 0.06% (2)
at wordpress.com. - 0.06% (2)
blog at - 0.06% (2)
this: - 0.06% (2)
your email - 0.06% (2)
a prompt - 0.06% (2)
and got - 0.06% (2)
manage servers - 0.06% (2)
scheduling server - 0.06% (2)
likely come - 0.06% (2)
point where - 0.06% (2)
doing work - 0.06% (2)
you finished - 0.06% (2)
held off - 0.06% (2)
2 comments - 0.06% (2)
dark. my - 0.06% (2)
the problem. - 0.06% (2)
night my - 0.06% (2)
the original - 0.06% (2)
people who - 0.06% (2)
might take - 0.06% (2)
first reported - 0.06% (2)
after i - 0.06% (2)
reported the - 0.06% (2)
i first - 0.06% (2)
that when - 0.06% (2)
a lawyer - 0.06% (2)
lights were - 0.06% (2)
course… and - 0.06% (2)
the form - 0.06% (2)
of this - 0.06% (2)
one this - 0.06% (2)
out to - 0.06% (2)
with cogeco? - 0.06% (2)
loading... outlook - 0.06% (2)
march 7, - 0.06% (2)
issues acknowledged - 0.06% (2)
them. i - 0.06% (2)
should be - 0.06% (2)
if the - 0.06% (2)
of them - 0.06% (2)
i couldn’t - 0.06% (2)
they would - 0.06% (2)
and write - 0.06% (2)
some alternatives. - 0.06% (2)
days after - 0.06% (2)
will not - 0.06% (2)
one word - 0.06% (2)
2016. not - 0.06% (2)
when windows - 0.06% (2)
changed since - 0.06% (2)
 to understand - 0.06% (2)
that date. - 0.06% (2)
december 7, - 0.06% (2)
was written - 0.06% (2)
go down - 0.06% (2)
in this - 0.06% (2)
they are - 0.06% (2)
10 first - 0.06% (2)
2017 9:45 - 0.06% (2)
march 23, - 0.06% (2)
why it - 0.06% (2)
can only - 0.06% (2)
comments on - 0.06% (2)
here’s an - 0.06% (2)
compromised and - 0.06% (2)
change it. - 0.06% (2)
my password, - 0.06% (2)
i tried - 0.06% (2)
into the - 0.06% (2)
interesting fact - 0.06% (2)
days: a - 0.06% (2)
to go. - 0.06% (2)
about windows - 0.06% (2)
that will - 0.06% (2)
until the - 0.06% (2)
is not - 0.06% (2)
the server - 0.06% (2)
you manage - 0.06% (2)
server restarts - 0.06% (2)
servers you - 0.06% (2)
have likely - 0.06% (2)
a point - 0.06% (2)
come to - 0.06% (2)
corporate desktop, - 0.06% (2)
and when - 0.06% (2)
take the - 0.06% (2)
that is - 0.06% (2)
time to - 0.06% (2)
not support - 0.06% (2)
a tech - 0.06% (2)
where you - 0.06% (2)
finished doing - 0.06% (2)
the action - 0.06% (2)
when you - 0.06% (2)
start a - 0.06% (2)
a program - 0.06% (2)
this will - 0.06% (2)
came out - 0.06% (2)
page enter - 0.06% (2)
still running - 0.06% (2)
prompt ‘your - 0.06% (2)
work and - 0.06% (2)
server needs - 0.06% (2)
the task - 0.06% (2)
one time - 0.06% (2)
i knew - 0.06% (2)
9:45 am - 0.06% (2)
107 days: - 0.06% (2)
in their - 0.06% (2)
a microsoft - 0.06% (2)
security nightmare - 0.06% (2)
have held - 0.06% (2)
comment i - 0.06% (2)
to use - 0.06% (2)
most of - 0.06% (2)
that it - 0.06% (2)
compromised for - 0.06% (2)
told the - 0.06% (2)
to know - 0.06% (2)
systems i - 0.06% (2)
the next - 0.06% (2)
off talking - 0.06% (2)
an account - 0.06% (2)
of hours - 0.06% (2)
a couple - 0.06% (2)
the product - 0.06% (2)
engineering team - 0.06% (2)
the end - 0.06% (2)
get it - 0.06% (2)
december 9th. - 0.06% (2)
gary and - 0.06% (2)
i spoke - 0.06% (2)
account, i - 0.06% (2)
on december - 0.06% (2)
it took - 0.06% (2)
and as - 0.06% (2)
he told - 0.06% (2)
that now - 0.06% (2)
to fix - 0.06% (2)
immediate steps - 0.06% (2)
four days - 0.06% (2)
out at - 0.06% (2)
check them - 0.06% (2)
i decided - 0.06% (2)
from changing - 0.06% (2)
that was - 0.06% (2)
a solution - 0.06% (2)
and b) - 0.06% (2)
and if - 0.06% (2)
later.’ i - 0.06% (2)
them out - 0.06% (2)
i don’t - 0.06% (2)
have to - 0.06% (2)
365 account - 0.06% (2)
my office - 0.06% (2)
he had - 0.06% (2)
end of - 0.06% (2)
told me - 0.06% (2)
to help - 0.06% (2)
(which is - 0.06% (2)
i spent - 0.06% (2)
account in - 0.06% (2)
don’t know - 0.06% (2)
message that - 0.06% (2)
world according - 0.06% (2)
who is - 0.06% (2)
seen a - 0.06% (2)
my microsoft account - 0.19% (7)
this:shareemailprinttwitterfacebooklike this:like loading... - 0.19% (7)
rate this:share this:shareemailprinttwitterfacebooklike - 0.19% (7)
this:share this:shareemailprinttwitterfacebooklike this:like - 0.19% (7)
windows to go - 0.14% (5)
be able to - 0.14% (5)
leave a comment - 0.14% (5)
am / leave - 0.11% (4)
problem with the - 0.11% (4)
one hundred and - 0.11% (4)
a big, huge - 0.11% (4)
hundred and seven - 0.11% (4)
to change my - 0.11% (4)
again. if you - 0.08% (3)
continue to get - 0.08% (3)
‘there’s a temporary - 0.08% (3)
microsoft security fail. - 0.08% (3)
had been compromised - 0.08% (3)
this message, try - 0.08% (3)
service. please try - 0.08% (3)
if you continue - 0.08% (3)
a few days - 0.08% (3)
days since i - 0.08% (3)
my world went - 0.08% (3)
huge microsoft security - 0.08% (3)
big, huge microsoft - 0.08% (3)
with my microsoft - 0.08% (3)
with the service. - 0.08% (3)
to get this - 0.08% (3)
message, try again - 0.08% (3)
a temporary problem - 0.08% (3)
please try again. - 0.08% (3)
in windows 10 - 0.08% (3)
to go gotcha - 0.08% (3)
gotcha in windows - 0.08% (3)
last night my - 0.06% (2)
they would have - 0.06% (2)
had been compromised, - 0.06% (2)
i told microsoft - 0.06% (2)
loading... outlook / - 0.06% (2)
/ hotmail issues - 0.06% (2)
i have held - 0.06% (2)
hotmail issues acknowledged - 0.06% (2)
/ 2 comments - 0.06% (2)
seven days since - 0.06% (2)
this:like loading... outlook - 0.06% (2)
world went dark. - 0.06% (2)
and i had - 0.06% (2)
i would not - 0.06% (2)
resolve the issue - 0.06% (2)
credit card information) - 0.06% (2)
(including credit card - 0.06% (2)
microsoft certified trainer - 0.06% (2)
this is no - 0.06% (2)
i first reported - 0.06% (2)
my lights were - 0.06% (2)
on of course… - 0.06% (2)
first reported the - 0.06% (2)
days after i - 0.06% (2)
off talking about - 0.06% (2)
cogeco? here are - 0.06% (2)
point where you - 0.06% (2)
finished doing work - 0.06% (2)
come to a - 0.06% (2)
you have likely - 0.06% (2)
you manage servers - 0.06% (2)
and got a - 0.06% (2)
prompt ‘your server - 0.06% (2)
blog at wordpress.com. - 0.06% (2)
your email address - 0.06% (2)
world according to - 0.06% (2)
with cogeco? here - 0.06% (2)
needs to reboot. - 0.06% (2)
windows 8.1 on - 0.06% (2)
was still running - 0.06% (2)
course… and i - 0.06% (2)
had plenty of - 0.06% (2)
were on of - 0.06% (2)
dark. my lights - 0.06% (2)
are some alternatives. - 0.06% (2)
other alternatives, but - 0.06% (2)
when my internet - 0.06% (2)
windows 10 first - 0.06% (2)
came out i - 0.06% (2)
to go. when - 0.06% (2)
fact about windows - 0.06% (2)
here’s an interesting - 0.06% (2)
to resolve the - 0.06% (2)
the end of - 0.06% (2)
7, 2016. not - 0.06% (2)
one word has - 0.06% (2)
was written december - 0.06% (2)
(note: this article - 0.06% (2)
march 23, 2017 - 0.06% (2)
been changed since - 0.06% (2)
that date.  to - 0.06% (2)
that my password - 0.06% (2)
10 first came - 0.06% (2)
days: a microsoft - 0.06% (2)
can only now - 0.06% (2)
understand why it - 0.06% (2)
out i was - 0.06% (2)
still running windows - 0.06% (2)
if you manage - 0.06% (2)
servers you have - 0.06% (2)
8:45 am / - 0.06% (2)
scheduling server restarts - 0.06% (2)
8.1 on my - 0.06% (2)
likely come to - 0.06% (2)
a point where - 0.06% (2)
server needs to - 0.06% (2)
a prompt ‘your - 0.06% (2)
work and got - 0.06% (2)
you finished doing - 0.06% (2)
go. when windows - 0.06% (2)
about windows to - 0.06% (2)
compromised and i - 0.06% (2)
my internet service - 0.06% (2)
have been compromised - 0.06% (2)
i told the - 0.06% (2)
told me that - 0.06% (2)
a comment i - 0.06% (2)
have held off - 0.06% (2)
do you think - 0.06% (2)
couple of hours - 0.06% (2)
plenty of other - 0.06% (2)
alternatives, but when - 0.06% (2)
the same address - 0.06% (2)
office 365 account - 0.06% (2)
again later.’ i - 0.06% (2)
want to be - 0.06% (2)
9:45 am / - 0.06% (2)
2 comments on - 0.06% (2)
an interesting fact - 0.06% (2)
check them out - 0.06% (2)
i don’t know - 0.06% (2)
it was not - 0.06% (2)
i would be - 0.06% (2)
they have a - 0.06% (2)
according to mitch - 0.06% (2)
password had been - 0.06% (2)

Here you can find chart of all your popular one, two and three word phrases. Google and others search engines means your page is about words you use frequently.

Copyright © 2015-2016 hupso.pl. All rights reserved. FB | +G | Twitter

Hupso.pl jest serwisem internetowym, w którym jednym kliknieciem możesz szybko i łatwo sprawdź stronę www pod kątem SEO. Oferujemy darmowe pozycjonowanie stron internetowych oraz wycena domen i stron internetowych. Prowadzimy ranking polskich stron internetowych oraz ranking stron alexa.