F5F Stay Refreshed Software Operating Systems System for visualizing data and images

System for visualizing data and images

System for visualizing data and images

K
Kunall
Member
205
03-05-2016, 02:53 AM
#1
I was searching for ways to simplify my tasks while handling frequent system reinstalls for various businesses. I wanted to know if others have tried creating images for both Windows 8 and Windows 7, especially since we use different brands like HP, Dell, and Lenovo. Could you confirm if this approach would be reliable across different motherboards? Also, I’m concerned about activation issues, particularly with Windows 8 activation in the BIOS. Any advice or suggestions would be greatly appreciated.
K
Kunall
03-05-2016, 02:53 AM #1

I was searching for ways to simplify my tasks while handling frequent system reinstalls for various businesses. I wanted to know if others have tried creating images for both Windows 8 and Windows 7, especially since we use different brands like HP, Dell, and Lenovo. Could you confirm if this approach would be reliable across different motherboards? Also, I’m concerned about activation issues, particularly with Windows 8 activation in the BIOS. Any advice or suggestions would be greatly appreciated.

S
Spartan_GB3
Member
204
03-12-2016, 09:56 PM
#2
You're likely to encounter Windows activation issues, which can vary based on the situation. It also depends on the specific Windows version that supports imaging. I hope someone can provide more detailed guidance. If you're restoring in Windows and need to copy multiple PCs at once, copying them over the network might be a better option than relying on an external drive.
S
Spartan_GB3
03-12-2016, 09:56 PM #2

You're likely to encounter Windows activation issues, which can vary based on the situation. It also depends on the specific Windows version that supports imaging. I hope someone can provide more detailed guidance. If you're restoring in Windows and need to copy multiple PCs at once, copying them over the network might be a better option than relying on an external drive.

X
xXJay_BugXx
Senior Member
559
03-13-2016, 12:06 PM
#3
Activation seemed to be the main challenge I anticipated... From what I recall, certain Windows 8 installers (the exact mechanism unclear) would extract the pre-installed key from the BIOS, which would work across all eight machines if that function was enabled. However, the seven machines where the key had been removed or stripped could pose a significant problem. I considered handling this at my previous role but never had the opportunity. My plan involved using ESXI/VSphere to deploy virtual machines running Windows 8, Windows 7, Pro, and Home, allowing me to apply the necessary updates and gather images from those installations.
X
xXJay_BugXx
03-13-2016, 12:06 PM #3

Activation seemed to be the main challenge I anticipated... From what I recall, certain Windows 8 installers (the exact mechanism unclear) would extract the pre-installed key from the BIOS, which would work across all eight machines if that function was enabled. However, the seven machines where the key had been removed or stripped could pose a significant problem. I considered handling this at my previous role but never had the opportunity. My plan involved using ESXI/VSphere to deploy virtual machines running Windows 8, Windows 7, Pro, and Home, allowing me to apply the necessary updates and gather images from those installations.

