Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
Bit-for-bit might work for you given that your hardware and apps are probably identical from machine to machine, but I would still go with the Microsoft Deployment Toolkit (MDT) in your scenario.
Install it on a workstation, import the Windows installation files, import the drivers for your...
What brand systems are you using? Many of the big manufacturers make it very easy to find drivers by providing enterprise driver packs. For example:
HP Driver Packs (Client Management Solutions)
Lenovo Microsoft SCCM and MDT Package Index
Dell Command- Driver Packs for Enterprise Client OS...
DanDirk, do you or are you intending to use SCCM or MDT to perform the upgrade for feature updates? Do you use MDT to generate your reference images?
One of the recommendations that I suggest for admins looking to make the feature update process easier in professional environments is to...
Glad you caught it. As youve discovered, you should not join the domain in your reference environment.
Are you using a VM for your reference environment?
Are you using a suspend step for the apps you must manually install?
Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros at...
You really wouldnt want to use your existing fat images with MDT, it would ignore the biggest benefit of MDT, the ability to make your deployment process modular.
What you really should do is:
1. Create a lab deployment share on a virtual machine, populated with your vanilla installation...
Sysprep just isnt the way to go for this sort of migration. It does strip out drivers, but only the basic components of most drivers. Just go through Programs and Features and remove any hardware-specific installations (mostly drivers). Before you transfer, disable anti-virus and enable all of...
One of the things to be wary of when transferring a complete environment like this are drivers with control software components. Sysprep removes all of the driver INFs and can remove some Sysprep aware software, but not all driver control software is Sysprep aware. You may be left with entries...
You should also consider the limitations of Sysprep. Sysprep will only remove the driver files themselves (INFs), along with initiating actions in Sysprep aware applications. This commonly means that while the drivers are removed, associated applications and configurations are not removed. You...
I can’t say with certainty, but my gut feeling is that you should NOT run Sysprep on this system. Sysprep prepares a system for disparate hardware by removing many of the drivers that tie it to the current platform. If the LSI drivers for your array are removed by Sysprep, the resulting...
The short answer is that no, you dont need to, but yes, you should. The reason why you should is to make diagnosis of crashes or performance issues down the road far easier, and to be sure that you will not encounter issues. If you are comfortable reinstalling if you encounter either of those...
Within this thread both sides to the question can be seen. Some users have reported that they have experienced issues from driver incompatibilities when transitioning between platforms, others have reported that the new environment runs without issues. The answer that can be determined from...
That is correct, for an official source see New build available to the Windows Insider Program at the Blogging Windows blog.
Brandon
Windows Outreach Team- IT Pro
Windows for IT Pros on TechNet
There are a few options here. The best by far is what has already been said, use the Microsoft Deployment Toolkit (MDT). With that said, there are several routes that you can take at this point.
If you have only the single reference system, it is completely configured, and you just need to...
If you are looking to do things the “Microsoft way”, then MDT is the way to go. The Windows 8.1 Jump Start is a much more recent resource for deployment and is highly recommended for anyone who deals with deploying Windows. Using the tools manually and independently is functional...