Posts by nimblegardener82

Andrew Peterson2 said:Why did you ditch OneDrive and Google Drive?

They haven't been abandoned—I simply want to explore what other options are out there...

First, you should check your computer settings to ensure a static IP hasn't been assigned...
If that isn't the case, simply open the Command Prompt—you can just type "cmd" into the search bar to bring up the window—and run the command ipconfig /release first—don't forget to hit enter—followed by ipconfig /renew.

I am seeking recommendations for top-tier document sharing services that support seamless online collaboration—I would appreciate some guidance here... One essential requirement for my selection process is the ability for multiple users to work on a single document simultaneously, with all edits appearing in real-time to everyone involved.
For instance, I am already aware of well-known options such as Microsoft OneDrive and Google Drive. If you could suggest some lesser-known alternatives that maintain high reliability, I would be most grateful—even if those services require a paid subscription.

Bryan Rivera83 said:Look, you can just grab a pre-made template in Microsoft Access for stuff like that

You Ziggy—it seems you aren't much of a beer drinker...

Thor is essentially the latest iteration of Locky Ransomware—which means you’ve hit a serious snag. You might be able to recover if you had a recent backup or a system restore point active... allowing you to roll everything back to how it was before the infection. I would suggest downloading http://www.shadowexplorer.com/downloads.html to see if any restore points are actually available. It will tell you if there is a way back. If not... then you're likely out of luck.

The Ransomware likely triggered because you opened a specific file containing Thor—it then proceeds to lock down every file with a matching extension. If you can identify which file caused this (a zip, a txt, etc.), simply deleting that original file might help.

If you aren't certain which file was the culprit, there is an open-source tool called MBRFilter that can block Ransomware (http://www.bleepingcomputer.com/news...r-boot-record/); you can find it on GitHub and install it fairly easily... if you feel up to it.

Larry Ortiz5 said:Give this a shot...

https://www.piriform.com/recuva

I have tried—and for several of the files, it simply returns a "Bad status" error. Is there any way to actually recover those specific documents?...

Jack Alvarez said:True—though how many people will actually end up using them is a different matter entirely... but it’s still worth a shot.

But how exactly? I know there are certain programs designed to perform a deep scan on a hard drive to recover data... but I'm curious about the specifics.

After performing a reinstall of Windows, certain files from my computer should not have been deleted—it seems an error occurred. Is there any way at all to recover this data?

Maria James94 said:You can totally handle the capture manually if you want. You'll just need to grab a WindowsPE bootable media that has ImageX tucked inside.

Here’s a quick example of how you'd capture the "C" drive and dump it onto "D":
imagex /capture c: d:\install.wim "Windows 7 x64 Ultimate" /compress maximum
imagex /capture "Description" /compress maximum

Once you're done, you'll have a .wim file ready to be uploaded to WDS whenever you need it.

I started by running Sysprep on the machine and setting it to shut down... Once I rebooted, I couldn't find my bootable media in the boot menu. So, I went through Recovery to access the command prompt. In the command prompt, I ran:

dism /capture-image /imagefile:c:\install.wim /capturedir:c:\ /name: windows

This gave me the install.wim file on the C drive, which I moved to the bootable media to install Windows on a different PC. Now, my question concerns the computer's SID—how does one influence that? Specifically, how to ensure it's unique for every installation performed via WDS...

Maria James94 said:Creating a Windows 10 image follows the same old playbook as everything else. Since you brought up WDS, I’m guessing you already have a WDS server sitting there ready to go.
If that's the case, just grab a machine (or a VM) and set it up exactly how you want it—install the OS, grab all the latest updates, and get all those necessary programs and drivers installed. Once you're happy with how everything looks on that machine, run Sysprep. After it restarts, boot from the network so you can hit that WDS server and capture the image. From there, you just follow the wizard; it's pretty much foolproof.

As for drivers, you don't actually have to bake them into the image itself. You can just host them on the WDS server, and it'll pull them during the installation process.

If you're looking to automate the whole deployment, you'll want to build an answer file using the Windows Assessment and Deployment kit (Windows ADK) and then just point the WDS to that file for the image.

I don't have a WDS server ready yet—so network booting isn't an option for me right now. I have just installed everything needed on the machine and ran Sysprep... Is it possible to put that image onto a USB drive first to test it out, and then eventually move the image over to the WDS later?

I am looking for guidance on how to create a Windows 10 image—complete with all necessary drivers, software, and configurations—so that I can later deploy it to other machines using Windows Deployment Services. If anyone could offer advice on the most effective way to build this image and which specific tools would be best to utilize... I would appreciate it. Are there particular pitfalls to watch out for during the configuration process? Should I be relying on Windows system image manager, or is there a better alternative...