J
Jujute
Member
59
03-13-2016, 01:08 PM
#4
Proper execution should eliminate activation worries if you follow the right steps with each setup. I applied this with VirtualBox and it performed well for a VM. Here’s a brief summary of my process: Set up a virtual machine for the desired operating system, allocate sufficient storage—around 45GB is ideal for OS and updates. Avoid using any activation codes during installation. You can extend the activation window before Windows requests activation details. If needed, you can restart the activation timer. For Windows 8.1, adjust the ISO to permit keyless installations. Add required updates, drivers, and skip VirtualBox add-ons. With virtualbox, create a new virtual hard drive, mount it, and copy your OS installation files after formatting. Locate install.esd and install.wim in the sources folder, remove the wrong version. When ready to image, use Run → Sysprep, change system cleanup mode, reboot, and log into admin. Remove the profile used for the image and make final tweaks. Re-run sysprep with OOBE as cleanup, confirm generalize, and restart. After rebooting, the VM will boot normally. Use Windows PE ISO (like Gandalf's Win8.1PE) for simplicity. Ensure DISM or ImageX is installed if using Vista. For Windows Vista, follow slightly different imaging steps. Open Command Prompt as admin, shut down the VM, then boot into the PE image. Identify drive letters for OS and installation files, then proceed to the next phase. If you need help with specific commands or settings, let me know.
J
Jujute
03-13-2016, 01:08 PM #4

Proper execution should eliminate activation worries if you follow the right steps with each setup. I applied this with VirtualBox and it performed well for a VM. Here’s a brief summary of my process: Set up a virtual machine for the desired operating system, allocate sufficient storage—around 45GB is ideal for OS and updates. Avoid using any activation codes during installation. You can extend the activation window before Windows requests activation details. If needed, you can restart the activation timer. For Windows 8.1, adjust the ISO to permit keyless installations. Add required updates, drivers, and skip VirtualBox add-ons. With virtualbox, create a new virtual hard drive, mount it, and copy your OS installation files after formatting. Locate install.esd and install.wim in the sources folder, remove the wrong version. When ready to image, use Run → Sysprep, change system cleanup mode, reboot, and log into admin. Remove the profile used for the image and make final tweaks. Re-run sysprep with OOBE as cleanup, confirm generalize, and restart. After rebooting, the VM will boot normally. Use Windows PE ISO (like Gandalf's Win8.1PE) for simplicity. Ensure DISM or ImageX is installed if using Vista. For Windows Vista, follow slightly different imaging steps. Open Command Prompt as admin, shut down the VM, then boot into the PE image. Identify drive letters for OS and installation files, then proceed to the next phase. If you need help with specific commands or settings, let me know.

I
Icetobi
Junior Member
13
03-13-2016, 03:44 PM
#5
This approach should function across different machines with various hardware setups. It’s a great idea! I’ll give it a go and wish it succeeds.
I
Icetobi
03-13-2016, 03:44 PM #5

This approach should function across different machines with various hardware setups. It’s a great idea! I’ll give it a go and wish it succeeds.

T
Tracyy14
Member
133
03-15-2016, 06:37 AM
#6
I've applied it across various laptop and desktop models for 7 and 8.1, with no compatibility problems—just driver updates from Windows. Each time you need, you install the relevant hardware drivers, which works smoothly in most situations.
T
Tracyy14
03-15-2016, 06:37 AM #6

I've applied it across various laptop and desktop models for 7 and 8.1, with no compatibility problems—just driver updates from Windows. Each time you need, you install the relevant hardware drivers, which works smoothly in most situations.

X
226
03-16-2016, 09:45 AM
#7
I can safely save drivers to USB drives without any problems. With several models, a 16GB USB works well... The main challenge is with 8/8.1 machines since the keys are stored in the BIOS rather than on the computer itself.
X
X_Impossible_X
03-16-2016, 09:45 AM #7

I can safely save drivers to USB drives without any problems. With several models, a 16GB USB works well... The main challenge is with 8/8.1 machines since the keys are stored in the BIOS rather than on the computer itself.

S
Sibertho
Junior Member
11
03-16-2016, 11:25 AM
#8
It shouldn't be a problem there at all; Windows will recognize it and add it automatically during setup. Based on my experience, I've only encountered a few issues with an embedded Windows key in about a hundred installations over the past eight months, though other problems have occurred as well. Edit: If the installation doesn't detect the key, it will ask you to enter it manually before beginning. This lets the system confirm whether the BIOS key is functioning properly. When creating your disk or USB drive, ensure it isn't configured for keyless installation.
S
Sibertho
03-16-2016, 11:25 AM #8

It shouldn't be a problem there at all; Windows will recognize it and add it automatically during setup. Based on my experience, I've only encountered a few issues with an embedded Windows key in about a hundred installations over the past eight months, though other problems have occurred as well. Edit: If the installation doesn't detect the key, it will ask you to enter it manually before beginning. This lets the system confirm whether the BIOS key is functioning properly. When creating your disk or USB drive, ensure it isn't configured for keyless installation.

V
Viper1022
Member
68
03-18-2016, 04:51 AM
#9
Alright, I'm ready to dive in.
V
Viper1022
03-18-2016, 04:51 AM #9

Alright, I'm ready to dive in.