How the method works?
Read the complete article here.
This Article will explain how they spy on you and how you can stop Microsoft from getting your IP Address without your permission.
How Microsoft Can Spy On You?
The answer is simple, via their NCSI ( Network Connectivity Status Indicator ).
Why should we care of it?
Well… each time we start our Windows Computer an Internet connection test is run automatically to test the Internet availability.
So each time we start it, our PC makes a connectivity request to a text file into the NCSI Server of Microsoft ( 184.108.40.206 & dns.msftncsi.com ).
The Text file should be located here:
Where’s the fun part?
Microsoft admitted that they DO NOT NOTIFY the user Before attempting to collect informations, infact it is automatically done if you have the Internet!.
Read the complete article here.
Just wanted to share word (sorry it took so long) that I’d been selected as a speaker at the upcoming dev.Objective() conference, in Minneapolis in Mid-May. Hope to see lots of my fellow CFers there, and of course new folks who were not CFers.
While the conference name has changed (from cf.Objective()), there are still plenty of CF-oriented topics, and of course as nearly everyone would point out, it’s good for everyone to expand their reach and focus.
To that end, I’ll be doing a topic a bit different than my normal focus of CF server troubleshooting. Instead, recognizing that there will be folks there who either use other servers, or develop web apps or mobile apps, I’ll do a bit of a “soft” topic on how to troubleshoot performance problems more generically, in:
- Hey, my web app’s slow. Where’s the problem?
- Check out Dan Wilson’s complementary talk
- I’ll also do a sponsored talk for the FusionReactor folks
- And there are several dozen more great talks at this great conference
CF911: Help, How do I connect sites to a new instance w/ the ColdFusion 10/11 webserver config tool?
This one causes a lot of heartburn for folks: you add a new instance in CF10 or 11 (in editions other than Standard, which do support adding instances), and you find that you can’t seem to have the web server configuration tool (wsconfig) connect sites to that new instance(s). You never see the new instance listed in the UI of the wsconfig tool. What gives?
The solution is relatively easy, and the problem could maybe be fixed (or at least warned about) by Adobe (and I just filed a bug report for it). Until that happens, I wanted to share this. For more, read on.
The fine folks at the Adobe CF blog posted a blog entry today, on “Sometimes ColdFusion services refuse to start normally post server restart” (by Rahul Upadhyay), which offers some helpful information on one possible solution to the stated problem.
That said, there are some concerns I have, with respect to how I fear some may read and take action based on it (especially the notion of deleting the cfclasses files, as a possible solution to the problem). I’m not contradicting Rahul, just elaborating on some points, as someone who (like them, perhaps) helps people with CF server troubleshooting every day.
I started to write these thoughts as a comment there, and (as often happens) it grew long so I thought it better to be a blog entry rather than a long comment, and point people here. Once I did that I decided to go further still, hoping to really help those interested to consider the issue more carefully. (It also gives me a chance to highlight again the Adobe CF team blog, something I recommend EVERYONE reading this should follow!)
By Charlie Arehart
Has this happened to you? You follow some resource on the web showing how to update the JVM CF uses to a new version, and then wham, CF won’t start. And now you may be stuck wondering, “what happened? how am I supposed to fix this?”
It’s a tragic position to be in. (I was tempted to title this, “Help. My JVM has fallen and CF can’t get up”, but I fear that dated and veiled 80’s reference would go over the heads of many of my readers.)
The thing is, there are several reasons why your attempt to update CF’s JVM can fail, and fortunately I can offer several things you can look at to hopefully quickly recover from or undo things. If you’re interested, read on.
Ok, so that’s clearly not my sentiment but rather that of a certain “Simon” (no other identifying info offered) in a blog comment in one of the recent CF team blog entries.
After complaining about how poorly he felt CF had responded to his seeking help, he threw in additionally that “the existing private consultants prices are a total joke – they are taking us for a ride!”.
Well, I just couldn’t let go his comment go unremarked.
I started to write my reply there, but it grew long (as is my wont). But rather than post there (where most comments are brief), I decided to post it here instead and point to it there. Perhaps some of my readers here may appreciate it as well, as I also talk about some thoughts on CF troubleshooting in general.
Have you ever faced the challenge of needing to migrate the CF Admin settings (datasources, mappings, scheduled tasks, etc.) from one machine to another? You may know of a couple of solutions (the CAR mechanism and the “import wizard” which runs at the end of installation).
But what if those solutions don’t work for you? Or what if you didn’t know of them before installation, and now you have dozens of dsn’s, scheduled tasks, mappings, or other settings you want to get from one machine/release to another?
You are NOT stuck having to manually copy settings from one screen to another! (And you should be very careful about the common hack solution of copying neo*.xml files from one instance to another, which may not always work and may break things.)
In this entry I’ll discuss how you CAN indeed import the CF admin settings from ANY release of CF into ANY OTHER release of CF, in a fully supported way, and which CAN be done even after installation of a new CF release.
I’ll also mention an important potential gotcha to beware, as well as how to to get around that.
Here’s a nice surprise for some about a change in CF11: you can now create and read CAR files (ColdFusion archive files, a CF Admin feature) in the STANDARD edition of ColdFusion 11. In prior releases, it was available only in ColdFusion Enterprise.
Read on for more, including a gotcha regarding importing from previous release Standard editions, but for many this news will be a delight and all they need to know.
For more on what the CAR mechanism is, finding more on it, the gotcha (and what NOT to do if you hit that gotcha), and info on still more hidden gems in CF, read on.
What the CAR mechanism is for
I don’t want to rehash what’s already well-documented in both the CF docs and various blog entries and articles, so I’ll point to those in a moment.
But briefly, the CAR mechanism has been a feature in the CF Enterprise Admin “Packaging & Deployment” section, and it allows one to easily export some or all settings of one CF admin into a single zip file (a “.car” file), which can then be imported into another CF admin. It’s a point and click interface (though its UI has its challenges, so see the resources below to better understand it before trying to use it.)
It can be great whether you are moving settings from one machine to another. It can even help with migration of settings from one release to another, though CF does that for you if you install a new release on a machine with an old one, in which case the Migration Wizard option is offered as a last step of installation.
If you didn’t catch it, Adobe has come out with a prerelease version of the pending Update 3 for ColdFusion 11, which (like update 14 for CF10) adds many things:
- bug fixes (over 160)
- support for new OS’s, databases, application servers, and web servers
- support for Java 8
- as well as updates to underlying technologies like Tomcat (now 7.0.54)
Note that while Tomcat is automatically updated, Java is not. That’s up to you to do. They do indicate that after the release, new installers for CF11 will come with Java 8. (If you’ve not updated the JVM that CF uses, it’s really pretty easy. 5 minutes work and a restart of CF, and easily reverted if you do things carefully. One of the best and relatively recent discussions of the steps is this article from good ol’ Ben Forta, from 2013.)
See the blog entry above for more on the details of what’s changed (it links to 2 PDFs, and the release notes has some known issues, albeit with little context). The blog entry also has the steps to follow to apply the update. Do be careful there.
Do test out the update yourself
It’s important that folks who rely on CF11 try the update out (on non-production systems, of course).
Many decried that CF10 Update 14 came out and had issues, so Adobe is providing this prerelease for people to check it out and iron out the kinks.
Of course, some will then say Adobe’s using users as guinea pigs. They’re damned if they do, damned if they don’t.
And yes, of course one could say “well they could do a better job vetting the release”. It’s complex software, and while all software has bugs, complex software can even more, and especially when CF has lots of integration and moving parts, and there are so many different platforms–and different ways that even folks on the same environment may configure things differently (For instance, even if you’re on Windows, what version? and what edition? and what database server? And what version and edition of that? And are you using IIS or Apache? And what version of Java are you using? Which edition of CF? And how have you configured each of these? Do you see all the permutations?)
So really: test it out for yourself, for your environment. You can wait and see if “others do the dirty work first”. But what if that’s how most respond? And what if your situation is just a little different than the few who may try it out?
Still, do keep an eye on comments in that Adobe blog entry over time, to learn from any challenges that others may face.
By Charlie Arehart