The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Yes. But even if I hadn't, none of my other systems would have any of the files an Insider build would want or need.
I use WSUS to update my systems - but I have the Insider VM query Windows Update directly every once in a while--that's how it can determine there's something available (newer Insider builds don't come through WSUS)
u can use tcpview / fiddler / microsoft network monitor etc to see what services are sending out data and disable them from the services or registry and also block ms in host file. i assume insider builds will be leaking telemetry like the mars rover...
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
I don't want to neuter the thing. I just want it to leave my network in a usable state when it's downloading updates. As mentioned in my original post, it's the only thing I have that manages to totally hog my bandwidth when it downloads updates and leaves nothing for other systems while it's doing that.
i assume insider builds will be leaking telemetry like the mars rover...
As an Insider build, it wouldn't be doing its job if it wasn't doing just that. It's running as a standalone VM that I barely use other than to test my own apps against, every once in a while.
Just like we can create checkpoints & restore Windows to an older state, this is possible on Linux(ubuntu server)?
For example, I'm installing a bunch of packages, all of a sudden I suspect I installed the wrong versions in between. And there's a pile of them. Instead of checking one by one, will it be possible to just clean wipe all the installations and take it back to the orginal state? Like maybe creating a checkpoint and then getting back there if something went wrong.
sounds easy, until you start running into symbolic links, devices, named pipes, temp filesystems and you've got dbus some of their newfangled thingymawatsits. ...ends up being a mess of of command line options for this or that.
not that it can't be done, get it right and create a script.
but yes can be done: in fact did it to clone an entire setup onto backup [different config] hardware - something windows definitely can't do. Cloned the SSD, unplug from source, plug into dest, boot... done. (just change the system name if you want to talk to it over a network.)
I've cloned the disks in windows to different hardware.
It's a pain, but the process was load over the required drivers for the new hardware.
Installable, but NOT installed.
Clone the drive. Put the clone in the different hardware machine, boot into safe mode without networking.
get the monitor/keyboard/mouse drivers first. Generics usually work at first.
Apply all of the drivers specific to this machine.
After about 10 reboots. You are pretty much good as gold.
Now, deal with all of the software/copy protection like QuickBOoks, etc.
That recognize the drive changed, or the CPU changed or the core hardware changed.
Back in the day WINNT, we did this in order to upgrade developers computers without reinstalling everything. Probably did this about 30 times.
Anything that causes a crash just requires safe mode boot, installed the new hardware driver, and delete the old one.
USB and Networking are the single biggest nightmares. And nowadays the entire Mainboard and subsystems.
See, every now and then I uploaded animated screenshot of my progress on the vector graphic eraser!
Now I have problem with the vector graphic unionizer! as seen here!
(can't close the loop, and the code run significantly slower when it should close )
Well, I used that app, ScreenToGif, to take those shots! really nice app!