tobiefysh.co.uk Report : Visit Site

Technical data of the tobiefysh.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host tobiefysh.co.uk. Currently, hosted in and its service provider is .

the related websites

guinnessworldrecords.com samsung.com ets.org ikea.com whc.unesco.org nice.org.uk theregister.co.uk nhm.ac.uk fis.com soundcloud.com 

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GSE containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

cce and speculative execution update 11th april 2018: the "a/v gate" (registry requirement) has now been removed. this means that cce guest vm's will now have the updates installed. panic over :-) just a heads up that by default cloud connector edition for skype for business online will not automatically download and install the january or february 2018 windows updates as they don't have anti-virus installed and therefore do not get the qualitycompat reg key as detailed here: https://support.microsoft.com/en-us/help/4072699/ documentation for av on cce only mentions the host and not the guest vms: https://technet.microsoft.com/en-us/library/mt740658.aspx (so therefore you can add the key to the host machine if no av is present) i suppose i could create a new base vhdx that has the qualitycompat key set (the same way that you can pause the update to add in a proxy), but seems a bit pointless when this is supposed to be a managed update service (fire and forget). i can see three (official) solutions that microsoft might go with: roll out a new version of cce that will add the key during the build process (hopefully in a new build they will fix my draining calls issue: www.tobiefysh.co.uk/2017/12/cce-210-draining-calls.html ) wait for the key to no longer be required (leaves cce guests vulnerable until then). this is a scenario that will happen eventually: " "q3: how long will microsoft require setting a registry key to receive the windows security updates? a3: microsoft added this requirement to ensure customers can successfully install the january and february 2018 security updates. microsoft will continue to enforce this requirement until there is high confidence that the majority of customers will not encounter device crashes after installing the windows security updates." source: https://support.microsoft.com/en-us/help/4072699/ tell customers that they need to manually add the key in (this is the worst option as the idea is that these vms don't need feeding and watering like "regular" windows servers). once i have an official response back from microsoft i'll update this post. update 1st march 2018 after logging this via o365 support and also via partner advisory support i've had back an update that this should be logged on the skype for business feedback forum as it is a design change..... i've logged it here: https://www.skypefeedback.com/forums/299913-generally-available/suggestions/33492559-cce-and-speculative-update i'd appreciate votes. and yes - i'm aware i called it speculative update (not speculative execution) on the feedback we discussed this internally and from the great contacts we have at modality systems we have now got an escalation into the product group. one late night phone call later and the problem is understood internally at microsoft. looking forward to getting some traction on this now. :-) posted by tobie fysh on tuesday, february 27, 2018 no comments: links to this post email this blogthis! share to twitter share to facebook share to pinterest skype for business server 2015 cu appearing in windows update again looks like microsoft have started pushing the latest skype for business 2015 cu via automatic updates: even thought the master kb for updates still says that they wont do this: seen on edge, front end, stand alone mediation and pchat servers. a change in policy at microsoft or someone messing up? if you do try to install this way then you're going to get a nice error as the cu (as usual) requires that the sfb services are stopped: if you do stop the services ( stop-cswindowsservice ) prior to running windows update, then the update will pop the installer window as if you had manually downloaded the update: as there is no database update since .281 maybe this is an okay way to install the updates, but just remember to restart the services afterwards if you are not going to be restarting the server! to be honest anyone who wants to have control over the deployment of the cu wont be allowing this anyway as they would control via wsus/sccm etc. posted by tobie fysh on saturday, december 16, 2017 no comments: links to this post email this blogthis! share to twitter share to facebook share to pinterest unable to login to skype for business online with bt home hub 6 - part 2 my frustrations with using the bt home hub 6 and skype for business online are documented here: www.tobiefysh.co.uk/2017/11/unable-to-login-to-skype-for-business.html here's my write up on how i've fixed it: first thing i tired was contacting bt. my first call was not great, eventually i got through to a team who i was told would be happy to talk to me about the issues but they would want a credit card number..... i made my excuses and left.... ;-) i tried again and got through to a grumpy lady who (after i asked if she could disable ip6 on the home hub 6) literally said: and said i should send the home hub 6 back < sigh > i went digging into the home hub 6 and found that i have both ip6 and ip4 public ip addresses, meaning things like my tado which don't support ip6 can continue to work: however my work laptop has an ip4 and ip6 address: so the easiest thing to force my sfb client to talk to the o365 homed servers would be to disable ip6 on my laptop. the correct way of doing that is documented here: https://support.microsoft.com/en-us/help/929852/how-to-disable-ipv6-or-its-components-in-windows but doing so would break direct access on my laptop, which would be a bad thing (tm) instead i forced the laptop to prefer ip4 over ip6 by making the following registry change: (reg change file here: https://1drv.ms/u/s!arx7ss1l4dqigzsrjsx7m0etarkbxui ) after a reboot i'm in business! hope that this helps someone out there. posted by tobie fysh on thursday, december 14, 2017 1 comment: links to this post email this blogthis! share to twitter share to facebook share to pinterest presence unknown..... but why! have had a long running issue with a single user at a customer where i was unable to im them or see their presence: however they could im me and see my presence fine. the customer has on-prem lync servers. i am on office 365 which is setup in a hybrid with our on-prem servers. other people in modality who are on-prem (response group users) could see this person fine (you want a name - okay, it's leon). it should be noted that i used to be able to see the presence and im with no issue, also, after i moved to o365 i could. something changed later* anyway - back to the story.... when leon im'd me i would get errors like this in my event logs: 504 server time-out ms-diagnostics: 27002;reason="from-uri domain is not in the receiver-tenant allow list";source="office365servername.infra.lync.com";appname="incomingfederation";originalpresencestate="0";currentpresencestate="0";meinsideuser="no";conversationinitiatedby="6";sourcenetwork="5";remotepartycandoim="yes" a search on that error didn't really bring anything up of value as it was talking about the whole domain needing white listing and that couldn't be correct as it was a single user issue. we tried moving to different pc's, different networks, investigated policies that leon had but all came up nil. the issue wasn't a big enough pain for leon to want to spend too much time troubleshooting but eventually while discussing about their customers office 365 plans a light bulb went off. "leon, have you got your user account in office 365 as well" after confirming he had it was as simple as turning off skype for business for his user account in the customers o365 tenant: and we were back in business: so what happened? my account is in office 365. leon's account was on-prem. he also had an account in office 365 but hybrid was not setup. therefore, when leon im'd me, his client talked to his on-prem edge, resolved the dns for modality edge, and got proxied to me in o365. however, when i attempted to im leon, my client talked to o365, who saw that there was a matching o365 tenant for the domain and sent the im

