![]() Now with these two scripts in hand, you are ready to make your Windows 10 image. call \\someserver\someshare\SomeSoftware.batĬall \\someserver\someshare\AnotherSoftwareInstall.batĬall "\\someserver\someshare\Some Printer.bat" Making these scripts is beyond the scope of this article, but once you have them, just put them each on a line. Next, comes the bulk of the script in which I just call a bunch of other pre-made scripts that silently install some software. Some day, I’d like to see a utility like Sophos’ Obfuscation Tool for use on other systems: del /f %windir%\Setup\Scripts\SetupComplete.cmdĭel /f %windir%\system32\sysprep\unattended.xmlĭel /f %windir%\system32\sysprep\Panther\unattended.xml Since the first script contains a username/password of a user that connects to the network share, we need to make sure this file gets deleted (including any cached copies).Īnd yes, I realize the irony of saving the password in cleartext, but in certain environments, it works to get the job done. The first part of the script is crucial for security. And as I mentioned, you could just put all of this into the SetupComplete.cmd script, but having a separate file is just easier and if you are in a position to need to be following this article, you probably follow this practice for other systems in your environment. So this script is the one that will actually start configuring Windows (deploying software, adjusting settings, etc.). This just makes it a little more future proof by being able to edit the script in an offsite location. So if you needed to make changes to the embedded SetupComplete.cmd script, you would have to remake the entire Windows image (this will become more clear in the following sections). You could just use one script here, but doing it this way allows you to edit the FirstBoot.bat script whenever you want (which I’ll show you how to make this script next). The first line of the script mounts a network share (where your second script will be stored), and the second line launches the script. Your first script is a script that runs automatically after sysprep is done configuring the computer after your soon-to-be-Windows-10-image is deployed and must be named SetupComplete.cmd: net use j: \\someserver\someshare\ /user:username "my_password_in_quotes" Keep these on the flash drive as well or backed up somewhere else. Copy it to a flash drive because you’ll be needing it later.īelow is a sample answer file I use (you’ll want to generate yours via Windows System Image Manager): Prepare Some First Boot Scripts Follow the guide until you have created an unattended answer file (skip the disk partitioning part). This is a large but critical task and deserves it’s own blog post. pkg format, so it could be easily run on a Mac or deployed through something like JAMF. This post describes how I went about creating a sysprep’d Windows image in a. But getting two completely different operating systems to deploy to a single piece of hardware in an automated fashion is a challenge. The reason being is that it’s very useful to only buy a single piece of hardware (Apple) and have it run Windows and macOS (and maybe Linux, too). I spent a long time trying to automate a dual-boot deployment of macOS and Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |