Customization in Sysprep
-
@george1421 For pinning and unpinning items from the task bar, this is something that must be run from a user’s profile. There is no way around it.
First look at the accepted answer here: https://community.spiceworks.com/topic/549865-vbs-script-for-pin-and-unpinning-taskbar-icons?page=1#entry-3612735
Now to implement this. Store that script someplace on the computer during reference image creation like c:\windows\setup\scripts
Now what you need to do just before you sysprep the system, create a short cut in the administrators start menu start up folder to call that script. Since you are using the
CopyProfile=truethat shortcut will be copied to each new user that logs into the computer. Cool!!The only problem is that shortcut will be launched each time the user logs in. So you need to modify the pin to task bar script to kill the short cut in the current user’s start menu. It sounds a little complicated but it really isn’t once you get the script running just like you need it.
-
Now that you updated your OP with the OS you want to support there are a few issues.
-
AFAIK you can not get VLK keys for Home edition of any OS. The OEM license that comes with Win10 Home doesn’t allow for customization of the image. You are only allowed to deploy “unaltered” from OEM media according to the Microsoft EULA. Just be aware that customizing and deploying the home version of the OS, this process may not survive a SAM license audit.
-
Since the Home editions are not intended for bulk deployment the setupcomplete.cmd will not run for you. But you can still use the on first login part of the unattend.xml script to call your setupcomplete.cmd.
-
Also since you are using the home version there is no AD concerns to deal with (not good or bad, only a data point).
-
Since you are using FOG 1.2.0, you may run into issues since Win10 support was not officially added until FOG 1.3.0 was released. You may also run into issues where FOG 1.2.0 doesn’t support the latest hardware, gpt formatted disks, or NVMe (M.2) drives. You might want to consider upgrading your version of fog and to the 1.3.x release (just be aware that fog 1.3.4 has a few annoying bugs, 1.3.5 should be released to address those bugs soon).
-
-
Thank you! Glad to finally post here after 6+ months of FOG usage!
What do you mean by ‘target OS’?
I see what you’re saying about OOBE. Unfortunately for us, we only have only one hardware type and have to get the machines 100% ready before first boot by the user. Our goal is to have the user boot the machine and jump straight to work - hence why we have to do all the OOBE ourselves.
-
-
The machines come with Windows Home Pre-installed, acquiring keys is a non-issue.
-
I will have to give this a try. If I call setupcomplete.cmd via the unattend.xml, will I invalidate or ruin the licenseof the machine on first boot, post deployment? (Correct me if I’m completely off-base with my question). The machines already have Windows 10 Home Licenses, and retain those licenses post-image currently.
-
Ah, good to know.
-
My apologies, I am using 1.3 as I have already imaged Skylake/nvme machines.
Another question based on your responses: To get the features I need, will I need to switch to Pro or Enterprise?
Thank you immensely for your time.
-
-
A clever solution! I will have to test this out. Thank you.
-
@Bromid How this is typically done, is you create a reference image using one of two ways. Audit mode setup or use Microsoft MDT to create your reference image.
Once your reference image is perfect then you sysprep and capture with FOG.
If you need customization post OOBE that can be done with the setupcomplete.cmd batch script that OOBE will call just before the login window is displayed. Or you can have windows auto login and run a batch script or any number of commands defined in the unattend.xml section.
Target OS == the operating system you are going to deploy. That is all.
-
@Bromid said in Customization in Sysprep:
- I will have to give this a try. If I call setupcomplete.cmd via the unattend.xml, will I invalidate or ruin the licenseof the machine on first boot, post deployment? (Correct me if I’m completely off-base with my question). The machines already have Windows 10 Home Licenses, and retain those licenses post-image currently.
This is a tricky question that I’m afraid I can not answer.
From a technical standpoint if you know where the OEM unattend.xml file is located, its possible for FOG to replace that file using a FOG post install script.
-
Ah. I install windows 10 Home onto the machine using a Windows USB Installer. I put the machine into audit mode, get all the drivers, programs, and data I need on the machine, run sysprep and upload to FOG. If I need to update the image, I deploy it to a machine (and because it goes through OOBE) I put it back into audit mode and update before syspreping again.
I see! Looks like setupcomplete.cmd may be the key element I was missing.
-
@Bromid There may be something else that may help you.
Consider using PDQ Deploy (or FOG Snapins I should probably promote that first, shame on me). With PDQ Deploy you can deploy applications or groups of applications to remote machines, as long as you have a user account that is a local administrator on the target computer. Again snapins will do the same.
PDQ Deploy has a paid for version that is not very expensive and worth the cost, but the free version will work for your task. You just need to script the software installs and execute that from a batch file in PDQ Deploy.
-
And my last final thoughts on this. You may want to review these two threads to see if they give you any additional guidance with your task.
https://forums.fogproject.org/topic/9394/trying-to-sysprep-windows-10-to-upload-to-fog-please-help
https://forums.fogproject.org/topic/697/windows-7-and-setupcomplete-cmd