URL analysis for tobiefysh.co.uk

https://www.tobiefysh.co.uk/2016/01/
https://www.tobiefysh.co.uk/2017/11/unable-to-login-to-skype-for-business.html
https://www.tobiefysh.co.uk/2012/
https://www.tobiefysh.co.uk/2016/09/
https://www.tobiefysh.co.uk/2014/12/
https://www.tobiefysh.co.uk/2013/12/
https://www.tobiefysh.co.uk/2018/02/cce-and-speculative-execution.html#links
https://www.tobiefysh.co.uk/2009/
https://www.tobiefysh.co.uk/2015/07/
https://www.tobiefysh.co.uk/2015/
https://www.tobiefysh.co.uk/2011/06/
https://www.tobiefysh.co.uk/2014/05/
http://www.tobiefysh.co.uk/2017/11/unable-to-login-to-skype-for-business.html
https://www.tobiefysh.co.uk/2010/06/
https://www.tobiefysh.co.uk/2017/12/unable-to-login-to-skype-for-business.html#links
shawnharry.co.uk

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name:
tobiefysh.co.uk

Registrant:
Tobie Fysh

Registrant type:
UK Individual

Registrant's address:
103 Clenchwarton Road
West Lynn
King's Lynn
Norfolk
PE34 3LJ
United Kingdom

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 10-Dec-2012

Registrar:
Mythic Beasts Limited [Tag = MYTHIC-BEASTS]
URL: http://www.mythic-beasts.com

Relevant dates:
Registered on: 01-May-2003
Expiry date: 01-May-2019
Last updated: 19-Apr-2017

Registration status:
Registered until expiry date.

Name servers:
ns1.mythic-beasts.com
ns2.mythic-beasts.com

WHOIS lookup made at 21:22:34 05-Mar-2018

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2018.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at http://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS tobiefysh.co.uk

  PORT 43

  TYPE domain

OWNER

  ORGANIZATION Tobie Fysh

TYPE
UK Individual

ADDRESS
103 Clenchwarton Road
West Lynn
King's Lynn
Norfolk
PE34 3LJ
United Kingdom
Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 10-Dec-2012

DOMAIN

  SPONSOR Mythic Beasts Limited [Tag = MYTHIC-BEASTS]

  CREATED 2003-05-01

  CHANGED 2017-04-19

STATUS
Registered until expiry date.

NSERVER

  NS1.MYTHIC-BEASTS.COM 45.33.127.156

  NS2.MYTHIC-BEASTS.COM 93.93.128.67

  NAME tobiefysh.co.uk

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2018.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at http://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED yes

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .