- This topic has 6 replies, 3 voices, and was last updated 4 years, 10 months ago by
.
-
Posts
-
So I’m familiar how to image a desktop with windows. You typically sysprep it and you capture and image. With the Wyse WIN 10 IoT and using WMS 1.4 I see that it has a Pull Image option. Once you kick off the Pull Image option job and the device gets the job it asks to either Pull Image after sysprep or just Pull image. This message it’s a bit unclear can someone tell me if I understand this correctly. If I click on pull after sysprep, I have to make sure that the Write Filter is off and then I run sysprep and reboot. If I select Pull image it’s assuming I already performed the sysprep and that I just want to pull the image??
Also I have tried doing a sysprep and then capture, but when the deploy the image to a device I runs through setting up a lot of stuff such as asking for user password and all that stuff that should already be on the image. I just want it to boot up and auto log to the built in user account.
Thank you in advance.
Here’s the steps I just posted in the other thread. For the image pull, yes, select Pull after Sysprep if you follow these steps. Selecting that will turn off UWF and reboot the client.
High-level description of how I prepare an image:
1. Download latest base image from DELL. Use the USB tool to put it on a stick and image a client.
2. Install/Uninstall/Configure all the crap I need in the image.
3. Strip out whatever I can to make the image as small as possible.
4. Turn on the write filter so WDA fires up and connects to WMS.
5. Schedule an image pull for the client. When this kicks off, it will turn off UWF and reboot the client. Log in as Admin
6. Open C:\Program Files\Wyse\WDA\Config\CCMProtocolConfig.xml and strip out the MAC Address, Owner ID, Wyse ID, Authentication Code and Group Key.
7. Run (as administrator) C:\Windows\Setup\BuildMaster.cmd. Pick your image preferences and let it do it’s thing. When it’s done, it will shut off. Turn it back on and it will upload the image to the WMS repository.
Hey MoPositive,
do you happen to know if your tutorial works for WES7 devices as well? Steps 1-4 are no problem. When trying to pull the image via WMS, I clicked on “Pull after Sysprep”. I assume that’s correct?! The client reboots and I continue with steps 6 and 7. However, on WES7 there’s no BuildMaster.cmd.
What should I do instead? “Just” reboot?
Do I HAVE to use sysprep? The image is used on devices with the exact same hardware.
I don’t have experience doing this with WES7. I would expect the experience to be similar and likely involves sysprep. Is there a C:\Windows\Setup folder? If so, what’s in it?
Yes, there’s a folder “C:\Windows\Setup”.
Content:
AddUsertoUsersgroup.vbs
Admin2.bat
AdminAutologon.reg
AdminSCCM.bat
Autologon.reg
BAActive.exe
Customization_Administrator.reg
Customization_HKLM.reg
DeleteFreeSpace.exe
Disk_Size.exe
fbwf_shortcut.vbs
Flash.wss
Flash_Temp.wss
Hagent_Auto.reg
Hagent_Manual.reg
HAgent_UI.exe
HAgent_UI.reg
Initialize_Temp.wss
MUITSUSBPresysprep.reg
NetXClean_Auto.reg
netxclean_Manual.reg
OSActive_Temp.wss
PlatformAgnostics.vbs
PnPApp.exe
Powershell_Wordpad.vbs
RemoveUserfromAdminGroup.bat
RemoveUserfromAdmingroup.vbs
SCCMCapture.reg
SCCMDeploy.reg
SCCMPartition.txt
sccm_oem_EDM.vbs
scripts
State
SynUI.reg
Sysprep.reg
Sysprep.xml
User.bat
W7-OSActive.exe
WES7_CustomSysprep4man.bat
WES7_SCCM_AdminRunonce.bat
WES7_SCCM_Capture.bat
WES7_SysprepAudit3.batI ran the WES7_CustomSysprep4man.bat, it took some time and eventually the device shut down. On the next boot it had to configure windows for “first time use”. After that, my language settings were pretty messed up. I ended up with a mix of English and German. So… I’m not sure that’s the road to go?!
I was going to suggest that file, WES7_CustomSysprep4man.bat. Still might be the right one but maybe there are other files that need to be configured for input to the process.
You might be better served moving this discussion in the WES forum as it’s really not specific to WDM/WMS.
When it shut down and then you turned it back on, did it make an attempt to upload an image or did it immediately boot to Windows?
When it shut down and then you turned it back on, did it make an attempt to upload an image or did it immediately boot to Windows?
It tried but failed due to an outdated version of Merlin. But that was to be expected.
I found a tutorial on DELL’s website (for WDM, but still): https://www.dell.com/support/article/de/de/debsdt1/sln293831/prepping-a-wes7-image-for-deployment?lang=en
So yeah, it seems to be the right file. I’ll give it another go tomorrow…
- You must be logged in to reply to this topic.