|
It must be legit, he hasn't asked for your bank details... 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The sad point is... how many people will actually answer that email?
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Have you checked if there was a Reply-To header?
If so, the poor Raffael who's address is used here will not get the answer.
If not, is's really bad. Especially when using a free email provider located in the EC where chances are good to be identified.
|
|
|
|
|
No, the reply to is accinf02030@yahoo.co.jp should anyone feel like writing to them.
veni bibi saltavi
|
|
|
|
|
Well, if people fall for the scam where you supposedly owe money to the IRS and they want to be paid in iTunes gift cards...
|
|
|
|
|
Why don't the hackers turn their botnets into tools for flooding those email addresses with so much spam that the idiots give up ever wading through them?
|
|
|
|
|
Your Email User-name: FatFinger@TypoGod.com
Your EMAIL Password: I-Type-H-When-I-Should-Type-B-
Your Date of Birth: Cheshvan 5, 5777
Your Country or Territory: Kaechon[^]
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
|
Let's say I'm crazy enough to install Windows Server 2016 to host an app I want to keep going in the cloud 24/7. There's no way to stop this thing from magically rebooting willy nilly outside of setting the normal business hours or whatnot... but say when not in that timeframe, Windows will up and just restart la la la without a care to the wind for a *server* app?
Did I miss the memo where MS started smoking crack?
Jeremy Falcon
|
|
|
|
|
Possibly MS has decided to cede the server market to Linux.
|
|
|
|
|
Jeremy Falcon wrote: Did I miss the memo where MS started smoking crack?
Have you been on a secret mission to Mars? Mickeysoft has slowly been losing its grasp on reality over the last ten years.
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
|
Well, I mean I knew it was doing that for the desktop app on Win10, but the server...
Anyway, Google says I can just disable the Windows Update service to stop it, so we'll see.
Jeremy Falcon
|
|
|
|
|
I think if you dig deep enough into some of the 'hidden' settings (taskscheduler/updateorchestrator) you might find a way to stop forced restarts. Sorry, it's Saturday and that's all I can offer. I am experimenting with the equivalent settings in WinTen and am waiting for evidence that the hack/setting actually works. Good luck! 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Anyway, Google says I can just disable the Windows Update service to stop it, so we'll see. *crosses fingers*
Jeremy Falcon
|
|
|
|
|
You just need to set a group policy. Or two actually.
If you still feel unsafe you can of course also disable the Windows Update Service.
|
|
|
|
|
Good. I mean I'm all for updates, but randomly restarting a server is bad juju.
Jeremy Falcon
|
|
|
|
|
I'm not having a server to check at the moment, but a quick googling found it for me: Prevent Windows Server 2012 from forcing a reboot after updates - Server Fault[^]
Chaoix wrote: Press Windows Key+R to open the run prompt.
Type "gpedit.msc" and press enter.
In the "Local Group Policy Editor", navigate to Computer Configuration > Administrative Templates > Windows Components > Windows Update.
Enable the "Configure Automatic Updates" policy and set it to "2".
Enable the "No auto-restart with logged on users for scheduled automatic updates installations" policy.
|
|
|
|
|
I just disabled the service. Living on the edge. 
Jeremy Falcon
|
|
|
|
|
Just don't forget to run it every now and then, there sadly is a reason they made such a stupid move. 
|
|
|
|
|
|
This is why I am really thinking, Linux is a better way to go than Windows OS, for server apps.
At this point, what with the .NET Core, Mono C#, etc., I shouldn't have any problems running a C# web server on Linux. I'll have to give that a try actually.
[edit]And as for the database, I really like PostgreSQL, and I think there's Linq2SQL support for that (I don't use EF!), though not sure. And since I'm not tied in with IIS on any of my web apps, I don't have to worry about that! [/edit]
Marc
|
|
|
|
|
I've always been a *Nix fan since I was a teenager, it's just this app requires Windows or else I wouldn't bother with it.
Jeremy Falcon
|
|
|
|
|
I know 'Topshelf' and I'm pretty sure 'Quartz.Net' also runs on Mono, so Linux is a serious option for services in C#
|
|
|
|
|
Npgsql[^]
PostgreSQL data provider for .NET.
It's awesome.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Jeremy Falcon wrote: Windows will up and just restart la la la without a care to the wind for a *server* app?
Hi,
An unpatched server on a network increases the risk of attack on all of the other networked devices.
It's time for everyone to realize that many computing devices are part of a global interconnected network. Over the last decade we have relied on human server administrators to be responsible for keeping up-to-date and applying security patches. That is not working very well.
It seems perfectly reasonable to give the server administrator several days or perhaps weeks to perform a manual reboot. if that does not happen... force the update.
I would suggest having a look at Manage updates using Windows Update for Business[^]
Most feature updates may be deferred for up to 180 days. Some security updates can be deferred for up to 30 days depending on severity. Unfortunately there are also remotely exploitable security issues that simply cannot be deferred.
One last thing...
You heard it here first. Within the next decade Linux distro organizations will be highly encouraged to have a similar forced-update mechanism. This will probably be negotiated and network-enforced via future trade agreements such as TPP and NAFTA and/or other future agreements.
Best Wishes,
-David Delaune
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
